Volume backups on your own schedule

A volume can be backed up every N minutes (15 or more) or on a cron in UTC instead of daily, and keep its backups by counts: the last N, and the newest in each of the newest N hours, days, weeks, months and years. The newest ready backup is always kept. Set it with schedule and keep on the backup policy, in every SDK, the console, MCP, /v1/volumes/{id}:backup-policy and the CLI: runtime volumes backup-policy <id> --every 60 --keep hourly=24,daily=7. schedule: null goes back to daily, and daily and retentionDays work as before. See volume backups.

100 free hoursin your first 30 days.

of a 1 GB machine

No credit card
Four sandboxes at once, 2 vCPU and 4 GiB each
Then prepaid credit from $10, no plan fee

Start free, no card