Resistro Cloud

Your database backup is worthless until it's been restored

Resistro is the single-binary backup and restore tool for PostgreSQL, MySQL, and MariaDB. Native Go engine, no external dump tools required. Built-in verification, restore drills, and encryption. On large databases it stays close to mydumper. On multi-table restores it is on par with myloader. And it does the parts the others leave out.

  • One binary. Pure Go. PostgreSQL + MySQL + MariaDB. No libmysqlclient, no separate tools.
  • Measured. Close to mydumper on large databases (about 1.11× slower). 1.6–2.0× slower on many small tables. Clearly faster than mysqldump.
  • Verified. Every backup can be drilled. Restore evidence with checksums, not just row counts.

Resistro Cloud: 28-day trial, no card required. Plans start at €9/month. Running it on your own infrastructure? Try Resistro Enterprise free for 14 days.

No card. First restore drill is the test — not a sales call.

New

Resistro Enterprise: the same backup baseline, in your infrastructure

In addition to Resistro Cloud: a management console for database backups that you install and run yourself, on your own infrastructure. IdP integration (OIDC, SAML, SCIM), BYOK/KMS encryption, air-gap mode, and built-in alerting. The CLI stays open source, Cloud stays SaaS — Enterprise completes the portfolio.

Engine boundary

What each engine gets today

PostgreSQL, MySQL, and MariaDB are equal engine paths: the shared engine supports all three including PITR (WAL streaming for PostgreSQL, binlog replay for MySQL/MariaDB). PostgreSQL 15, 16, 17 and 18 are tested in our CI on every change. MariaDB 10.6, 10.11, 11.4, 11.8 and 12.3 are tested in our CI on every change, including a 3-node Galera cluster.

Engine
Backup today
Restore evidence
PITR today
Not covered
PostgreSQL
Logical, daily (Solo/Starter), hourly (Business/Pro)
Daily check + drills
Verified E2E on staging (WAL streaming)
Hard RTO/RPO; real-size PITR
MySQL/MariaDB
Engine-level, logical + binlog
Restore path incl. PITR (binlog replay)
Binlog archiving + restore measured (mysql84, maria1011); no staging E2E yet
Hard RTO/RPO; real-size PITR
Open-source engine proof

The CLI came first. Cloud adds agent, monitoring, and evidence.

Resistro started as an open-source CLI and engine, not as a SaaS dashboard. The shared engine supports PostgreSQL, MySQL, and MariaDB including PITR (binlog replay). Resistro Cloud adds the operating layer for small PostgreSQL, MySQL, and MariaDB setups: setup review, agent attachment, monitoring, restore drills, and evidence. PostgreSQL, MySQL, and MariaDB are treated equally in the engine and in Cloud.

  • Apache-2.0 source: UUXO/resistro
  • PostgreSQL, MySQL, and MariaDB backup and restore path
  • Measured backup: about 1.11× slower than mydumper on large databases, 1.6–2.0× slower on many small tables, clearly faster than mysqldump
  • Measured restore: on par with myloader on multi-table datasets (0.92–1.04×), 1.13× slower on the 9.7 GB / 29-table measurement, 1.395× slower on an older single-table measurement
  • Prometheus exporter, textfile metrics and alerting hooks
  • MySQL/MariaDB engine support including PITR (binlog replay)
  • Interactive terminal UI (TUI): run `resistro interactive`, recommended for first-time users
  • Release binaries on GitHub (current: v1.6.74)
  • Since v1.6.54: parallel MySQL restore and parallel backup verification. The new chunker (v2) is no longer the default since v1.6.55, v1 remains the default. At 501,000 rows we measure no gain for these features, the benefit is expected on large tables and is not yet proven there
Dogfooding

We run our own production database on Resistro Cloud.

