Give every customer their own live numbers
Run one installation and give each of your customers a workspace of their own: their own console, their own sign-in, their own limits. Your onboarding creates them through an API, and usage per workspace feeds your billing.
Illustrative
Isolated by design, configured by them
Each of your customers gets a workspace of their own, kept apart from every other one. They sign in to their own console, invite their own people and tune their own metrics and rules, while you keep the installation running.
- Its own database, API keys, users and console
- Their own single sign-on (Okta, Microsoft Entra ID or any OpenID Connect provider), passkeys and two factors
- Owners decide who gets in, with which role and which sign-in methods
- Limits and plan features set per workspace
- Your operators manage workspaces; they never see a workspace's data
Members
- ALOwner
- JKEditor
- MSEditor
- RBViewer
Sign-in
- Single sign-on with Okta
- northwind.example verified
- Two factors required
Limits this month
- Events6.2 M / 10 M
- Members12 / 20
- Webhooks4 / 10
Operators manage it; they never see its data
Illustrative
Onboarding that runs itself
Your sign-up or billing system talks to the platform API: it creates a workspace when a customer signs up, writes the limits of their plan, pauses it when a payment fails and removes it when they leave. Usage per workspace comes back by the hour, day or month, ready for your invoices.
- Create workspaces, safe to retry: your own customer id keeps it to one
- Set limits and plan features, and change them when the plan changes
- Suspend with a reason, resume, delete and restore within 30 days
- Invite the first owner, and recover access when an owner is locked out
- Read usage per workspace: events, questions, triggers fired and decisions
- A customer signs up
Your sign-up or checkoutPlan: Growth - Workspace created
POST /v1/platform/tenantsReady in seconds - Limits set
PATCH /v1/platform/tenants/{id}10 M events · 20 members · decisions on - Usage metered
GET /v1/platform/tenants/{id}/usagePer hour, day or month
Illustrative
Shape a plan for every customer
These are the levers each workspace carries. Combine them into the plans you sell; the engine enforces them.
| Lever | What you set | When it's reached |
|---|---|---|
| CountsMetrics and rules, members, API keys, webhooks | How many of each a workspace may have | Creating one more is refused |
| Monthly volumeEvents and questions | How much a workspace sends and asks per month | Owners are warned at 80 % and 100 %; nothing stops |
| Plan featuresTriggers, webhooks, decisions, AI help | Which of them a workspace may use | Not included means not available |
| AI budgetSpend on model calls per month | A cap on what the workspace's AI steps may cost | AI steps answer their fallback; rules keep working |
| Request rateRequests per second, burst, batch size, or a tier | How fast a workspace may call the APIs | Extra requests are asked to retry |
| API key lifetimeIn days | How long a workspace's keys may live | Keys can't be made to outlive it |
| Where it runsShared or dedicated instance | Which instance takes the workspace | Chosen when it's created; a workspace stays there |
Many workspaces, on an installation for you
Offering workspaces to your own customers means an installation that is yours: one we run for you, or one you run yourself.
- DedicatedNo public offer yet
An instance only for you
We run an instance that takes only your workspaces, one per customer, in a location chosen with you. Upgrades, scaling, monitoring and backups stay with us.
- Workspaces
- As many as you agree with us
- Limits come from
- Agreed in your contract
- Operated by
- Us
- Self-hostedNo public offer yet
In your cloud, under a license
Run the whole engine where your data already lives, with both consoles and every API. A signed license sets how many workspaces you may create, the events per month and the features.
- Workspaces
- As many as your license allows
- Platform API
- Yours, with your own system console
- If the license lapses
- Production keeps running
A workspace lives in one instance for good: it doesn't move between instances later. Compare all three ways to run it
Let's plan your customers' workspaces
Tell us who your customers are, what they would count and how many workspaces you expect. There's no public offer for platforms yet, so we agree the details together.