Reliability

Backup policy

Backups are part of Kyrbit's recovery workflow, but customers should still keep their own important copies.

What backups are for

Backups are meant to recover from common mistakes, failed updates, corrupted worlds, and host issues. They are not a permanent archive or a guarantee against every kind of data loss.

Beta retention

Closed-beta backup retention may change while restore workflows are hardened. The current infrastructure keeps short local retention and offsite retention according to the active node backup configuration.

Restore drills

Production readiness requires regular restore drills, checksum verification, and documented recovery time before paid launch.

Customer copies

Keep your own copies of worlds, configs, plugins, mods, and bot code that you cannot afford to lose.

Deleted or abusive workloads

Backups for deleted, suspended, or abusive workloads may be removed or retained temporarily for abuse, security, billing, or legal review.

Legal holds and disputes

Kyrbit may preserve related account, audit, support, billing, and backup records when needed for abuse investigation, security review, legal process, chargebacks, or dispute handling.