forge.SingleInstance() and forge.Standalone() landed in v1.23.0, covering URL patterns the module system could not handle before.
SingleInstance() registers GET /{prefix} only and serves the first published record. Standalone() places items at /{slug} while keeping the list at /{prefix}. CRUD, lifecycle, and MCP tools are unchanged.
Marketing campaigns and blog posts can now have clean top-level URLs - /launch, /my-first-post - without custom routing code.
Your homepage and about page can be managed via MCP or CLI, no redeploy needed when content changes. The URL model your site needs, out of the box.
Your client's site runs on go build and a single binary.
No Node.js. No lock files. No npm install that breaks on someone else's schedule.
You ship once. It runs. The only moving part is your content.
Clone it and give it a spin: forge-cms.dev
Add an agent to your workflow. Remove one. Nothing else changes.
There is no orchestration layer to update, because there is no orchestration
layer. Each agent knows only its trigger and its task. They coordinate through
content state, not through each other.
Forge is headless. One URL returns HTML to browsers, JSON to your frontend framework, and AI-optimised output to agents.
No extra endpoints. No glue code. Content negotiation is built in. Your choice of frontend does not matter.
Build your Next.js, Svelte, or Astro site on top. The backend does not care.
Clone it: forge-cms.dev
The Chinese Steamroller: Quantifying the Systemic Threat to Europe’s Industrial Base #EUTech
China’s industrial rise now represents a systemic shock for the European economy. Over the past decades, Beijing has built a productive apparatus of unparalleled scale, combining significantly lower costs, massive overproduction and very rapid technological upscaling. China has become the world’s leading manufacturing producer and is generating record trade surpluses, durably reshaping the global industrial geography.
Which EU countries dominate passenger rail travel and who lags? #EUTech
forge-agent adds an embedded agent runtime to Forge apps. Jobs trigger on
content lifecycle signals or cron.
The job itself is a Forge content type: draft to test, publish to activate,
archive to stop. No redeploy. No config file. Results are written back via
MCP, through the same lifecycle enforcement as all other content.
Building sites for clients? Your next client will ask if their site works with AI.
Forge is a headless content backend with MCP built in. You bring the frontend. Their AI agent handles the content via typed tools, with the same rules that apply to human editors.
Give it a spin: forge-cms.dev
Your content triggers your AI. Publish a post and four social drafts appear
before you close the tab.
No webhook to configure. No external service to maintain. The agent runtime
runs inside your Forge process, wired to the same lifecycle signals as the
rest of your app.
Forge CMS
EU News
