I'm building Insculpt — an all-in-one workspace (visual builder + CMS + automation + design + AI generation) targeting a beta this November. Sharing a few of the technical decisions in case they're useful to anyone building something similar:
One schema, two consumers — the live editor preview and the server-side publish compile step use the exact same component definitions, so there's no editor-to-published drift.
Diff-only manifest storage — only diffs from component defaults are stored, across six maps (instances, props, styles, presets, breakpoints, tokens). Keeps autosave payloads and AI generation costs down.
Hard compile boundary — published output is compiled server-side inside a Queue consumer Worker. Client-side compilation is fine for editor preview, but never for publish — letting the browser compile untrusted HTML into stored output is a real injection risk.
Stack: Next.js, Hono on Cloudflare Workers, Neon Postgres, Cloudflare R2/KV/Queues, all picked to stay cheap at low usage.
Studio (visual builder) is ~80% done and paused while I finish Content (the CMS). Currently targeting a November beta. Waitlist's open if anyone wants to follow along or get early access: Click Here
Top comments (0)