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 How it works
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
Add your databases or file systems once, then choose where backups should be stored. Khizaana securely encrypts your credentials and validates every connection before your first backup runs.
Connection verified
Postgres
03 Ship to storage
Choose when backups should run, then let Khizaana handle the rest. Every backup is verified, uploaded to your storage, retained according to your policy, and ready to restore whenever you need it.
Nightly · production-db
Weekly · staging files
Immutable vault
[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 restore from any destination without rewriting scripts.
Point-in-time recovery and verified snapshots so a bad deploy never becomes a data loss event.
Restore completed
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. Khizana knows the difference and handles it for you.
Point Khizana at a project and one scheduled job captures the database and the Storage buckets into a single verified archive, 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 Khizana 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. Khizana 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. Khizana applies the right TLS mode and dump flags for it, so the backup you take is one you can actually restore.
[04] PRICING
Self-host the open-source control plane. Unlimited jobs, your infrastructure, community support.
Self-hosted
$0
Forever · open source
Unlimited backup jobs
Community Discord
Managed Khizaana with immutable vaults, priority alerts, and a hosted control plane for your team.
SSO, SLAs, VPC deployment, and a dedicated partner when compliance and uptime are non-negotiable.
SSO, audit logs, and retention policies tuned to your compliance stack.
Contracted uptime SLAs with priority restore windows when incidents hit.
Team size
50+ seats
Deployment
Hybrid · VPC
[05] FAQ
Yes. The Community edition is open source and free forever. You run the control plane on your own infrastructure with unlimited backup jobs and community support.
Connect Postgres, MySQL, MongoDB, and file systems as sources, then ship snapshots to S3, Azure Blob, Google Drive, Dropbox, and other object stores. More connectors ship regularly.
Yes, and they are treated as first-class rather than as a generic Postgres box. Pick your host when you add a source and Khizana 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 adds a managed control plane, immutable vaults, priority alerts, and team features so you spend less time operating Khizaana itself. Community stays fully capable for self-hosted setups.
Yes. Point-in-time restores spin up verified copies to a destination you choose while your live sources keep serving traffic.
Enterprise plans include SSO, audit logs, contracted uptime SLAs, VPC or hybrid deployment, and a dedicated success contact. Talk to sales for a custom quote.