Resistro Enterprise: the same backup baseline, in your infrastructure
Resistro Enterprise is the third operating mode — not a new product promise, just the same backup path, installed at your site.
Resistro Cloud backs up self-managed Postgres setups through an agent, with a customer-side key and restore evidence. That stays. Now there’s also Resistro Enterprise: a management console that companies run on their own infrastructure — for database backups that should never leave the data center.
That completes the portfolio:
- CLI — open source, for anyone who wants to run backup and restore themselves.
- Resistro Cloud — SaaS-managed backups with an agent, monitoring, and restore drills.
- Resistro Enterprise — the same operating layer, installed at the company.
Enterprise relates to Cloud like a different plan, not a different product. Same idea: backups that actually restore. Different operating location: your infrastructure instead of cloud.resistro.org.
What the console can trigger — and what it cannot
The console is deliberately a subset of the CLI, not CLI parity. It triggers backup, restore test, drill, PITR restore, retention changes, and key management. Everything else — verify, catalog, chain, forecast, estimate, WAL archive control, encryption rotate — is agent-side or terminal-only, and the console stays read-only there or does not show it at all.
What Enterprise is today
Resistro Enterprise is a management console for self-hosted operation that you install on your own infrastructure. Today it covers:
- Identity providers: OIDC, SAML, and SCIM — role-based access via IdP mappings, automated user provisioning.
- BYOK/KMS: customer-managed master key for backup encryption (envelope encryption), provider choice of local file, HashiCorp Vault Transit, or AWS KMS.
- Air-gap operation: central egress guard (
RESISTRO_AIRGAP=1) blocks all outbound connections; MFA/TOTP QR codes are generated locally, no external service required. - Audit export: CSV or PDF, plus machine-readable retention and recoverability reports.
- Alerting: built-in rules (backup failed/overdue, drill, PITR, agent offline, license, anomaly detection) with email, webhook (Slack, Teams, PagerDuty) channels.
- High availability (Active/Passive): two console instances against the same PostgreSQL, automatic takeover on console-instance failure. Leader election via PostgreSQL advisory lock, split-brain constructively excluded. Takeover ≤ ~2 s after connection loss (default poll 2 s). Database failure itself is not covered — a PostgreSQL standby is recommended (streaming replication, e.g. Patroni).
- Incident runbook: triage via
/healthand/admin/doctor(database, schema, license, air-gap), support bundle as ZIP via/admin/supportorresistro-console doctor(secrets redacted), restore path via/admin/recoverabilitywith evidence PDF. - Custom branding: company logo and color scheme in the console.
Data and keys stay on your network. There is no mandatory upload into Resistro’s SaaS storage.
That’s the distinction that matters to many buyers: not “more features,” but data residency and operational ownership staying with the company.
What it is not
Enterprise is not a hard SLA, not a SOC 2 seal, and not a replacement for your own operations. The console doesn’t replace the Linux host or the restore drill itself — that still runs through the resistro engine, the same as with the binary, not through a dashboard. Enterprise makes access, evidence, and operational data visible and controllable, inside your network.
If you use Cloud because you don’t want your own backup ops, stay on Cloud. If you’re not allowed to let backups leave your network, or you want to run the console yourself, take Enterprise.
The portfolio in one sentence
The CLI is the tool. Cloud is the operated service. Enterprise is the same service, run by you.
Open source stays open source. Cloud stays the narrow SaaS path for small self-managed Postgres setups. Enterprise closes the gap for companies that need the management layer in-house.
Installation, upgrade, and evaluation
The console is deployed via an installer (install-console.sh): downloads the release artifact, verifies the SHA256 hash against the manifest, installs the binary and systemd unit. The agent installer (install-agent.sh) follows the same pattern on database hosts. Both installers are idempotent — existing configuration is preserved on reinstall.
Updates run via resistro-console upgrade: a full pg_dump is taken before every migration; if any migration fails, the run aborts and the database stays at the pre-upgrade state. The upgrade path is tested across two version steps (N-2).
For evaluation, a parameterized eval bundle (make eval-bundle KUNDE=... LIMIT=... DAYS=...) produces a release tarball, signed eval license, and quick-start guide in a single call. On conversion to a full license, the same CA key pair is reused — no new binary needed.
Who it fits
Enterprise fits when:
- databases run self-managed (typically Postgres; MySQL/MariaDB remains a limited logical path, as before),
- backup and restore need to be evidenced,
- storage and control must stay on your own infrastructure,
- someone internally can run the console.
It doesn’t fit if you want to back up a managed database (RDS, Supabase, and similar) or need a promise that goes beyond the trust framework.
Next step
Cloud remains trialable at cloud.resistro.org, 14 days, no card. Enterprise is the other plan: installing the management console on your own infrastructure.
If you want to check the fit, start with the trust model — the same limits apply, only the operating location changes.