Why Forge?
Forge is a Go framework for content that needs a lifecycle. You define content types as Go structs; Forge generates draft/publish/archive state, HTTP routes, storage, SEO endpoints, JSON API, and MCP tools. The same typed permission model applies whether a human uses the CLI, an AI agent uses MCP, or an external system calls the API. There is no admin UI - that is intentional. You manage content via your favorite AI agent of choice, or CLI or API. Forge is the plumbing, not the editor.
When to choose Forge
| vs. | Choose Forge when... | Choose X when... |
|---|---|---|
| Custom Go (no framework) | You need content lifecycle, auto-generated MCP tools, AI agent access, feeds and sitemap without building it yourself | Your data model is too custom for Forge's struct-based content model, or you have no content lifecycle to manage |
| Hugo / Astro | Content changes at runtime (publish/unpublish/schedule), you need a JSON API, agents must create or update content | Content is mostly static, deploys to a CDN, and your team commits content to git |
| Payload / Directus | You want zero runtime dependencies, type-safe content model in Go code, no separate admin process, MCP as first-class citizen | You need a rich admin UI for non-technical editors, a large plugin ecosystem, or complex field UIs |
| Headless SaaS (Contentful, Sanity) | Self-hosted, no vendor lock-in, content API and AI index included without extra cost | You need a hosted, fully managed service with no ops overhead |
| WordPress | Single Go binary, type safety, AI agents via MCP, minimal infrastructure | You need thousands of plugins, a familiar UI for non-technical editors, WooCommerce, or a large support community |
If you're not sure, start with the Getting Started guide.
For a broader overview - including a demo video - see Should I use Forge?.