The Rindle Cloud dashboard shows the desired deployment and what the packed OVH fleet has actually applied. The control plane keeps reconciling until those two states match.
Read the dashboard
- Status —
provisioning,active,suspended,deleting, ordeleted. - Topology — the SQL master-only or Sync master-plus-follower shape requested by the current desired version.
- Observed — the assigned OVH box, desired/applied fleet generations, and each process unit’s reported state.
- Connect — one
RINDLE_URLand one server-onlyRINDLE_DATABASE_TOKEN. - Plan — the current SQL or Sync SKU and monthly price.
An active app is converged when the box reports an applied generation at or beyond the desired generation. A reconcile failure remains visible and retries automatically. A capacity shortage leaves the app queued until a slot is available.
Change plans
The dashboard’s Change plan control switches the desired topology:
| Plan | Serving processes | Price |
|---|---|---|
| SQL | HCTree master | $5/month |
| Sync | HCTree master + one read follower | $10/month |
Moving SQL → Sync adds a follower, which restores the master’s current lineage and then tails its ordered journal. Moving Sync → SQL removes that follower. The app’s URL, token, master, data, and backup lineage stay the same.
Every serving process is currently a fixed 5 GB database · 1 CPU · 512 MB slot. The managed product does not currently expose CPU, RAM, volume, region, or follower-count controls. For those deployment choices, self-host the built topology.
Suspend and reactivate
A failed payment suspends the app and unschedules its serving processes without discarding its volume or backup lineage. Once billing is resolved, use Reactivate to charge the current plan and converge the processes again.
Deletion of an OVH fleet app currently requires operator action. The dashboard says so before accepting a request.
Billing
SQL is $5/month for one serving slot. Sync is $10/month because it adds a second serving slot. Streaming backup is always on and included. Ingress and egress are free. The new price from a plan switch applies at renewal.
What scaling means today
Rindle’s engine supports one HCTree master feeding multiple read followers, but Rindle Cloud intentionally exposes only two SKUs today: master-only SQL and master-plus-one- follower Sync on the packed OVH fleet. Managed regional placement and a multi-follower fleet remain future product shapes, not dashboard options.
The one application ingress means those future topology changes will not require an SDK or environment-variable migration.
Next steps
- Connect your app — use the unified managed connection.
- Deploying & scaling — current hosted and self-hosted shapes.
- Run the daemon — the read follower operated by the Sync plan.
- Is Rindle for you? — where the single-ordering-master model fits.