Deploy Instatic — Self-Hosted Webflow Alternative

Deploy and Host Instatic on Railway

Instatic is the open-source alternative to Webflow, Framer, and WordPress — a self-hosted visual CMS with a canvas editor, collections, pages, media, forms, and auth, all in one server. Its defining feature: it outputs clean, semantic HTML and compact CSS with no framework runtime, no builder attributes, and no "div soup," so your pages load fast and stay fully portable. This template deploys Instatic with a persistent volume, generated secret keys, and health checks configured, so you're building websites visually — with none of the lock-in — in minutes.

What This Template Deploys

A single self-contained service. A persistent volume holds the SQLite database and uploaded media, so your site, content, and files survive redeploys. The entire stack — editor, CMS, plugins, and publishing — runs from one Bun server, with no external database required by default.

About Hosting

Instatic is refreshingly simple to run, and understanding a couple of things makes the most of it — all handled here.

One server, SQLite by default — nothing extra to wire. The visual editor, content management, media, authentication, forms, plugins, and publishing all run from a single Bun instance. SQLite is the right default for most sites, stored on the persistent volume alongside your uploads, so there's no separate database to provision. For a team of authors or managed database backups, you can switch to PostgreSQL — but most sites need only the volume.

Clean static HTML output — the whole point, and your anti-lock-in edge. Unlike Webflow and Framer, which keep your site on their infrastructure wrapped in a proprietary runtime, Instatic publishes plain semantic HTML and compact CSS — no editor machinery left in the page. Your site loads like a static file because it usually is one, and you can host the output anywhere. Real ownership: the pages, the data, and the deployment are all yours.

Persist the volume — it holds your whole site. Your SQLite database (pages, collections, content, form submissions, users) and all uploaded media live on the mounted volume. Without it, a redeploy wipes your site. This template mounts it, so everything persists, and you update Instatic by redeploying the latest image while your data stays intact.

Sandboxed plugins that can't exfiltrate data. Instatic's plugins run in isolated QuickJS-WASM sandboxes with no filesystem, no environment access, and no network unless you explicitly grant it — a fundamentally safer model than WordPress's plugin ecosystem. Extend your site without opening the security holes plugins usually bring.

Built-in forms and real access control. Form submissions go straight to your database with no third-party service, and Instatic ships granular role-based access control, TOTP two-factor auth, account-lockout protection, and audit logging — genuinely multi-user and production-minded, not just a page builder.

Set up your admin on first visit. Railway generates Instatic's secret keys automatically on deploy; open your Railway URL to create your first admin account, then start building pages on the canvas and modeling content with collections.

Typical cost: ~$5/month on Railway for the single lightweight service and volume. Instatic is MIT-licensed and free — no monthly Webflow or Framer subscription, ever.

How It Compares

Webflow and Framer offer great visual editing but keep your site on their servers for a recurring fee — stop paying and the site stops. WordPress gives ownership but leaves you managing a plugin ecosystem with far more access than it should have. Instatic's edge is combining the visual editing of Webflow with true ownership: clean, portable HTML output, a single self-hosted server, and sandboxed plugins — your site, your data, your deployment, at flat cost.

Deploy in Under 5 Minutes

1. Click Deploy on Railway — Instatic builds with a volume and generated secret keys (~2 minutes)
2. Confirm the volume is mounted for the database and media
3. Open your Railway URL and create your first admin account
4. Build pages on the visual canvas and model content with collections
5. Publish — Instatic outputs clean HTML you can serve anywhere

Update to new versions by redeploying the latest image; your data stays on the volume.

Common Use Cases

• Visual website building — design pages on a canvas without writing code, self-hosted
• Webflow / Framer replacement — the same visual workflow without the subscription or lock-in
• Agency and client sites — build a site and hand off a portable, self-hostable deployment
• Marketing sites — fast, clean-HTML landing pages you fully own

Configuration

Persist the volume — it's your whole site. The SQLite database and media live on the volume; without it, a redeploy wipes your site. This template mounts it, and you update by redeploying the latest image while data stays intact.

SQLite by default, Postgres optional. Most sites need only the volume-backed SQLite. Switch to PostgreSQL via DATABASE_URL for a team of authors or managed backups.

Dependencies for Instatic Hosting

• Railway account — ~$5/month for the single service and volume
• A persistent volume for the database and media (included and mounted)
• Nothing else for SQLite mode — no external database required
• Optional: PostgreSQL for multi-author teams or managed backups

Deployment Dependencies

• Instatic GitHub Repository
• Instatic Documentation
• Instatic Docker Image
• Railway Volumes Documentation

Implementation Details

The template runs the official ghcr.io/corebunch/instatic image as a single Bun server that hosts the entire application — visual canvas editor, content engine, media management, authentication, forms, plugin system, and static publishing — with a persistent volume for the SQLite database and uploaded media. SQLite is the default and suits most sites; PostgreSQL can be configured via DATABASE_URL for teams wanting shared authoring or managed backups. Railway generates the required secret keys and configures health checks automatically on deploy.

Instatic's defining characteristic is its output: pages are published as clean, semantic HTML and compact CSS with no framework runtime or builder attributes, so sites are fast and fully portable — the output can be hosted anywhere, and moving the whole app between Railway, a VPS, or a client's server is a redeploy rather than a migration. Plugins execute in isolated QuickJS-WASM sandboxes with no filesystem, environment, or network access unless explicitly granted, a markedly safer model than typical plugin ecosystems.

Access control is granular, with role-based capabilities, TOTP two-factor authentication, account-lockout protection, and audit logging; form submissions are stored directly in the database without third-party services. Updating is done by redeploying the latest image, with the database and uploads persisting on the volume, which is the component to back up.

Frequently Asked Questions

What makes Instatic different from Webflow? Webflow keeps your site on its servers for a monthly fee, wrapped in a proprietary runtime. Instatic is self-hosted and outputs clean, portable HTML you fully own — the same visual editing without the lock-in or subscription.

Do I need a separate database? No — Instatic uses SQLite by default, stored on the volume alongside your media, so there's nothing extra to provision. Switch to PostgreSQL via DATABASE_URL only if you need shared authoring or managed backups.

Does my site persist across redeploys? Yes — the SQLite database (pages, content, form submissions, users) and uploaded media live on the volume and survive redeploys. Back up the volume to preserve your whole site.

Are the plugins safe? Yes — plugins run in isolated QuickJS-WASM sandboxes with no filesystem, environment, or network access unless you explicitly grant it, so they can't quietly exfiltrate data, unlike typical plugin ecosystems.

Why Deploy Instatic on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Instatic on Railway you get an open-source visual CMS with the setup handled — a single Bun server, a persistent volume for your site, generated secret keys, and automatic HTTPS. Build websites visually and publish clean, portable HTML you fully own, self-hosted on infrastructure you control.