Overview
What WaferCMS is and how the pieces fit together
WaferCMS is a self-hosted container CMS. Editors use the admin UI; apps read (and optionally write) published content over an HTTP API. Postgres stores content; S3-compatible storage holds uploads.
Early software (v0.1.1). Contributors: Local Compose. Production: TLS in front of the apps — Deploy.
What you get
| Capability | What it does |
|---|---|
| Collections | Schema-driven content types with drafts and publish |
| Assets | Image uploads to object storage (private until you mark them public) |
| Admin UI | Editor SPA (cms-client) |
| Content API | Sessions for the admin UI; scoped API keys for apps (cms-server) |
| Optional AI | Item drafts and an admin task agent via OpenRouter (off by default) |
Pieces
| Piece | Role |
|---|---|
| cms-server | Auth, content API, files, optional AI |
| cms-client | Admin SPA — API URL from CMS_API_BASE at container start |
| Postgres | Content and users |
| Object storage | Uploads (RustFS in the default Compose) |