Fimo
For developers

Deliver the site.
Keep your focus.

You become the site’s support channel the day it goes live: every headline change or testimonial swap lands as a Slack ping mid-work. Fimo ends that. Deliver on your stack, hand over the keys, keep only the reviews you want.

Merge rules
instead of Slack pings.

You set the rules. Git enforces them.

The rest of the team edits the live site visually while the code stays yours, in your repository. Protected branches keep anything unwanted from reaching production, and you review pull requests only when it matters.

How autonomous agents work
your-repo
agents/
seo/
GOAL.mdREQUIRED
SOUL.mdOPTIONAL
capabilities.yamlOPTIONAL
config.yamlOPTIONAL
skills/BUILT-IN
scripts/OPTIONAL
references/OPTIONAL
assets/OPTIONAL
plugins/DEFERRED
.envGITIGNORED

Hand over a site that improves itself.

Agents in your repo. Yours to shape.

Most handovers start slow decay: stale content, SEO that never happens, a redesign six months later. A Fimo site comes with agents that keep working on it: files in the repo, versioned, reusable.

How custom agents work

Every change is a branch. Every review is one diff.

Isolated environments. One diff to review.

Agents don’t experiment in production. Every branch spins up a disposable copy of your stack in milliseconds. When the work is done, you read one diff covering code, schema, and content together.

How isolated environments work
New post published
FieldValue
TitleHow agentic workflows actually finish
Slugstructuring-agentic-workflows
Entry IDae873e4a-af94-4d1b-ae46-4a80f10747bb
Publish date2026-06-11

Deploy once.
Site and agents, live.

Global edge, SSL, CDN. No second pipeline.

One fimo deploy and your site and your agents go live together, no second pipeline. Every branch gets a preview URL, so you see the real site before production. A bad release rolls back in one click. You decide what goes live.

How deployment works
How it works

From handoff to autopilot.

Install.

An SDK wires your content so it becomes editable. No rebuild, no migration.

Delegate.

Marketing edits without you. Agents work in isolated environments and open PRs for review.

Deploy.

Preview every change on its own URL, then send it live. Bad release? Roll back in one click.

Built by the team behind Strapi.

Fimo comes from the founders of Strapi, the leading open-source headless CMS. A decade of content infrastructure for millions of developers, distilled into a platform built for the agent era.

70K+
GitHub stars
Millions
of developers served
FAQ

Questions developers ask.

No. Build with Claude Code, Codex, Cursor, or whatever you already use, on your usual stack: Next.js, Astro, React, Vite, TypeScript. Fimo is framework-agnostic: it works over the output and turns it into an editable, autonomous site without changing your workflow. Details on your AI stack.

Yes. Fimo is a git-based, framework-agnostic CMS: use it as a Next.js CMS, a React CMS, or an Astro CMS, and it works the same with Vite, Remix, or SvelteKit. It runs over whatever your framework outputs, so nothing about your build changes; your content simply becomes editable, and every edit lands as a clean commit in your repo.

It installs an SDK and wires your content pieces so they become editable, without touching the rest. No rebuild, no migration, no proprietary layer between you and your codebase.

Yes. The site stays real code in your repository, in your own GitHub organization. Every action relies on Git and is reversible.

It breaks its own environment, not your site. Each agent works in a sandbox with a dedicated server, database, and media library, and nothing reaches production until the branch is merged. Delete the branch and the experiment never happened.

Only the ones you choose. Merge rules are per action type: let content updates auto-merge, have schema changes ask you first, keep deletions gated. Protected branches enforce it, so nothing unwanted reaches production without a review. You set the rules once and adjust them as trust grows.

Yes. An agent is a folder in your repo: a GOAL.md for the mission, an optional SOUL.md for tone, a config for schedule and scope. The easiest way to create one is to prompt your coding agent (Claude Code, Cursor, whatever you use): Fimo comes with a skill for it, so you describe what you want and it creates the agent for you. Build your own, or run agents from the community ecosystem.

Lighthouse, mobile responsiveness, broken-link checks, technical SEO, GEO. All optional and all yours to shape: run the ones that fit, drop the ones that don’t, or build your own from scratch.

Inline on the live page, by chat, through the CMS, or from Slack and Teams via MCP. Anything you can do with your coding agent, they can do from a message.

It is a CMS built the way developers work: Git underneath, real code, isolated environments, reviewable diffs, and a visual layer on top so the rest of the team never needs you for a headline again.

Start building.

Join 2,000+ teams shipping autonomous websites with Fimo.