Modern site stacks split design, content, media, forms, and hosting across multiple vendors; Instatic collapses that surface into one Bun server so the published site is mostly plain HTML and compact CSS. That matters because it removes runtime baggage from public pages while keeping a full-featured visual editor and content model under the owner's control.
What Sets It Apart
- Single-server approach: the admin, editor and publisher all run in one Bun process; published pages are baked to disk as static files and served with minimal runtime.
- Design-first editing: a real canvas with reusable Visual Components, templates, loops and Core Framework tokens so design tokens drive the entire site, not ad-hoc classes.
- Plugin sandboxing and safety: plugins run inside a QuickJS‑WASM sandbox with owner-granted permissions (no network or FS by default), reducing the risk of hostile plugins.
- Provider-agnostic AI integration: an AI agent can manipulate the canvas as real nodes; drivers talk to LLMs over HTTP/SSE (Claude, OpenAI, OpenRouter, local Ollama or others you supply) without vendor SDKs.
- Practical defaults for hosting: SQLite by default, Postgres for teams, one-click Railway deploy templates, and a single Docker image for self-hosting.
Who It's For — Trade-offs
Great fit if you want a self-hosted, design-driven CMS that produces clean, framework-free public pages and prefer control over relying on multiple third-party services. It’s useful for blogs, portfolios, small businesses, and teams that value readable output and local data ownership. Look elsewhere if you need a mature plugin marketplace, enterprise analytics today (first-party analytics are on the roadmap), or if you cannot run Bun in your environment. Expect opinionated architecture (TypeScript + Bun + React admin) and a pre-1.0 codebase where APIs and workflows may still evolve.
