Your choices about data
We use cookies that are required for this site to work. Anything beyond that — measuring how the site is used, or personalising what you see — happens only if you say yes.
Priced per tenant, not per seat.
What it costs depends on isolation, not
Talk to us
There are no numbers on this page, and that is deliberate.
A price list implies the product is the same for everyone who buys it. This one is not: what changes between tiers is how far your data sits from everyone else's, which payment rails you settle on, and what we commit to in writing. Those are answers to questions about your business, so we would rather ask them than print a figure you will spend a call correcting.
WHAT YOU ARE CHOOSING BETWEEN
Three shapes of tenancy
The same capabilities underneath in every case. What differs is how much of the platform is yours alone.
Isolated
Your own schema, your own payment gateway, named response times.
Start a conversationEvery tier includes the consent gate, accessibility widget and bilingual surfaces — those are not upsells.
What actually changes
The row that decides most conversations is the first one.
| Feature | One vertical | Platform | Isolated |
|---|---|---|---|
| Data isolation | Shared schema, row-scoped | Shared schema, row-scoped | Schema per tenant |
| Identity and access | |||
| Verticals included | One | All | All |
| Payment gateway | Platform account | Platform account | Your own merchant account |
| Consent and privacy gate | |||
| Accessibility widget | |||
| English and Spanish surfaces | |||
| Written response times |
Row-scoped means every query carries your tenant id and the database enforces it. Schema-per-tenant means your rows are not in the same tables as anyone else's.
BEFORE YOU WRITE
The questions that come up first
Because the number would be wrong for most readers. Isolation, payment rails and response commitments move it more than usage does, and we would rather answer honestly in a short call than anchor you to a figure that does not apply.
A product surface with its own customers — dental practice software, a storefront, a devotional. The capabilities beneath it are shared regardless; a vertical is what your customers see, not what runs it.
Yes, and the isolated tier is the one that takes planning: moving to a schema of your own is a migration with a date, not a switch. Coming to us already knowing you will need it is cheaper than arriving there later.
On the isolated tier, yes — you settle into your own merchant account. Elsewhere payments run through the platform's, which is simpler to start and means the money lands with us first.
You get it out in a documented format, and we say so here rather than in a clause you would have to ask for. Leaving being difficult is not a retention strategy we are interested in.