The community platform behind our amateur-radio project, 11m-band.de, stores its live PostgreSQL database as an ordinary Resistro Cloud tenant — the same product path we sell, not a separate internal setup. Backups run on an hourly cadence, monitored for silent failures, using the same agent, the same encryption, and the same default storage path through Hetzner data centers in Germany/EU every customer gets. If the restore path broke, we would be the first to notice.

  • Live PostgreSQL of a real production app, not a demo database
  • Runs as an ordinary Resistro Cloud tenant, not a separate internal setup
  • Hourly backup cadence, monitored for silent failures
  • Same encryption and default storage path through Hetzner data centers in Germany/EU every customer gets
Evidence example

What a restore drill produces

A customer-triggered restore drill produces a dated result record and a restore-evidence PDF: selected backup, restore target, outcome, and operator notes. It is evidence for the tested restore path, not a legal certification or SLA.

  • Backup and restore target recorded
  • Restore outcome and checks captured
  • PDF packaged for internal review or customer evidence
Read trust model
Dogfooding — our own production database

Recent restore drill runs, unedited

We run Resistro Cloud in production against our own control-plane database — not against customer data. Shown are the most recent automated restore drills, pulled directly from the pipeline; the full list opens on click. No results are curated or removed.

Resistro Evidence badge
# Date Status RTO Engine Format Size Checks
1 05:40 UTC passed 2.118s postgresql chunked <1GB – – – – ✓ ✓
2 05:08 UTC passed 0.938s postgresql chunked <1GB – – – ✓ ✓ ✓
3 05:08 UTC passed 2.198s postgresql chunked <1GB – – – ✓ ✓ ✓
4 05:04 UTC passed 2.009s postgresql blob <1GB – – – – ✓ ✓
5 15:31 UTC passed 9.072s mysql blob <1GB – – – ✓ ✓ ✓
6 15:31 UTC passed 0.419s mysql blob <1GB – – – ✓ ✓ ✓
Show all 200 runs 194 more, unedited
# Date Status RTO Engine Format Size Checks
7 15:31 UTC passed 0.599s mysql blob <1GB – – – ✓ ✓ ✓
8 12:06 UTC passed 2.407s postgresql chunked <1GB – – – ✓ ✓ ✓
9 05:40 UTC passed 2.13s postgresql chunked <1GB – – – – ✓ ✓
10 05:08 UTC passed 0.977s postgresql chunked <1GB – – – ✓ ✓ ✓
11 05:08 UTC passed 2.077s postgresql chunked <1GB – – – ✓ ✓ ✓
12 05:04 UTC passed 2.13s postgresql blob <1GB – – – – ✓ ✓
13 15:31 UTC passed 9.232s mysql blob <1GB – – – ✓ ✓ ✓
14 15:31 UTC passed 0.378s mysql blob <1GB – – – ✓ ✓ ✓
15 15:31 UTC passed 0.715s mysql blob <1GB – – – ✓ ✓ ✓
16 15:06 UTC passed 2.133s postgresql chunked <1GB – – – ✓ ✓ ✓
17 05:40 UTC passed 2.26s postgresql chunked <1GB – – – – ✓ ✓
18 05:08 UTC passed 2.18s postgresql chunked <1GB – – – ✓ ✓ ✓
19 05:08 UTC passed 1.073s postgresql chunked <1GB – – – ✓ ✓ ✓
20 05:04 UTC passed 2.207s postgresql blob <1GB – – – – ✓ ✓
21 18:06 UTC passed 2.201s postgresql chunked <1GB – – – ✓ ✓ ✓
22 15:31 UTC passed 0.357s mysql blob <1GB – – – ✓ ✓ ✓
23 15:31 UTC passed 0.658s mysql blob <1GB – – – ✓ ✓ ✓
24 15:31 UTC passed 9.732s mysql blob <1GB – – – ✓ ✓ ✓
25 05:40 UTC passed 2.146s postgresql chunked <1GB – – – – ✓ ✓
26 05:08 UTC passed 1.008s postgresql chunked <1GB – – – ✓ ✓ ✓
27 05:08 UTC passed 2.149s postgresql chunked <1GB – – – ✓ ✓ ✓
28 05:04 UTC passed 1.983s postgresql blob <1GB – – – – ✓ ✓
29 22:06 UTC passed 2.089s postgresql chunked <1GB – – – ✓ ✓ ✓
30 06:45 UTC passed 0.358s mysql blob <1GB – – – ✓ ✓ ✓
31 06:45 UTC passed 0.698s mysql blob <1GB – – – ✓ ✓ ✓
32 06:45 UTC passed 9.07s mysql blob <1GB – – – ✓ ✓ ✓
33 05:40 UTC passed 2.165s postgresql chunked <1GB – – – – ✓ ✓
34 05:08 UTC passed 0.878s postgresql chunked <1GB – – – ✓ ✓ ✓
35 05:08 UTC passed 2.223s postgresql chunked <1GB – – – ✓ ✓ ✓
36 05:04 UTC passed 2.211s postgresql blob <1GB – – – – ✓ ✓
37 01:06 UTC passed 2.14s postgresql chunked <1GB – – – ✓ ✓ ✓
38 06:45 UTC passed 0.291s mysql blob <1GB – – – ✓ ✓ ✓
39 06:45 UTC passed 0.752s mysql blob <1GB – – – ✓ ✓ ✓
40 06:45 UTC passed 10.147s mysql blob <1GB – – – ✓ ✓ ✓
41 05:40 UTC passed 2.206s postgresql chunked <1GB – – – – ✓ ✓
42 05:08 UTC passed 0.944s postgresql chunked <1GB – – – ✓ ✓ ✓
43 05:08 UTC passed 2.127s postgresql chunked <1GB – – – ✓ ✓ ✓
44 05:06 UTC passed 2.149s postgresql chunked <1GB – – – ✓ ✓ ✓
45 05:04 UTC failed 1.498s postgresql blob <1GB – – – – – –
46 05:03 UTC passed 0.954s postgresql chunked <1GB – – – ✓ ✓ ✓
47 05:03 UTC passed 2.142s postgresql chunked <1GB – – – ✓ ✓ ✓
48 05:02 UTC passed 2.076s postgresql blob <1GB – – – – ✓ ✓
49 11:07 UTC passed 2.269s postgresql chunked <1GB – – – ✓ ✓ ✓
50 06:45 UTC passed 9.584s mysql blob <1GB – – – ✓ ✓ ✓
51 06:45 UTC passed 0.333s mysql blob <1GB – – – ✓ ✓ ✓
52 06:45 UTC passed 0.565s mysql blob <1GB – – – ✓ ✓ ✓
53 05:40 UTC passed 2.227s postgresql chunked <1GB – – – – ✓ ✓
54 05:03 UTC passed 2.138s postgresql chunked <1GB – – – ✓ ✓ ✓
55 05:03 UTC passed 0.915s postgresql chunked <1GB – – – ✓ ✓ ✓
56 05:02 UTC passed 2.112s postgresql blob <1GB – – – – ✓ ✓
57 14:07 UTC passed 2.128s postgresql chunked <1GB – – – ✓ ✓ ✓
58 06:45 UTC passed 0.308s mysql blob <1GB – – – ✓ ✓ ✓
59 06:45 UTC passed 0.716s mysql blob <1GB – – – ✓ ✓ ✓
60 06:45 UTC passed 9.384s mysql blob <1GB – – – ✓ ✓ ✓
61 05:40 UTC passed 2.028s postgresql chunked <1GB – – – – ✓ ✓
62 05:03 UTC passed 1.004s postgresql chunked <1GB – – – ✓ ✓ ✓
63 05:03 UTC passed 2.133s postgresql chunked <1GB – – – ✓ ✓ ✓
64 05:02 UTC passed 2.238s postgresql blob <1GB – – – – ✓ ✓
65 18:07 UTC passed 2.158s postgresql chunked <1GB – – – ✓ ✓ ✓
66 06:45 UTC passed 0.328s mysql blob <1GB – – – ✓ ✓ ✓
67 06:45 UTC passed 0.624s mysql blob <1GB – – – ✓ ✓ ✓
68 06:45 UTC passed 9.59s mysql blob <1GB – – – ✓ ✓ ✓
69 05:40 UTC passed 2.051s postgresql chunked <1GB – – – – ✓ ✓
70 05:03 UTC passed 0.972s postgresql chunked <1GB – – – ✓ ✓ ✓
71 05:03 UTC passed 2.13s postgresql chunked <1GB – – – ✓ ✓ ✓
72 05:02 UTC passed 2.015s postgresql blob <1GB – – – – ✓ ✓
73 22:07 UTC passed 2.124s postgresql chunked <1GB – – – ✓ ✓ ✓
74 06:45 UTC passed 0.339s mysql blob <1GB – – – ✓ ✓ ✓
75 06:45 UTC passed 0.736s mysql blob <1GB – – – ✓ ✓ ✓
76 06:45 UTC passed 9.735s mysql blob <1GB – – – ✓ ✓ ✓
77 05:40 UTC passed 2.191s postgresql chunked <1GB – – – – ✓ ✓
78 05:03 UTC passed 1.008s postgresql chunked <1GB – – – ✓ ✓ ✓
79 05:03 UTC passed 2.08s postgresql chunked <1GB – – – ✓ ✓ ✓
80 05:02 UTC passed 2.032s postgresql blob <1GB – – – – ✓ ✓
81 02:07 UTC passed 2.026s postgresql chunked <1GB – – – ✓ ✓ ✓
82 06:45 UTC passed 0.654s mysql blob <1GB – – – ✓ ✓ ✓
83 06:45 UTC passed 9.588s mysql blob <1GB – – – ✓ ✓ ✓
84 06:45 UTC passed 0.311s mysql blob <1GB – – – ✓ ✓ ✓
85 05:40 UTC passed 2.046s postgresql chunked <1GB – – – – ✓ ✓
86 05:07 UTC passed 2.646s postgresql chunked <1GB – – – ✓ ✓ ✓
87 05:03 UTC passed 0.925s postgresql chunked <1GB – – – ✓ ✓ ✓
88 05:03 UTC passed 2.08s postgresql chunked <1GB – – – ✓ ✓ ✓
89 05:02 UTC passed 2.627s postgresql blob <1GB – – – – ✓ ✓
90 17:03 UTC passed 2.33s postgresql blob <1GB – – – – ✓ ✓
91 16:07 UTC passed 2.778s postgresql chunked <1GB – – – ✓ ✓ ✓
92 05:40 UTC passed 2.076s postgresql chunked <1GB – – – – ✓ ✓
93 05:24 UTC passed 0.885s postgresql chunked <1GB – – – ✓ ✓ ✓
94 05:24 UTC passed 2.104s postgresql chunked <1GB – – – ✓ ✓ ✓
95 20:07 UTC passed 2.866s postgresql chunked <1GB – – – ✓ ✓ ✓
96 17:03 UTC passed 2.722s postgresql blob <1GB – – – – ✓ ✓
97 13:07 UTC passed 0.715s mysql blob <1GB – – – ✓ ✓ ✓
98 13:07 UTC passed 9.653s mysql blob <1GB – – – ✓ ✓ ✓
99 13:07 UTC passed 0.278s mysql blob <1GB – – – ✓ ✓ ✓
100 05:40 UTC passed 2.05s postgresql chunked <1GB – – – – ✓ ✓
101 05:24 UTC passed 2.092s postgresql chunked <1GB – – – ✓ ✓ ✓
102 05:23 UTC passed 0.879s postgresql chunked <1GB – – – ✓ ✓ ✓
103 23:07 UTC passed 2.781s postgresql chunked <1GB – – – ✓ ✓ ✓
104 17:03 UTC passed 2.634s postgresql blob <1GB – – – – ✓ ✓
105 13:07 UTC passed 9.241s mysql blob <1GB – – – ✓ ✓ ✓
106 13:07 UTC passed 0.304s mysql blob <1GB – – – ✓ ✓ ✓
107 13:07 UTC passed 0.692s mysql blob <1GB – – – ✓ ✓ ✓
108 05:40 UTC passed 2.058s postgresql chunked <1GB – – – – ✓ ✓
109 05:24 UTC passed 0.889s postgresql chunked <1GB – – – ✓ ✓ ✓
110 05:24 UTC passed 1.992s postgresql chunked <1GB – – – ✓ ✓ ✓
111 02:07 UTC passed 2.798s postgresql chunked <1GB – – – ✓ ✓ ✓
112 17:03 UTC passed 2.476s postgresql blob <1GB – – – – ✓ ✓
113 13:07 UTC passed 0.636s mysql blob <1GB – – – ✓ ✓ ✓
114 13:07 UTC passed 9.245s mysql blob <1GB – – – ✓ ✓ ✓
115 13:07 UTC passed 0.381s mysql blob <1GB – – – ✓ ✓ ✓
116 06:07 UTC passed 2.839s postgresql chunked <1GB – – – ✓ ✓ ✓
117 05:40 UTC passed 2.161s postgresql chunked <1GB – – – – ✓ ✓
118 05:24 UTC passed 1.967s postgresql chunked <1GB – – – ✓ ✓ ✓
119 05:24 UTC passed 0.883s postgresql chunked <1GB – – – ✓ ✓ ✓
120 17:03 UTC passed 2.452s postgresql blob <1GB – – – – ✓ ✓
121 13:07 UTC passed 0.281s mysql blob <1GB – – – ✓ ✓ ✓
122 13:07 UTC passed 0.598s mysql blob <1GB – – – ✓ ✓ ✓
123 13:07 UTC passed 9.541s mysql blob <1GB – – – ✓ ✓ ✓
124 09:07 UTC passed 2.813s postgresql chunked <1GB – – – ✓ ✓ ✓
125 05:40 UTC passed 2.103s postgresql chunked <1GB – – – – ✓ ✓
126 05:24 UTC passed 2.143s postgresql chunked <1GB – – – ✓ ✓ ✓
127 05:23 UTC passed 0.892s postgresql chunked <1GB – – – ✓ ✓ ✓
128 17:07 UTC passed 0.97s postgresql chunked <1GB – – – ✓ ✓ ✓
129 17:07 UTC passed 2.188s postgresql chunked <1GB – – – ✓ ✓ ✓
130 17:03 UTC passed 2.509s postgresql blob <1GB – – – – ✓ ✓
131 13:07 UTC passed 2.63s postgresql chunked <1GB – – – ✓ ✓ ✓
132 13:07 UTC passed 8.999s mysql blob <1GB – – – ✓ ✓ ✓
133 13:07 UTC passed 0.38s mysql blob <1GB – – – ✓ ✓ ✓
134 13:07 UTC passed 0.755s mysql blob <1GB – – – ✓ ✓ ✓
135 05:40 UTC passed 2.107s postgresql chunked <1GB – – – – ✓ ✓
136 17:07 UTC passed 0.875s postgresql chunked <1GB – – – ✓ ✓ ✓
137 17:07 UTC passed 2.055s postgresql chunked <1GB – – – ✓ ✓ ✓
138 17:07 UTC passed 2.961s postgresql chunked <1GB – – – ✓ ✓ ✓
139 17:03 UTC passed 2.845s postgresql blob <1GB – – – – ✓ ✓
140 13:07 UTC passed 9.281s mysql blob <1GB – – – ✓ ✓ ✓
141 13:07 UTC passed 0.352s mysql blob <1GB – – – ✓ ✓ ✓
142 13:07 UTC passed 0.611s mysql blob <1GB – – – ✓ ✓ ✓
143 13:04 UTC passed 2.381s postgresql blob <1GB – – – – ✓ ✓
144 05:40 UTC passed 2.043s postgresql chunked <1GB – – – – ✓ ✓
145 22:06 UTC passed 2.672s postgresql chunked <1GB – – – ✓ ✓ ✓
146 18:53 UTC passed 0.931s postgresql chunked <1GB – – – ✓ ✓ ✓
147 18:53 UTC passed 2.106s postgresql chunked <1GB – – – ✓ ✓ ✓
148 13:07 UTC passed 0.692s mysql blob <1GB – – – ✓ ✓ ✓
149 13:07 UTC passed 9.575s mysql blob <1GB – – – ✓ ✓ ✓
150 13:07 UTC passed 0.301s mysql blob <1GB – – – ✓ ✓ ✓
151 13:04 UTC passed 2.758s postgresql blob <1GB – – – – ✓ ✓
152 05:40 UTC failed 0s postgresql chunked <1GB – – – – – –
153 01:06 UTC passed 2.815s postgresql chunked <1GB – – – ✓ ✓ ✓
154 18:53 UTC passed 0.911s postgresql chunked <1GB – – – ✓ ✓ ✓
155 18:53 UTC passed 2.063s postgresql chunked <1GB – – – ✓ ✓ ✓
156 13:07 UTC passed 9.138s mysql blob <1GB – – – ✓ ✓ ✓
157 13:07 UTC passed 0.242s mysql blob <1GB – – – ✓ ✓ ✓
158 13:07 UTC passed 0.695s mysql blob <1GB – – – ✓ ✓ ✓
159 13:04 UTC passed 2.552s postgresql blob <1GB – – – – ✓ ✓
160 05:40 UTC passed 2.059s postgresql chunked <1GB – – – – ✓ ✓
161 05:06 UTC passed 2.863s postgresql chunked <1GB – – – ✓ ✓ ✓
162 18:53 UTC passed 0.926s postgresql chunked <1GB – – – ✓ ✓ ✓
163 18:53 UTC passed 2.02s postgresql chunked <1GB – – – ✓ ✓ ✓
164 13:07 UTC passed 0.618s mysql blob <1GB – – – ✓ ✓ ✓
165 13:07 UTC passed 9.122s mysql blob <1GB – – – ✓ ✓ ✓
166 13:07 UTC passed 0.359s mysql blob <1GB – – – ✓ ✓ ✓
167 13:04 UTC passed 2.507s postgresql blob <1GB – – – – ✓ ✓
168 09:06 UTC passed 2.789s postgresql chunked <1GB – – – ✓ ✓ ✓
169 05:40 UTC passed 1.948s postgresql chunked <1GB – – – – ✓ ✓
170 18:53 UTC passed 0.981s postgresql chunked <1GB – – – ✓ ✓ ✓
171 18:53 UTC passed 1.978s postgresql chunked <1GB – – – ✓ ✓ ✓
172 13:07 UTC passed 9.957s mysql blob <1GB – – – ✓ ✓ ✓
173 13:07 UTC passed 0.338s mysql blob <1GB – – – ✓ ✓ ✓
174 13:07 UTC passed 0.67s mysql blob <1GB – – – ✓ ✓ ✓
175 13:04 UTC passed 2.757s postgresql blob <1GB – – – – ✓ ✓
176 12:06 UTC passed 2.746s postgresql chunked <1GB – – – ✓ ✓ ✓
177 05:40 UTC passed 2.051s postgresql chunked <1GB – – – – ✓ ✓
178 05:26 UTC passed 0.317s mysql blob <1GB – – – ✓ ✓ ✓
179 05:26 UTC passed 0.657s mysql blob <1GB – – – ✓ ✓ ✓
180 05:26 UTC passed 8.522s mysql blob <1GB – – – ✓ ✓ ✓
181 18:53 UTC passed 0.887s postgresql chunked <1GB – – – ✓ ✓ ✓
182 18:53 UTC passed 1.916s postgresql chunked <1GB – – – ✓ ✓ ✓
183 16:06 UTC passed 2.962s postgresql chunked <1GB – – – ✓ ✓ ✓
184 05:40 UTC passed 2.009s postgresql chunked <1GB – – – – ✓ ✓
185 05:26 UTC passed 0.259s mysql blob <1GB – – – ✓ ✓ ✓
186 05:26 UTC passed 0.66s mysql blob <1GB – – – ✓ ✓ ✓
187 05:26 UTC passed 9.49s mysql blob <1GB – – – ✓ ✓ ✓
188 20:06 UTC passed 2.805s postgresql chunked <1GB – – – ✓ ✓ ✓
189 18:53 UTC passed 0.922s postgresql chunked <1GB – – – ✓ ✓ ✓
190 18:53 UTC passed 1.906s postgresql chunked <1GB – – – ✓ ✓ ✓
191 05:40 UTC passed 1.992s postgresql chunked <1GB – – – – ✓ ✓
192 05:26 UTC passed 0.375s mysql blob <1GB – – – ✓ ✓ ✓
193 05:26 UTC passed 0.668s mysql blob <1GB – – – ✓ ✓ ✓
194 05:26 UTC passed 9.669s mysql blob <1GB – – – ✓ ✓ ✓
195 00:06 UTC passed 3.039s postgresql chunked <1GB – – – ✓ ✓ ✓
196 18:53 UTC passed 0.946s postgresql chunked <1GB – – – ✓ ✓ ✓
197 18:53 UTC passed 1.807s postgresql chunked <1GB – – – ✓ ✓ ✓
198 05:40 UTC passed 1.932s postgresql chunked <1GB – – – – ✓ ✓
199 05:26 UTC passed 0.333s mysql blob <1GB – – – ✓ ✓ ✓
200 05:26 UTC passed 0.677s mysql blob <1GB – – – ✓ ✓ ✓

