Know what broke
what changed.
Meraki Backup saves every configuration endpoint in your Cisco Meraki organisations as plain JSON. It shows the difference between any two snapshots and names the admin behind each change. It only reads from Meraki, and a restore runs only after you approve its plan.
● Runs on your servers · ● Read-only API access · ● Secrets never stored · ● Plain JSON, no lock-in
The Meraki dashboard is easy to change
and hard to undo.
Changes go unnoticed
A rule is edited or an SSID is renamed, and nobody notices until users start calling.
No version history
The dashboard has no full history of your configuration, so rebuilding a known-good state means relying on memory and screenshots.
Recovery is manual
Putting settings back by hand across dozens of networks takes a long time and is easy to get wrong when you're under pressure.
Back up, compare, restore.
Meraki Backup uses the Meraki Dashboard API. It needs no agents on your network.
Connect
Add a Meraki API key. Backups only ever read.
export MERAKI_API_KEY=…
Snapshot
Every configuration endpoint for every organisation is saved as plain JSON, along with Meraki's change log.
meraki-backup run --all-orgs
Compare
Compare any two snapshots to see exactly what changed, and which admin changed it.
meraki-backup diff A B
Restore
Review the restore plan first. Nothing is written until you type yes.
meraki-backup restore apply
Built by people who've had
to undo a 2 a.m. change.
Every API endpoint
Endpoints come from each organisation's own OpenAPI spec, not a hand-maintained list, so new Meraki features are included automatically.
Exact diffs
Compare any two snapshots to see each setting that was added, removed or changed, down to a single field.
Who changed it
Each snapshot saves Meraki's change log since the previous one. Diffs, alerts and the dashboard show which admin made a change, and when.
Secrets never stored
Wi-Fi passwords (PSKs), RADIUS secrets, SNMP community strings and licence keys are replaced with a salted hash. A changed password still shows up in a diff.
Safe snapshots
Each organisation is built in a temporary folder and swapped in only when complete. A failed run never replaces a good snapshot.
Fast across many organisations
Each organisation is read with several requests at once, kept just under Meraki's limit of 10 requests per second, and several organisations are backed up at the same time.
Proof of what was backed up.
Every endpoint is recorded in _coverage.json, so you know exactly what each backup did and didn't capture.
- Captured: saved in the snapshot
- Not applicable: that product isn't used in this network
- Skipped: live data or deprecated endpoints
- Failed: reported clearly, never hidden
One tool, two kinds of teams.
Look after every client's network.
- Back up many client organisations at the same time
- Answer "what changed?" with a diff and a name, not a guess
- See which client admin made a change, and when
- Roll back a bad change before it costs you the client
Change control for your own network.
- A dated, readable record of every configuration change
- Evidence for audits and change reviews
- Recover from mistakes in minutes, not hours
- Plain JSON you can keep in Git or your own storage
Runs on your infrastructure.
Your data stays there.
Meraki Backup runs on servers you control. Your API key, your snapshots and your change history never leave your environment.
- Runs on a server or VM you control
- Snapshots are written to your own storage as plain JSON
- Schedule it with the tools you already use
- Keep snapshots in Git, back them up, search them with
grepandjq - No proprietary format, so nothing locks you in
A managed, hosted option is also available, where we run Meraki Backup for you. Ask about it on your demo.
Safe by default.
A backup tool that can damage your network is worse than none. Meraki Backup is designed so it can't do that by accident.
Backups only read
Backups never write to Meraki. Only restore apply writes, and only after it shows its plan and you type yes.
No secrets stored
PSKs, RADIUS secrets, SNMP community strings and licence keys are saved as salted hashes, never in readable form.
No half-finished snapshots
A snapshot is only saved once it's complete. A failed or interrupted run leaves the last good one untouched.
Stays under Meraki's limits
Stays just under the limit of 10 requests per second per organisation, so it won't slow down your other API tools.
Questions, answered.
Will Meraki Backup change anything in my Meraki dashboard?
Not unless you ask it to. Backups only read. The one command that writes is restore apply, which shows you its full plan first and does nothing until you type yes.
What exactly does it back up?
Every configuration endpoint the Meraki API offers for your organisations. The list comes from each organisation's own OpenAPI spec, not a hand-maintained one. Live data such as client lists, and deprecated endpoints, are skipped and recorded as skipped in _coverage.json.
Are passwords and keys stored?
No. Wi-Fi PSKs, RADIUS secrets, SNMP community strings and licence keys are replaced with a salted hash. You can still see in a diff that one changed, but the actual value is never saved.
How do I know who made a change?
Each snapshot also saves Meraki's change log since the previous one. Diffs, alerts and the dashboard use it to show which admin made each change, and when.
What happens if a backup fails partway through?
Your last good snapshot is kept. Each organisation is built in a temporary folder and only swapped in once it's complete.
What format are backups in?
Plain JSON files. You can read them, search them, keep them in Git, or move them anywhere. There's no proprietary format and no lock-in.
Where does Meraki Backup run?
On your own infrastructure. It's self-hosted software, so your API key, snapshots and change history stay in your environment. If you'd rather not run it yourself, a managed, hosted option is also available. Ask about it on your demo.
Your network changes overnight.
Now you'll know exactly how.
See Meraki Backup run against a real Meraki organisation in a 30-minute demo.