Skip to main content

RedwoodSDK demo

The RedwoodSDK demo renders the Openfield campaign with React Server Components and keeps checkout inside the Cloudflare Worker. One server route validates the contribution, resolves the catalog price, creates an order, and redirects to Inttegro Checkout.

About the app

This is the current Cloudflare-native RedwoodSDK, not the legacy RedwoodGraphQL stack. The demo preserves its Worker runtime instead of presenting a generic Node container as an equivalent deployment.

What it demonstrates

  • React Server Components and Web-standard request handling in RedwoodSDK
  • A Worker-held API key and application-lifetime Inttegro client
  • Trusted Product and Price lookup before Order creation
  • Bounded tiers, retry-safe idempotency, and a readable OPENFIELD-… order number
  • Safe completion, cancellation, validation, and configuration states

Run the demo

Add the API key to .dev.vars, configure the campaign Product and Price IDs, and run the Worker locally. The released README contains the exact development, type-generation, test, and production-build commands.

Follow the integration

  1. src/checkout.ts validates the tier, resolves the trusted catalog pair, and creates the order.
  2. src/worker.tsx connects the Worker route, React rendering, safe errors, and checkout redirect.

Production boundary

Openfield demonstrates immediate funding. A production service must persist contributions, consume authenticated server events, reconcile missed events, and change public totals only from verified payment state. Future pledges, escrow, organizer payouts, tax receipts, and regulatory onboarding are separate product and compliance concerns.

Continue