Getting started
backlex Cloud is the hosted control plane — it provisions, bills, and operates your backlex project instances. Create an org, spin up a project, ship in ~30 seconds.
backlex Cloud is the hosted control plane at cloud.backlex.com. It manages the things that sit around your data: organizations, projects, regions, billing, deploy keys, the audit log, webhooks, integrations, and enterprise SSO. It provisions and bills the backlex project instances themselves — each project runs as its own isolated worker, reachable at <slug>.backlex.com.
The project’s own data plane — collections, schema, app users — is managed by the project admin that ships inside each provisioned instance, not here. Keep the two mental models separate:
| Concern | Managed in |
|---|---|
| Organization, members, billing, regions | Cloud (this control plane) |
| Projects: provisioning, domains, backups, alarms | Cloud |
| Collections, schema, app users, permissions | Project admin (inside each instance) |
1. Create an organization
Section titled “1. Create an organization”On first sign-in you’re guided through onboarding. An organization is the billing + membership boundary; every project and API key belongs to one. You pick a data residency (eu or global) — it’s fixed for the life of the org (GDPR), so choose deliberately. Residency governs where every project’s database is placed.
2. Create a project
Section titled “2. Create a project”From the dashboard, New project asks for a name and a template. The database location follows your residency — placed automatically for global orgs (with an optional location hint) or within the EU boundary for eu orgs. Cloud provisions a dedicated worker (Workers for Platforms), wires its database and storage, seeds an admin credential, and brings it live at <slug>.backlex.com — typically in under a minute. See Provisioning & lifecycle.
3. Automate it
Section titled “3. Automate it”Everything in the UI is also an API. Mint an API key, then drive the REST API or point an AI agent at the MCP server. Subscribe to webhooks or connect Slack/Datadog/GitHub to react to project events.
Members hold one role per org, checked on every write:
- owner — full control, incl. billing and deleting the org.
- admin — manage projects, members, keys, integrations, SSO.
- developer — create projects/branches/alarms; no member or billing changes.
- viewer — read-only.