Fimo

Developers, start here.

Connect the site you built with one command and keep your stack. Content, agents, previews and hosting come on top.

npx fimo@latest init
Read the docs

One command to connect.

Your coding agent runs npx fimo@latest init on the site it built. The content becomes editable and a first preview opens. Next.js, Astro, Svelte and React Router.

Claude Code, Codex, Cursor, Devin, Copilot, Warp, Antigravity.

Bring your AI stack.

Claude Code, Codex, Cursor or whatever you use keeps building the site. Fimo attaches to the site, not to the tool, so mix them freely.

Everything technical.

What your coding agent uses to build, run and ship the site.

CLI

Connect a site, scaffold pages and deploy a preview, from your terminal.

Skills

Install the Fimo skills and your coding agent builds sites whose content is editable.

MCP server

Your coding agent reads the site’s data and acts on it from the tool it runs in.

SDK

A typed SDK to query and automate the site from its own code.

Plugins

Claude Code and Codex plugins, so Fimo lives inside the tools you already run.

Built-in agents

SEO, GEO, content and translation agents, each with its own routine and expertise.

Version history

Every version of the site is kept, code and content together. Restore one in a click.

Docs

Reference and guides for the CLI, the SDK and the MCP server.

Every run on its own copy.

Each branch and each agent run works on a private copy of the site, with its own preview. The live site is untouched while it runs.

Its own server, data and media.

A full copy of the stack: a server, a database and a media library. Ready in milliseconds, thrown away when the work ships.

One diff for code and content.

Code, schema, content and labels change together, in one diff. Every version is kept, so any change can be restored.

Deploy once. Site and agents, live.

fimo deploy sends the site and its agents to a preview link. Publish when it looks right. HTTPS, custom domains and version history included.

How hosting works

Questions about the technical side.

Straight answers.

Claude Code, Codex, Cursor, Devin, GitHub Copilot, or anything else that writes code. Fimo is attached to your site, not to a coding tool, so your team can mix tools freely and the site stays editable either way.

JavaScript sites built with Next.js, Astro, Svelte or React Router. More frameworks are coming.

Yes. Connect it and your team edits the content on the page or in structured fields, stored in Fimo and versioned on every edit. Claude Code keeps working on the same code, exactly like before.

Yes. Fimo works with any design tool, such as Figma or Claude Design. For a visual change like the color of a button, ask the chat in Fimo or prompt Claude Code or Codex.

No. Your coding agent keeps building the site the way it does today. Fimo adds the content, the agents, the previews and the hosting around it.

A full, disposable copy of your site: its own server, database and media library, on its own link. Every branch and every agent run gets one, so you see the change for real before it goes live.

Yes. Content edits, schema changes and agent runs work against the branch’s own data, never against the live site’s. Delete the branch and its environment goes with it.

In milliseconds. It exists as soon as the branch does, so neither agents nor teammates wait for a staging server.

Staging is one queue the whole team shares, and one broken experiment blocks everyone. Here every branch and every agent run gets its own copy of the stack, so work runs side by side and every preview shows exactly what will ship.

Where to next.

Agent library

Every ready-made agent and what it runs on its own, from SEO and GEO to content and compliance. Add yours in plain words.

Deploy with one command

One command deploys your website and your agents to a preview. Publish when you are ready. Fast hosting, SSL, CDN, and custom domains included.

Connect your website.

Try Fimo online first, then run one command on your code when you are ready.

Try Fimo for freeRead the docs

We use cookies to measure how the site is used and make it better. See our cookie policy.