Instatic: The Open-Source CMS That Replaces Webflow, Framer, and WordPress — 5,200+ GitHub Stars

Why Developers Are Moving Away from Traditional CMS Platforms

Building a modern website has become unnecessarily complex. You start with a headless CMS for content, add a framework for the frontend, choose a hosting provider, integrate a form service, connect analytics, set up an image CDN — and suddenly you're managing six different dashboards, paying six different bills, and debugging integration issues at 2 a.m.

This fragmentation is exactly what Instatic aims to solve. With over 5,200 GitHub stars and growing rapidly (426 new stars today alone), this open-source project is gaining traction among developers who want complete control over their websites without sacrificing the convenience of visual editing.

Instatic takes a radically different approach: everything lives in one server. The visual editor, content engine, media management, authentication, forms, plugins, and publishing system all run from a single Bun instance that you can host anywhere. And unlike many modern site builders, the pages it produces are clean, semantic HTML — no framework runtime, no builder attributes, no div soup.

What Makes Instatic Different from Webflow, Framer, and WordPress

True Self-Hosting with Zero Vendor Lock-in

Unlike Webflow and Framer, which lock you into their hosting infrastructure, Instatic is MIT-licensed and fully self-hosted. You own everything: the code, the data, the deployment. Run it on Railway, Render, your own VPS, or even a Raspberry Pi. Your site, your rules.

WordPress gets closer to this ideal, but decades of legacy code and a plugin ecosystem that often prioritizes backward compatibility over modern development practices make it feel dated. Instatic is built from the ground up with modern web standards: TypeScript, Bun (a fast JavaScript runtime), and a clean separation of concerns.

Clean Static Output

Most visual site builders embed their own JavaScript runtime into every page they publish. This creates bloat, slows down load times, and makes your site dependent on third-party scripts. Instatic takes the opposite approach: published pages are plain HTML and CSS files with no framework overhead.

When you view the source of an Instatic-published page, you see semantic HTML that's readable and maintainable. The site loads like a static file because, for the most part, it is one. This translates to faster page loads, better SEO, and easier debugging.

Integrated Design System with Core Framework

Instatic includes Core Framework, a design-token engine already used by thousands of WordPress professionals. Instead of manually managing colors, fonts, and spacing across dozens of pages, you define design tokens once and they propagate everywhere.

• Color tokens that automatically generate shade scales — define one brand color, get a complete palette
• Fluid typography that scales mathematically with viewport size
• Consistent spacing scales that maintain rhythm across breakpoints
• Utility class generator that produces lean, optimized CSS

Your entire design system lives as data. Change one token, and every page using it updates automatically.

The AI Agent That Actually Edits Your Pages

One of Instatic's most innovative features is its built-in AI agent that doesn't just generate code — it directly manipulates the canvas. Describe what you want in natural language, and the AI builds it as real, editable nodes on your page.

Unlike AI tools that dump raw HTML or screenshots, Instatic's AI writes semantic HTML for structure and CSS for style, using the same import pipeline you'd use when pasting markup. The result is fully editable within the visual editor.

The system supports multiple AI providers: Claude, OpenAI, OpenRouter, or local models via Ollama. You bring your own API key, use your preferred model, and pay only for what you use. No vendor lock-in, no surprise bills.

Two Specialized Scopes

The AI agent operates in two distinct modes:

• Site scope (35 tools): Builds entire pages, manages layouts, creates components
• Content scope (15 tools): Edits content entries, updates text, manages data

This separation ensures the AI has the right tools for each task without overwhelming it with unnecessary capabilities.

Real-World Example: Building a Portfolio Site in Under an Hour

Let's walk through a practical scenario. Sarah, a freelance designer, needs a portfolio site that showcases her work, includes a contact form, and can be updated easily. Here's how she'd use Instatic:

