One platform, priced by sites. Every module included. Docs All systems operational
Build it freeNo card · no time limit Start free
Native module · Backups

One-click website backup. Your whole site, snapshotted.

SGEN's website backup module bundles your database, content, settings, and media into a single portable .sgen archive, a complete point-in-time snapshot of the site, taken with one click. No plugin to license, no off-site service to wire up: it is a native module included on every plan.

Every snapshot you take lands in one Backups panel. Search by filename, rename a snapshot inline to mark a milestone, and clear out old archives with a bulk action. Each snapshot is a self-contained recovery point you can hold before a risky change.

Why this matters

The change you are about to make should never be the one with no way back.

Most site disasters happen on an ordinary afternoon: an edit that cascades, a bad import, a settings change that breaks more than it fixes. Without a recent snapshot, the recovery story is a support ticket and a host's rolling backup you have never seen. SGEN Backups puts a fresh recovery point one click away, so the moment before a risky change is always recoverable.

A snapshot before you touch anything

Take a backup right before a redesign, a content migration, or a settings change. It captures the whole site as it stands, so you have a known-good point to fall back to.

One file, the entire site

A single .sgen archive carries the database, your pages and content, your settings, and your uploaded media together. There is no piecing it back from three exports.

Native, not a bolt-on

Backups is built into the platform alongside your other 23 modules. The snapshot engine and the management panel ship in the box, so a recovery point is a button in your dashboard with nothing to install or keep current.

What the module does

Capture it, name it, manage it - all from one panel.

The Backups panel is the whole surface: every snapshot you have taken, in one list, with the controls to organize them. Three jobs, in the box.

Create

A single + Create a Backup action bundles your database (a full SQL dump) and your entire uploads directory into one .sgen archive. The job runs in the background and the new snapshot appears in the list when it completes.

Organize

Rename any snapshot inline to mark what it is, "pre-product-launch-v2" reads better than a timestamp. Search the list by filename, and page through your history ten snapshots at a time.

Prune

Delete a single snapshot, or select several and clear them in one bulk action. The panel confirms the result, so you can keep the recovery points that matter and let the rest go.

Managing the list

Rename a snapshot in place. Clear a batch in one move.

The Backups panel is built to keep a tidy history. Click a filename and it becomes an editable field, press Enter to save the new name. Tick several rows and the bulk action removes them together, then tells you exactly what happened.

Inline rename, search, and a bulk delete with a clear confirmation - the whole list, managed from one screen.

How a backup is made

Press create. The engine does the rest in the background.

When you create a backup, SGEN dispatches a background job that dumps your database and zips it together with your uploads directory into one .sgen file. A banner shows while the job runs, so you can keep working, and the finished snapshot drops into the list when it is ready. Each archive is named with the site and a timestamp by default, and you can rename it afterward.

What ships in the box

One module. The snapshot engine and the panel, in the box.

Backups bundles three things into one native module: the snapshot engine that captures your database, content, and media; the .sgen archive format that packs it into one portable file; and the management panel where you search, rename, and bulk-delete your history. Taking a recovery point is a button in your dashboard, not a separate purchase to wire up and keep current.

Snapshot engine.sgen archiveManagement panelIncluded storage
When you need to go back

A snapshot is a recovery point. Restoring from it is a deliberate, assisted step.

A restore replaces a site's entire database and media with the contents of a snapshot, so it is a full rollback, not a partial undo. Because it is that consequential, recovery is handled as a deliberate operation with your platform team rather than a one-tap button buried in a list. The value the snapshot gives you is certainty: a known-good point in time you captured on purpose, ready when you need to roll back to it.

Works with the rest of the platform

Backups sit under everything your other modules build.

A snapshot captures the whole site, which means it captures the work your other native modules produce: the forms and leads, the pages, the products, the settings. Take a backup before a big change in any of them, and you have a clean point to return to.

Questions

Frequently asked questions about Backups

What is in a backup? +
One .sgen archive bundles your full database (a complete SQL dump) together with your entire uploads directory, your media. That means a single file holds the site's content, settings, and media as a complete point-in-time snapshot.
How do I take a backup? +
Open the Backups panel and click + Create a Backup. The job runs in the background, an in-progress banner shows while it works, and the new snapshot appears in the list when it completes, named with the site and a timestamp by default. You can rename it afterward.
Can I rename or delete old backups? +
Yes. Click a filename to rename it inline and press Enter to save. Delete a single snapshot from its row, or tick several rows and use the bulk action to clear them together, the panel confirms the result. Deleting a snapshot is permanent, so prune deliberately.
How do I restore a site from a backup? +
A restore is a full rollback: it replaces the site's database and media with the contents of the snapshot. Because that is a consequential operation, recovery is handled as a deliberate, planned step with your platform team rather than a casual one-click button. The snapshot is your recovery point; the restore is the planned cutover back to it.
Are backups automatic or scheduled? +
Backups are taken on demand: you create a snapshot when you want a recovery point, typically right before a risky change. Treat it as a deliberate "save point" you take before edits, migrations, and updates, not a hands-off scheduler.
Is Backups an extra add-on? +
No. Backups is one of 23 native modules included on every plan: the snapshot engine, the .sgen archive format, and the management panel all ship in the box, with the storage included. You can exercise it on the free Sandbox across unlimited staging sites before you pay anything.
Included in your plan

A recovery point for your whole site, one click away. From $39/mo.

SGEN Backups is one of 23 native modules included in every plan. Take and manage snapshots on the free Sandbox across unlimited staging sites before you pay anything.

From $39/mo, billed annually. $47 monthly. 2-week trial, cancel anytime. Every module included.