Trust
Two-factor authentication
Most products check the second factor at the login screen. Ours checks it in the database, which is the difference between a control and a curtain.
- Available on
- All plans
- Method
- Authenticator app (TOTP), with recovery codes
- Enforced in
- Postgres, across 30+ tables and file storage
What it does
Enrol an authenticator app and keep recovery codes for the day you lose it.
Enforcement lives in the database, not just the login screen: once 2FA is on, a password-only session cannot read your documents at all. Postgres itself refuses, across more than 30 tables and file storage.
Why that distinction is the whole point
A login-screen check protects the login screen. Anything that reaches the data another way, a stale session or an API path that forgot to ask, walks straight past it. Putting the rule in the database means every route to the data inherits it, including the ones nobody remembered to audit.
Questions
Two-factor authentication, answered
Recovery codes are issued at enrolment for exactly that.
The documents. Once it is on, a password-only session cannot read them: the refusal happens in Postgres, across more than 30 tables and file storage.
All of them.