Platform
The platform behind DealerOS.
Authentication, organizations, memberships, permissions, feature flags, audit logging, and billing are implemented in the Orzeko platform foundation used by DealerOS.
Capabilities
Shared platform capabilities
Multi-tenant data isolation
Organizations and their data are separated at the application layer, with tenant context enforced on every request.
Server-side permission guards
RBAC checks run on the server before business logic — not only in the UI.
Audit trail
Security events and meaningful changes are logged for operators who need visibility and accountability.
Feature flags
Enable modules and roll out changes per organization without shipping separate builds per customer.
Shared identity & billing
One account hub for sign-in, org management, product access, and subscription state.
Postgres-backed storage
Application data lives in PostgreSQL with migrations and schema discipline across services.
Implementation notes
How the shared foundation is enforced
We describe what exists in the product today. Compliance certifications and third-party attestations are not listed here until they are verified.
- Tenant context is established at the edge of each request and carried through server handlers.
- Permission checks are centralized so DealerOS modules do not reimplement access control ad hoc.
- Audit events capture who did what, when — for security review and operational debugging.
Get started
Explore DealerOS
See how DealerOS brings dealership operations into one workspace.