Solution
The platform ships as one codebase with two backends: the Next.js API for smaller deployments, and Rust services for the performance-critical domains at scale. Which one you run is configuration, not a different product.
Managed cloud, your own cloud account, or on-premises.
Row-level, schema-per-tenant or database-per-tenant, chosen per deployment.
Sign in against your identity provider.
Pin the deployment to a region you name.
REST APIs and event streams for your data warehouse and CRM.
A mapped, dry-run import from your current system before cutover.
Performance-critical domains — accounting, billing, inventory, notifications, sync, attendance — exist both as a Next.js route and as a Rust service behind the same API contract. Small deployments run one process; large ones scale the service out. The client never changes.
We do not advertise an uptime SLA or a certification we have not been audited for. What we will do is describe the mechanisms — isolation, RBAC, an append-only hash-chained audit trail, crypto-shredded erasure, encryption in transit and at rest — and let your team assess them.
