Security & GDPR

Your servers. Your data.

FlatRun runs on your infrastructure and sends no telemetry. Your projects, databases and secrets stay where you put them, which keeps GDPR and data residency in your hands.

Open source, MIT licensed ยท Runs on any Linux server with Docker

Self-hosted, always

FlatRun runs on your servers. There is no FlatRun cloud between you and your apps, and no telemetry: the agent reports nothing about you or your projects to us.

Data where you put it

Projects, databases, backups and secrets stay on the servers you choose, in the country you choose. FlatRun only sends data to services you connect yourself.

Open source

Every line is on GitHub under the MIT license, so you can read exactly what runs on your server.

GDPR

Built for European data protection.

No processor in between

We never receive your users' data, so there is no data processing agreement to sign with FlatRun.

Residency you control

Run FlatRun in Germany, France, the Netherlands or wherever your obligations require. Data stays in that jurisdiction.

Erasure is deleting a folder

A project is a directory. Deleting the project removes its directory and the data inside it.

No hidden transfers

Without a third party hosting the platform, there are no cross-border transfers to assess for FlatRun itself.

Outbound connections

What leaves your server, and when.

FlatRun connects out only for things you use or switch on. Nothing on this list sends your users' data to us.

Update checks
GitHub releases, when someone opens the updates page
Templates
The FlatRun marketplace, when someone browses templates
AI assistant
The provider you configure, off until you do, with secrets redacted
Backups
The S3-compatible store you configure
Secret managers
Infisical, Vault or OpenBao, Doppler or 1Password Connect, if you connect one
Metrics export
The OTLP endpoint you configure
Certificates
Let's Encrypt, for the domains you add

Practices

How FlatRun protects what it runs.

TLS for every domain

Certificates are issued and renewed automatically, and their expiry is tracked.

Sealed secrets

Secrets are encrypted at rest, can be rotated on a schedule, and are never shown again once saved.

Scoped access

Users and API keys have roles, and keys can be limited to specific projects.

Container isolation

Each project runs in its own containers with its own network.

Reviewable changes

Plan a change, see what it affects, then apply it. Stale plans are refused.

Plain files

Configuration and data are files you can read, back up and keep in version control.

Found a vulnerability?

Please report it privately so we can fix it before it is public.

Star us on GitHub