Security
Your book is your business. Here is what actually keeps it yours — in the terms a broker cares about rather than a certificate wall.
Every table is protected by row-level security keyed to your account. It is not a filter the application remembers to apply — the database itself will not return another account's loads, whatever the application asks it for.
PODs, delivery orders and rate confirmations live in private storage. Opening one mints a short-lived signed link for you alone; there are no public URLs to leak or guess.
The board exports to CSV in the same column order it shows on screen, so it drops straight back into Excel. An escape hatch you can actually use is worth more than a promise not to need one.
The application is a static bundle served from the edge with no server of its own to compromise. Data goes directly from your browser to Postgres over TLS, authenticated as you.
A broker should be able to leave on a Tuesday with every row they put in, without asking anybody's permission or paying for the privilege.
You sign in, you see your loads, and nobody else's account can reach them — not because the application filtered them out, but because the database refused. Documents open through links that expire. The export button works every day, not just the day you leave.
There is no server in the middle holding a copy of your book, and no background job shipping it anywhere. The shortest path between your browser and your rows is the whole architecture.
Load a sample book and look around before you put a real load in it.
LoadScope