How it is built
Who can see what, and what the software is not permitted to do
Isolation enforced by the database rather than by our own care, an audit trail the application has no permission to rewrite, and nineteen things a person can be allowed to do. Every one of them demonstrable on the call.
Dana Reyes · Sep 21, 11:04 AM
Dana Reyes · Sep 21, 11:04 AM
D. Reyes · Sep 17, 9:22 AM
D. Reyes · Sep 17, 9:20 AM
Update and delete are revoked from the application on this table. It cannot rewrite what it wrote.
Who can see what
Nineteen things a person can be allowed to do
Not a tier list with a Pro column. These are the actual permissions, and every one of them is checked by the system rather than assumed by the interface.
Permissions attach to groups, never to a person. So “why can she do that?” has exactly one answer, and it is a group you can look at.
Administrator cannot be granted or removed. It is implicit, which is what stops a company locking itself out of its own account at 5 p.m. on a Friday.
A refusal names the permission that was missing, so the person who hit it can tell an administrator what to turn on instead of filing a ticket that says “it says no”.
- IncidentsFile on behalf of a driver
- IncidentsRecord a back-office mistake
- IncidentsProgress incidents
- IncidentsWithdraw a report
- IncidentsSet responsibility and cost
- IncidentsDelete a report permanently
- IncidentsWrite internal notes
- FleetEdit drivers and vehicles
- FleetManage fuel cards and toll tags
- FleetDownload the roster
- FleetImport the roster by spreadsheet
- ComplianceRecord and renew expirations
- ComplianceDefine compliance requirements
- IntegrationsConnect an ELD or TMS
- IntegrationsMatch ELD or TMS assets to NAVYAX records
- SentinelCheck and sign off Sentinel tasks
- GhostRunRead the ELD feed on demand
- SettingsManage depots
- SettingsManage incident categories
How it is built
The boring parts, which are the ones that matter
Every line here is a mechanism rather than a promise, and each one is the kind of thing you can ask us to demonstrate on the call.
Isolation is the database's job, not ours
Every company's rows are separated by a policy inside PostgreSQL. A query that forgets its filter returns nothing at all — it cannot return somebody else's records, because there is no path by which it could.
The application's own database role owns nothing
PostgreSQL always lets a table's owner bypass isolation, so the role the software runs as owns no tables and is not permitted to bypass anything. Migrations use a different role entirely.
It refuses to start if isolation is not in force
On boot the service checks that it is not privileged, owns nothing, and that the policies exist. If any of that is wrong it stops. A misconfiguration takes the system down rather than quietly exposing it.
The audit trail is append-only at the database level
Update and delete are revoked from the application's own role on every history table. Not a policy we follow — a permission the software does not hold. It cannot rewrite what it wrote.
Every audit row names a person
A status change, a cost decision, a note: each carries who did it, when, and — where it was our support staff rather than yours — that it was ours, by name.
The part that holds your data has no public address
It is not firewalled off the internet; it is not on the internet. Nothing outside the private network can route to it, including us.
One more, quietly
Repeated failed sign-ins meet a cool-off that grows — and it is a cool-off rather than a lock, because an account anyone can lock by typing a known email address is a way to stop a driver filing a report at the roadside. A wrong password and an address that was never registered are indistinguishable from outside, so the sign-in page cannot be used to find out who works for you.
Book a demo
Twenty minutes, on your own data if you want
Send a roster beforehand and we will import it first, so what you are looking at is your fleet rather than a made-up one.
You will get a reply from a person, usually the same day. There is no sequence, no sales team and no follow-up drip — there is one of us.
If you would rather not use the form, hello@navyax.com and (227) 268-4898 both reach the same place.