For small self-managed database setups. Not for every database stack.

Fits

  • You run a small self-managed PostgreSQL, MySQL, or MariaDB setup, typically 1 to 10 databases.
  • A daily backup on Solo and Starter — or hourly from Business — is sufficient for your setup.
  • You need restore evidence but do not have an internal backup-ops team.
  • You need restore evidence you can explain internally or to customers.

Requires

  • A reachable Linux host where the Resistro Cloud agent can run.
  • A customer-held encryption key that you store and protect yourself.
  • Operator-assisted restore handling instead of a self-service restore portal.

Not for

  • You need hard uptime/support guarantees, service credits, or a fixed restore time.
  • You need hosted or managed database support (managed MySQL/MariaDB, RDS, Supabase), or fully automated self-service restore.

Unsure? Read the trust model · too serious for self-serve? Mandate at renz-it-consult.de.

Agent alone not enough? Setup sprint and drill as a mandate — fixed scope, fixed price: renz-it-consult.de.

Promise summary

What Resistro promises today

Backup baseline

Agent-based baseline

Software, agent attachment, and monitoring instead of a managed-retainer promise.

Database baseline

Daily backups on Solo and Starter, hourly from Business. The agent asks for work on a 1h default interval on every plan; the plan decides how often a backup is actually taken.

