Before showing a single page, we need solid ground: secure accounts, a database that keeps each customer’s data apart, hosting we know well, and backups we know how to restore. That is what these first weeks are for.
One account for all our products
A Zenit account works across all our tools, Arko included. The sign-in screens are our own, and the service that holds passwords runs on our own servers. Passwords are never stored in plain text, two-factor authentication is available as soon as you create your account, and sessions are kept on the server: your browser only holds a secure cookie.
Each organisation in its own space
Data lives in a PostgreSQL database. Each organisation can only see its own, and the database itself enforces that rule, row by row, on top of the application’s own checks. A mistake on one screen is therefore not enough to show another customer’s data.
Back up, then make sure we can restore
The database is archived continuously and copied every night. Copies are encrypted before they leave our servers. A backup is only worth something if you can bring it back into service: we run full restore exercises and record the outcome of each one.
Why start here
None of this is visible. It is what decides whether a service holds up over time, though, and it is much harder to fix after the fact than to do from the start.