Daily automated backups for PostgreSQL, MySQL, MongoDB, and Redis. Import a pg_dump from anywhere, download backups, and restore from Claude, Cursor, or Codex.
Native dumps you can take anywhere
PostgreSQL backups use pg_dump in custom format, MySQL uses mysqldump, MongoDB uses mongodump, and Redis saves an RDB snapshot. Each backup is a standard file, so you can download it through a link that expires within an hour and restore it with the usual tools on any other host.
Daily backups with the retention you choose
Turn on scheduled backups for a database and NEXUS AI backs it up once a day. The scheduler checks every hour, so a restart never skips a day. Automatic backups are kept for 7 days by default, and you can raise the retention for more history.
Restore in place or into another database
Restore a backup into the same database to recover, which replaces its current data, or into another database of the same engine in your organization to refresh staging or test a migration first. Restoring MySQL into PostgreSQL, or any other engine mix, is rejected before anything changes. Every restore is recorded in the audit log.
Import a backup from another host
Moving from Heroku Postgres, Supabase, RDS, or MongoDB Atlas? Upload an existing dump of up to 5 GB with nexus db backup-upload, then restore it. PostgreSQL accepts pg_dump custom format or a plain SQL file, MySQL a SQL dump, MongoDB a mongodump archive, and Redis an RDB file.
Restore from your AI assistant
Connect Claude, Cursor, Codex, or another MCP client and ask in plain words: back up the orders database, list last week's backups, or restore last night's backup into staging. Listing and downloading need db:read. Creating backups, restoring, and changing the schedule need db:admin, so an agent can only restore when you grant it.
What it is not: point-in-time recovery
These are daily logical backups plus the on-demand backups you take, not continuous point-in-time recovery. Take an on-demand backup before a risky migration. Standalone databases add their own snapshots, and Azure Database standalone instances restore to a point in time through Azure.
Dashboard, CLI, or AI assistant
Back up, schedule, and restore from the terminal
Find the database service, take a backup, keep daily backups for two weeks, and restore one into a staging database of the same engine.
List the database services and copy the service ID.
Take an on-demand backup and turn on daily backups with the retention you want.
List backups, then restore in place or into another service with restore-to.
nexus db services
nexus db backup <service-id>
nexus db backup-schedule <service-id> --enable --retention 14
nexus db backups <service-id>
nexus db restore-to <staging-service-id> <backup-id>
nexus db restore <service-id> <backup-id> --yes restores in place and replaces the current data. Take a fresh backup first.
Connect an MCP client to https://mcp.nexusai.run/mcp and grant db:read, or db:admin when the agent should create backups or restore.
The agent calls nexusai_db_services_list to find the database.
It calls nexusai_db_backup or nexusai_db_backup_list, then nexusai_db_restore_to for a staging copy.
It reports the backup it used and the restore result.
Back up the orders database in my shop deployment. Then restore last night's backup into the staging database so I can test the new migration against real data.
Restores through MCP need the db:admin scope. Without it, the agent can list and download backups but cannot change data.
Open a database deployed with your app, or find it with nexus db services.
Take an on-demand backup and turn on daily backups with the retention you want.
Download a backup, or upload a dump from another host.
Restore in place, or into another database of the same engine to test first.
Backup format and restore behavior
Engine
Backup format
Uploads accepted
Restore
PostgreSQL
pg_dump custom format
pg_dump custom format or plain SQL
In place or into another PostgreSQL database
MySQL
mysqldump SQL file
mysqldump SQL file
In place or into another MySQL database
MongoDB
mongodump directory, compressed
mongodump --archive --gzip file
In place (existing collections dropped first) or into another MongoDB database
Redis
RDB snapshot
RDB file
In place or into another Redis database
Backups for each kind of database
Database
How it is backed up
How it restores
Database deployed with an app
Daily scheduled and on-demand native dumps, downloadable, 7-day default retention
In place or into another database of the same engine
Standalone database on NEXUS AI
Snapshots on demand
Into a new database; the source is never touched
Standalone database on AWS RDS, Google Cloud SQL, or Azure Database
Snapshots through the cloud provider
Into a new database instance
Frequently asked questions
How often do automatic backups run?
Once a day for every database with scheduled backups turned on. The scheduler checks every hour and backs up any database whose last backup is more than 24 hours old, so a restart never skips a day. You can also take a backup on demand at any time.
How long are backups kept?
Automatic backups are kept for 7 days by default. You can raise the retention, for example with nexus db backup-schedule --retention 30, but not lower it below 7 days. While scheduled backups are on, the retention window applies to every backup NEXUS AI creates, scheduled or on demand. Uploaded backups are kept until you delete them, and you can download any backup to keep it longer.
Can I restore to a point in time?
Not for databases deployed with an app. Those are daily and on-demand logical backups, so you restore to the moment a backup was taken. Take an on-demand backup before a risky change. Azure Database standalone instances support point-in-time restore through Azure.
Can I import a pg_dump from Heroku, Supabase, or RDS?
Yes. Create a pg_dump custom-format file or a plain SQL dump on the old host, upload it with nexus db backup-upload to a PostgreSQL database on NEXUS AI, and restore it. Uploads can be up to 5 GB.
Does restoring overwrite my data?
An in-place restore replaces the database's current data with the backup. To check a backup first, restore it into a different database of the same engine, such as a staging copy, with restore-to.
Can I restore a MySQL backup into PostgreSQL?
No. A backup can only be restored into a database of the same engine. NEXUS AI rejects a mismatched restore before changing anything.
Can Claude or another AI assistant restore my database?
Yes, when you allow it. MCP clients such as Claude, Cursor, and Codex can list, download, create, and restore backups. Listing and downloading need the db:read scope; creating backups, restoring, and changing schedules need db:admin.
Can I download my backups?
Yes. Each backup downloads through a signed link that expires within an hour, from the dashboard, nexus db backup-download, or the MCP download tool. The file is a standard dump you can restore anywhere.
Which databases and plans include backups?
Backups cover PostgreSQL, MySQL, MongoDB, and Redis databases deployed with an app on NEXUS AI, on every plan. Standalone databases, which need a paid plan, use snapshots instead.
Are backups included for standalone databases?
Standalone databases use snapshots. On NEXUS AI you create a snapshot on demand and restore it into a new database without touching the source. Cloud standalone databases use the provider's snapshots.