Flarelink — your backend, on your own Cloudflare

How it works

Three steps to a backend that's yours.

01

Connect your Cloudflare

Paste a scoped Cloudflare API token. Flarelink only touches resources when you explicitly ask it to provision or change one.

02

Create a project

One click provisions an auth Worker, a D1 database for your users, and a KV namespace for sessions — all in your account, with the keys shown to you once. Add R2 storage later when you need files.

03

Build and ship

Install @flarelink/client and call auth, storage, from(…) with one URL and one service key. Manage it all in one dashboard.

Everything an app backend needs

Four pieces. One honest view.

The parts you'd otherwise stitch together from four vendors — running on your own Cloudflare resources, costed transparently, managed in one place.

Au

Auth

Drop-in authentication with sessions, social providers (Google + GitHub), magic links, and email verification. User records live in your own D1 — not on a vendor you can't leave.

OAuth Magic links Sessions in KV Editable templates

Db

Database

A real SQL database on Cloudflare D1, with saved snippets, a visual table + schema editor, a multi-tab SQL console, and a type-safe client.

SQLite Saved snippets Table editor Type-safe SDK

St

Storage

Object storage on R2 with signed upload URLs and zero egress fees. Files go straight from the browser to your bucket — Flarelink stays out of the byte path.

S3-compatible Signed URLs No egress File browser

Em

Email

Send password resets, magic links, and verification through Cloudflare Email Sending or Resend. Editable templates with live previews — no second SMTP vendor to wire up.

Transactional Templates CF Email Resend

One install. Four services.

From zero to a wired backend.

One typed SDK with the same surface as the platforms you already know — auth, storage, from(…). The dashboard provisions everything in your account; the SDK speaks to it directly.

~/acme

$ npm install @flarelink/client

# 8.2 KB · zero runtime deps

✓ auth sessions · OAuth · magic links

✓ database D1 · table editor + SDK

✓ storage R2 · signed upload URLs

✓ email CF Email or Resend

ready · open the dashboard

You own it

The infrastructure is yours. We just keep it calm.

Most backend platforms rent you their servers and hope you never leave. Flarelink runs entirely on your Cloudflare account, so leaving is a non-event — which is exactly why people stay.

Your data sits in your D1 and R2 — we hold a scoped token, never a copy.

Cancel anytime and your backend keeps running. There's nothing to migrate off.

You pay Cloudflare directly for usage. Flarelink is a flat fee — no markup on egress.

FAQ

The honest answers.

How does Flarelink see my account?

You create a scoped Cloudflare API token and paste it in. Flarelink uses it to read and provision your D1, R2, Workers, KV, and Email through Cloudflare's public APIs. It only writes when you explicitly provision or change a resource in the dashboard.

Where does my data actually live?

In your own Cloudflare account. Auth users and app data go in your D1 database; files go in your R2 bucket. Flarelink stores configuration and a scoped token — never a copy of your data.

Is this an official Cloudflare product?

No. Flarelink is an independent backend platform built on Cloudflare's public APIs. We're not affiliated with or endorsed by Cloudflare.

What happens if I cancel?

Your backend keeps running — it's your infrastructure. You lose the Flarelink dashboard and SDK access, but the database, bucket, auth Worker, and email config stay exactly where they are.

Do I need all four services?

No. Use only what you need — run Flarelink just for auth, or just to manage an R2 bucket. The dashboard shows what you use and stays quiet about the rest.

Your backend, on your own Cloudflare.