Edge Architecture Check

1. Deploy

Is your app deployed on Cloudflare Workers or Pages (production URL)?

Edge deploy is the baseline for this stack.

2. Deploy

Do you have a custom domain with working HTTPS (not only workers.dev)?

Customers and email auth need a real host.

3. Auth

Can a user sign in today (Magic Link and/or OAuth) on production?

No auth → no gated product.

4. Auth

Is your transactional email sending domain verified (SPF/DKIM) at your ESP?

Unverified domains block Magic Links in production.

5. Payments

Can a user start Checkout (Stripe or equivalent) from your site?

No checkout → no revenue path.

6. Payments

Do you verify payment webhooks server-side and update membership in a database?

Client-only “payment success” pages get abused.

7. Payments

Is the dashboard/downloads blocked until membership is active?

Ungated assets leak; over-gated assets break after pay.

8. Data

Do users/sessions/memberships persist in D1, Postgres, or similar?

Edge apps still need durable identity + entitlements.

9. Data

Are downloadable files served from object storage (R2/S3) behind auth?

Public bucket URLs get scraped; huge files don’t belong in git.

10. Security

Are API secrets only in Worker secrets / env — never in the client bundle?

Leaked Stripe/Auth keys end launches.

11. Ops

Can you find auth and webhook failures in logs within a few minutes?

First real user will fail in a way tutorials never show.

12. Ops

Have you rehearsed pay → email → dashboard on production with a fresh account?

If you haven’t, your first customer becomes the test.