Current
The web command center is live.
Customer work, service execution, workforce controls, fleet context, billing evidence, compliance records, reporting, and administration run from the browser product today.
Some companies have a workhorse. We're building you a War Horse.
Platform architecture
DestrierOS is shaped around production-grade workflows first: revenue, service, fleet, mobile field work, shared kiosk terminals, workforce, learning, compliance, finance, analytics, documents, operations, automation, and communications under one permissioned operating model. The platform story is controlled work, connected records, and evidence that follows the process.
Where the platform stands now
Current
Customer work, service execution, workforce controls, fleet context, billing evidence, compliance records, reporting, and administration run from the browser product today.
Current
GPS and device signal now connect locations, assets, drivers, geofences, trips, maintenance, and event review back to the operating record.
Completed
The replacement audit maps what DestrierOS can prove today, what is provider-dependent, and what remains gated by pilots, accountant review, mobile validation, or kiosk packaging.
Next
The mobile app is in early-alpha field validation, and the kiosk appliance is ship-ready with completed case design, hardware packaging, NFC, pairing, sync, Wi-Fi, update paths, offline replay, and device governance.
Current web version
The browser product is the current primary system of record for customer work, dispatch, workforce, fleet, finance evidence, compliance, reporting, administration, and support.
Early alpha app
The mobile app is in early-alpha field-work validation while it is being rebuilt for field capture, offline work, evidence, scheduling, customer context, GPS-assisted workflows, and approvals.
Linux version running
The native desktop app gives Destrier a local workstation surface for offline compatibility, field-office resilience, and long-running operator workflows beyond a browser session.
Ship-ready appliance
The kiosk appliance is ship-ready for time-clock and location registry terminals with RFID/NFC credential flows, offline event replay, org governance, completed case design, packaging, Wi-Fi setup, pairing, sync, and update paths.
Fleet signal live
Dedicated hardware and mobile GPS signals feed locations, assets, drivers, geofences, maintenance, trip evidence, and exception review into the same operating record.
Current product status
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.
Run the work
Follow a customer from lead to job, field execution, kiosk punch, documents, invoice handoff, and reporting without rebuilding context in every department.
Surface the next action
Queues, approvals, missing evidence, stale work, inventory pressure, support issues, GPS exceptions, and kiosk/device health are meant to be visible before they become surprises.
Keep evidence
Sensitive actions leave an audit trail: approvals, role changes, exports, billing adjustments, field closeout, kiosk events, support assist, compliance reviews, and release operations.
Decide faster
Leadership gets a cross-surface picture of operating health, workload, adoption, risk, margin, field movement, and follow-up without waiting on another spreadsheet cleanup.
Phase W.31-W.61
Web command center readiness
Harden the browser product as the command center for enterprise operating workflows, release-certification evidence, and the shared data model that mobile, kiosk, and device surfaces extend.
Phase W.62-W.66
Infrastructure pivot and release controls
Keep the web platform on managed cloud infrastructure, route fleet hardware through a dedicated ingestion edge, close release guardrails, and establish Schardt operator administration.
Phase W.67-W.78
Fleet enterprise hardening
Deepen trip evidence, device-signal quality, road context, geofences, maintenance, driver identity, coaching, and fleet rollout confidence.
Phase W.79-W.212
CRM, service, communications, and enterprise module buildout
Deepen the core operating layers buyers care about: revenue, service, communications, workforce, learning, compliance, finance, analytics, documents, operations, automation, and platform administration.
Phase W.213-W.224, W.226-W.235
Buyer-ready web product
Public positioning, dashboard release communication, configurable command views, granular access, observability, backups, background jobs, integrations, communications depth, scale, reporting infrastructure, onboarding, tenant administration, trust, APIs, industry packs, AI, automation, analytics, accessibility, procurement readiness, and capacity tuning.
Phase W.236-W.311
Pilot, launch, and operating cadence
Customer-facing product polish, pricing and billing operations, finance/accounting replacement depth, customer-owned payment processor connections, public replacement audits, customer-ready integration access, feature-build stacks for ATS, ERP, EAM, EHS, and CLM, lint/build hygiene, mobile and kiosk rollout gates, public claim cleanup, production pilot, pilot remediation, rollout, post-launch polish, partner groundwork, product program governance, and long-term maintenance after the web platform is credible.
Phase M.1-M.55
Mobile field app web parity
The mobile app is being rebuilt screen by screen around foundation, field capture, offline sync, GPS-assisted workflows, device policy, web parity, real-device testing, and production field crews.
Phase K.1-K.19
Kiosk terminal ship readiness
Workforce time-clock and site-access kiosk appliance work is ship-ready with completed case design, NFC, pairing, sync, Wi-Fi, update paths, offline replay, and device governance.
Phase K.20
Product maturity review
Review the full product after web, pilot, mobile, and kiosk tracks so the next era is driven by customer evidence instead of internal backlog noise.
Operational category map
Salesforce
Revenue operations, customer overview, quotes, forecasting, and sales activity.
ServiceNow
Service intake, work queues, SLAs, approvals, escalations, and knowledge.
Workday
Employee lifecycle, time, leave, payroll closeout, and workforce reporting.
Cornerstone
Learning authoring, assignments, certifications, assessments, and core compliance loops; SCORM/xAPI, proctored exam, and content marketplace parity are not claimed.
Samsara
Fleet visibility, Teltonika-backed devices, telematics, geofences, maintenance, coaching, and rollout support for industrial operations.
Vanta
Controls, evidence, access reviews, risk, corrective actions, and audit exports.
QuickBooks
Invoicing, customer-owned provider-dependent payments, receivables, payables, bank import/reconciliation, tax evidence for professional review, and accountant-reviewed closeout.
Power BI
Curated operational dashboards, governed saved reports, scheduled analytics packages, executive KPI governance, source lineage, and scoped exports; arbitrary semantic modeling, unrestricted data lake, and full BI platform parity are not claimed.
Documents
Governed templates, approval and signature evidence, controlled external sharing, renewal tracking, contract visibility, and repository migration support.
Company and product names referenced on this page are trademarks of their respective owners and are used solely to describe common software categories and operational workflows. Category references describe DestrierOS coverage boundaries, not claims of full vendor parity unless the named replacement sprint and final gap audit have accepted that claim.
Operating model
CRM and revenue operations
Revenue operations and customer overview
Service operations
Service intake, queues, SLAs, and approvals
Fleet and telematics
Fleet, devices, telematics, and maintenance
Workforce HR
HR, time, leave, kiosk punches, payroll closeout, and self-service
Learning and readiness
Learning, certifications, assessments, and readiness
Trust and compliance
Trust, controls, evidence, risk, and audit exports
Finance and accounting
Invoicing, payments, reconciliation, and financial controls
Analytics and reporting
Dashboards, report builder, scheduled analytics, and KPIs
Trust foundations
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.