Backups you can prove will restore
Most tools verify the dump ran. Norcube verifies it actually restores: automated tests recover each backup into a throwaway database and confirm the data came back, with a restore-health score and alerts when anything fails or silently stops.
We test your restores, not just your dumps.
A green "backup succeeded" only proves the dump ran. Norcube automatically restores your backups into a disposable database, confirms the data actually came back, and tears it down — on a schedule, on a sample of backups, or on demand. Connecting takes a minute: paste a connection string, pick a schedule, and every following backup can prove itself.
- Restore drills into a throwaway database — never the one being backed up
- Passed badge per backup, restore-health score per database
- Alerts when a backup fails, a test can't confirm your data, or a schedule silently stops
Security is not an add-on. It is the foundation
Your database credentials and backup data are treated as the most sensitive assets they are — encrypted at every stage, isolated in every process.
Credentials never in plain text
Encrypted on input, stored encrypted at rest, decrypted only in an isolated server during the backup job. Never transferred unencrypted.
Encrypted archive storage
Archives stored with AWS server-side encryption. Client-side encryption coming soon — your data encrypted before it leaves the sandbox.
Isolated execution
Every job runs in its own sandboxed server — no shared processes, no shared memory. Destroyed after the job completes.
Simple backups, no surprises
Multiple data sources
Configure as many databases as you need — production, staging, client databases. Each gets its own schedule and backup history.
Gzip download
Every backup is stored as a compressed gzip archive. Download from the dashboard whenever you need it — no lock-in, no proprietary format.
Configurable schedules
Set backup frequency based on your needs. Hourly for critical production databases, daily for staging environments, or anything in between.
Encrypted storage
Backup archives are stored in S3 with AWS-managed server-side encryption. Client-side encryption inside the Fargate task is coming soon — your data encrypted before it even leaves the sandbox.
MySQL & Redis · coming soon
MySQL and Redis support is in development. Same simple workflow — add connection, set schedule, download when needed.
Pay for what you use. Nothing more
Two metrics — job runtime and storage. Both start with a free tier. Volume discounts kick in automatically as you grow.
Billed per second of backup job execution. The clock starts when the isolated server begins your backup and stops when it finishes. The first hour each month is free.
Questions, answered
Quick answers to what teams ask us most about Backup. Need something else? Email [email protected].
Which databases does Backup support?
How do I schedule backups?
What backup methods are available?
How long are backups kept?
Can I restore from within Norcube, or do I have to download the dump?
How do I know a backup will actually restore?
How are credentials and backup files protected?
Backup your first database in five minutes
Three required steps, two optional. Norcube takes care of the encryption, scheduling, retention, and the moment you regret deleting the wrong row.
-
Add a data source
Open Data sources → Add and paste your PostgreSQL or MongoDB connection details. Credentials are encrypted with AWS KMS the moment you save them; the cleartext never touches our database.
-
Create a backup policy
Pick a cron schedule (e.g. 0 2 * * * for nightly at 2 a.m.), retention (choose how many days to keep snapshots, plus a minimum recent count to always keep), compression (gzip or zstd), and encryption mode (SSE-KMS by default). One policy can serve many data sources.
-
Attach the policy to the data source
Link them together and choose the storage destination region. The scheduler picks the attachment up on the next tick — no redeploy, no manual cron.
-
Run it manually to verify (optional)
Hit Run now to trigger an immediate backup. You will see the job state move queued → running → success, with a downloadable artifact at the end. Use this to confirm credentials and network reachability before relying on the schedule.
-
Restore or download (optional)
Every successful job leaves an encrypted artifact you can download as a gzip archive, or restore in-product into a new database, the existing one (overwrite), or a fresh server you provision. Three target modes, each with a pre-flight writability check and a full restore log.
Other products on the platform
Backup was the first Norcube product. The rest of the platform shares the same pay-as-you-go pricing and the same dashboard.
AI translations with API export
Multi-language sync, glossary-aware AI translation, i18n JSON via REST API.
Read more PulseCheckUptime monitoring that runs alongside your backups
HTTP, SSL, and domain monitoring with email, SMS, phone, and webhook alerts.
Read more DomainRadarDomain intelligence — bulk WHOIS at a million domains a request
Availability checks, parsed WHOIS data, AI name generation, brand monitoring via Certificate Transparency.
Read more PromptHubVersioned prompts and auto-generated SDK functions
Handlebars templating, typed variables, registry of every prompt your AI features use.
Read moreStop worrying about database backups
Free tier included. No credit card required. Add your first data source and schedule a backup in under a minute.