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

This is our standard policy. You can define a different one according to your needs:

Daily backup of the database and the file system, with retention of the last 10 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 for 30 days, allowing restoration to an exact minute or second within that window (see Disaster recovery).

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.

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.