Documentation
A working backend — auth, database, storage, email — running on your own Cloudflare account. Flarelink provisions it and gets out of the way; it never sits in your app's request path.
flarelink.from(…) builder looks familiar but the trust model is different (no row-level security yet; database + storage are server-only).Connect Cloudflare, provision a project, install @flarelink/client, ship sign-in. The shortest path from zero to a deployed app.
Sign-up, sign-in, OAuth, magic links, password reset. Browser + server safe.
A typed query builder over your D1, plus a raw-SQL escape hatch. Server-only.
Presigned R2 uploads and downloads — bytes go browser → R2 directly.
Step-by-step Google + GitHub OAuth app setup with the exact redirect URIs.
Presign on the server, upload from the browser, record the key, show it back.
Every AuthError / StorageError / DatabaseError code, with causes and fixes.
Why custom domains matter, what SameSite=None; Partitioned means, a per-browser troubleshooting matrix.
Inherited Cloudflare limits, KV eventual consistency, presign clamps, list pagination.
Framework quickstarts
Paste-able setup plus a "protect a route" recipe for each. Same SDK, same calls — only file paths and env conventions change.
Building with an AI coding agent? Point it at llms.txt (concise map) or llms-full.txt (every page inlined).