Tenant isolation at the database
Every tenant-scoped row is guarded by PostgreSQL Row-Level Security keyed to the active account — not application checks that can be forgotten.
Multi-tenant isolation is enforced in the database, not just the app. Security is our architecture, not a checkbox.
Every tenant-scoped row is guarded by PostgreSQL Row-Level Security keyed to the active account — not application checks that can be forgotten.
TLS everywhere, encrypted storage, and signed URLs for every document upload.
Granular roles — Admin, Dispatch, Safety, Accounting — with per-company scoping and custom roles per org.
Structured, scrubbed logs and access trails. Secrets never touch code or logs.
Every tenant-scoped table carries an account reference and a PostgreSQL Row-Level Security policy keyed to the active account, set per request. The application connects through a database role that cannot bypass RLS — a boot-time probe refuses to start the server otherwise. Cross-tenant access goes through a small, audited surface, not ad-hoc queries.
The result: one tenant can never read another's rows, even if application code has a bug. That guarantee lives where it can't be forgotten — in the data layer.
Per-company role scoping, custom roles, and IP allowlisting. SSO/SAML on the enterprise roadmap.
Every sensitive action is recorded with who, what, and when — exportable for your own audits.
Your data is yours. Export or delete loads, drivers, and documents on request, anytime.
We use a short list of reputable cloud and AI providers under contractual confidentiality — published on request.
Start free in minutes. Connect your ELD and inbox, and let the AI Pilot take the busywork — dispatching, drafting, and watching risk around the clock.