Sign-in, sign-up and passkeys are live. What's new
What this page says is built and readable in the source. Every number here is a value from a file.
scrypt with N=32768, r=8, p=1 and a 64-byte length, plus its own salt per password. Verification always runs a full derivation — even when the address does not exist. Otherwise the response time alone would reveal which addresses do.
32 random bytes in a cookie with HttpOnly and SameSite=Lax. The database holds only the SHA-256 digest — reading it yields no valid session. Without “stay signed in” the cookie gets no lifetime and dies with the browser.
Sign-in with face, finger or device PIN over WebAuthn. The private key never leaves the device; the platform stores only the public part.
AES-256-GCM with its own data key per entry, wrapped by the installation's master key. The last four characters are shown.
The boundary sits in the data layer, not in the interface: a query without an organisation aborts instead of returning rows. A foreign record is refused even when its id is known.
A case waiting for an approval keeps waiting when you close the browser. You decide from any device, and the server enforces it — not the interface.
Operations
The platform is an application and a Postgres database. Both run on your machine, in your data centre or in your cloud. With Ollama every model request stays local too — then not a single character leaves the building.
Audit
Whoever has to explain why an agent did something gets the answer in plain language — not as a database dump.
Thirty minutes on the platform, with the source next to it.