Security
An overview of architecture, deployment and safeguards
Tenants and access
The backend isolates each tenant in its own database instance, so data is kept strictly separate. Users can be assigned to multiple roles, where each role is tied to specific permissions for features, data access and actions. Role assignment is checked server-side before critical functions are released.
Deployment and environment
Deployment runs through a pipeline that only pushes tested, working builds into production. Preview versions are validated in advance on a separate server before being reported to the pipeline as approved. Production runs on a Hetzner server in Germany, so both compliance and low latency are ensured for European customers.
Backups and storage
All tenants' databases are backed up automatically every day at 3am. Images, files and the backup archives themselves live in an encrypted S3 bucket used for both storage and replication. That keeps sensitive information protected even if one storage location were compromised.
If you find a bug, please file a bug report so we can fix it quickly.
Related topics
- Security settings — enforce organisation-wide mandatory 2FA
- Users & roles — assign roles and control permissions at a fine-grained level
- GoBD archiving — how SimpliServ archives and stores data in an audit-proof way
- Activity log — trace who changed which object and when
How is this guide?