Agentless backup and restore for a Strapi instance, with nothing installed in the CMS being backed up. In development.
Generated on request from the live content of this site. Nothing about it is stored ahead of time. File name Tech-Style-Strapi-Remote-Backup-Pro-Product-Brochure.pdf.
Back up and restore any Strapi instance without installing a plugin in it. Point the tool at a URL, sign in with admin credentials, and it does the rest: no dependency added to your CMS, no redeploy, no code running inside your production process.
Installing one means adding a dependency to a live CMS, redeploying it, and asking someone to trust code running inside their production process. If you are an agency or a consultant backing up a client's instance, that is often not merely inconvenient: you may have no deploy access at all.
This runs entirely outside the target. It authenticates against the same admin API the Strapi admin panel itself uses, so there is nothing to install, nothing to redeploy, and nothing to uninstall afterwards. It cannot destabilise the CMS it is backing up, because it is not running inside it.
Content entries across all collection and single types, drafts and published, every locale. The media library with its folder structure. Content-type and component schemas, captured as they stood at backup time.
Pick content types, pick individual records, and choose how many relation hops to follow. Restoring a handful of articles pulls in the authors and categories they point at, so you do not end up with records referencing things that no longer exist.
Restore writes to a live CMS, so it always produces a diff first: creates, updates, deletes, skips, plus warnings about schema drift and relations that would land unresolved. Nothing is applied without confirmation.
Local or network folder works today. S3 and anything speaking its API (MinIO, Cloudflare R2, Wasabi, Backblaze), Azure Blob, Google Drive, Dropbox, OneDrive, SFTP and FTPS are behind a provider interface with retention rules per destination. They are designed and registered, but they still throw when called.
Designed to run recurring backups as a Windows Service or a systemd daemon, so a machine that slept through three nightly windows produces one catch-up backup on waking rather than three. Scheduling lives in the engine by decision, not in the desktop app. It ships with the app.
A plain .zip any operating system can open, with SHA-256 checksums per entry and optional AES-256-GCM encryption. A backup format that needs its own software to inspect fails at exactly the moment it matters most.
The command line is a first-class way to use this, not a debugging shortcut. Anything the app can do, an expert can do from a terminal, because the app drives exactly the same engine rather than reimplementing it.
The command line is what exists today: login, backup, restore, inspect and verify, for developers, CI pipelines and headless servers. A bootstrap installer stages a pinned, checksum-verified Node runtime and puts a strapi-backup command on the PATH for anyone who would rather not think about Node at all (measured working on Windows, not yet run on macOS or Linux).
The desktop app is designed and skeletoned, not built. Twenty-four C# files carry the final signatures behind an Avalonia UI, and nothing behind them runs yet. When it lands it adds a visual content-type picker with relation-depth control, the restore diff, scheduling, and secure storage of destination credentials in the operating system's own keystore, bundling its own runtime so there is nothing to install first.
$ npx strapi-remote-backup-pro backup --url https://cms.example.com --email admin@example.comBoth majors are behind one dialect boundary, because they disagree about nearly everything structural: how records are identified, whether fields are nested, how draft state is expressed, how locales are linked. Which version an instance speaks is detected by probing its behaviour rather than trusting a version string that may be absent, proxied away, or simply wrong.
v5 is the one that is proved. The round trip has been run repeatedly against two live Strapi 5.52.0 instances and compared record by record. The v4 dialect is written to the same interface but has never been run against a v4 instance, so we describe it as written, not supported. If you have a v4 estate that needs backing up, talk to us and we will prove it against yours rather than ask you to trust a claim.
One limitation that will not go away: Strapi v4 identifies records only by an instance-local numeric id. Restoring a v4 archive into a different instance therefore needs an explicit identity mapping. That is a property of v4 rather than of this tool, and it is reported plainly instead of quietly producing duplicates.
It is exchanged once for a session token and dropped, never written to disk, never into an archive, never into a log.
Strapi throttles admin login. A failed sign-in is never retried automatically, because an automatic retry would lock you out of your own CMS.
Concurrency is capped low by default and rate limiting is honoured with backoff. A backup must never be the reason a site goes down.
Windows DPAPI, macOS Keychain, libsecret on Linux, never a configuration file. Profiles reference secrets rather than containing them, so they are safe to share.
Published under the MIT licence, free to use commercially, like the rest of our open-source work. The archive format is specified in full, so if this tool ever disappears, your backups do not become unreadable.
Unzip an archive and you get a manifest describing what is inside, your content as one JSON record per line, and your media files. No proprietary container, and nothing you need us for.
backup-2026-08-18T1430.zip ├── manifest.json always plaintext, always first ├── schemas/ content types & components, as captured ├── content/ │ └── api--article.article.ndjson one JSON record per line ├── media/ │ ├── media.ndjson filenames, folder paths, hashes │ └── files/ named by content hash, de-duplicated └── meta/ ├── locales.json └── run-report.json counts, durations, warningsThe manifest is the one entry that is never encrypted, so an archive can be listed and identified without its passphrase.
Copy, migrate and live-sync content between Strapi environments. On the official Strapi Marketplace.
An origin server for images and media at scale.
Oracle-to-PostgreSQL migration assessment, on PyPI.
Tech Style Ltd is a UK technology company building enterprise software, procurement intelligence and AI platforms. Tell us what you are trying to do and we will tell you honestly whether we are the right people for it.
| This document online | www.tech-style.co/product-strapi-remote-backup |
|---|---|
| Website | www.tech-style.co |
| Enquiries | hello@tech-style.co |
| Products | www.tech-style.co/products |
| Partner programme | www.tech-style.co/partners |
Strapi Remote Backup Pro: Product Brochure, typeset when you click, from the content above.