Trucker Flow is multi-company by design. Per-company Row-Level Security, role-based access, audited sensitive data, and hardened headers protect every department from dispatch to settlements.
A request is checked again at each layer on its way in. A failure in one layer does not silently open the next — and the innermost layer is the data itself.
Every response is served over TLS with strict security headers — HSTS, nosniff, clickjacking and referrer protection.
Signed-in users are mapped to one of ten roles that gate navigation and every page in the app.
Postgres enforces company scoping on every table, so a tenant can only ever reach its own rows.
Invoices, payments, settlements and escrow move through secured routines that lock the rows they touch.
Privileged and sensitive actions are logged — and if the record cannot be written, the action is refused.
Each layer is enforced independently
Concrete protections the product enforces today — described honestly, with no certifications, uptime figures, or customer counts we have not earned.
Every table enforces Postgres Row-Level Security scoped by company. A company only ever sees its own data — isolation is applied in the database, not just the app layer.
Ten roles map navigation, page gates, and database policies to what each person should see — from owner to driver.
HR sensitive records are deny-by-default and reached only through an audited server-side funnel. Identifiers like SSNs are never sent to the browser.
Financial movements run through secure database routines that lock the rows they touch — never ad-hoc multi-step edits that could drift or double-apply.
Sensitive actions are written to an audit log so privileged access and changes can be reviewed after the fact.
Responses are served with strict security headers to harden the browser session against common web attacks.
The same posture we apply when we build and review every feature.
App-layer permission checks and database Row-Level Security must agree. A bug in one layer does not silently open the other.
Each role reaches only the data its job requires. Privileged cross-boundary writes go through an explicit, permission-checked funnel.
Money, custody, and sensitive-data paths fail closed: when their permission check or audit write cannot complete, the action is refused. Routine actions record their audit entry on a best-effort basis.
Your users can enroll an authenticator app today. Requiring multi-factor authentication for every office user in your company is a company setting that takes effect once our team turns on enforcement for your account, so ask us about it during onboarding. On our side, the Trucker Flow team's protected platform actions and new operator invitations always require multi-factor authentication; requiring it for every screen of our internal console is a switch we control.
We'll show you exactly how isolation, roles, and auditing work for your operation.