Product updates, in plain language. Follow along from the dashboard or watch the public repo.
The docs are now a real multi-page reference — every topic at its own URL, instant search, and a set of deep-dives that take you from zero to a deployed app without reading Worker source.
/ for instant search across every page; copy buttons on all code blocksRebuild the auth Worker byte-for-byte and confirm what's deployed in your account matches the published source — in one command. The closed dashboard orchestrates; the auth Worker you run is verifiable.
npx @flarelink/verify checks your live deploymentBind auth.yourdomain.com to your auth Worker from the dashboard. TLS issues automatically, no DNS dance, no Worker redeploy — the workers.dev URL stays as a fallback.
provisioning… to active when the cert landsThe full v0.2 surface of @flarelink/client is live. flarelink.from(...) and flarelink.sql\`...\` ship today — every interpolated value is automatically bound, every identifier validated on both ends.
.select / .where / .orderBy / .limit / .offset / .insert / .update / .deleteINVALID_IDENTIFIER, D1_QUERY_FAILED, etc.SDK v0.2 storage methods are wired straight to four routes on your auth Worker. Per-project service keys gate every call — Flarelink keeps only a SHA-256 hash.
storage.from(bucket).createSignedUploadUrl / createSignedDownloadUrl / remove / listThe wizard now provisions everything atomically — D1, KV, auth Worker, R2 keypair, service key — under one orchestration with rollback on any partial failure. No more half-provisioned projects.
Bundle auth Worker + R2 keypair + attached D1s under a customer-named project. Two projects on the same Cloudflare account get fully independent module sets.
Two big surfaces landed together. The R2 dashboard is end-to-end — credentials, buckets, files. The SQL editor learned tabs, saved snippets, and bind-param inputs.
? placeholders surface as inputs.sql file for portabilityThe customer-facing auth Worker, bundled and uploaded to your account. Sessions in KV (cost pattern 1), users in D1, OAuth + magic links + verification all wired. Configurable email module — pick Cloudflare Email Sending or Resend.
baseURL from request URL so custom domains "just work"Cleanup ahead of v0.1. Rotate-token UI for connections. PBKDF2 instead of scrypt for dashboard auth (fits the Workers free-plan CPU budget). Diagnostic + recovery scripts for the messy edge cases we hit during R2 onboarding.