Fimo
Serve

Deploy with one command.

One command deploys your website and your agents to a preview. Publish when it is right: a global edge with SSL, CDN, and custom domains included.

One command

Preview first.
Publish when it is right.

One command, and a real copy of your site is running on its own preview URL in seconds. Share it, check it, change it. Your agents ship with it: no pipeline to set up, nothing to configure.

When it looks right, publish. Going live is one click, and every publish is kept, so you can always step back to a previous version.

The platform

Deploy once. Delivered everywhere.

No servers to size, no cache headers to tune. Caching, routing, and scale are outputs of the deploy, handled by the platform.

A global edge network

Your pages are served from the location closest to each visitor. Distance stops being a performance problem.

Zero configuration

Push code and the platform derives the infrastructure: caching, compression, and routing, set on every deploy.

A preview for every branch

Each branch and each agent run gets its own preview URL. Review the real site before anything is published.

Version history

Every state of your site is kept. Restore a previous version from history: 1 day on Free, 90 days on Pro.

Automatic HTTPS

Certificates are issued and renewed for you, on every domain. Nothing to request, nothing to track.

Always-on DDoS mitigation

Malicious traffic is filtered at the edge before it reaches your site, around the clock.

Autoscaling

Capacity follows demand. Spikes are absorbed, with nothing to provision and nothing to tune.

Custom domains

Point a domain and it is live with SSL in minutes. Attach as many domains and subdomains as you need on Pro.

Agents included

Your agents are files in your repo, deployed exactly like your pages. No second pipeline, no separate infrastructure. One command, and they run on their schedules, in their own branches, for your review.

Publish

Going live is a decision, not a side effect.

Deploys land in previews. Production changes only when someone publishes main, from the CLI or from the Publish button in Studio. Every publication is kept in history, so a previous state is one restore away.

Agent runs never publish. They leave their work in a branch with a report, a preview, and a diff, and wait for your review.

FAQ

Questions about deploying.

Fimo hosts it for you on a managed global edge network. Your pages are served from the location closest to each visitor, with automatic HTTPS, always-on DDoS mitigation, and autoscaling. There are no servers to provision and nothing to maintain.

No. Caching, routing, compression, and CDN distribution are outputs of the deploy, not settings you manage. Run fimo deploy and the platform builds the infrastructure your site needs. There are no cache headers to tune and no config files to keep current.

fimo deploy pushes a branch and brings up its preview. Nothing is public yet. Publishing takes main live, with fimo deploy --publish, fimo publish, or the Publish button in Studio. Both run the same validation first, so what you publish is what you previewed.

They ship with your site. An agent is a folder of files in your repo, so the same fimo deploy pushes your pages and your agents together. Cloud runs use the committed configuration, on the schedules you set, each in its own branch.

Yes, on Pro. Point your domain at Fimo and it is configured automatically, including the SSL certificate and renewals. You can attach multiple domains and subdomains to one site. Every project also gets a free fimo.site address you can rename.

Yes. Every state of your site is kept in history, code and content together: 1 day on Free, 90 days on Pro. Restore any of them from Studio if a publication goes wrong.

No. Your site is a standard codebase in your Git repo, and your agents are plain files beside it. Fimo hosting is the fastest way to run both together, but you own every line and can move it whenever you want. No black box.
Keep exploring

Where to next.

Start with your website.

Try Fimo online in seconds, then connect your coding agent and publish when you are ready.