A monthly hosting charge can cover several different things. Before deciding whether it is too high—or whether a free tier is enough—ask what is included.
The original article separates infrastructure from the work of building and maintaining a site. That distinction is worth keeping. Cheap infrastructure does not make maintenance unnecessary, and a recurring service fee is not automatically a charge for an idle server.
01 / FIELD NOTESWhat can fit on a free tier
The supplied account describes a familiar small-project combination: static pages, a serverless API, a modest database, and image storage. Navarro's original write-up reported no monthly infrastructure charge at its usage level.
That is a historical account of one FiveM community project. It is not a quote for a commercial website or a promise about the next billing period.
Resource allowances and permitted uses are separate checks. A deployment can be small enough for a plan and still fall outside that plan's allowed use.
Provider check — September 29, 2026: Vercel's Hobby guidance restricts that plan to non-commercial personal use. Cloudflare Pages pricing distinguishes static requests that do not invoke Functions from Functions requests billed as Workers usage. These are specific plan rules, not a statement that every kind of website traffic is free.
02 / FIELD NOTESPut the recurring costs in separate rows
Separate the bill into its real parts.
All starting values are fictional assumptions in USD. They are not provider prices or an MRoot quote.
Illustrative total. Excludes the build, taxes, payment fees and usage overages.
Read the figure without interaction
Example: an $18 annual domain plus $6 monthly email and $25 monthly maintenance totals $390 annually. These are invented inputs, not market prices. A monthly equivalent spreads an annual charge; it is not a billing schedule.
Eligibility and commercial-use terms still need checking independently of the amount.
The worksheet uses annual domain cost and monthly hosting, email, other tools, and maintenance. The sample values are made up so the arithmetic is visible. Replace them with amounts from the services you actually use.
A blank amount means it is not known. It does not mean zero. An entered zero is allowed, but it still needs a reason when this becomes a real budget.
The annual estimate is domain + 12 × monthly services. The monthly equivalent spreads the annual domain cost across twelve months; it is not necessarily how the provider charges your card.
03 / FIELD NOTESWhat is not covered by a free server bill
The original article calls out the domain, transactional email, spam protection, and someone to build and maintain the site. A quote should say which of those are included and which remain separate accounts or responsibilities.
A service may offer a free allowance while still needing setup, monitoring, configuration, or an upgrade later. “Free to use at this volume” is not the same as “no work to operate.”
This example excludes the initial build, taxes, refunds, payment-processing fees, and usage overages. It is deliberately not a calculator for every provider's billing model.
04 / FIELD NOTESWhere the bill changes later
More stored data, heavier media delivery, additional background work, and commercial-use requirements can change the plan a site needs. The precise trigger depends on the provider and configuration.
Provider check: Cloudflare's Workers pricing lists a paid-plan minimum and usage-based charges. It also has specific billing treatment for Workers Caching. Use the actual product's pricing page rather than assuming that a saved response makes requests free.
05 / FIELD NOTESAsk what the fee buys
The original closing treated many hosting fees as money paid for nothing. That conclusion cannot be made from the amount alone.
A recurring agreement may include backups, updates, support, monitoring, incident response, or reserved help. It may also include little beyond hosting. Ask for the breakdown and the boundaries instead of guessing.
The useful question is: which costs are provider charges, which are ongoing work, and who is responsible when something stops working?
For one documented deployment rather than a general price promise, see the Navarro article. Keep its original cost context attached to it.
Source, dates, and what this page verifies
Based on the complete supplied project/article account. Original publication dates and source URLs are retained. This is an edited reference, not a published update or a new audit of the original application.
Official technical clarifications checked September 29, 2026 are explicitly marked and linked beside the relevant passages. They are distinct from the original author's historical claims. The jq and Docker excerpts remain unchanged and carry their source limitations.
New interactive examples are bounded local teaching tools; they do not scan a website, process credentials, contact AWS, build an image or report a production measurement. No repository, staff account, service terms, résumé, price or live backend was changed.
See docs/batch-6/SOURCE-REVIEW.md for the separation of source-derived claims, external documentation and authored illustrations.