Own database schema
Every tenant gets its own schema, plus separate schemas for audit logs and files. Companies that need it get their own schema again, one level deeper.
Security
Separated in the database, not by a filter in the code. Exportable in full, at any time, in a documented format. And cancellable without a conversation about why.
Separation does not happen in the application, where a forgotten filter would be enough to break it. It happens in the database itself.
Every tenant gets its own schema, plus separate schemas for audit logs and files. Companies that need it get their own schema again, one level deeper.
The database itself refuses rows belonging to another tenant — regardless of what the application asks for. A programming error cannot hand out foreign data, because the query never returns it.
Files live outside the web root, in an area of their own per tenant, reachable only through time-limited signed links.
No consecutive numbers anywhere. Counting upwards to find someone else's record is not possible.
Not optional extras — this is how the platform is put together.
Two-factor authentication with backup codes, account lock after five failed attempts, session rotation on sign-in, automatic sign-out after an hour of inactivity.
Who did what, when, from where. Immutable, separated per tenant, exportable — for your own audits as much as for ours.
Virus scan on upload, type and content checked, quarantine for anything suspicious, encryption at rest, signed links with an expiry.
A strict content security policy: scripts and styles only from our own server. No CDN, no tracker, no third-party code. Nothing loads that we did not write.
API keys with limited scope and their own rate limit, versioned endpoints, signed webhooks. A leaked key can be revoked without affecting anything else.
Daily, encrypted, held separately from live data — and restored on a test schedule, because a backup nobody has restored is not a backup.
For companies under 50 people the BSI built a procedure with 27 requirements in six fields, the DIN SPEC 27076. We have arranged this page along those same six fields — the structure is good, and it lets you work through what matters in order.
One contract, one processor, one record. Who changed what is a question with an answer — and mandatory staff training with deadlines and progress is a module, not a side agreement.
Second factor with backup codes, lockout after five attempts, sign-out after an hour. Visibility is set per document, not per user group — and a private team stays private.
Daily, encrypted, held separately from live data — and restored on a test schedule, because a backup nobody has restored is not a backup.
Setting up, running, watching, backing up and keeping current is part of what you buy. It is not an item on your list, and there is no server in your office that someone has to remember.
Uploads are checked and anything suspicious goes into quarantine. In the browser nothing runs that did not come from our own server: no CDN, no tracker, no third-party code. Your own workstations stay your field — that is exactly where the BSI procedure helps you.
Dedicated machines instead of shared cloud instances, Nuremberg and Falkenstein, separated zones, and a private network between the services.
Not one of these six fields is answered by a badge. All six you can click on during a demonstration.
The strongest argument for a platform is that it does not need to hold you.
All your data in open, documented formats. No request needed, no notice period, no fee.
The structure of your data is written down. Someone else can pick it up — that is the point.
A cancellation button in your account, not a letter to an address. You get confirmation in writing immediately.
If you know this field, here is the short version: no framework of the month, no managed service we cannot see into, nothing that needs a rewrite in two years. Boring, current, and chosen because it holds.
Python
One language from the web request to the geo pipeline. No second stack to hire for, no bridge between two runtimes that nobody wants to maintain.
PostgreSQL
Row-level security inside the database, not a filter in the application. Even a mistake in our own code cannot hand one tenant another tenant's rows.
RKE2
Kubernetes — but the distribution that ships hardened to the CIS benchmark, built for regulated environments. Not vanilla with a checklist taped to it afterwards.
Hetzner
Nuremberg and Falkenstein, with Helsinki on request. Dedicated machines, not shared cloud instances — and a provider under German law, not a subsidiary of one.
Django
„The web framework for perfectionists with deadlines“ — their words, and our reason. Migrations, permissions and an admin that exists on day one instead of in sprint nine.
Redis
Sessions and cache, encrypted, never on a shared instance. A restart costs nobody their login.
S3 storage
S3-compatible object storage on our own machines, for documents, images and exports. No bucket at a hyperscaler, no egress bill.
Longhorn
Block storage replicated three times with hard anti-affinity — this is where mail storage and the platform's volumes live.
ASGI
Asynchronous from the start, not bolted on: WebSockets over Channels and Redis, in the same process as the rest.
REST API
Everything the interface can do, the API can do, versioned under /api/v1/ and documented. Your own software is a first-class client.
Content-Security-Policy
No inline scripts, no external sources — and it is enforced by tests rather than by good intentions. A smuggled CDN turns a test red.
You never touch any of it. There is no server access and no cluster access — not as a restriction, but because operating it is what we sell. Updates, certificates, backups and monitoring happen without a ticket from you.
Ask them here first. Rivy knows the architecture, the contract and the limits — and says so when something is outside them.
Ten questions on NIS2 and the GDPR, five minutes, no sign-up. You get a list of your gaps — not a score.
Start the self-check Read the backgroundLooking for something else? Our applications and the documentation are one click away.
AI assistant — may make mistakes. Not legally binding.