PreviewRestore points you can audit.
Encrypted, deduplicated snapshots of what DevSewa runs for your application — databases, uploads, server volumes — taken on a schedule by the fleet backup manager. Run a job on demand, read every receipt, and request a restore check that proves a snapshot can be read back.
console · run a job
POST /v1/applications/{id}/backups/jobs/{job_id}/run
→ 202 { "run_id": "run_5c0a…", "status": "queued" }
GET /v1/applications/{id}/backups/runs/{run_id}
→ { "status": "succeeded", "snapshot_id": "snap_…",
"started_at": "…", "finished_at": "…", "requested_by": "devsewa" }What you get · preview
Backups, without running it.
Served from backups.api.devsewa.com and managed from the console. Backed by BACKUP_MANAGER_APP, mediated by the DevSewa control plane. In preview: it opens for early-access customers as the fleet pairing for their account completes.
- Scheduled jobs per application with retention you can see
- Run on demand and follow the run to a receipt
- Receipts carry snapshot id, size, duration and a redacted error if any
- Restore checks: a real read-back, recorded in the audit trail
- Test and live environments back up to separate repositories
- Repository credentials never leave the backup manager
Isolation
How it stays yours.
- Tenant
- Jobs are owned by DevSewa under your engine tenant; the manager confines every call to it
- Nodes and agents
- Operator-only; the console never lists another customer’s storage
- Receipts
- Stamped with the tenant and who requested the run
Still to come
- Export to your own storage
- Restore into a fresh server from the console
Add Backups to your application.
Create an account, register a test application and exchange your first ticket in under ten minutes.