# What it means to host a website on Cloudflare Static assets and dynamic application requests have different limits and billing behavior. A brochure site can keep most public pages static while processing enquiries separately. An article can be delivered as an HTML asset while its contact form posts to a Worker that validates and stores the enquiry. Free-tier eligibility is conditional; it is not a promise of unlimited dynamic processing or free domain renewal. A deployment record should identify which checks were local and which were performed against the real production host. Local database writes prove that the local flow can work; they do not confirm a remote binding, secret or domain rule. If an owner-controlled account setting prevents live verification, record that specific dependency rather than publishing an invented success URL. Keep the free-tier discussion operational. State which services are being used, where their current limits are documented and what should be monitored. Avoid treating a count of requests as a count of people, especially when bots and repeated asset requests are involved. The business needs to understand what would fail if a dynamic limit were reached and which public pages remain independent. This is a more useful promise than describing the deployment as universally free without explaining the actual request paths and responsibilities. ## Separate public file delivery from application work A promotional website often contains information that can be prepared ahead of time: home, service pages, package descriptions and articles. These can be generated as static HTML and delivered with images, styles and other assets. A contact form has a different job because it receives new information and must validate and store or deliver it. Treating these two paths separately makes the system easier to understand. Cloudflare Workers Static Assets supports serving prepared site files alongside Worker code. The official documentation distinguishes requests served as static assets from requests that invoke the Worker. This distinction matters for plan limits and operating behavior. A statement that a site is on Cloudflare does not, by itself, describe which requests execute code or which limits apply. For an illustrative brochure site, an article can be served directly as a file while the enquiry endpoint runs validation and storage logic. The static page should not need to execute the application solely to display its body. This arrangement can also make the public information less dependent on a dynamic operation that is temporarily unavailable. ## Understand what free hosting does and does not mean A free plan has documented conditions. Check the current official limits when configuring and reviewing the deployment rather than copying an old number from a blog post. Pay attention to the distinction between static delivery, dynamic requests, storage and other products used by the application. These are not interchangeable measures of visitor capacity. If routing is configured so that matching requests always run the Worker first, those requests follow the Worker’s applicable limits. The Cloudflare documentation explains that exceeding the relevant free-tier request allowance can cause those routed requests to fail rather than fall back automatically to static delivery. Routing is therefore part of the architecture, not merely a deployment detail. Free static hosting does not include domain registration, domain renewal, every external integration or continuing maintenance. A business mailbox may use a separate provider. Paid tools should remain explicit operating items. Do not interpret a free hosting option as a guarantee of infinite dynamic processing or a promise that all future features have no cost. ## Plan accounts, environments and checks Keep the owner’s account and project boundaries clear. A preview should use an isolated environment and should not copy live enquiry data unnecessarily. The production site needs its own correct configuration, database bindings and secrets where applicable. Never place private secrets into public assets or a general content configuration. Domain setup is another separate task. Confirm ownership and authorization before modifying DNS, preserve unrelated records such as email configuration and avoid changing other projects. A custom-domain deployment should be checked on that real hostname, including secure access, canonical behavior and the contact endpoint. A successful local build does not prove those external settings are ready. Before release, inspect the generated asset count and file sizes, test missing-page behavior and verify that public content is available without a client-side application having to construct it. Test the form in the appropriate environment and inspect the resulting record. A page that loads correctly does not establish that its database or anti-spam secret is configured. After release, keep a small operational record: which project serves the site, which storage receives enquiries, who reviews failures and where current platform-limit documentation can be found. Record any live checks that were not performed instead of assuming local results apply to production. The practical benefit is an understandable deployment: public information can be delivered as prepared files, while the limited dynamic work is handled deliberately. Whether a particular customer project fits a free tier depends on its implementation and usage. The written proposal should describe that fit and its boundaries, rather than selling the provider’s name as a universal lifetime-cost guarantee. ## Practical checklist - Inspect current plan limits - Separate preview and production - Monitor form failures **A concrete example:** An article can be delivered as an HTML asset while its contact form posts to a Worker that validates and stores the enquiry. **A boundary to keep clear:** Free-tier eligibility is conditional; it is not a promise of unlimited dynamic processing or free domain renewal. ## Your next step [Tell Orvunweb about your project](/en/start-a-project/) ## Related reading - [Domain, hosting and SSL explained](/en/blog/domain-hosting-and-ssl-explained/) - [Static website or content management system?](/en/blog/static-website-or-content-management-system/) - [Protecting contact forms against spam](/en/blog/protecting-contact-forms-against-spam/) - [Business website service](/en/services/business-website/) - [Compare packages](/en/pricing/) ## Related services - [Business website](/en/services/business-website/) --- Locale: en Canonical: https://orvunweb.com/en/blog/what-it-means-to-host-a-website-on-cloudflare/ Updated: 2026-09-16 - [Cloudflare — Static Assets billing and limits](https://developers.cloudflare.com/workers/static-assets/billing-and-limitations/)