Unverified

Self-hosted visual CMS

Instatic

Design, manage, and publish fast websites from one self-hosted Bun server.

Instatic is an MIT-licensed visual CMS that combines a canvas editor, content and media management, users, plugins, forms, analytics foundations, and a publisher that emits semantic HTML and compact CSS.

CMSPage builderSelf-hostedBunTypeScriptMIT
01

Screenshots

Instatic visual editor with layer tree, website canvas, and style controls
Instatic media library with folders, filters, upload controls, and image assets
02

How it works

  1. Step 1

    Start the Bun server

    Install dependencies and run the documented development or built server with SQLite by default.

  2. Step 2

    Create the owner and site

    Use the first-run flow to establish a site and its owner account.

  3. Step 3

    Design and manage content

    Build pages in the visual editor and manage structured content, media, users, plugins, and forms.

  4. Step 4

    Publish and operate

    Publish semantic HTML and compact CSS, then back up the database and uploads folder.

03

Capabilities and scenarios

  • Visual canvas editor and design framework
  • Structured content, media, users, forms, and plugins
  • SQLite or Postgres storage
  • Semantic HTML and compact CSS publishing
  • Self-hosting and one-click deployment paths

Good starting points

Scenario 1

Self-host a marketing site or portfolio

Scenario 2

Build an editable small-business website

Scenario 3

Create a vertical site builder with custom modules

Scenario 4

Extend a CMS with sandboxed plugins and workflows

04

Fit and limitations

Fit at a glance

Project type
Self-hosted visual CMS
Repository set
1 repository
Runtime status
Unverified

Known limitations

  • Collected from public repository documentation; runtime behavior was not executed for this publication.
  • The README explicitly describes the project as version 0.0.x and warns that APIs and workflows can change before 1.0.
  • Plugin permissions, AI providers, forms, user data, and public deployment require a separate security review.
  • Database and uploads must be backed up together.

Confirm before starting

  • Bun >=1.3.0 and <1.4.0 for the captured source.
  • SQLite for the default development path or a user-provided Postgres database.
  • Persistent storage for the database and uploads, plus a tested backup and restore path.
  • User-controlled owner credentials, secret keys, AI-provider settings, and deployment configuration.
05

Repository set

These repositories form the complete project workflow. Follow setup order and include optional services only when the confirmed goal needs them.

Setup 1Required

CoreBunch/Instatic

Visual editor, CMS server, publisher, plugins, documentation, and deployment assets

Default branch
main
Captured revision
v0.0.14; commit d1f0942b1c1eb8842b032e6718bfbdabf25cd6d0
Author / maintainer
CoreBunch and Instatic contributors
License
MIT
The default development path uses SQLite; the README documents SQLite or Postgres through a shared database interface.

Catalog updated 2026-07-29. Reconfirm licenses, revisions, environment requirements, and runtime behavior from each repository before starting.

Project lineage

Project relationships

Every extension should preserve a clear path back to its sources.

01

Upstream projects

Where this project started

No upstream projects yet

02

Peer projects

Projects with the same upstream

No peer projects yet

03

Downstream projects

Published work derived from this project

No downstream projects yet