One company. One database. No exceptions.
Freight data is commercial data: your rates, your customers, your margins. CargoHub is built so another company’s workspace can’t reach yours, even by mistake.
Own database per company
Each company gets its own database and database role, its own storage bucket, its own Redis and its own web, API and worker processes. There are no shared tables with a company filter that one bug could skip.
Identity check on every start
The API and workers refuse to serve if the company identity in their configuration differs from the one stored in the database, and workers reject jobs for another company.
MFA, sessions and resets
Owners and platform staff must use an authenticator app. Activation and reset links are single-use and expire; a password reset signs out every other session.
Audit with reasons
Approvals, overrides, role changes, period reopenings and service changes are recorded with who, when and why. Audit logs are kept apart from engineering logs.
Backups you can restore
Point-in-time backups with a 15-minute recovery point and a 4-hour recovery target. Restores go to an isolated cluster first, and identity is verified so one company is never restored onto another’s host.
Pakistan hosting & FBR
Business data is hosted in Pakistan. Invoice data leaves your workspace only when you submit it to FBR, and messages go to WhatsApp or SMS only when you send them.
Hiding a menu is not authorization.
Every API call is checked. Effective access is the intersection of what your plan includes, the user’s permission, role and record scope, the workspace’s service mode and the state of the record itself.
| Permission | Dispatcher | Accountant | Fleet Manager | Read-only |
|---|---|---|---|---|
| Book bilties | ||||
| Dispatch trips | ||||
| Post invoices | ||||
| Submit to FBR | ||||
| See margins |
Every sensitive action has a name and a reason.
Posting invoices, overriding rates, adjusting stock, reopening a period or changing a role asks for a reason and writes it to the audit trail. Support staff can only enter your workspace through a time-limited grant you approve, logged on both sides.
Added “Verify POD” · reason: covering LHR desk
IRN 7F2K-99QX-31MM
Chrome · Lahore · MFA
The details your IT team will ask about.
TLS in transit; encrypted disks and backups at rest.
Hashed with a modern algorithm, never shown or emailed; sign-in is throttled.
Rotating refresh tokens, hashed at rest, revoked on reset.
Server-generated storage keys inside your boundary; signed links limited by type, size and time.
Company ID on every log line, job, object and backup.
Per-company budgets and retrieval; customer text treated as untrusted.
Sent only from your verified workspace address; single-use.
PDF and AI work capped per company so one busy workspace can’t slow another.
Need our security questionnaire answered?
We’ll send the security pack and join a call with your IT or audit team.