VPS Snaps vs Ottomatik
Same job counts. Different jobs.
Their tiers allow 3, 50 and 250 backup jobs, and so do ours. Theirs are databases and files with storage included; ours add snapshots, Docker, Kubernetes and test restores.
Scan server
Looks for WordPress, Laravel, Craft CMS, and Ghost installs in common web-root locations. Database credentials are read automatically where the config format allows it.
Storage destination for created jobs
www/acme-blog
/var/www/acme-blog
File backupDatabase backup (acme_blog)
www/acme-app
/var/www/acme-app
File backupDatabase backup (acme_app)
sites/acme-docs
/home/deploy/sites/acme-docs
File backupDatabase backup (ghost_prod)
The short version
We wrote both columns. If the left one describes you, buy theirs — you will be happier and we would rather not have the churn.
Pick Ottomatik if…
Six situations where they are the better answer.
- You only need a few databases backed up, and want it cheap. Their $14 Lite plan includes three database or file backup jobs. Ours start on Standard at $45 a month ($30 billed annually); the plans below it cover files, provider snapshots and Kubernetes, not databases.
- You want storage included. Every plan of theirs carries hosted storage, from 5 GB on Lite to 200 GB on Agency. Ours include none, by choice.
- You want your whole team in on the cheapest plan. Their pricing page lists unlimited users on Lite, and their home page says servers are unlimited. Our plans below Pro have one team member and a server allowance.
- Your database is on Supabase. Their Supabase backups run from their servers, with nothing to set up on your side. We have no Supabase integration.
- You want MySQL binlogs. They list binlogs as a backup type; we take full dumps on a schedule.
- You need Dropbox as a destination, or backups every minute. Both are on their pages. Ours go to S3-compatible buckets or Google Drive, at most every 5 minutes.
Pick VPS Snaps if…
Six situations where we are.
- You back up more than databases and files. Provider snapshots on eight clouds, Docker volumes, Kubernetes, WordPress sites through a plugin, Cloudflare DNS zones and managed Postgres on Railway, Render and Coolify all run from the same dashboard as PostgreSQL, MySQL, MariaDB and MongoDB.
- You want proof a backup restores without doing it yourself. A scheduled test restore builds a throwaway server on your own cloud, restores the backup onto it through the same code a real restore uses, checks it, and deletes the server.
- You want the server back, not only the data. From Standard we build a replacement server on your own cloud from the newest backup, and Pro and Agency can keep one warm and fail over to it.
- You want uptime monitoring in the same place. Monitors confirm an outage before alerting and put the server's newest backup in the alert, with status pages, from Starter up.
- You want to pay annually. Ours takes about a third off; their pricing page lists monthly prices only.
- Your machines have no inbound route. Our Agent dials out, so there is no SSH port to open. Their pages describe backups as commands sent over SSH from their servers.
Price, tier by tier
Matched by position. The job counts line up exactly on the three tiers they publish, so the difference is in what a job can be and what the plan includes.
| Tier | VPS Snaps | Ottomatik | Their tier includes |
|---|---|---|---|
| Freevs their Free | Free1 backup job · daily · no database backups | Free | First backup, free forever |
| Startervs their Lite | $15/mo$10/mo billed annually3 backup jobs · daily · no database backups | $14/mo | 3 backup jobs · daily · 5 GB storage |
| StandardNo match on their side | $45/mo$30/mo billed annually20 backup jobs · every 12 hours · databases included | — | No tier at this position |
| Provs their Professional | $85/mo$57/mo billed annually50 backup jobs · every 5 minutes · databases included | $79/mo | 50 backup jobs · every 5 minutes · 100 GB storage |
| Agencyvs their Agency | $175/mo$117/mo billed annually250 backup jobs · every 5 minutes · databases included | $199/mo | 250 backup jobs · every minute · 200 GB storage |
Read that honestly: the monthly prices are close, and which is cheaper depends on the tier. What separates the two is what a job is allowed to be. Every job of theirs can be a database. Ours can be a provider snapshot, a folder of files or a Kubernetes namespace on any plan, and a database or a Docker volume from Standard up. Their plans also include storage, and ours include none.
After the backup
Both products restore a database from the dashboard onto another server. The difference is what happens when nobody is asking for a restore.
Their database pages suggest restoring onto a different server as a simple way to test an old backup. That is a good habit, and it is a manual one.
A test restore does it on a schedule. We build a throwaway server on your own cloud, restore the newest backup through the same code an emergency would use, check that it arrived, and delete the server. A backup that does not come back alerts you the day it is tested, not the day you need it.
A replacement server goes a step further. From Standard, we can build a new server on your cloud from the newest backup when the original is gone. Pro and Agency can keep one warm and move traffic to it.
Where the backup runs
Theirs run as commands sent over SSH from their servers, and their Supabase backups run from their servers outright. That is how they can back up a database with no server beside it.
Ours run on your server over SSH, through the Agent inside your network, or inside your own Railway or Render project, and upload from there to your storage. Where a platform leaves nowhere to run, the dump streams through our worker to your storage and is never written to our disks. Either way, the only copy is yours.
Line by line
Every cell in their column was read off one of their public pages. Where those pages are silent it says so, rather than guessing.
| Capability | VPS Snaps | Ottomatik |
|---|---|---|
| What gets backed up | ||
| PostgreSQL, MySQL, MongoDB | ||
| MariaDB | Not stated | |
| MySQL binlogs | ||
| Supabase | From their servers | |
| Files and directories | ||
| Provider snapshots | 8 clouds | Mentioned, clouds not named |
| Docker volumes | Not stated | |
| Kubernetes | Not stated | |
| WordPress from inside WordPress | Not stated | |
| Where backups live | ||
| Your own S3 or S3-compatible bucket | ||
| Google Drive | ||
| Dropbox | ||
| Storage included in the plan | 5 GB – 200 GB | |
| Restoring | ||
| Restore from the dashboard | ||
| Restore onto a different server | ||
| Scheduled test restores on a throwaway server | Not stated | |
| Replacement server built from a backup | Standard and up | Not stated |
| Plans | ||
| Database backups | Standard and up | Lite and up |
| Team members, entry paid tier | 1 | Unlimited |
| Servers | 1 to 150, by plan | Unlimited |
| Fastest schedule | Every 5 minutes | Every minute |
| Annual billing | About a third off | Not stated |
| Reach and alerting | ||
| Machines with no inbound route | Outbound-only Agent | Not stated |
| Slack, Teams, Google Chat, Discord | All plans | Not stated |
| Webhooks | Agency | Listed, plan not stated |
| Uptime monitoring and status pages | Starter and up | Not stated |
Ottomatik prices, job counts, schedules and included storage were read from ottomatik.io/pricing in October 2026; it shows monthly prices only, so no annual figure is given for them. Everything else in their column comes from their home page and their database, Supabase and file backup pages. Where those pages do not say, the cell reads "Not stated", which is a fact about their marketing rather than their software. Prices and features may have changed since. Our column is read live from the plan records this app enforces.
FAQs
Can’t find the answer you’re looking for? Reach out to our support team.
Is Ottomatik cheaper than VPS Snaps?
Month to month, at some tiers: the table above has both prices side by side, read live on our side. Two things move the answer more than the sticker price. Their plans include storage and ours include none. And their $14 Lite plan backs up databases, while ours start on Standard. If three MySQL dumps a day is all you need, theirs is the better deal.
Do you back up Supabase?
No. We have no Supabase integration. Ottomatik does: the backup runs from their servers, so you need nothing of your own beside the database. If Supabase is what you need backed up, theirs covers it and ours does not.
What does a test restore actually prove?
That the newest backup comes back on a machine that had nothing on it. We build a throwaway server on your own cloud, restore the backup onto it through the same code a real restore uses, check the result, then delete the server. Failures alert you, and a test that could not start says so instead of blaming the backup. It covers database, file and Docker jobs, runs on the schedule you choose, and is off until you switch it on, because the throwaway server is billed to your cloud account.
Can I run both while I decide?
Yes. Our archives are plain .sql.gz and .tar.gz files in your own bucket, so there is nothing proprietary to convert later. Point a VPS Snaps job at the same database, let both run for a week, and keep the one you trust. Whatever they already stored stays wherever you told them to store it.
Is this comparison kept current?
Our column is read live from the same plan records the app enforces, so it cannot drift. Their column was read off ottomatik.io, with the date printed under the table. If it looks stale, treat their pricing page as the source of truth, and tell us so we can fix it.
Powerful features to give you peace of mind
Rest easy knowing your data and your reputation are safe.
- Bring your own storage
- Backups land in your own S3-compatible bucket — Backblaze B2, Wasabi, Cloudflare R2, or plain S3 — or in your own Google Drive. You hold the keys and the data.
- Snapshots stay with your provider
- Provider snapshots are created through the provider's own API and never leave your account. We store the snapshot ID, not the image.
- Eight providers, one dashboard
- DigitalOcean, Hetzner, Vultr, Linode, AWS EC2, AWS Lightsail, Google Compute Engine and Microsoft Azure — scheduled and reviewed from the same place.
- A replacement server on demand
- Recover now builds a new server on your own DigitalOcean, Hetzner, Vultr, Linode, AWS EC2, AWS Lightsail, Azure or Google Compute Engine account, from its snapshot or from its backups, software included.
- Failover on any cloud
- When a server stops answering, its traffic moves to the recovery server: by reserved or floating IP where your cloud has one, or by your DNS on Cloudflare, which works on every cloud.
- Know it's down, with the way back
- Uptime monitors for sites, ports and scheduled jobs confirm an outage before alerting, name the server's newest backup, and publish a status page. On paid plans.
- Your DNS zones, backed up
- Every record in a Cloudflare zone, kept in your own storage as a BIND file too. A restore previews what differs and writes back only that.
- Schedules that fit your traffic
- Hourly, daily, weekly, monthly, or a fixed interval in minutes — anchored to your timezone, so a 02:00 job stays at 02:00 across a DST change.
- Retention that prunes itself
- Set how many days to keep. Older snapshots and archives are cleaned up after each successful run, so storage bills stay flat.
- Every run on record
- Status, duration, size and trigger, with each step it took in order and its warnings and errors kept in place — so a failure tells you which step broke.
- Checksummed on upload
- Every archive is hashed as it streams to your bucket and the checksum is stored with the run, so you can verify what landed.
- Run on demand
- Trigger any job by hand before a migration or a risky deploy, without touching its schedule or its retention window.
- Alerts on five channels
- Email plus Slack, Microsoft Teams, Google Chat, and Discord — on success, on failure, and on a job that missed its schedule entirely.
- Encrypted credentials
- SSH keys, database passwords, and storage secrets are sealed with AES-256-GCM before they touch the database.
- Team access with roles
- Invite your team into a shared workspace as owner, admin, or member, so backups outlive whoever set them up.
“I'm constantly spinning up WordPress and Laravel applications for clients, and backups are one of those things that are easy to put off until something goes wrong. VPS Snaps can detect the applications on a server and help create the file and database backup jobs, which makes getting proper backups in place much faster.”
Run both for a week. Keep the one you trust.
Our free plan needs no card and never expires, and our archives are plain files in storage you own, so there is nothing to migrate in either direction.
No credit card required. Cancel anytime.