Backups

We back up your environment periodically and verifiedly, so it can be recovered in the event of a failure, error, or incident.

What gets backed up

Your environment's database, with continuous backup that allows restoring to an exact point in time before an incident (point-in-time recovery, PITR; see Disaster recovery).
The file storage (documents and attachments) associated with your application, via periodic backups: restoration goes to the latest available backup.
The environment's configuration (which is also version-controlled; see How we work).

Where and how

Backups are stored in object storage located in Spain (Sarenet infrastructure, in Spain; see Sub-processors).
They are kept for a defined retention window and rotated automatically: old backups are deleted once they exceed their period.

Standard retention policy

These are the platform's standard values, not the policy of every service: your service's backup plan can be agreed in writing with a different policy — always with a minimum recovery window of 7 days — and is set out in your contract:

Daily backup of the database and the file system, with retention of the last 14 days. Available whether your environment is on our Kubernetes platform or on a dedicated private server.
For environments on Kubernetes, in addition: database point-in-time recovery within that same 14-day window, allowing restoration to an exact minute or second (see Disaster recovery).
The full database backup runs every night, between 01:00 and 05:00 (Spanish time, in both winter and summer).

Tailored to you

The frequencies and windows above are the standard. If you need a different policy (longer retention, more frequent backups...), we adjust it to your plan. The database recovery window is configured per environment, with a minimum of 7 days, for the reason explained below.

Immutable backups

The last 7 days of database backups are immutable: during that period they cannot be modified or deleted. Not by us either, not with administrator permissions, and not by our storage provider.

This is deliberate protection against the worst case: if credentials were compromised and someone tried to destroy your backups, the last 7 days would survive. We always keep at least one recent copy in storage that is independent of the environment.

There is a trade-off we would rather tell you about: that same guarantee means a deletion request cannot be applied to backups until that period expires. See Retention and deletion.

Separation of backups

Backups are stored separately from the environment they protect. A problem in the running environment does not affect the backups, and vice versa.

Recovery

Having backups is only worthwhile if you can actually recover from them. That's why we run restoration tests and have a disaster recovery plan in place.