Sell your own AI workspace. Daslab runs it, under your name.
Name it, set your prices, start; Stripe is connected on the onboarding call. Your customers sign in at your domain and every workflow becomes a scene: its data, its tools, the agent that runs it, and the history of everything it did. Daslab is the line in the footer.
filter last_visit < 2025-08 ✓
draft 4 letters ✓
What it costs, and what stays with you
Your customers pay you, at your prices, into your Stripe account. Stripe Connect takes our share off each charge, so there is no invoice between us. Model usage on our keys is metered at list price; on your own keys it costs you nothing from us. The terms below are the self-serve ones, for starting today; past them, or inside your own product, we price on the setup.
- 10% of your subscription revenue, taken on each charge through Stripe Connect. Nothing to invoice.
- Model usage at list price when a call runs on our keys. Calls on your own keys cost you nothing from us. A hard, prepaid compute cap per workspace; no overage invoices.
- Up to 2,500 users across all your customers; how many customers, and how many seats each, is whatever you sell. Past that, the terms below.
- We operate it. Shared infrastructure, upgrades, backups, the on-call. You keep the customers.
Priced on your setup
Two and a half thousand users is where the self-serve terms stop being the right ones: the share comes down with volume, and whatever your setup needs goes into the same quote. The workspace inside your own product, your sign-in, private infrastructure or your own servers, a DPA and an SLA. There is no list for that, because the setups differ too much to put on one.
Talk to us →What you do in the first thirty days
Nothing on day one needs an engineer. Everything you inherit from us can be swapped for your own later, one item at a time.
Live at your domain
- Name, logo, domain. A CNAME and a verification.
- Stripe connected. Your prices on our plan screens.
- Models run on Daslab credits, billed to you at list price. Sign-in and integrations work on Daslab’s OAuth apps; consent screens say Daslab.
First paying practices
- Subscriptions land in your Stripe. Our fee comes off each charge.
- Plan limits hold: seats, scenes, a monthly compute cap per workspace.
- Support console. Connection health, which key served each call, the failover log.
More of it is yours
- Your Anthropic key is tried first; your compute bill drops with it.
- Your Google OAuth app. Consent screens now say Brightside.
- Stripe, domain, prices: unchanged. If you ever want the server itself, the same instance runs on your machines.
Three ways to run it, one row at a time
Same software in all three. Colour shows whose each layer is.
Your users never sign up for a workspace
Some of the companies who come to us are not reselling a workspace at all. They already sell software, every customer runs their own customised instance of it, and their desk answers questions that can only be settled by going and looking inside one of those instances. It goes behind that desk instead of in front of a customer: no plan screens, no second place to log in, no new name for anyone to learn.
What your users touch
Your product, on the screen they were already on. A ticket in your own queue or a call to your own API starts the scene, and the answer comes back where it was asked.
What your staff sees
Which run answered which request, what it read on the way, and where it stopped for a person to approve something. Every run is recorded and reviewable, including the ones that got nowhere.
Whose keys, whose data
Your model contracts are tried first, with ours underneath at list price if you want the fallback. The data and the traces are yours, and we do not train on them.
There is no subscription revenue here for us to take a share of, so the terms above are not the ones that fit. What this costs is built from the specifics instead: how many people it serves, whose infrastructure it runs on, and what your agreement has to say. Talk to us →
Who is the data processor?
On Daslab Cloud and whitelabel, Daslab operates the servers and you sign a data-processing agreement with us; your customers sign theirs with you. Self-hosted, the data never reaches us.
Why do consent screens say Daslab at first?
Because on day one the Google and Microsoft apps are ours, verified once for everyone. Register your own app for a provider and the screen says your name for that provider. Most do it for Google first and leave the rest.
Do my customers see Daslab?
In the footer, as Powered by Daslab, and on inherited consent screens. Nowhere else: the domain, the login page, the emails and the invoices carry your name.
What do I owe you if every call runs on my own keys?
The platform fee and the share of revenue. Compute you pay your provider directly; we take no markup on model usage, on our keys or yours.
What happens when I pass 2,500 users?
Nothing switches off. It is the point where we stop pricing you from the page and price you on your setup, and that goes in your favour: the share comes down with volume. It counts users across all your customers, so a hundred small practices and five large firms are the same number to us; how you package seats is your business. Write to us before you get there, with the numbers.
Can it run inside my own product?
Yes. Your sign-in, your API, the workspace embedded where your users already are. That is the shape above, and it is an enterprise setup.
Can I move to my own servers later?
Yes. It is the same instance configuration on your machines. You take the server, the database and the vault; the customers, the domain and the Stripe account are already yours.