Skip to main content
Fimo bills AI credits, bandwidth, and database compute beyond each site’s allowance. Hosting itself (the CDN, SSL, image delivery, server functions, builds) is included in every plan and rolled into the bandwidth meter. This page is the fine print behind those numbers. Current prices and allowances are on the pricing page.
Bandwidth charges also cover the hosting services listed below. See Fimo pricing for current rates and included allowances.

Plans at a glance

Every plan, including Free, can run agents manually or on a schedule. On Free, new runs pause when the AI-credit allowance is exhausted, and public serving pauses when the bandwidth allowance is exhausted. The allowance renews with the next billing period. Starter is the first paid plan. It adds event-triggered agents and custom domains, and meters usage beyond its allowances. Agents and content entries are unlimited on every plan, and seats are never metered. An organization that subscribed to a paid plan earlier keeps the price on its subscription. Version-history retention, analytics retention, storage limits, included usage, and current rates vary by plan. The pricing page is the source of truth for those values. When a site allowance is full, the Sites page keeps Create site visible but unavailable and explains the limit.

What counts as bandwidth

Bandwidth is the data served to your visitors, from every origin Fimo uses: the CDN for your pages and code, and the media store for your images and files. It is measured on the full size of each response, including headers and compression, and reported per site in your usage dashboard. A rough guide for a typical site with 1 MB pages: 1 GB is about 1,000 pageviews, or about 25,000 requests.

What the bandwidth price includes

Hosting platforms usually meter a dozen things. Fimo meters one. Everything in this table is covered by the per-GB price and never appears on your invoice.
Hosting providers often bill separately for requests, image transformations, cache operations, origin transfer, function compute, and build time. Fimo folds those resources into one bandwidth meter instead.

Fair use

The bandwidth price assumes a normal page: text, code, fonts, and images in ordinary proportions. Fair use is about 50,000 requests per GB, roughly 55 requests per 1 MB pageview and twice what a well-built page needs. Sites far beyond that ratio, for instance an API polled every second by many clients, or a page that reloads hundreds of tiny files on every visit, are not metered differently. We reach out and work out the right setup together. This is a conversation, not a surprise on the invoice.

Storage

Storage is the physical size of the uploaded files in your media library. Each plan has a hard upload limit rather than a billable storage overage. Delete files to make room. Media is stored and served through a CDN with no per-image or per-download charge, which is why serving images is part of bandwidth rather than a separate line. See the pricing page for current limits.

Database compute

Pages are served from the CDN and never touch your database. Comments, forms, previews, and Fimo Studio do. Database compute counts the time your site’s database is awake, weighted by its size, in compute-unit hours: an hour awake at the smallest size is a quarter of one. It counts every branch of the site’s database, including the branches agents work in. Most sites use little compute because the database sleeps when idle. Each site has its own monthly allowance: 100 compute-unit hours on Free and Starter, 400 on Pro. One site never uses another’s unused hours. From 1 November 2026, compute beyond a site’s allowance on Starter and Pro is paid from your extra usage budget, the same budget that covers bandwidth: $0.08 per compute-unit hour on Starter and $0.05 on Pro. Organizations on the earlier Pay-as-you-go plan pay the Starter rate. Fimo never charges more than the budget. Without a budget, or once it is spent, the site’s database stops at its allowance until the next month or until you raise the budget. On Free, the database always stops at its allowance. The Hosting usage page in billing shows the compute your sites used beyond their allowances this period, how many sites went over, and what it costs. Usage is imported every hour. When a site passes 75% of its allowance, Fimo emails the organization’s owners and admins once for that site and billing period. The email says what happens at the allowance: with extra usage on, the database keeps running within the budget; on Starter or Pro without it, the database stops until you turn it on; on Free, it stops until you upgrade or the month resets.

When a database limit is reached

Requests that need your project’s database can fail when a database limit is reached. This can affect content, forms, previews, and pages that fetch content at runtime. Already generated static pages may continue to work. While a limit is reached, the Sites page marks the affected site with Database limit. Inside the site, a Database limit button in the header shows what is affected, and Content and Assets show that they are unavailable instead of loading. The rest of Studio stays open. The details say how to lift the limit:
  • Starter and Pro without extra usage: turn on extra usage. Owners and admins get Manage extra usage.
  • Extra usage on, budget spent: raise the budget, from the same button.
  • Free: upgrade your plan. Owners and admins get Upgrade plan.
  • Any other limit: Contact support opens a support request about the affected site.
Contact support stays available in every case. The content API returns HTTP 402 with the code database_quota_exceeded. As soon as Fimo raises the limit, every open Studio tab of the organization checks the site’s database again and returns to normal by itself. Coming back to a tab checks again too, so there is nothing to press or reload. Fimo emails the organization’s owners and admins once per recorded incident, with the same way out as Studio, subject to their email preferences and delivery restrictions. Repeated failures do not send repeated messages. Another incident can send a new email after Fimo verifies that the affected database accepts requests again.

Agent environments and builds

Each agent run gets its own environment: a sandbox, a database branch, and a copy of your assets. Previews of an agent’s work are served from that environment and do not trigger a deployment. Your site rebuilds only when changes are published, and those builds are included.

Enterprise

Above roughly 1M pageviews a month, or when you need volume terms, a custom SLA, or a security review, contact us. The meters are the same. The terms are negotiated.

Frequently asked

No. Uploaded files count toward the media storage limit, and image delivery counts toward bandwidth like everything else. Image transforms do not create a separate customer charge.
No. Function time, revalidation, and origin transfer are inside the bandwidth price. Very heavy server work on every request falls under fair use. Ordinary server rendering does not.
No. One flat rate everywhere.
No. Pro includes more bandwidth and charges less for each GB beyond it. Free has no bandwidth overage billing: public serving pauses at the allowance. See the pricing page for the current rates.
Open your organization’s billing page in Fimo Studio. Bandwidth is under Hosting usage, with a Details page that breaks the current billing period down.

What’s next

Billing & credits

Check your organization’s balance and usage.

Pricing

Current prices, allowances, and plans.