Why we built Forge

Most content tools force a choice: write code, or use a visual editor. Forge refuses the choice. You define your collections in TypeScript, edit them in a polished admin, and deliver over REST.

Code-first, always

Your schema is a real program, not a database blob a UI generated once. That means version control, code review, and types end to end. The admin is a convenience layered on top, never the source of truth.

EU by default

Every byte stays in the European Economic Area. No overseas sub-processors, no surprise data flows. GDPR is the floor, not a feature you bolt on later.

Headless, on purpose

Forge stores content and serves JSON. Your site is whatever you want to build — Astro, Next.js, a static export. Bring a frontend; Forge brings the content.