1. Deploy (2 minutes): Click the Railway deploy button, wait for the instance to spin up, log in with the auto-generated credentials.
2. Set up design tokens (5 minutes): Define her brand colors (primary: #2563eb, secondary: #7c3aed), choose a type scale, and set spacing values. The system generates the complete palette and utility classes.
3. Build the homepage (20 minutes): Use the AI agent to generate the hero section ("Create a hero section with a headline, subheading, and CTA button"), then manually refine the layout. Drag components for the portfolio grid, testimonials, and footer.
4. Create a project collection (10 minutes): In the Data workspace, create a "Projects" table with fields: title, description, thumbnail, category, and live URL. Add a few sample projects.
5. Set up the portfolio loop (5 minutes): Create a loop component that displays projects in a grid, pulling from the Projects collection. The loop automatically handles responsive layouts.
6. Add the contact form (5 minutes): Drag form fields onto a contact page. Instatic creates the matching database table automatically. Submissions go directly to her database — no third-party form service needed.
7. Publish (1 minute): Hit publish. The site compiles to static HTML/CSS and deploys to her custom domain.

Total time: under an hour. Total cost: Railway's free tier (or ~$5/month for a dedicated instance). No subscriptions to Webflow, no form service fees, no image CDN costs.

Key Benefits of Choosing Instatic

• Complete ownership: MIT license means you own everything — no licensing fees, no usage limits, no surprise price increases
• Single-server architecture: One Bun instance handles everything, reducing complexity and operational overhead
• Clean static output: Published pages are semantic HTML and CSS with no framework bloat, resulting in faster load times and better SEO
• Integrated AI agent: Build pages with natural language while maintaining full editability
• Flexible database options: SQLite for simple sites, Postgres for teams and complex workflows
• One-click deployment: Railway, Render, or Docker — get live in minutes, not hours
• Built-in design system: Core Framework provides professional-grade design tokens out of the box
• Secure plugin system: Plugins run in isolated QuickJS-WASM sandboxes with explicit permission grants
• Real access control: 38 granular capabilities, TOTP two-factor authentication, account lockout protection
• Self-contained forms: Form submissions go directly to your database — no third-party services required
• Command palette: ⌘K for everything — navigate and execute actions without touching the mouse
• Audit logging: Every admin action is recorded in an append-only log for accountability and debugging

Getting Started with Instatic

Option 1: One-Click Deploy (Recommended)

The fastest way to get started is Railway's one-click deploy:

1. Visit the Instatic GitHub repository
2. Click the "Deploy on Railway" button
3. Wait ~2 minutes for deployment
4. Access your admin panel and start building

Railway automatically generates secret keys, attaches storage, and configures health checks. No terminal required.

Option 2: Docker Self-Hosting

For those who prefer their own infrastructure:

INSTATIC_IMAGE=ghcr.io/corebunch/instatic:latest \
docker compose -f compose.prod.yml -f compose.sqlite.yml up -d

This single command pulls the image and starts Instatic with SQLite. Switch to compose.postgres.yml for Postgres support.

Option 3: Local Development

To run Instatic locally for development or testing:

git clone https://github.com/CoreBunch/Instatic.git
cd Instatic
bun install
bun run dev

Requires Bun (the fast JavaScript runtime) installed on your system.

Frequently Asked Questions

Is Instatic really free?

Yes, Instatic is 100% free and open-source under the MIT license. You can use it for personal projects, client work, or commercial sites without any licensing fees. You only pay for your hosting infrastructure (which can be as low as $5/month on Railway or free on their free tier).

Can I migrate from WordPress to Instatic?

Instatic includes a "Super Import" feature that can ingest entire static sites, including HTML, CSS, images, and fonts. While there's no direct WordPress plugin, you can export your WordPress site as static HTML (using plugins like Simply Static) and then import it into Instatic. The import process shows you all conflicts before writing anything, and the entire operation is a single undo.

How does the AI agent work? Do I need to pay for it?

The AI agent is built into Instatic but uses your own API keys for Claude, OpenAI, OpenRouter, or a local Ollama instance. You pay only for the API calls you make. If you use a local model via Ollama, the AI features are completely free (though you'll need sufficient hardware to run the model).

Is Instatic suitable for e-commerce sites?

Instatic is primarily designed for content-driven sites: portfolios, blogs, documentation, marketing sites, and small business websites. While you could technically build a simple product catalog using its data tables and loops, it's not optimized for full e-commerce functionality (shopping carts, payment processing, inventory management). For e-commerce, consider dedicated platforms like Shopify or WooCommerce.

Can multiple people edit the same Instatic site?

Yes, Instatic supports multi-user access with granular role-based permissions (38 distinct capabilities). When using Postgres as the database backend, you get managed backups and better concurrency for teams. SQLite works fine for single-author sites or small teams with light editing schedules.

What happens if I want to leave Instatic?

Since Instatic publishes clean static HTML and CSS, migrating away is straightforward. Your published site is just files on a server — no proprietary format, no database dependency. You can host them anywhere that serves static files (Netlify, Vercel, GitHub Pages, any web server). Your content is stored in standard database formats (SQLite or Postgres) that you can export at any time.

Does Instatic support custom domains and HTTPS?

Yes, Instatic works with any domain and supports HTTPS. When deploying on Railway or Render, HTTPS is configured automatically. For self-hosted setups, the deployment guides include instructions for setting up Caddy as a reverse proxy with automatic TLS certificate management.

How do plugins work in Instatic?

Instatic plugins are zip packages with a manifest file. Server-side plugin code runs in isolated QuickJS-WASM sandboxes with no filesystem access, no environment variables, and no network access unless explicitly granted by the site owner. This security model is far stricter than WordPress plugins, which often have full server access. Plugins can add HTTP routes, admin pages, storage, scheduled jobs, canvas modules, and media adapters.