Three ways to buy. The arithmetic is on the page.
Most enterprise platforms hide their pricing. We publish our anchors and show the math, because a director building a shortlist shouldn't have to book a call to learn whether we're in range. The platform is an annual commitment. Seats bill monthly, because headcount moves and a multi-year system shouldn't charge you for people who left, with a floor at 80 percent of the count you commit to. Above 2,500 seats, pricing is negotiated.
Pick the deployment. The platform is the same.
On-prem license
- Employee seat$12/mo
- Admin / builder seat$95/mo
You run it on your own infrastructure. The base covers the platform, background services, the MCP server, and the first 100 employee and 5 admin seats. Upgrades are part of the license.
- ✓First 100 employee and 5 admin seats included in the base
- ✓Seats bill monthly and move with headcount, with a floor at 80% of the committed count
- ✓Volume breaks at 1,000 and 2,500 seats, held at the committed count for the term
- ✓Air-gapped deployment available
- ✓Your database, your hardware, your keys
Managed, on your cloud
- Employee seat$12/mo
- Admin / builder seat$95/mo
- Non-production environment$24K/yr
Same license and the same per-seat rates, plus we operate the platform inside your own AWS, Azure, or GCP account. Patching, upgrades, monitoring, backups, and the background services are ours to run. Two invoices: our platform fee, and your own cloud bill at cost.
- ✓Infrastructure passes through at cost. You keep your cloud discounts.
- ✓Take it over yourself later. Nothing to migrate.
Modernization services
- Per-seat feesNone. Fixed price.
We reengineer a legacy system on your actual schema and hand your developers the keys at roughly 90 percent complete. The pilot is 4 to 6 weeks: one legacy schema onboarded, the security model configured, a working starter application, and governed AI access demonstrated on your real data.
- ✓Typical build and hand-off: $120K, 10 to 14 weeks
- ✓Time and materials at $200/hr blended when needed
- ✓The goal is hand-off, not a permanent bench
Run your own numbers.
- Platform base (includes 100 employee seats, 5 admin seats)$50,000/yr
- 400 additional employee seats × $12/seat/mo$4,800/mo
- 5 additional admin seats × $95/seat/mo$475/mo
Anchor pricing, not a quote. The annual figure holds today's headcount for twelve months. Seats are billed monthly and follow your headcount up, and down as far as the floor. Infrastructure for managed deployments passes through at cost on your own cloud bill, so it isn't in here.
What a typical division actually pays.
A division with 500 employees and 10 admins, self-managed on-prem:
- Platform base (100 employee + 5 admin seats included)$50,000/yr
- 400 additional employee seats × $12/seat/mo$4,800/mo
- 5 additional admin seats × $95/seat/mo$475/mo
The annual figure holds 500 employees for twelve months. Seats bill monthly, so if the division drops to 450 people the bill drops with it the following month, down to a floor of 80 percent of the committed count. The platform base doesn't move either way.
For scale: published and estimated enterprise pricing for comparable platforms runs roughly $60K to $250K per year at this size, and the common alternatives either can't run on your own infrastructure or make you write the security layer yourself.
Where the platform actually pays off.
A single app rarely justifies a platform. A portfolio does. Set your app count and current tool spend, and check our assumptions against your own numbers.
The fine print, up front.
An employee seat uses applications built on the platform. An admin seat builds and manages them: schema registration, security configuration, validation rules, queues and connectors, and the admin console. If someone only fills in forms and runs reports, they're an employee seat.
Because they're different commitments. The platform is a multi-year decision and it's priced that way. People are not: teams grow, contractors roll off, a division reorganizes. Charging a year up front for a seat someone gives up in March is a bill nobody should have to defend, so seats are counted monthly.
The bill follows it. Seats are counted at the start of each month and invoiced on that count, up or down, with no amendment and no true-up at renewal. Downward movement stops at 80 percent of the seat count you commit to for the term, so a normal year of attrition and reorganization is absorbed but the term still means something. Your volume break is held at the committed count for the term, so shrinking inside the floor doesn't also cost you the discount. The platform base and any environment fees stay on the annual term.
Subscription: an annual platform term with seats billed monthly inside it. If your procurement requires perpetual, we structure it as roughly 2.5 times the annual figure plus 20 percent annual maintenance, which is the industry-standard range.
Your cloud infrastructure. It runs in your own account and passes through at cost, so you keep your enterprise agreement discounts and your data never sits in our tenancy.
A sales conversation. At that scale pricing depends on seat mix, environments, and compliance requirements, and it's negotiated rather than published.
Yes. The subscription includes support and platform upgrades. Premium support tiers with tighter response commitments are scoped in the enterprise conversation.
Yes. It's the same platform on the same database either way. Moving is an operations hand-off, not a migration.
Want the number for your actual situation?
Thirty minutes with your seat counts and requirements beats any calculator.