Fimo

Decap CMS vs Fimo: An editor for your Git repository, or a website that runs itself?

Updated November 2026

Decap gives your Git repository an editor. Fimo gives your website agents that keep working.

Decap CMS is a free, open-source editor that saves your team’s edits as commits to your Git repository. Fimo takes the site your coding agent built, lets your marketers edit it on the page, and runs agents that keep improving it.

Decap CMS is a free, open-source editor you add to your site at /admin. Every save becomes a commit to your Git repository, and your site is deployed wherever you already deploy it. That’s a clean, honest model, and it’s why coding agents reach for it. What it doesn’t do is anything after the save: the site only improves when somebody opens the editor. Fimo starts from the site your coding agent built, lets your marketers edit it on the live page, hosts it, and runs agents that keep improving SEO, content, links and translations on their own.

Read the full breakdown

People choose Decap for good reasons. It costs nothing, it’s MIT-licensed, it has no vendor to outgrow, and every change your team makes sits in Git history next to the code, reviewable like any other commit. With the editorial workflow turned on, an edit turns into a pull request that moves through Draft, In review and Ready before it’s merged.

The trade-offs show up around the edges. Decap doesn’t host anything, so sign-in is your job: on GitHub, every editor needs push access to the repository, or you run an OAuth proxy, set up Git Gateway, or pay for Decap Turbo’s hosted sign-in. Editors work in form fields beside a preview pane rather than on the page itself. And nothing in Decap watches the site once it’s live: meta descriptions, internal links, stale pages and other languages are still somebody’s job.

Fimo is built for that second half. Its agents run on a schedule against the whole site, each run leaving a report, a preview and a diff, and every version is kept so any change can be restored. If what you need is an editor for a static site you already host, Decap is hard to beat on price. If what you need is a site that keeps getting better without anyone scheduling the work, that’s Fimo.

Decap CMS vs Fimo at a glance

Decap is an editor you add to your own stack. Fimo is the editor, the hosting and the agents in one place.

Based on public documentation as of November 2026. Spot something wrong? Tell us at hello@fimo.ai and we'll fix it.

Swipe the table to see both columns.

Capability
Decap CMS
Fimo
What it is
A free, open-source editor added to your site at /admin
A platform: an editor on the live page, hosting and agents
Where edits are saved
Text files committed to your Git repository
Fimo's own CMS, with the site's code beside it
Editing
Form fields with a preview pane
Inline editing on the live page, every plan
After publish
Nothing changes until an editor opens the admin
Agents keep improving SEO, content, links and translations
Review
Editorial workflow: Draft, In review and Ready, one pull request per change
Each agent run leaves a report, a preview and a diff, every version kept
Hosting
Yours: you deploy the site where you already do
Included: hosting, SSL, CDN and preview links
Show all 10 capabilities
Sign-in for editors
Push access on GitHub, an OAuth proxy, Git Gateway or paid Decap Turbo
Teammates are invited to the site, no Git account needed
Translations
Per-field i18n settings, with limits on lists and objects
Translation agent covers content and interface strings
Price
Free (MIT licence), Decap Turbo plans for hosted sign-in
Free plan, then usage-based plans, no seats
Maintained by
Independent open-source maintainers in the EU
The Strapi team

What you can do with Fimo that you can't with Decap CMS

  • Edit the copy on the live page instead of in a side form
  • Invite marketers without giving them access to your Git host
  • Run SEO, GEO and content agents on the site on a schedule
  • Translate content and interface strings in the same pass
  • Get hosting, SSL, CDN and preview links without a second vendor
  • Restore any earlier version of the site from its history

Decap waits for an editor, Fimo’s agents keep working

Both platforms let a person change the copy. The difference is what happens on the days nobody does.

decap cms · editor

A person opens /admin, edits, saves

Decap is an editor and only an editor. A teammate signs in at /admin, changes fields in a form, checks the preview pane and saves. The save becomes a commit, or a pull request with the editorial workflow, and your usual deploy picks it up. Every improvement starts with a person finding the time to make it.

Read the full breakdown

There are no scheduled jobs, no SEO checks and no agents in Decap’s documentation. That’s a deliberate scope rather than a gap in the product: it was built to give a static site a friendly editor, and it does that well.

fimo · agents

You describe the job, the agent keeps doing it

Fimo runs an agent for each job a site needs after launch. The SEO agent audits and fixes every page, the content agent refreshes what has drifted, and the translation agent covers your other markets. They run on a schedule and publish on their own, each run leaving a report, a preview and a diff, and every version is kept so any change can be restored.

Read the full breakdown

If you’d rather approve first, tell them, and they leave each change as a preview until you publish. Your marketers still edit whatever they like on the live page in the meantime.

Git for the code, Fimo for the content

