The Platform
One platform. Eight modules. Every AI employee runs on it.
Pax Equitas is a single intelligence platform: one identity layer, one governance model, one data boundary, one audit log. The eight modules below are how you operate it — not eight products to buy.
The modules
Each module is a working surface of the same platform. Open any of them and you are looking at the same organizations, the same registry, the same audit log.
Command Center
Your whole AI workforce and product portfolio on one screen.
Organizations & Teams
Orgs, roles, seats, and invitations — enterprise identity done right.
Product Registry
A truth-audited catalog: nothing is sellable until it's verifiably real.
White-Label Studio
Your name, your domain, your colors — the whole workforce under your brand.
Partner Hub
Referrals, resale, and managed customers for agencies and resellers.
Deployment Center
Request → approve → provision → activate, with health you can see.
Governance & Compliance
Legal holds, compliance reviews, audit trails, spend caps, kill switches.
Developer Center
APIs, webhooks, keys, and sandboxes for building on the platform.
What every module shares
Shared infrastructure is the point. None of the following is per-module, per-product, or optional.
One identity
A single directory of people and AI roles; every product inherits it.
One data boundary
Organization-scoped rows everywhere — tenant isolation is structural, not configured.
One governance model
Default-deny capabilities and maturity gates, identical on every module.
One audit log
Append-only events for every privileged action, human or AI, on any module.
One automation spine
AI roles run as governed actors on shared infrastructure — never as bolted-on bots.
One security posture
Server-side enforcement on every request; the UI is never the boundary.
One deployment pipeline
Request, approval, provisioning, and health — the same five stages for everything.
One white-label layer
Brand the surface per tenant; the trust layer underneath stays locked.
The architecture is enterprise-shaped by construction: multi-tenant with organization-scoped rows, enforced server-side on every request, deployed through an approval pipeline, and recorded in an append-only audit log. White-labeling sits on top of that spine and changes none of it.
One platform across the ecosystem
Everything Pax Equitas operates — the workforce, the industry solutions, the partner channel — runs on this platform rather than beside it.
AI Workforce
Nine roles employed on this platform — permissioned, audited, stoppable.
Insurance claims
The flagship industry: claims operations run on workforce roles and claims engines.
Property intelligence
The engine catalog behind the workforce — property, storm, and claims intelligence.
Public advocacy
Legal and nonprofit advocacy teams run the same roles under the same governance.
Licensing
Per-organization licensing with explicit acceptance — the commercial edge of the registry.
White-label partners
Agencies and resellers put their brand on the workforce; the platform stays the same underneath.
Enterprise deployments
Sandbox to production through approval and health checks — never one-click provisioning.
The operating companies
The organizations that prove the platform in production, documented as proof.
Straight answers
- Do we have to adopt the whole platform?
- No. You license individual products or AI roles; the platform is the infrastructure they all run on, not a bundle you buy. Licensing one product gives you the same identity, governance, and audit foundation as licensing ten.
- Can the platform run under our brand?
- Yes — colors, logo, domain, email identity, and product names are set per tenant through White-Label Studio. Maturity labels and platform chrome are deliberately not brandable, so readiness can never be re-labeled.
- What happens when a product isn't ready?
- It cannot be licensed, and it cannot reach a production environment — the registry's maturity gate enforces both in code. Public pages show the same derived state, so nothing on this site can outrun the registry.
- Who can act inside our organization?
- Only identities you granted capabilities to — human or AI — under default-deny access checked server-side on every request. Every privileged action they take writes an append-only audit event.
See the platform run a workforce.
One demo covers the modules end to end: hire a role, watch the gates, read the audit trail.