The latest articles on DEV Community by Pawan Agrawal (@paw1xd). https://dev.to/paw1xd https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4059276%2F5a2125c6-9236-4340-b76f-4742c81faf69.png https://dev.to/paw1xd en Pawan Agrawal Sun, 09 Aug 2026 17:48:17 +0000 https://dev.to/paw1xd/architecture-notes-from-building-an-ai-first-no-code-app-builder-solo-2152 https://dev.to/paw1xd/architecture-notes-from-building-an-ai-first-no-code-app-builder-solo-2152 <p>I'm building <strong>Insculpt</strong> — 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:</p> <p>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.<br> 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.</p> <p>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.<br> Stack: Next.js, Hono on Cloudflare Workers, Neon Postgres, Cloudflare R2/KV/Queues, all picked to stay cheap at low usage.</p> <p>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: <a href="https://insculpt.io/?from=dev" rel="noopener noreferrer">Click Here</a></p> ai architecture softwareengineering