Pricing
Priced against how you work — not a tier you grow into.
Pax Equitas is licensed per organization through a conversation. This page explains the model: what an engagement looks like, what it is priced on, and what happens after you ask.
Licensed per organization — talk to us.
Per-seat licensing, metered services, and white-label terms are all quoted directly; nothing here is self-serve checkout. You will find no numbers on this page — not because they are hidden, but because every engagement is quoted against your actual seats, usage, and deployment model rather than a tier you have to grow into.
Engagement models
Four ways a conversation starts.
Not feature tiers — there are none. These are the shapes an engagement actually takes, each ending in a quote against how you really work.
AI Workforce
Available todayHire one or more AI employees, licensed to your organization and governed from day one.
Teams that want a specific role staffed — intake, claims analysis, compliance — without adopting the whole platform at once.
How it’s structured
- Per-seat licensing per role, per organization
- Metered services where a role consumes them (lookups, documents, analyses)
- Explicit plan limits enforced at request time, not reconciled at month end
Roles carry honest availability labels derived from the product registry — a role that is not ready cannot be licensed, and this page cannot override that.
Platform & enterprise
Custom engagementRun the operating platform itself — identity, licensing, governance, deployment, and audit for your whole organization.
Organizations that need the employment infrastructure, not just an employee: multiple roles, multiple teams, central governance.
How it’s structured
- Organization-level licensing across the roles and products you adopt
- Deployment model (shared platform or dedicated instance) set at approval time
- Every license carries explicit limits — seats, usage, environments
Enterprise engagements are scoped against your actual operation in a conversation, because the approval-gated pipeline is the product — there is no tier to grow into.
White-label & partner
Early conversationsPut your brand on the workforce — branded instances, partner referral tracking, and your own commercial motion.
Partners and resellers who want to sell governed AI employees under their own name, with Pax Equitas as the platform behind them.
How it’s structured
- Partner terms are quoted per engagement — commercial tiers are not published
- Branding, domain, and product naming configured per tenant through White-Label Studio
- The same maturity and approval gates apply under any brand
The partner program is taking applications; commercial terms are settled in the application conversation, not on this page.
Developer & API
Planned — not yet offeredBuild on the same APIs that power our own consoles — documented, versioned, and honestly labeled by build status.
Engineering teams that want to integrate the workforce or platform data into their own systems.
How it’s structured
- Commercial API access is not yet offered — the developer surface documents what exists and what is design-stage
- Register interest through the docs; sandbox access follows the platform's approval pipeline when it ships
The Developer Center is deliberately candid about which API surfaces are built versus specified. Nothing is sold against a design document.
A handful of standalone products carry their own purchase paths on their own properties; those remain theirs. Everything offered on this site goes through the approval-gated licensing pipeline above — no module is separately purchasable just because it has a page.
Why no price grid
Licensing here is gated by verified product maturity: a product below the licensable range cannot be sold, and that rule is enforced in code, not in a policy document. A public price on something the registry will not license would be fiction — so prices appear when checkout does, and neither appears before the founder decision that governs them.
The same honesty applies in your favor: nothing auto-provisions on payment, deployments pass an explicit approval pipeline, and every license carries limits you agreed to rather than limits discovered on an invoice. The absence of a buy button is the governance story, visible.
Pricing FAQ
Asked by every serious evaluator.
Why are there no prices on this page?
Because published numbers would be decorative. Licensing is approval-gated and quoted per organization against your actual seats, usage, and deployment model. A price grid that nobody can check out against is theater, and this site does not do theater.
Is there a free trial or self-serve checkout?
No. Every license today is issued after a conversation, and nothing auto-provisions on payment — deployments go through an explicit approval pipeline. Sandbox evaluation happens inside that engagement, not through a credit-card form.
Can I buy a single module or product on its own?
Some products are licensed individually; others are platform capabilities that are not sold separately. What can be licensed is controlled by each product's verified maturity status — a product below the licensable range cannot be sold, and that gate is enforced in code, not policy.
What does requesting a demo commit me to?
Nothing. A demo request creates an inquiry that a human follows up on. There is no automated outreach sequence behind the form, and no obligation attached to the conversation.
How is white-label or partner pricing structured?
Partner commercial terms are set per engagement in the application conversation. We do not publish illustrative commissions or partner tiers, because illustrative money on partner surfaces is banned by a standing platform rule.
Start the conversation.
Fifteen minutes to match plan limits to your actual operation — that is the whole barrier to entry.