Implementation reference / Cloudflare Pages

Architecture

A static-first website with a small persistence layer, deployed entirely through Cloudflare Pages.

One website. Two request paths.

Astro builds HTML, CSS, JavaScript and static assets into dist/. Pages serves those assets. The application’s _routes.json includes only /api/* for Functions invocation.

File-based handlers at functions/api/early-access.ts and functions/api/remove.ts receive the form requests. Their DB binding provides direct access to D1.

Keep each layer small.

Rendering
Content is generated at build time. Reading a public page does not require a database query or a client-side application shell.
Browser behavior
TypeScript handles theme preference, navigation, scroll scenes, code copying and form submission. Native HTML submission is also supported.
Persistence
Prepared SQL statements validate persistence and deduplicate email addresses through a unique database constraint.
Secrets and accounts
Cloudflare deployment credentials stay outside browser code. Public documentation contains neither credentials nor subscriber records.

There is no separate standalone Worker application, external form provider or financial backend in this project.

Find the implementation.

Project structure
src/pages/          Static Astro routes
src/layouts/        Shared page shells
src/components/     Reusable SVG and UI components
src/content/        Product language, navigation and API contract
src/scripts/        Browser interactions
src/styles/         Themes, layout and motion
public/             Brand assets, headers and route rules
functions/api/      Pages request handlers
functions/_lib/     Validation and HTTP helpers
migrations/         D1 schema migrations
tests/              Local browser and API checks
wrangler.jsonc      Pages build output and DB binding

src/content/brand.ts owns the shared reward terminology. src/content/api.ts defines the published OpenAPI document and error-reference metadata. public/_headers defines static response headers; API response headers live in functions/_lib/http.ts.

The financial architecture is open.

No blockchain, custody provider, settlement system, purchase-data provider or legal reward instrument has been selected in the published product information. The website’s hosting architecture should not be confused with the future financial architecture.

See Tokenomics for the known status of those product decisions, and the official Cloudflare Pages Functions documentation for platform behavior.