MySQL/MariaDB

The shared engine supports MySQL and MariaDB including PITR (binlog replay) — on the same footing as PostgreSQL, measured in the engine and in Cloud.

Restore evidence

PITR boundary

PITR is proven — WAL streaming for PostgreSQL (verified E2E on staging) and binlog replay for MySQL/MariaDB (measured in a test harness) — but it is not a current product promise, not a continuous guarantee, and not a hard RTO/RPO commitment.

Restore tests

Restore tests as ongoing operating checks for the defined restore path.

Restore drills

Customer-triggered drills with restore-evidence PDF and operator-assisted result handling.

Security & storage

Zero knowledge

AES-256-GCM client-side before upload; the server receives only a SHA-256 hash of the key, never the key or plaintext data.

Default storage path

Hetzner data centers in Germany/EU; backups are stored encrypted. Roles, subprocessors, and transfers are reviewed in the privacy/AVV package.

Monitoring

Stale backup

Alerting after roughly one day; current monitor threshold: 28h.

Health smoke

Daily `/healthz` smoke test for public product paths.

Roadmap

What is deliberately not promised yet

This item is intentionally marked as roadmap. It is not part of today's operating promise, but it shows which procurement question Resistro needs to close next.

Roadmap

SOC 2 Type II

SOC 2 Type II is the evidence enterprise and regulated buyers expect for continuously operated controls. Resistro treats SOC 2 Type II as roadmap, not as an existing certification.

