Cloudflare Pages, Netlify and Vercel can all publish a static site from Git. The useful distinction is what happens beyond the generated files: functions, forms, previews, framework adapters, access controls and billing.
For a documentation site or exported frontend, start with the static output and your traffic budget. For an application using server rendering or platform services, compare those dependencies before moving. DanubeData is included as an option for teams that want static hosting in Germany.
Last reviewed: 2 November 2026. Prices below retain their original currencies; tax and usage charges can change the total. This is a documentation-based comparison, not a performance benchmark. We operate DanubeData.
Quick verdict
| Your priority | Start by evaluating | Decision to check |
|---|---|---|
| Static files with substantial public traffic | Cloudflare Pages | Static delivery pricing and Pages build limits |
| Forms and integrated deployment workflow | Netlify | Credit consumption and dependencies on Netlify services |
| Next.js with server rendering or ISR | Vercel | Framework features, developer seats and metered services |
| Static output hosted in Germany | DanubeData Static Sites | Team plan limits and any backend you need separately |
There is no measured fastest platform in this article. An edge network can help distant visitors, but cache rules, asset size, application code and the visitor network all affect the result.
Cloudflare Pages
Cloudflare Pages combines Git builds and preview deployments with static delivery on Cloudflare's network. Pages Functions use the Workers runtime; check runtime compatibility before assuming that a Node.js application can run unchanged.
Builds and domains have plan limits
| Pages limit | Free | Pro | Business |
|---|---|---|---|
| Builds per month | 500 | 5,000 | 20,000 |
| Concurrent builds per account | 1 | 5 | 20 |
| Custom domains per project | 100 | 250 | 500 |
These are the tiers in Cloudflare's Pages limits. A Workers Paid subscription is a separate billing decision; it does not by itself turn the Pro build allowance into the Business allowance. The limits page also documents build timeouts, file limits and a soft project limit, so “unlimited everything” is misleading.
Pages pricing documentation distinguishes free, unlimited static asset requests from metered Functions. Budget for any Workers, storage or database services you attach. A static homepage does not make its API free.
Where it fits
- A largely static site with traffic that would otherwise consume a bandwidth allowance.
- A team already comfortable with Cloudflare routing and the Workers ecosystem.
- A project whose build can stay within the account's build concurrency and duration limits.
Check form handling, authenticated previews and framework adapters separately. Cloudflare Access is an option to investigate for restricted previews; lack of a built-in basic-auth toggle does not mean custom Workers code is the only access-control route. Review what a global cache may serve and where logs and dynamic services process data if location matters to your requirements.
Netlify
Netlify's appeal is the surrounding workflow: repository deployments, previews, forms and functions. Those features can save application work. They also become part of a migration's scope if the site relies on them.
Current credits and legacy accounts
| Current advertised plan | Base subscription | Monthly credits |
|---|---|---|
| Free | $0 | 300 hard limit |
| Personal | $9/month | 1,000 |
| Pro | From $20/month, unlimited members | From 3,000 |
The current pricing page replaces the old universal $19-per-member comparison. Netlify's credit-plan documentation says accounts created from 4 September 2025 use credit-based plans; earlier accounts may retain Legacy plans. Check your team's actual plan before using a migration cost estimate.
On the documented credit model, production deployments cost 15 credits each, bandwidth 20 credits/GB, web requests 2 credits per 10,000 and compute 10 credits/GB-hour. These meters share the allowance. Preview deployments do not consume production-deploy credits, but their traffic still counts. Form submissions are currently listed as free and unlimited. Check auto-recharge settings and the effect of reaching a limit.
Where it fits
- Teams using Forms or Functions that would otherwise have to build and operate replacements.
- Content and frontend workflows that benefit from deploy previews and integrated build tooling.
- Projects whose measured traffic and release frequency fit a credit tier.
Do not count team size twice: the current Pro offer includes unlimited members. Conversely, do not compare only the subscription price when the site has frequent production releases or large downloads. Review authentication dependencies individually rather than assuming an old Identity integration is a portable part of the static files.
Vercel
Vercel is a natural candidate for Next.js applications using server rendering, incremental regeneration and framework-aware deployment. For a static export, compare the simpler file-hosting requirements too: using Next.js does not automatically require a running Next.js server.
The current pricing page advertises Pro from $20/month, $20 of included usage credit, paid developer seats and free viewer seats. It now lists Flat Rate CDN for Pro alongside separately priced builds, compute and other services. The old “1 TB then $40 per 100 GB” table is therefore not a reliable current quote.
Hobby is for personal, non-commercial use. A business should evaluate an eligible paid plan. Password protection also has plan or add-on conditions; it is not accurate to describe it as Enterprise-only.
Where it fits
- Next.js applications whose runtime features and previews reduce work for the team.
- Projects that need application hosting as well as delivery of generated files.
- Teams that can separate paid developer access from viewer access and monitor the services they consume.
Before leaving, inventory image optimization, middleware, revalidation, scheduled jobs and platform storage. Some have equivalents elsewhere, but they are not copied by downloading a deployment directory.
DanubeData Static Sites
DanubeData Static Sites serves static output in Falkenstein, Germany. It supports Git, CLI and ZIP deployment, managed TLS, basic authentication and deployment history. Applications needing a running backend belong on a separate service such as Rapids or a VPS.
| Team plan, excluding VAT | Sites per team | Storage per site | Monthly bandwidth | Domains per site |
|---|---|---|---|---|
| Free | 2 | 100 MB | 10 GB | 2 |
| Starter, €2.99/month | 10 | 500 MB | 100 GB | 10 |
| Pro, €9.99/month | 50 | 2 GB | 500 GB | 50 |
Account limits can lower the available site count. Plan choice is about sites and usage, rather than a fee for each teammate. A 2 TB traffic scenario exceeds the listed Pro allowance; do not treat €9.99 as an unlimited-bandwidth quote.
Compare the features your site actually needs
| Requirement | What to verify |
|---|---|
| Git and previews | Repository permissions, branch rules, preview URLs and who can view them |
| SPA routing | A direct request to a nested route, plus a genuine missing-asset 404 |
| Forms | Submission storage, spam controls, notifications and export |
| Functions and SSR | Runtime, supported dependencies, secrets, timeouts and database connectivity |
| Restricted access | Whether protection covers previews, production, assets and the intended users |
| Recovery | How to restore an earlier deployment and whether external state also needs recovery |
| Data location | Content, request logs, builds, APIs and third-party scripts separately |
Hosting in Europe is a location choice, not automatic GDPR compliance. Document processors, retention, analytics and external services for your own application. Do not infer a provider's legal suitability solely from its headquarters or CDN map.
Cost examples with explicit usage
Consider five developers maintaining a static site with 20 production deployments, 10 GB outbound transfer and 100,000 web requests in a month, with no compute or other metered services. On the Netlify credit rates above: 20 × 15 + 10 × 20 + 10 × 2 = 520 credits. That exceeds Free's 300 and fits Personal's usage allowance, but a team needing Pro collaboration starts with the Pro subscription, not five times an old seat price.
A release-heavy month changes the result. At 100 production deployments, 100 GB transfer and one million requests, the same calculation is 1,500 + 2,000 + 200 = 3,700 credits. That exceeds the base Pro allowance. Choose the applicable tier or additional credits and include any compute before estimating the bill. These are arithmetic examples, not observed customer usage.
For DanubeData, compare the same site's size, number of domains and monthly bandwidth with the team plans. For Cloudflare, check builds and attached runtime services. For Vercel, quote developer access and current usage terms. Keep USD and EUR separate unless you state an exchange rate and date. Neither a five-person team nor 100 GB transfer alone determines every provider's bill.
How to compare performance fairly
- Deploy the same output, compression settings and cache policy.
- Test a first request and a repeated request from the regions your visitors use.
- Measure HTML and large assets separately; report cache status and payload size.
- Check real-user loading and interaction metrics after a controlled rollout.
- Time builds independently of visitor performance. Dependency caching and generator versions can dominate build time.
We have not run those measurements for this refresh, so there are no latency numbers or fastest-provider claims here.
A practical decision guide
Choose the platform that removes the most work for your actual site. Cloudflare is worth evaluating when static delivery cost dominates. Netlify earns a place when its forms and deployment workflow are useful. Vercel is worth the runtime comparison for Next.js features. DanubeData fits static output when German hosting and a team plan match your needs.
For a migration inventory and cutover checklist, read the Netlify alternatives guide. For repository documentation, also compare GitHub Pages alternatives.
Frequently asked questions
Can I put any Next.js application on static hosting?
Only if it can produce the complete static output your application needs. Server-only handlers, per-request rendering and runtime image processing need a suitable backend or a different implementation. Verify your framework's export requirements before switching.
Is Netlify still priced per member?
Current credit-based Pro advertises unlimited members. Legacy contracts may differ. Use the account's billing plan and credit usage, rather than a historical comparison table.
Does a German origin keep every site interaction in Germany?
It does not determine where your analytics, forms, embedded assets or API calls go. Include those services and your operational access in the data-flow review.
Compare DanubeData Static Sites plans and deployment options before creating a site. Keep your current deployment available until the replacement passes your checks.