Security

Your data stays yours — and you can check it

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.

  • Separated in the database itself Row-level security in PostgreSQL. Even a mistake in our own code cannot hand one company another company's rows.
  • You can leave whenever you want A complete export in a documented format, at any time, without asking us first. Leaving is a button, not a negotiation.
  • Everything is on the record Every record keeps its history, administrators get an audit log. Who changed what, and when, is a question with an answer.

Your data is not next to anyone else's

Separation does not happen in the application, where a forgotten filter would be enough to break it. It happens in the database itself.

1

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.

2

Row-level security in PostgreSQL

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.

3

Separate storage areas

Files live outside the web root, in an area of their own per tenant, reachable only through time-limited signed links.

4

Identifiers that cannot be guessed

No consecutive numbers anywhere. Counting upwards to find someone else's record is not possible.

What is built in

Not optional extras — this is how the platform is put together.

Access

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.

Audit trail

Who did what, when, from where. Immutable, separated per tenant, exportable — for your own audits as much as for ours.

Files

Virus scan on upload, type and content checked, quarantine for anything suspicious, encryption at rest, signed links with an expiry.

In the browser

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.

Interfaces

API keys with limited scope and their own rate limit, versioned endpoints, signed webhooks. A leaked key can be revoked without affecting anything else.

Backups

Daily, encrypted, held separately from live data — and restored on a test schedule, because a backup nobody has restored is not a backup.

Six fields, six answers

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.

1

Organisation and awareness

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.

What is built in Staff and training

2

Identities and permissions

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.

What is built in What you can see for yourself

3

Data backup

Daily, encrypted, held separately from live data — and restored on a test schedule, because a backup nobody has restored is not a backup.

What is built in

4

Patches and changes

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.

See the architecture

5

Protection against malware

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.

What is built in

6

Systems and networks

Dedicated machines instead of shared cloud instances, Nuremberg and Falkenstein, separated zones, and a private network between the services.

See the architecture

Not one of these six fields is answered by a badge. All six you can click on during a demonstration.

What you can see for yourself

Everything above happens below the surface. These seven you can click on during a demonstration.

  • Every invoice has a visibility Shared, company-wide or private — set per document, not per user group. Invoices, advanced search
  • Private teams are private A private team is visible to its members only; a public one to everyone with access to Teams. Teams, overview
  • The stock journal is only ever added to A correction is a second booking. Nothing is overwritten, so every stock level can be traced back. Stock, journal
  • Sustainability figures carry an audit trail Who entered which value, and when — in its own area, next to the figures. ESG, audit tab
  • Contracts pass an approval Draft, ready to send, sent, closed. A sent contract is not a closed one, and it does not say so either. Contracts, states
  • Hours are approved, not booked through Time entries go into an approval queue before they reach an invoice. Time recording, administration
  • Records keep their history Contacts, projects and contracts each carry a history tab that records what changed. Any record, history tab

You can leave

The strongest argument for a platform is that it does not need to hold you.

Full export, any time

All your data in open, documented formats. No request needed, no notice period, no fee.

Documented schema

The structure of your data is written down. Someone else can pick it up — that is the point.

Cancel with one click

A cancellation button in your account, not a letter to an address. You get confirmation in writing immediately.

What we build on

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, end to end

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 in the database

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, the hardened one

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

German data centres

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 framework for perfectionists

„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

Sessions and cache, encrypted, never on a shared instance. A restart costs nobody their login.

S3 storage

objects, self-hosted

S3-compatible object storage on our own machines, for documents, images and exports. No bucket at a hyperscaler, no egress bill.

Longhorn

mail and volumes

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

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

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, no foreign sources

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.

Questions your data protection officer will ask

Ask them here first. Rivy knows the architecture, the contract and the limits — and says so when something is outside them.

See the architecture

Where do you stand?

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 background

Help & Support

Looking for something else? Our applications and the documentation are one click away.