FAQ

Hard questions, narrow answers

Who is Resistro Cloud for?

Resistro Cloud is for small self-managed PostgreSQL, MySQL, or MariaDB setups, typically 1 to 10 databases: solo developers, small agencies, and small SaaS teams on their own Linux host. A daily backup on Solo or Starter — or hourly from Business — is enough, restore evidence matters, and there is no internal backup-ops team.

What is explicitly covered today?

A database backup baseline with a plan-based cadence — daily on Solo and Starter, hourly from Business — AES-GCM encryption, customer-held keys, default storage through Hetzner data centers in Germany/EU, a daily restore-path check, stale-backup alerting after roughly one day with a current 28h monitor threshold, and a daily `/healthz` smoke test. PostgreSQL, MySQL, and MariaDB share the same engine-level backup, restore, and PITR paths in Cloud.

Does the daily restore test mean my specific database is fully validated every day?

No. The daily restore test is an operating check of the defined restore path. It ensures the restore mechanism does not silently break, but it does not mean every customer database is individually validated every day in a full emergency scenario.

Is point-in-time recovery available?

PITR is proven but not a current product promise in Cloud. PostgreSQL WAL-streaming PITR is verified end-to-end on staging; MySQL/MariaDB binlog-replay PITR is measured in a test harness (archiver over 10 minutes plus a successful restore). There is no continuous PITR guarantee, no real-size claim, and no hard RTO/RPO.

