Building RedwoodSDK in the open and shipping for real‑world teams

We built RedwoodSDK, and we ship with it

RedwoodSDK is our Cloudflare‑first framework for building fast, secure, developer‑friendly apps. We build it in the open — and we prove it in production on real systems.

On recent engagements, we’ve shipped multi‑tenant, mission‑critical apps on Cloudflare Workers using RWSDK’s routing model, interruptor‑based permissions, and a clean split between admin and end‑user surfaces.

Go PRZM: Tow‑to‑claim platform on Cloudflare (in progress)

We’re building this with the Go PRZM team, using RedwoodSDK.

• A towing/insurer platform spanning dispatch to release with auditable, end‑to‑end trails.
• Digital dispatching, police rotation, impound management, and time‑tracking/billing in one place.
• Insurer flows from FNOL to valuation and sale, with real‑time visibility while vehicles remain in‑facility.
• AI‑assisted damage review and valuation inputs to speed decisions.
• RedwoodSDK under the hood: route‑level interruptors for auth/roles/permissions, admin/app split for bundle isolation, Hyperdrive for external MySQL, and R2 for images/video — all deployed via a deterministic CI/CD pipeline.

Why Cloudflare + RedwoodSDK

• Performance by default: Global edge execution keeps P95s low without extra ops.
• Security built‑in: Route‑level interruptors (auth, roles, permissions) guard access at the router.
• Operational simplicity: No servers to babysit. Use Workers, Hyperdrive for external DBs, and R2 for object storage.
• Great DX: A clear router, layered layouts, and typed contexts make teams faster and code easier to review.

What we’ve been shipping

• Two‑surface apps: Dedicated admin and app shells, each with its own Document and Layout for clean UX and bundle isolation.
• Route‑level authorization: Interruptors for requireAuth, requireAdmin, and fine‑grained requirePermission.
• Cloudflare‑native data: External MySQL via Hyperdrive; asset storage on R2; secure, environment‑scoped bindings.
• Repeatable environments: Migrations and idempotent seeding for dev/CI; deterministic builds and deploys.
• Confidence via tests: Playwright E2E coverage for routing, permissions, and critical user journeys.

What RedwoodSDK brings

• First‑class routing: render → layout → route/prefix composition with typed ctx.
• Interruptors: Small async functions that can short‑circuit requests for auth, permissions, and feature flags.
• Layouts & Documents: Layered UI shells per surface (e.g., admin vs app) without cross‑polluting bundles.
• Cloudflare ergonomics: Works seamlessly with Workers, R2, Hyperdrive, and wrangler multi‑env deployments.

Consulting with the RedwoodSDK team

We supplement framework work with consulting for teams that want Cloudflare‑native results, fast.

• Greenfield builds: Design and deliver production apps on Workers (admin + app, edge caching, secure routing).
• Migrations: Move from legacy stacks to Workers, preserving correctness and improving performance.
• Performance & hardening: Latency audits, permission model reviews, and secure bindings/secret hygiene.
• Enablement: Pair with your team, establish patterns, and leave you with a maintainable codebase.

Work with the team behind RedwoodSDK; we apply these patterns in your codebase and feed improvements back into the framework.

Let’s work together

Have a project you want to run on Cloudflare with RedwoodSDK? We can help:

• Architecture and design sprints
• Implementation and delivery
• Audits, performance tuning, and training

Get in touch: peter@redwoodjs.com