Insculpt

Overview

Insculpt is a schema-first, no-code/low-code visual app builder for indie developers and small SaaS teams. Every app built in Insculpt is defined as structured, versioned schema rather than generated code — which means it stays permanently editable, in the visual editor, for the life of the product. AI (via Insculpt Forge) speeds up the building process, but it’s an accelerant layered on top of the schema, not the product’s core pitch.

The Problem

Most AI app-builders generate code once and hand it off — after that, further changes mean prompting again or dropping into a codebase by hand. No-code platforms solve the editability problem but are often rigid, siloed, and slow to adopt real AI assistance. Indie builders end up choosing between “editable but limited” and “AI-fast but disposable.”

The Solution

Insculpt is built around a single idea: one schema, two consumers. The same schema package drives both the visual editor and the publish pipeline, so what you see in the builder is exactly what ships.

• Studio: A drag-and-drop visual editor with a component/property system, slot-based composition, and design-token-driven styling — no raw HTML or arbitrary CSS by default.
• Content: A structured CMS with schema-based collections, SEO fields, and localization, publishing straight into the same schema pipeline.
• Forge: A prompt-to-app engine that generates Studio and Content structures from a description — output is reviewed and stays fully editable, never a one-shot code dump.
• Flows & Canvas (roadmap): visual backend automation and a design/prototyping surface that syncs into production-ready Studio structures.

Technical Architecture

The product is a Turborepo/pnpm monorepo. The editor (apps/app) is built with Next.js, Tailwind, shadcn, and Base UI, with Zustand for editor state and dnd-kit for the canvas interactions. The API (apps/api) runs on Hono over Cloudflare Workers, backed by Drizzle ORM and Neon Postgres, with better-auth handling sessions. Published sites compile server-side — never in the browser — via Cloudflare Queues and Workers for Platforms, with assets served from R2. External API keys never touch the client; all third-party calls route through a server-side resource proxy.

+--------------------+      +--------------------+      +----------------------+
| Studio Editor      | ---> | API (Hono/Workers) | ---> | Publish Pipeline     |
| (Next.js, Zustand)  | <--- | (Drizzle/Neon)      | <--- | (Queues, R2, Workers)|
+--------------------+      +--------------------+      +----------------------+

Key Highlights & Impact

• Schema-Driven, Not Code-Generated: Apps remain fully editable in the visual builder indefinitely — no “eject and hand-code” cliff.
• Multi-Platform Foundation: Web ships first; the schema is designed to extend to mobile (React Native/Expo) and desktop (Tauri) without breaking changes.
• Solo-Built, Production-Minded: Architected with real security boundaries from day one — server-side-only compilation, a resource proxy for secrets, and optimistic-concurrency autosave — despite being built by a single founder on a constrained budget.