Why is Hetzner EU different from AWS Frankfurt?

Storage location is not the whole jurisdiction question. The default storage path uses Hetzner data centers in Germany/EU; backups are stored encrypted. AVV/TOMs, subprocessors, and third-country transfers need to be reviewed in the privacy package before customer use. This is not legal advice and not a promise about authority-access or third-country-transfer risks.

What is the target RPO?

It follows the plan: around one day on Solo and Starter, around one hour from Business. The agent asks for backup work on a 1h default interval on every plan, but the active plan decides how often a backup is accepted. The target is derived from that cadence and is not a hard guarantee.

How does restore work?

Restore is manual and operator-assisted. There is no self-service button. Customers can trigger restore drills on demand to verify the restore path and download a restore-evidence PDF.

What does the restore-evidence PDF show?

The restore-evidence PDF documents the time, scope, and result of a concrete restore drill. It is structured evidence for the tested restore path, not a legal certification and not a compliance certificate.

Is there a support guarantee or a fixed restore time?

No. There is no support guarantee, uptime guarantee, service-credit model, or fixed RTO commitment.

How does Resistro detect backup failure?

Resistro uses heartbeat- and Prometheus-based monitoring. The current stale-backup alert threshold is 28 hours without a successful backup signal.

What does customer-held key mean in practice?

