Rindle Cloud hosts the Rindle data tier. Choose a SQL database, add live queries with Sync, or connect a PostgreSQL source through the preview integration. Your application connects through one stable URL. You deploy your browser application and API server on your chosen app host.
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. The dashboard offers these managed topologies. Review its plan quote when provisioning:
| Plan | Topology | Includes |
|---|---|---|
| SQL | one HCTree write master | SQL, interactive transactions, migrations, streaming backup |
| Sync | the same master plus one read follower | everything in SQL, plus live queries and subscriptions |
| Postgres preview | capture gateway and Rindle read follower | live queries over your PostgreSQL data; writes stay in Postgres |
Each serving process uses a fixed 5 GB database · 1 CPU · 512 MB slot. The managed topology includes streaming backup.
2 · Choose the write authority
Choose SQL for an ordinary database used through @rindle/sql-client,
Drizzle, or rindle sql. Choose Sync for live queries and subscriptions,
including server read models and synced browser apps. These two plans use Rindle
as the write authority.
Choose Postgres preview when PostgreSQL must remain authoritative. The form
collects the source connection and capture credentials; the dashboard supplies a
rindle pg prepare command for your source database. Read the
Postgres source guide before provisioning. Its type,
mutation-replay, and operational limits still apply to managed deployment.
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
as the requested processes become ready. Deployment details show the requested
configuration and the latest state reported by the host.
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. For a Postgres-sourced app, this connection supplies Rindle reads and subscriptions; writes still go to your own Postgres. 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 --migrateThe 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 --cloudNext steps
- Connect your app — use the unified URL and token.
- Scale & operate — inspect convergence, switch plans, or reactivate an app.
- Deploying & scaling — compare local, self-hosted, and managed shapes.
- SQL client — use Rindle as a fetch-native SQL database.