BaseCLF documentation
A backend you can understand before you ship.
BaseCLF assembles authentication, D1, R2 storage, instant APIs, and row-level policies into one Cloudflare-native workflow.
The commands, policy documents, and API behavior in these docs match the shipped engine: create-baseclf, baseclf policy, and the baseclf-js client are on npm. Studio opens on fixture data; connecting a deployment makes every screen read that deployment for real: Simulator, Policies, Tables, Auth, Storage, and Health. Storage shows the rules rather than the objects, because a directory belongs to a caller and Studio has no identity. Health reports the checks the deployment can run on itself; usage numbers are recorded against your Cloudflare account and are read through the local bridge, which holds your credential so the page never does.
Choose your path
| Goal | Start here | What you get |
|---|---|---|
| Launch a project | Quickstart → | Install, configure, deploy, and verify a first request. |
| Control data access | Policy DSL → | Rules, auth claims, rejection behavior, and SQL examples. |
| Check fit | Compatibility → | Supported features and deliberate caveats. |
Important boundaries
- BaseCLF runs in your Cloudflare account; it is not a hosted database service.
- Direct database access (
wrangler d1 execute, the D1 console) bypasses the policy engine by design. - Compatibility rows mirror the engine repository's README tables, which are maintained against its tests.