Sell your own AI workspace. Daslab runs it, under your name.
Name it, connect Stripe, set your prices. 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 platform fee 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.
- 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.
- Unlimited workspaces under your instance; seats and scenes are whatever you sell.
- We operate it. Upgrades, backups, the on-call. You keep the customers.
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.
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.
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.