Rindle

Rindle Cloud

Cloud quickstart

Provision managed Rindle SQL or a synced Rindle backend, then connect with one URL and one server-only token.

View as Markdown

Rindle Cloud runs Rindle on a packed OVH fleet. The Cloudflare-hosted control plane owns billing, placement, DNS, and desired state. rindle-poold converges the processes on each OVH box. Every app gets one stable https://app-<id>.rindle.cloud ingress, so the physical topology never leaks into application configuration.

This page gets you from signup to a running database. Connect your app covers the SDK wiring.

1 · Sign in and add a card

Create an account at cloud.rindle.sh and add a payment method. Rindle Cloud has two fixed plans:

Plan Topology Includes Price
SQL one HCTree write master SQL, interactive transactions, migrations, streaming backup $5/month
Sync the same master plus one read follower everything in SQL, plus live queries and subscriptions $10/month

Each serving process uses a fixed 5 GB database · 1 CPU · 512 MB slot. Streaming backup is always on and included. Ingress and egress are free.

2 · Choose SQL or Sync

Choose SQL for an ordinary database used through @rindle/sql-client, Drizzle, or rindle sql. Choose Sync when the app also needs Rindle’s API server, optimistic browser client, live queries, and subscriptions.

The Sync follower runs beside the master on the selected fleet box. Managed regional placement and multi-follower read scaling are not offered yet. The deployment guide distinguishes today’s hosted menu from the larger self-hosted topology.

3 · Provision

Submit the form. The dashboard shows the app moving from provisioning to active and tracks both sides of convergence:

  • the desired version written by the control plane
  • the OVH box and process units reported by rindle-poold
  • the desired and applied fleet generations

If fleet capacity is temporarily full, the app remains queued and convergence retries automatically.

4 · Connect

Once the app is active, the Connect panel supplies exactly two values:

RINDLE_URL=https://app-<id>.rindle.cloud
RINDLE_DATABASE_TOKEN=<server-only-token>

Keep both values on the server. The one URL routes SQL and migration traffic to the HCTree master and, on the Sync plan, read, lease, and subscription traffic to the follower. Browsers call your API server and discover their public WebSocket endpoint from a query lease. They never receive the database token.

Continue with Connect your app for SQL and Sync examples.

CLI workflow

A one-follower rindle.ncl can provision the Sync plan directly:

rindle login
rindle deploy --migrate

The command waits for the managed app, stores its non-secret binding in .rindle/cloud.json, and can apply local migrations through the Cloud control plane. For a master-only SQL app, create it in the dashboard and bind the project before running remote migrations:

rindle link app_…
rindle migrate apply --cloud

Next steps