Open source, self-hosted, free
The binary is the right choice if you want to run the tool yourself and take full ownership of the operating model.
- Apache 2.0
- Self-hosted
- Free to run
- Same product core as Cloud
Operating model
Binary vs. Cloud
Resistro comes in two forms: the open-source self-hosted binary and Resistro Cloud. The question is not which one is "better". The question is which operating model fits your setup and the way you work.
Hosted by Resistro
Cloud is the right choice if you want to use Resistro without carrying the operational workload yourself.
- Hosted by Resistro
- Same core product
- Smaller defined service scope
- Built for small self-managed Postgres setups
When should you pick the binary?
Pick the binary if you want to operate the tool yourself.
- You already run your own hosts and services.
- You are comfortable owning backup jobs, updates, monitoring, and alerting yourself.
- You want full control over deployment and operating model.
- You prefer an open tool over a hosted service.
The binary makes sense when you deliberately want a self-hosted setup and the additional operational work is acceptable to you.
When should you pick Cloud?
Pick Cloud if you want to use Resistro, but do not want to carry the operation yourself.
- You run self-managed PostgreSQL.
- Hourly backups are sufficient for your setup.
- You do not want to build or maintain your own backup system.
- You want a smaller, tightly-scoped service instead of an enterprise backup product.
Cloud is currently built for solo developers and small teams with small self-managed PostgreSQL setups. It is not for enterprise requirements, not for managed database platforms, and not for setups where PITR or SLA commitments are mandatory.
The core product is the same
- Same product core
- Same basic approach: PostgreSQL backups with a focus on a traceable restore path
- Same narrow product philosophy: no inflated enterprise promises
If you run the binary, you are not using a cut-down demo. It is the same product in a different operating model.
What differs in practice
- You run Resistro yourself.
- You own deployment, updates, monitoring, and operational upkeep.
- You decide how far to take alerting, observability, and operating routines.
What differs in practice
- Resistro runs the service for you.
- Billing runs through Paddle.
- You are primarily buying less operational overhead, not a fundamentally different product.
Short version
Choose the operating model that matches your reality
Pick the binary if you want control and self-hosting is normal for you. Pick Cloud if you have a small self-managed Postgres setup and do not want to operate the backup tool yourself. If you already know you need PITR, enterprise SLAs, managed-database support, or fully automated self-service restore, Resistro is not a good fit today in either form.