The backend uses session-based authentication with opaque access and refresh tokens.
Passwords are hashed with argon2id.
Database tokens are encrypted with MASTER_KEY using AES-256-GCM.
- rate limiting
- Helmet security headers
- CORS restriction through configuration
- audit logging for sensitive operations
- Changing an email or password requires the current password.
- Changing a password revokes all other sessions and keeps the current one.
- Admin password resets revoke all sessions for the affected user.
- User API responses never include password hashes or session tokens.
- Admins can create users with
operatororreadonlyroles. Only superadmins can assignadminorsuperadmin.
- never commit secrets to the repository
- rotate
MASTER_KEYcarefully because it affects token decryption - back up the control-plane database and managed SQLite files separately
- use the audit log for user and database operations
The backend only manages databases that are explicitly created, imported, discovered from a mounted path or registered by URL and token.
It does not infer credentials from arbitrary servers.