Skip to main content
Your coding agent builds the site. Fimo owns everything after the build — and keeps it editable by non-developers and operable by AI. One source of truth, two surfaces: the fimo CLI for you and your agent, and Fimo Studio for your non-technical teammates. Here are the pieces that make that work.

​
The building blocks

One website, with its own code, content, media, and settings. A project lives inside an organization and is linked to a local directory by .fimo.settings.json (written once by fimo init — never edit it). It’s a real git repo with fimo as the remote, so there’s no lock-in.
See Projects & onboarding.
A git-shaped, isolated clone of the project: a git branch plus its own database, sandbox, preview URL, and assets. Every project starts on main; you create more for feature work, preview them per-env, then merge back and publish. CLI commands target the env of your current git branch.
See Environments.
Structured content lives in the CMS, not in code. You declare schemas (content models like BlogPost or Product) and create entries against them. Editors change entries in Studio without touching code; your app renders them with generated hooks and fimo/ui components.
See Content & CMS.
A central library for images, videos, and files — uploaded once and reused across the site. You can also generate images and video with AI. Fimo tracks dimensions, alt text, and captions.
See Media & AI generation.
Static UI copy — headings, buttons, nav, placeholders — is wrapped in t('key') in code, and its value lives in the database so editors can reword it. Add locales in fimo-config.json to serve the same site in multiple languages.
See Labels, locales & i18n.
Contact, signup, and feedback forms are defined as JSON, pushed with the CLI, and rendered from a generated, validated client. Submissions are captured server-side and readable from the terminal or Studio.
See Forms.
Agents-as-files that live in your repo and run on a schedule (or on demand) to keep the site alive — SEO audits, content translation, broken-link sweeps, post-deploy checks. They reach the server through fimo deploy.
See Scheduled agents.
Fimo hosts your site. fimo deploy gives an on-demand hosted preview; fimo deploy --publish goes live from main. Every deploy also emits an AI-friendly markdown version of the site. Your default URL is <slug>.fimo.site, with custom domains available.
See Deploy & publish.
The visual web app your non-technical teammates use — visual editing, the CMS, the media library, version history, SEO, and publishing — over the exact same project the CLI drives.
See Fimo Studio.

​
What’s next

Quickstart

From fimo init to a live site.

Build with the CLI

The full fimo command surface.

Billing & credits

AI credits, environment hours, and bandwidth.