Skip to content
Trust center

Backup policy

What kanman backs up, how long backups are kept, and how data is restored, in kanman Cloud and in the self-hosted edition.

Version 1.0 Updated November 15, 2026

Purpose

Customer data in kanman can be restored after a fault, and backups follow the same location and deletion rules as the data itself.

kanman Cloud

  • The database is backed up daily by the hosting provider.
  • Backups are kept for seven days and stay in the same EU region as the data (Stockholm, Sweden).
  • Repositories are not backed up by kanman: kanman keeps no copy of your code, which stays in your code host.
  • Run machines hold no data worth backing up; they are discarded after each run.
  • A deleted team or workspace is erased 30 days after deletion; after that it disappears from the backups as they roll over.

Self-hosted edition

  • The edition ships backup and restore scripts for Docker Compose and Kubernetes, covering the database and stored files with a checksum check.
  • An update takes a backup first, and a failed update restores the previous release’s files and database.
  • Restoring from a backup is tested automatically in kanman’s release pipeline.
  • Where backups are stored and how long they are kept is your choice.

Team apps on your runners

With a shared backup folder configured, each app’s data is backed up hourly and before every change. When a runner is removed or stays offline, another runner takes the app over and restores its newest backup.

Review

This policy is reviewed when the hosting or the self-hosted edition changes, and at least once a year.