Skip to main contentSkip to navigationSkip to footer
    Cloud · Service

    Push to Git.
    Live in 300 cities.

    Your repository, connected to Cloudflare Pages. Every push builds and goes live on Cloudflare's network, every branch gets its own preview URL, and the last release is one click away.

    See pricing
    At a glance
    From $0
    One-time setup: one site, one domain. Hosting plan $99 a year
    0+
    Cities on Cloudflare's network
    0
    Builds a month at no charge on Cloudflare
    WHAT'S INCLUDED

    Repository to domain. Set up once.

    The Starter package covers one site, one domain, production and preview, up to 25 redirect rules and two rounds of changes after you review the preview. More sites and environments are quoted in writing, and the add-ons below are priced on their own.

    The pipeline
    01
    Cloudflare Pages project connected to your GitHub or GitLab repository
    02
    Build command, output folder and Node version set for your framework
    03
    Environment variables for production and preview, kept out of the repository
    04
    A preview URL for every branch and pull request
    05
    Production deploys from the main branch only
    Domain and delivery
    01
    Custom domain, with DNS records on Cloudflare
    02
    SSL certificate issued and renewed by Cloudflare
    03
    Redirects from www, old paths and the previous host, up to 25 rules
    04
    Cache and security headers in a _headers file
    05
    Workers, D1, KV and R2 are priced add-ons, listed below
    Handover
    01
    One-click rollback, shown on your own project
    02
    Alerts when a deployment fails
    03
    A written runbook: deploy, preview, roll back, add a domain
    04
    A 30-minute handover call on the Cloudflare dashboard
    Priced add-ons
    01
    Workers, edge code such as a form handler or API route: $169
    02
    D1 database and KV storage, schema and bindings set up: $169
    03
    R2 object storage for images and uploads, with access rules: $79
    04
    Each add-on is tested on a preview URL before it goes live
    WHAT IT COSTS

    Setup from $69.

    Setup is a one-time price. After setup, the Cloudflare Pages hosting plan is $99 a year. Workers, D1 and KV, and R2 are add-ons. Cloudflare's own usage is billed to your account, and its entry plan costs nothing.

    $0
    Setup, one time
    One site, one domain, production and preview, up to 25 redirects, two rounds of changes. More sites, environments and redirects are quoted in writing.
    $0
    Hosting plan, a year
    Cloudflare Pages hosting after setup, billed yearly. Optional: you can run the project yourself from your own account.
    $0
    Workers, or D1 and KV
    Each is an add-on, priced once. R2 object storage is $79.
    0–3 wk
    Typical Cloud plan
    For a full move to Cloudflare. A single site is shorter, and the scope sets the date.
    0 min
    First call
    The repository, the framework and the domain, then a written scope.
    HOW LONG

    Four steps. One switch.

    The current site keeps serving visitors until DNS moves. The scope puts a date on each step.

    01
    In your account

    Repository

    Your Git repository connected to a Pages project in your Cloudflare account.

    02
    On a preview URL

    Build pipeline

    Build command, environment variables and output set. The site builds and runs on a pages.dev address.

    03
    At the switch

    Domain and DNS

    DNS records copied, custom domain attached, SSL issued, redirects tested. Then the switch.

    04
    After launch

    Monitoring

    Deployment alerts set, rollback shown, runbook handed over.

    IF IT GOES WRONG

    The old site stays up.

    Until DNS points at the new one.

    01

    Proved on a preview URL

    The site builds and runs on a pages.dev address before the domain moves.

    02

    One click back

    Cloudflare keeps every deployment. Returning to the previous one is a single click in the dashboard.

    03

    A failed build changes nothing

    If a build breaks, the live site keeps serving the last good deployment.

    04

    Your account, your repository

    The project sits in a Cloudflare account in your name, connected to a repository you own.

    05

    Scope in writing

    Sites, environments, domains and redirects are listed before work starts. A change is priced before it is made.

    06

    Bugs fixed

    Anything in the delivered scope that does not work as agreed is fixed as part of the setup.

    WHO IT'S FOR

    Sites in Git. Shipped often.

    If the second list sounds closer, start with the page it names.

    Cloudflare Pages fits

    • 01
      A static or Jamstack site

      React, Next.js, Astro, Vue, Svelte or plain HTML, served from Cloudflare's network, with edge code, a database or storage added when needed.

    • 02
      A team that reviews before it ships

      Every pull request gets its own URL to open on a phone before it merges.

    • 03
      A site still uploaded by hand

      FTP uploads and manual SSL renewals, replaced by a push to Git.

    • 04
      A launch that cannot go dark

      Deploys with no maintenance window, and a way back if one goes wrong.

    Start somewhere else

    • 01
      There is no site yet

      Website Development builds it on React, Next.js, Astro or TanStack Start, and deploys it as part of the build.

    • 02
      A WordPress or PHP site

      Pages serves built files, not PHP. Linux & WordPress Hosting is the better home.

    • 03
      A Shopify store

      Shopify hosts Liquid themes itself. See Shopify Theme Development.

    STANDARDS YOU CAN CHECK

    Checked. Then switched.

    Each one is checked before the domain moves.

    01

    Builds from a clean clone

    The build runs from the repository alone, with a pinned Node version and a lockfile.

    02

    HTTPS on one host

    HTTP redirects to HTTPS, and www and the bare domain resolve to one canonical address.

    03

    No secrets in Git

    Keys and tokens live as encrypted environment variables in Cloudflare, never in the repository.

    04

    Preview kept apart

    Preview and production use separate variables, and preview URLs are kept out of search results.

    05

    Redirects tested

    Every old URL on the redirect list returns a 301 to a live page, checked before and after the switch.

    06

    Runbook in the repository

    Deploy, preview, rollback and domain steps written in the README, next to the code.

    BEFORE YOU BRIEF

    Before the first push.

    Cloudflare bills your own account. Its entry plan costs nothing and includes 500 builds a month, any number of sites, and no bandwidth meter on static files. Paid plans raise the build limits. The scope says which plan your site needs, and why.
    Yes. The Cloudflare Pages hosting plan is $99 a year. It is optional: the project sits in your own Cloudflare account either way, and you can run it yourself after handover. What the hosting plan covers is written in the scope.
    React, Next.js, Astro, Vue, Svelte and plain HTML. Anything that builds to static files deploys as it is. Where a framework renders on the server, that code runs on Cloudflare Workers, and the scope says so before work starts.
    Yes. The domain stays with your registrar. Its nameservers point to Cloudflare, which then issues and renews the SSL certificate. Every existing DNS record, email included, is copied across before the switch so mail keeps arriving.
    No. The site is built and checked on a pages.dev address while the current host keeps serving visitors. DNS moves only after the preview is approved, and the old host stays in place until the new one is confirmed.
    A build that fails never replaces the live site. A build that succeeds but looks wrong is rolled back from the Pages dashboard in one click, because Cloudflare keeps every earlier deployment. The runbook shows where that button is.
    A deploy is a build, then an upload. The build takes about as long as it does on a laptop. When it finishes, Cloudflare publishes the files across its network. The dashboard shows the time taken by every deployment.
    Yes, with Cloudflare Workers, which run code at the edge beside the site. Workers are an add-on at $169, on top of the $69 deployment. A form handler, an API route or a redirect service is scoped in writing first.
    Both are add-ons. D1 (a SQL database) and KV (key-value storage) are $169 together. R2 object storage for images, uploads and downloads is $79. Cloudflare's own usage is billed to your account, and its entry allowances are published by Cloudflare.
    You do. The Pages project sits in a Cloudflare account in your name, connected to a Git repository you own. Any developer you hire later starts with the full history.
    4 SERVICES · CLOUD

    More in Cloud.

    Your repository.
    Live.

    A 30-minute call about the site and where it runs today. A written scope after it.

    See pricing