Use the Rindle Cloud dashboard to inspect deployment status, change between SQL and Sync plans, or reactivate a suspended database. The dashboard distinguishes the requested deployment from the processes currently running.
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, or the Postgres gateway-and-follower preview shape.
- 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, Sync, or Postgres preview plan and its quote.
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 |
|---|---|
| SQL | HCTree master |
| Sync | HCTree master + one read follower |
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.
A Postgres-sourced app cannot switch to SQL or Sync, and an existing SQL or Sync app cannot switch to Postgres. That would change the write authority. Create a separate app for that integration; changing the plan does not migrate its data. A Postgres app can update its source settings within the preview recovery rules.
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
The dashboard quotes the selected plan and its billing terms. Review those terms when changing plans or reactivating an app. Resource topology and application connection settings are documented separately here.
What scaling means today
Rindle’s engine supports one HCTree master feeding multiple read followers, but Rindle Cloud exposes fixed SQL and Sync shapes plus a Postgres source preview. The Postgres preview uses a gateway in place of the Rindle write master. Managed regional placement and a multi-follower fleet are not dashboard controls.
The current SQL and Sync plans use the same application URL and connection options.
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.