Backup data is encrypted with AES-GCM and the key stays on the customer side. That is the entire promise, including no key recovery if the customer loses the key.

Which setups are outside the intended scope?

Hosted or managed database platforms such as managed MySQL/MariaDB, RDS, or Supabase, and requirements outside the defined small self-managed ICP. Self-managed PostgreSQL, MySQL, and MariaDB are all first-class engine paths in Cloud.

Does the daily `/healthz` smoke test mean full platform monitoring?

No. It verifies basic reachability of central public product paths, not a full uptime or end-to-end guarantee.

Why is the communication so narrow?

Because Resistro Cloud sells only what can be narrowly evidenced today: bounded promises, restore verification, and explicit limits instead of broad security rhetoric or implied guarantees.

Is Enterprise a different engine?

No. Same resistro engine. Different operating mode: the management console and the backups run on your own infrastructure instead of ours. The console is deliberately a subset of the CLI: it triggers backup, restore test, drill, PITR restore, retention changes, and key management, and is read-only otherwise.

Does Enterprise replace Cloud?

No. Cloud remains the SaaS path. Enterprise is for teams who want to run the management console themselves and cannot or do not want to put backups into the SaaS store.

Your first passed restore drill, in 28 days.

28-day Cloud trial, no card required: connect the agent, let a backup run, trigger a restore drill. You'll end up with dated evidence — target, result, PDF — or find out your old backup theater doesn't hold. Fits self-managed PostgreSQL, MySQL, or MariaDB setups, typically 1 to 10 databases; not managed-DB platforms with a hard uptime/support SLA.