$0 to start4 services· 4 auto-onboard

$0 Cloudflare-Native

Simplicity-obsessed devs who want everything on one platform

Full-stack app on Cloudflare alone — one vendor, one dashboard, one bill

Cloudflare Pages hosts your static or server-rendered frontend. Workers runs your server code at the edge. D1 is your SQL database. R2 is your object storage (S3-compatible, zero egress). KV is your key-value store. All on the same platform, same dashboard, same billing. Generous free tiers across the board. Trade-off: you're fully locked into Cloudflare's runtime model (no Node.js for Workers — it's a V8 isolate), but the operational simplicity is hard to beat.

What's in the box

Every service has a transparent affiliate disclosure. Most have none.

GitHub

✓ wizard

Source control, auto-deploy to Cloudflare Pages

Free tier: Unlimited private repos
No affiliate — SPARKi earns nothing here

Cloudflare

✓ wizard

Pages (hosting) + Workers (compute) + D1 (SQL) + R2 (storage) + KV + DNS + CDN + SSL

Free tier: Pages: unlimited sites + bandwidth. Workers: 100K requests/day + 10ms CPU per request. D1: 5M row reads/day, 100K row writes/day, 5 GB storage. R2: 10 GB storage + zero egress (this is the crazy-good part). KV: 100K reads/day, 1K writes/day, 1 GB storage.
No affiliate — SPARKi earns nothing here
When to upgrade: Any individual service exceeds its free tier → Workers Paid ($5/mo for 10M requests) + per-product pricing for D1/R2/KV ↗

Sentry

✓ wizard

Error tracking (has a Workers integration)

Free tier: 5,000 errors/mo
No affiliate — SPARKi earns nothing here

Pico

✓ wizard

Uptime monitoring

Free tier: Free — SPARKi's sister project
No affiliate — Pico is SPARKi's own tool

How to set it up

4 of 4 services are onboarded automatically by SPARKi's wizard. The rest you set up by following the steps below.

  1. 1Create GitHub + Cloudflare accounts
  2. 2Copy tokens to .env: GITHUB_TOKEN, CLOUDFLARE_API_TOKEN
  3. 3Create a Cloudflare Pages project connected to your GitHub repo
  4. 4Create D1 database + R2 bucket + KV namespace via wrangler CLI
  5. 5Add providers block to sparky.config.yaml with cloudflare + github + sentry + pico
  6. 6Restart SPARKi: pm2 restart sparky --update-env
  7. 7Verify: /sparki packages setup cloudflare-native

Ready? SPARKi can onboard most of this for you.

Open SPARKi and run /sparki start cloudflare-nativefor <your-project> in a direct message. SPARKi will walk you through 4 services one at a time, verify each API key live, and write the config automatically.

Open SPARKiBrowse other packages