Architecture
Your app, a generated CMS, storage underneath.
Stackpress sits between TypeScript routes and your database. Media goes through the same adapters you already configure.
TypeScript App
Routes, loaders, and UI stay in your framework. You query Stackpress the way you would query any typed server module — no separate frontend SDK to vendor.
Stackpress CMS
The admin is generated from your collections and globals. Editors work in /cms. Developers never configure that UI beside the schema.
Content
Documents live as collections and singleton globals. The same records the CMS edits are the records find and getGlobal return.
Media
Uploads are stored through a storage adapter and referenced from documents. A proxied /cms/file route is how the app serves bytes.
Storage / DB
A database adapter (MongoDB in this site) holds documents. An S3-compatible adapter holds files. Email and other services plug in the same way.
Content infrastructure, without the abstraction tax.
Define your model in TypeScript. Give your team a powerful editing experience. Ship typed content wherever you need it.
Open the CMS