Rascal Pages
A website builder where the customer owns the code
Problem
Webflow and Squarespace lock customers in: you can build a site but never own it. The goal: a site product where every customer site is a real, standalone Next.js repo — while creating one stays as easy as filling a form or making a call.
Solution
Repo-per-site architecture
Every customer site is its own GitHub repo and its own Vercel project. A deliberate, ADR-documented tradeoff: the operational load of N deployments is accepted because the ownership promise requires it — handoff to the customer’s GitHub is one command.
Sites born from a conversation
An ElevenLabs voice agent runs the interview, n8n + Claude generate the site config from a 1,200-line versioned system prompt, and provisioning creates the repo, project and subdomain automatically — resolving collisions across up to 25 candidates.
A visual editor without lock-in
17 block types with dedicated editors: inline editing, drag-and-drop ordering, undo/redo, autosave and per-site design tokens. Alternatively, write content in Obsidian and push to Git.
Provisioning that survives failure
The five-step pipeline (repo → seed → Vercel project → domain → registry) checkpoints state to the database after every step. An interrupted run is left diagnosable — no orphaned repos. A dry-run mode makes the pipeline unit-testable.
Gallery
