Skip to main content
Craftspace is one process. It serves the API, the web app, the MCP endpoint and the connection gateway, and it runs its own Postgres (PGlite) inside itself. There is nothing to install alongside it.

​
Docker

/data is the whole durable surface: the database, the generated secrets, the unpacked assets. Back up that volume and you have backed up the install. To build the image yourself, docker build -t craftspace . from a checkout.

​
Binary

Each release carries a single executable for linux-x64, linux-arm64 and darwin-arm64. It holds the server, the web app, PGlite’s wasm and every extension bundle.
craftspace supervise starts the app, restarts it if it dies, and can swap itself for a newer version from the Settings screen. craftspace serve runs the server alone, without the supervisor. Data goes under CRAFTSPACE_HOME, which is /data in production and ~/.craftspace otherwise.

​
Behind a proxy

The app speaks plain HTTP on 8080 and does not terminate TLS. Put Caddy, nginx, Traefik or a cloud load balancer in front of it.
Forward X-Forwarded-Proto and X-Forwarded-Host. The auth layer builds callback URLs from the host it was reached on, and a proxy that drops those headers produces sign-in redirects pointing at the wrong origin.
An example with Caddy:

​
From source

Node 22 or newer. See local development for the watch-mode setup.