Connect your sources, choose your storage destination, schedule jobs, and let Khizaana handle the rest.
works with the tools modern teams already use:
[01] HOW IT WORKS
01 Create a project
Group related backups into a single project like Production, Staging, or Development. Keep databases, storage destinations, schedules, and backup history organized from day one.
Source
production-db
Destination
s3 · backups
02 Connect sources and storage
Add your databases or file systems once, then choose where backups should be stored. Khizaana encrypts your credentials at rest and lets you test every connection before your first backup runs.
Connection verified
Postgres
03 Schedule and forget
Choose when backups should run, then let Khizaana handle the rest. Every backup is checksummed, uploaded to your storage, size-checked, retained according to your policy, and ready to download whenever you need it.
Nightly · production-db
Weekly · staging files
Every 6h · orders-mongo
[02] PLATFORM
Jobs succeeded
128
+12%
Data protected
4.2 TB
+8.1%
Failed jobs
0
0%
Avg. duration
6m
-14%
Backup volume
Postgres, MySQL, Mongo, filesystems — self-hosted or on Supabase, Neon, RDS and Atlas. Ship to S3, Azure, Drive, or Dropbox from one place.
Inspect every job, fork the pipeline, and self-host when compliance demands it.
Connect sources once, schedule jobs, and download any backup from its destination without rewriting scripts.
Every archive is SHA-256 checksummed and size-checked after upload, with a signed download link ready when you need to restore.
Backup verified
production-db · 2m ago
[03] CONNECTORS
Managed Postgres and MySQL are not the same as the database on your own box: TLS is mandatory, you are never superuser, and half the connection strings on the dashboard cannot be dumped at all. Khizaana knows the difference and handles it for you.
Point Khizaana at a project and one scheduled job captures the database and the Storage buckets into a single verified archive. Add a passphrase and it is encrypted before it leaves the worker.
We catch the pooler mistake. Supabase's transaction pooler on port 6543 accepts a connection but can never be dumped. Paste it in and Khizaana rejects it immediately, instead of failing at 3am on your first scheduled run.
The whole database
Every schema you own, including the auth schema that holds your users — not just the public tables.
Storage buckets
Uploads live outside Postgres, so a database dump alone silently loses them. Khizaana pulls the files too.
A restore that works
Dumps are taken without ownership and grant statements, so they replay cleanly into a fresh project.
Pick your host when you add a source. Khizaana applies the right TLS mode and dump flags for it, so the backup you take is one you can actually restore.
[04] PRICING
Start on the Free plan or self-host the open-source stack. 3 backup jobs per project, with every source and destination.
Get startedFree
$0
Forever · open source
3 backup jobs per project
Every source and destination
20 backup jobs per project and up to 20 MongoDB collections per source, billed monthly through Stripe.
Start Pro PlanUnlimited backup jobs and whole-database MongoDB backups for teams that have outgrown Pro.
Unlimited backup jobs in every project, with no plan caps.
Whole-database MongoDB backups, without listing collections one by one.
Jobs per project
Unlimited
MongoDB backups
Whole database
[05] FAQ
Yes. Khizaana is MIT-licensed, and you can run the API, worker, and scheduler on your own infrastructure with Docker. On the hosted service, the Free plan includes 3 backup jobs per project.
Connect PostgreSQL, MySQL, MongoDB, whole Supabase projects, and file directories as sources, then send backups to Amazon S3 or any S3-compatible store, Azure Blob Storage, Google Drive, or Dropbox.
Yes, and they are treated as first-class rather than as a generic Postgres box. Pick your host when you add a source and Khizaana applies the right TLS mode and dump flags for it — including stripping ownership and grant statements, which is what usually makes a managed-database dump fail to restore. Supabase, Neon, Amazon RDS and Aurora, Google Cloud SQL, Azure Database, DigitalOcean, Railway, Render, Heroku, Timescale, PlanetScale, and MongoDB Atlas are all supported.
Yes. Add a Supabase source and one job captures the Postgres database — including the auth schema holding your users — alongside the contents of your Storage buckets, in a single verified archive. Files in Storage sit outside Postgres, so a database-only dump loses every upload without telling you.
Pro raises the limits: 20 backup jobs per project instead of 3, and up to 20 MongoDB collections per source instead of 3. Every plan gets the same sources, destinations, verification, encryption, and alerts.
Every successful run has a short-lived signed download link. Archives come straight from pg_dump, mysqldump, mongodump, or tar, so you restore them with the standard tools, and passphrase-encrypted archives decrypt with plain openssl. One-click restore to the source is on the roadmap.
Enterprise removes the plan limits: unlimited backup jobs per project and whole-database MongoDB backups without listing collections. SSO, audit logs, and contracted SLAs are not available yet, so get in touch if you need them.