Backup · database protection

Your databases, backed up automatically

Configure your PostgreSQL and MongoDB data sources, set a schedule, and let Backup handle the rest. Download any snapshot as a gzip archive whenever you need it.

Start free in 60 seconds Read docs →

PostgreSQL & MongoDB Scheduled backups Gzip download Multiple data sources Free tier included MySQL & Redis coming soon

prod-postgres · 30d timeline

30 / 30 restored clean

scheduled backup waiting

3 data sources

0 completed

0 B total size

PG prod-postgres 2.4 GB —

MDB analytics-mongo 890 MB —

PG users-postgres 1.1 GB —

01 — how it works

Connect. Schedule. Forget about it.

Add your database connection, pick a backup frequency, and Backup takes over. Every snapshot is stored and available for download as a gzip archive — no CLI gymnastics, no cron jobs to maintain.

Add data sources in seconds — just a connection string
Configurable schedule — hourly, daily, or custom
Download any snapshot as .gz from the dashboard

Try Backup free

prod-postgres · 30d timeline

30 / 30 restored clean

security

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.

principle 01

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.

principle 02

Encrypted archive storage

Archives stored with AWS server-side encryption. Client-side encryption coming soon — your data encrypted before it leaves the sandbox.

principle 03

Isolated execution

Every job runs in its own sandboxed server — no shared processes, no shared memory. Destroyed after the job completes.

What it does

Simple backups, no surprises

PostgreSQL backups

Full pg_dump snapshots of your PostgreSQL databases. Compressed and stored automatically on schedule.

MongoDB backups

Full mongodump snapshots of your MongoDB databases. Same scheduling, same download, same peace of mind.

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.

Credential encryption

Your database credentials are encrypted the moment you enter them and never stored or transferred in plain text.

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.

Isolated backup execution

Every backup job runs in its own sandboxed server — fully isolated from other jobs and other customers.

MySQL & Redis · coming soon

MySQL and Redis support is in development. Same simple workflow — add connection, set schedule, download when needed.

Pricing

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.

Free tier: 1 hour / month

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.

Job runtime — Per-second billing for backup job execution time.

First 1 hr / month Free

1 – 20 hrs / month $0.18 / hr

20 – 100 hrs / month $0.144 / hr

Over 100 hrs / month $0.108 / hr

Common questions

Questions, answered

Quick answers to what teams ask us most about Backup. Need something else? Email [email protected].

Which databases does Backup support?

PostgreSQL and MongoDB. Connect any standard instance — managed (RDS, Atlas), self-hosted, or running in your own cluster — and Backup handles the rest.

How do I schedule backups?

Cron expressions, with timezone awareness. Backup policies bundle the schedule with compression, encryption, retention, parallelism, and bandwidth throttle — attach a policy to a data source and it runs automatically. You can also trigger a backup manually any time.

What backup methods are available?

Logical dumps (pg_dump for Postgres, mongodump for MongoDB) for portable archives you can restore anywhere, physical backups for fast cold-start restores, and point-in-time recovery with continuous WAL/oplog archiving for the lowest possible RPO. Pick per policy.

How long are backups kept?

Two retention dials, enforced together: age (default 30 days) and count (default keep last 7). Either limit ejects older snapshots automatically. Both are configurable per backup policy, so the same data source can have a daily/7-day policy and a weekly/1-year policy side by side.

Can I restore from within Norcube, or do I have to download the dump?

Both. Every snapshot is downloadable as a gzip archive (or zstd) for restore on your own machines. In-product restore is also built in, with three target modes: restore into a new database, overwrite an existing one, or spin up a new server.

How are credentials and backup files protected?

Database credentials are stored encrypted using AWS KMS envelope encryption. Backup artifacts are encrypted at rest in S3 with KMS by default (SSE-S3 and client-side encryption are also supported). Connections to your database use TLS where the engine supports it. All processing happens in EU infrastructure under GDPR.

Quickstart

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.

About 5 min

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 (default 30 days + keep the last 7), 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. Three target modes, one click each.

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.

LangSync

Stop worrying about database backups

Free tier included. No credit card required. Add your first data source and schedule a backup in under a minute.

Start free in 60 seconds Read the docs

Free tier Get started at no cost

No credit card Start building now

Standard formats pg_dump & mongodump as gzip

Download anytime Your data, no restrictions