Hi everyone! I'm Sukriti, part of the team at Zmanda. Let me be honest about who this is for, because this product covers a lot of ground and plenty of you don't need us yet. You need a 3rd -party backup tool like Zmanda when a prospect sends over their security questionnaire. Somewhere past question 40 it stops asking about SSO and starts asking: whether your backups are encrypted whether they're immutable how often they're tested what your recovery time objective is whether you can produce audit logs For most founders that's the first time backup lands on the roadmap. Whoever wrote the pg_dump cron job can't answer any of it, and a screenshot of an S3 bucket isn't an answer. After a while, you look up and realise you administer things now. Not managed Postgres, actual VMs, a Proxmox box, a database you tune yourself, a fileserver, twelve laptops with source code on them. Zmanda Pro is built for that middle: past cron jobs, not yet ready for an enterprise contract and a certified admin to run it. Why use a third-party backup like Zmanda? You may have answers like: "My cloud provider backs it up." They guarantee their infrastructure's durability, not your data's recoverability. RDS snapshots live in the same account as the database — same credentials, same blast radius. If that account is compromised or closed, the snapshots go with it. An independent copy exists to survive the failure of the thing it's copying. "We have a script." Most people do. The real question is whether anyone has ever restored from it, and whether something holding your credentials can reach it. Ours writes to immutable storage — S3 Object Lock, GCS Object Lock, or ZFS snapshots. On S3 and Wasabi that includes Compliance Mode, which an admin credential can't shorten. Deleting a backup you shouldn't be able to delete should be impossible, not discouraged. How it's priced? Per machine, not per gigabyte. On the Business plan that's $5.99 per workload per month whether that workload holds 100GB or 10TB; Business Plus is $6.99. VMs, physical servers and databases are all the same unit. No data metering, no renewal multiplier. The part I'd want to know if I were you: Your backup data never passes through our servers. It's chunked, deduplicated and encrypted on the client, then goes straight to a destination you own, your S3 bucket, Wasabi, Azure, GCS, a NAS, a local disk. We hold the control plane and the metadata. We cannot decrypt your backups, and with zero-trust mode on there's no password-reset path either. And if you'd rather we hold nothing at all, you can self-host the entire server. Internet-connected, if data sovereignty is the constraint. Or fully air-gapped, if internet access isn't permitted where you work. Software only ,there's no appliance to buy, which is where most "on-prem" backup has ended up. Coverage: 30+ workload types from one console: VMware vSphere/ESXi, Hyper-V, Proxmox, Windows and Linux servers, SQL Server, Oracle, MySQL, MongoDB, MariaDB, Microsoft 365 (Exchange, SharePoint, OneDrive, Teams), Synology and QNAP, SMB/CIFS file shares, and Windows/Mac/Linux laptops. Forever-incremental after the first full. Client-side dedup delivers up to 90% storage reduction — 10:1 validated in production. Being straight about what it isn't — There's no free plan. Free trial, yes. Extendable beyond 30-days if you need it. — If everything you run is managed PaaS — Vercel, Supabase, Neon, PlanetScale — and you administer no servers, your provider's point-in-time recovery is fine for now. If you run backup for a living: what made you switch the last time you switched?

Zmanda Pro

Enterprise data backup, recovery, and resilience

Enterprise data backup, recovery, and resilience