0 public addresses
Tool files live outside the web root, so no address serves one. Asking for /private_tools/ answers 404 - see PrivateStorageTests.
Trust & transparency
Most tools ask you to take their word for it. This page is built the other way round: the numbers are read from this portal's own database as the page loads, and every promise names the code or the automated test that would catch it if it stopped being true.
Measured now
Counted at 14 Oct 2026, 20:03 - not cached, not rounded up, and not written by the marketing department.
The promises
Each one is a property of the design rather than a commitment to try harder - and each names where to look.
Tool files live outside the web root, so no address serves one. Asking for /private_tools/ answers 404 - see PrivateStorageTests.
The audit log is insert-only: the admin refuses add, change and delete, including for a superuser.
Signed in, granted, plan covers it, fingerprint unchanged, tool sign-in possible - all five run before a single byte is read.
Run with 'manage.py test portal'. 67 of them cover team sharing: codes, teams, rights, policies and the log.
The audit runs inside the upload request, so there is no queue to go stale and a tool is never live before it passed.
An account downloads everything held about it as one JSON file, and the whole workspace can be exported as CSV - log, tools, teams, accounts and shares.
Getting things out
Your tools, your log and your people come out as files, a calendar feed, a signed webhook or an API call. Nothing here needs an account with anybody else.
How to verify any of this
Ask the site for /private_tools/ and for any file name under it. Both answer 404: the folder sits outside the web root, and no URL rule mentions it.
Open the admin as an administrator and try to change or delete a log entry. The buttons are not there and the views refuse: the log is insert-only.
Poll /healthz - plain JSON, no secrets - and watch it report the database, both private stores, the audit rules and the last audit run.
Every promise here is backed by an automated test. The suite runs with manage.py test portal, and FINAL_REPORT.md records what each run proved.
Everything a client needs to check the portal for themselves.
Seven days of everything, then a plan - and rights that manage people, not tools.