Iterating With Guardrails
w/handoff provides isolated sandbox environments where clients and stakeholders can safely iterate on features, styling, and copy without risking production or slowing down developer velocity.
Database & Backend Environments
Setting up a sandbox shouldn't mean exposing your production systems or messing up database schemas. w/handoff offers secure, clean environment configurations for backend and database stacks.
Connect client sandboxes securely to staging databases and backends using isolated environment variables. Schema guardrail hooks (similar to Claude Code) intercept database operations to block any destructive migrations or edits instantly.
Ephemeral Sandbox Lifecycle
All iteration sessions execute inside ephemeral, isolated sandboxes hosted on Cloudflare's serverless containers.
1. Request Subdomain Ingress
A client or stakeholder visits your project URL (e.g., client-a.withhandoff.com). Cloudflare DNS routes the incoming traffic to the central Orchestrator Worker at the edge.
GET https://client-a.withhandoff.com/ Host: client-a.withhandoff.com User-Agent: Client Browser Status: Ingress Handshake OK
How Handoff Works Under the Hood
Behind the sandboxed client interface lies a secure build pipeline designed to ensure code safety and developer control.
Developer Guardrails
Every edit submitted by the client is verified inside the isolated build container. If it breaks TypeScript definitions, fails linting, or violates config limits, the build is blocked.
Formal Code Review
When iterations exceed simple styling adjustments, the handoff protocol packages the changes as a standard Git pull request. You review the code directly in your GitHub flow.