Built around clear boundaries.
Your IT records describe how your business works. Protecting them starts with how the application is built.
Organisation isolation
Each operational record belongs to an organisation. Every protected request verifies the current session, membership, role and the organisation that owns the requested record. PostgreSQL row policies provide an additional boundary when deployed with the documented runtime role.
Controlled access
Opaque, revocable sessions are stored in HTTP-only cookies. Passwords use salted scrypt hashing. Roles resolve to centrally defined permissions, enforced by the server. MFA, verified email and recovery are release requirements for the next authentication phase.
Accountable changes
Significant record and organisation changes create append-oriented audit events in the same transaction as the change. Audit metadata contains field names rather than sensitive form values.
No infrastructure credential storage
There are no infrastructure password or secret fields. Do not store passwords, private keys, VPN secrets or recovery credentials in notes or diagrams. External password-manager links are a future capability.