SOLVED
Should I use Forge?
Forge is for teams that want their AI to handle content — creating, scheduling, and publishing it — without losing control of where data lives or who can do what.
Get started
No dashboard required.
Your AI handles publishing through a structured API. Your team stays in the tools they already use.
Full control, zero risk.
Role-based access means your AI can only do what you allow. Draft content never leaks.
Live in minutes.
Connect once. From that point, a conversation is all it takes to publish.
Forge is for you if you want your AI to handle your content operation -- and you need that to be safe, auditable, and fully under your control.
If your team manages content manually today, or if you are evaluating whether an AI can take over that work without introducing new risks, this is what Forge addresses.
The problems it solves
Your AI publishes things it should not. Most platforms leave it to developers to enforce what is draft and what is live. One oversight and an unfinished piece goes public. Forge enforces four states at the platform level -- Draft, Scheduled, Published, Archived. Anything outside Published is invisible to visitors, search engines, and AI indexes. Your agent works within the same rules. There is no bypass.
You do not control where your content lives. Hosted platforms store your content on infrastructure you did not choose and cannot inspect. Forge is self-hosted. Your data stays on your server, in your jurisdiction. Your legal team can audit it. A regulator can inspect it. Nothing leaves without your say-so.
A vendor holds your content stack hostage. If a SaaS CMS raises prices or shuts down, migration is painful and your content is at risk. Forge is open source. You own the stack. You can move it, inspect it, and run it anywhere.
You cannot give an AI exactly the right level of access. Forge issues tokens scoped to a role -- Author, Editor, Admin. An agent with Author access can draft and publish, but cannot delete another editor's content. The same access rules apply to humans and AI agents. You define the boundary once. The platform enforces it everywhere.
What comes with it
Delivery Every content type gets a list page, a detail page, an RSS feed, and sitemap entries. SEO metadata and Open Graph tags on every page. AI index formats built in, so agents can read your content without extra work. The same URL serves HTML to a browser, JSON to an API, and an AI-readable format to an agent.
Lifecycle and storage A database is created from your content definition. Content moves through Draft, Scheduled, Published, and Archived. Nothing reaches your audience before it is ready.
Navigation Site navigation is managed through the same interface as content -- not hardcoded markup. Your agent can manage it too.
Operations System monitoring is included from day one. Problems surface during setup, not in production. There are no third-party packages in the stack -- nothing that can break on someone else's schedule.
See it in action
Go deeper
Each of the following covers one part of the stack in detail:
Ready to put your AI to work?
Forge is open source and self-hosted. Get started in minutes.