Decap keeps everything in Git. Fimo keeps the code in Git and the content in its own CMS.

With Decap, an edit is a commit: a text file in your Git history, next to the code, deployed by whatever already deploys your site. That’s the main reason teams like it, and it’s worth saying plainly: if you want every entry to live as a file in Git, choose Decap.

Read the full breakdown

Fimo keeps the site’s code in Git too. Connect an existing application with fimo link and its repository, history and GitHub origin stay where they are, while Fimo adds itself as a second remote and hosts the previews and the live site. The content your coding agent wrote moves into Fimo’s own CMS, where marketers edit it on the page and agents can work on it, with every version kept.

What Decap CMS does well

For a static site with a team comfortable in Git, Decap gives you a lot for nothing.

Free and open source

MIT-licensed and free for everyone, with no vendor, no seats and no usage meter. Decap Turbo is optional and only adds hosted sign-in, roles and media.

Your Git workflow

Every save is a commit, and with the editorial workflow every change is a pull request that moves through Draft, In review and Ready before it merges.

Your hosting, your stack

Decap adds an editor and leaves the rest alone: you keep your framework, your CI and your host, on GitHub, GitLab, Bitbucket, Gitea, Forgejo or Azure.

Decap CMS vs Fimo pricing: free editor versus included work

Decap is free, and you run the rest of the stack. Fimo meters the work its agents do, hosting included.

Decap CMS

PlanPrice
Decap CMSFreeMIT licence, you host it
Decap TurboPlansHosted sign-in, roles, media

decapcms.org, November 2026. Decap does not host your site: hosting, a sign-in service for editors and any SEO or translation tools are separate.

Fimo

PlanPrice
Free$0SEO and GEO agents, no card
Starter$99/moAll agents, daily runs, your own domain
Pro$299/moEvent-triggered runs, 99.9% uptime SLA
EnterpriseCustomSSO, audit logs, SLA

Metered on AI credits, agent-hours and bandwidth, never on people or sites. Free runs the SEO and GEO agents weekly. Starter adds all the agents, daily runs, your own domain, roles and permissions, and analytics, and Pro adds AI traffic, event-triggered runs and a 99.9% uptime SLA, each with bigger allowances. No seat is ever billed, so the manager who edits one page a quarter costs you nothing.

Thinking about moving from Decap CMS?

Your entries are already files in Git, which makes this one of the easier moves.

The honest path

Connect the site, then let your agent move the entries

Run fimo link in the repository, so its code, history and GitHub origin stay as they are. Your coding agent, with the Fimo skills installed, then reads each Decap collection and recreates it as editable content in Fimo, keeping the components it already uses.

Lists, nested objects and per-locale files are the parts to check by hand. A small marketing site is a day or two of agent time plus review.

What you get back

Editing on the page, and agents on the site

Editors no longer need access to your Git host or a sign-in service you run yourself, and hosting moves into the plan.

What you give up is having every entry as a file in Git and a free tool with no vendor, so if those matter most, stay on Decap.

Decap CMS vs Fimo: which one fits your team

Choose Decap CMS if

  • You want every entry as a file in Git
  • Your site is static and you already host it
  • You want a free, open-source editor and nothing more

Choose Fimo if

  • Your site came out of Claude Code, Codex or Cursor
  • Marketers should edit on the page, without a Git account
  • You want the site to keep improving without anyone scheduling it

Common questions

Yes, under a new name. Netlify CMS became Decap CMS in February 2023, and it is now maintained by independent open-source contributors in the EU.

No. Decap is an editor you add to your site at /admin, and you deploy the site wherever you already do. Fimo includes hosting, SSL, a CDN and preview links in every plan.

With the GitHub backend, every editor needs push access to the repository. Git Gateway, an OAuth proxy you run, or the paid Decap Turbo can avoid that. In Fimo, teammates are invited to the site and edit on the page without a Git account.

Not in its documentation as of November 2026: it is an editor, and every change starts with a person. Fimo runs agents for SEO, GEO, content, links and translations on a schedule.

Yes, for code you already have. Connect an existing application with fimo link and its repository, history and GitHub origin stay where they are: Fimo adds itself as a second remote and hosts the previews and the live site. A site you start in Fimo lives in Fimo’s Git, with the full history available to clone at any time.

By default they publish on their own, within the work you switched on, and every version is kept so any change can be restored. If you’d rather approve first, tell them: they then leave each change as a preview and publish only when you ask.

Fimo runs on JavaScript sites built with Next.js, Astro, SvelteKit, React Router, TanStack or Vite. If you want every entry to stay a file in Git, or you need a free editor and nothing else, Decap is the better fit.

Fimo is free to start.

Bring the site your coding agent built and have an agent running before anyone asks for a budget.