Tenant boundaries
The platform is designed around company-scoped records, memberships, permissions, and row-level security. That matters when one system holds CRM, HR, finance, fleet, learning, compliance, analytics, and communications data.
Some companies have a workhorse. We're building you a War Horse.
Security and trust
A unified operating system only works if access, evidence, and production discipline are treated as core product work.
DestrierOS is being built to hold sensitive operational data across departments. Security is not only login and passwords. It is tenant isolation, permission boundaries, audit history, controlled exports, and recoverable production operations.
Current product status
DestrierOS is led by the current web command center, with native desktop, mobile, and kiosk workflows expanding around field operations.
For commercial and industrial teams, the current web version is the primary working surface for customer work, field execution, fleet visibility, workforce controls, billing, compliance evidence, and reporting. A Linux native desktop version is running as the local-workstation path for offline compatibility and field-office resilience. The mobile app is in early-alpha field-work validation and is being rebuilt screen by screen for field-ready web parity; the mobile app is in early-alpha validation until real-device pilots prove the workflow. Kiosk hardware case design and packaging are complete, and the kiosk appliance is ship-ready for customer field use with NFC, pairing, sync, Wi-Fi, update paths, offline replay, and device governance.
Privileged work leaves evidence
Money movement, HR documents, compliance changes, access changes, exports, approvals, release actions, and service-role operations belong in auditable workflows.
Production operations are part of the product
The sprint program includes release controls, infrastructure health review, promotion evidence, fleet-ingestion monitoring, observability, backups, background jobs, incident response, pilot readiness, and long-term maintenance. The server workload is limited to the dedicated fleet-ingestion edge while the web platform remains on managed cloud infrastructure.
Trust posture matures over time
The platform now tracks advanced trust center packages, security review summaries, audit export scopes, retention settings, access review cadence, incident disclosure process, and compliance mappings so enterprise buyer reviews can start from controlled evidence instead of ad hoc documents.
Current trust pillars
Tenant isolation and RLS
Company-scoped records and row-level security are core to the data model so multiple organizations can operate without cross-tenant exposure.
Granular roles and controlled workflows
Permissions are intentionally split across modules and sensitive workspaces, with audit expectations for money, HR, compliance, access, exports, approvals, and privileged actions.
Evidence where work happens
Controls, access reviews, policy acknowledgements, financial changes, service actions, communications, and workflow events are meant to generate reviewable history.
Production discipline on the roadmap
Release controls, infrastructure health review, promotion evidence, fleet-ingestion monitoring, observability, backups, background jobs, incident response, pilot readiness, and long-term maintenance are planned as first-class product work.