The best Netlify alternative depends on what you are leaving. A Hugo blog is mostly a build and DNS migration. A site using Netlify Forms, Functions, Identity or server rendering is an application migration too.
This guide compares six alternatives, then walks through the checks needed to move a static site safely. It includes DanubeData, the platform we operate, alongside services that may suit a different workflow.
Last reviewed: 2 November 2026. Provider documentation and public plans are linked below. Prices keep their original currencies; this is not a latency benchmark or a tested migration report.
Reasons to switch, and reasons to stay
You want a different pricing model
First check your account. Netlify currently advertises Free with 300 monthly credits, Personal at $9/month and Pro from $20/month with unlimited members. Older accounts may retain Legacy plans. The old $19-per-member, 100 GB and 300-build-minute baseline should not be used as the universal current offer.
With credits, release frequency and delivery usage matter together. Look at production deploys, requests, bandwidth, compute and recharge settings. Moving to a different host can change the units you pay for, but it does not remove the need to budget for traffic and any external services.
You want a different workflow or hosting location
A directory-first CLI, repository documentation, a shared full-stack platform or a German origin can each justify a different shortlist. Record the requirement precisely. “European hosting” might mean the origin, stored content, logs, build processing or all of those; a global CDN and a single-region origin answer different questions.
You want less coupling
Generated HTML, CSS and JavaScript are portable. A platform form endpoint or authentication service is a dependency. Replacing it has implementation and operating costs. Staying on Netlify can be sensible when those services already work and the total bill is acceptable.
Alternatives at a glance
| Platform | Good starting use case | Main migration check |
|---|---|---|
| GitHub Pages | Public repository documentation | Usage policy, routing and Actions workflow |
| Cloudflare Pages | Static delivery on an edge network | Pages limits and Workers dependencies |
| Vercel | Next.js applications with runtime features | Static export versus SSR and paid access |
| Render | Frontend alongside application services | Workspace bandwidth and pipeline usage |
| Surge | Publish a built directory from a CLI | CI automation and paid request features |
| DanubeData Static Sites | Static output hosted in Germany | Team plan capacity and separate backends |
1. GitHub Pages: repository documentation
GitHub Pages fits a project whose documentation and source belong in the same repository. Public repositories can use Pages with GitHub Free; private-repository availability depends on the GitHub plan. Jekyll is supported, and a custom Actions workflow can publish another generator's output.
GitHub's limits include a 1 GB published-site limit and a soft 100 GB monthly bandwidth limit. The soft 10-builds-per-hour limit does not apply to a custom GitHub Actions publishing workflow; that does not make Actions usage unlimited.
- Useful: documentation can be reviewed with the source, with custom domains and HTTPS.
- Check: nested client-side routes, access requirements and whether the site fits the usage policy.
- Boundary: GitHub explicitly restricts using Pages as free hosting for an online business, e-commerce or a site primarily facilitating commercial transactions or SaaS. It is not a universal replacement for a business frontend.
For a wider shortlist in this category, see GitHub Pages alternatives.
2. Cloudflare Pages: static delivery and the Workers ecosystem
Cloudflare is worth evaluating when delivery traffic dominates the bill. Its Pages pricing separates static asset requests from metered Functions. A site serving files and a site invoking a function on every request have different costs.
Pages build limits are 500 monthly builds/one at a time on Free, 5,000/five concurrent on Pro and 20,000/20 concurrent on Business. Concurrency is per account. Custom domains are limited per project to 100, 250 and 500 respectively. Workers Paid is not the name of a Pages tier with 20 concurrent builds.
- Useful: Git deployments, previews and direct-upload workflows.
- Check: runtime compatibility, build duration, file limits and any KV, D1 or R2 integration.
- Boundary: forms, authentication and data-location requirements need their own design. For restricted previews, investigate Cloudflare Access rather than assuming all protection requires custom code.
3. Vercel: Next.js beyond static files
Vercel deserves a close look if the reason for moving is framework support rather than a smaller static-hosting bill. Next.js server rendering, regeneration and runtime integrations are a different requirement from uploading a prebuilt directory.
Pro starts at $20/month; developer access and metered services affect the final cost. The current page lists Flat Rate CDN, so older fixed-bandwidth overage examples should be re-quoted. Hobby is for personal, non-commercial use.
- Useful: a framework-aware build and preview workflow for applications.
- Check: image optimization, server handlers, middleware, environment variables and revalidation.
- Boundary: a static-only host cannot run those server features simply because it accepts Next.js output. Export the site or keep a compatible runtime.
4. Render: frontend and backend in one workspace
Render Static Sites provides repository-triggered deployments, custom domains and a global CDN. Static sites count against the workspace's included outbound bandwidth and pipeline minutes. Read the current workspace plan rather than assuming an old 100 GB/500-minute bundle applies.
- Useful: keeping a frontend near the workflows for APIs, workers and databases on the same platform.
- Check: redirects, SPA rewrites, previews, protected content and the total workspace bill.
- Boundary: an API hosted as a web service is a separate service. Free web-service sleep behaviour should not be described as a static-site cold start.
A shared dashboard does not prove that all services run in one region or have the same availability. Choose backend regions and recovery options deliberately.
5. Surge: publish a built directory
Surge offers a direct CLI workflow for a site you build locally or in CI. The current plans list a free account tier and Pro at $30/month. Free now includes custom domains and certificates, previews, revisions and collaborators; an older comparison saying it has no previews or collaboration is out of date. Pro adds request features including password protection and redirects/rewrites.
- Useful: shipping a static directory without coupling publishing to a hosted build pipeline.
- Check: who builds the output, token scope, domain ownership and how CI failures stop publication.
- Boundary: application code that needs a persistent backend still needs another service.
A CLI push is convenient for a prototype, but production deployments should still be reproducible. Pin dependencies, preserve the output and record which commit was published.
6. DanubeData Static Sites: German hosting and a team plan
DanubeData Static Sites hosts static output in Germany, with Git, CLI and ZIP deployment. Managed TLS, basic authentication and deployment history cover common publishing needs. Dynamic backends are separate, for example on Rapids.
| Plan, excluding VAT | Sites/team | Storage/site | Monthly bandwidth | Domains/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 site count. This is a team plan, so adding a colleague does not use an old Netlify-style seat calculation. Check output size and domains per site as well as the number of sites.
- Useful: exported documentation, landing pages and frontends when Germany is the required hosting location.
- Check: routing, build requirements, usage allowance and integrations that previously ran on Netlify.
- Boundary: uploading files does not replace Forms, Identity, Functions or a server-rendering runtime.
Feature checklist before choosing
Instead of treating a row of checkmarks as equivalent functionality, write down the behaviour you need:
- Deployments: Git provider, monorepo root, build command, output directory and branch controls.
- Previews: who can see them, how they expire and whether they use production APIs.
- Routing: redirects, rewrites, trailing slashes, clean URLs and genuine 404 responses.
- Protection: production versus preview access, HTTPS and whether assets can bypass authentication.
- Recovery: a known previous build, activation steps and separate recovery for forms or databases.
- Operations: logs, secrets, usage alerts, ownership and support needs.
A cost scenario that does not multiply old seat prices
Suppose three people maintain five static sites with 50 GB of total monthly transfer. That is enough to shortlist capacity, but not enough to calculate a Netlify credit bill: how many production deployments and requests occur, and is there compute? A current Pro quote starts with its tier and usage, not $19 × three.
For DanubeData, Starter has capacity for up to ten sites and the displayed 100 GB monthly bandwidth allowance, subject to account and per-site limits. Twelve months at €2.99 is €35.88 excluding VAT before any other charges. This is a plan calculation, not a claim that it replaces every Netlify service.
On other providers, include CI, runtime, paid access and external form or authentication services where required. Keep USD and EUR separate or state the exchange rate. A percentage-saving claim based on different feature sets or an old contract is not a useful buying decision. The three-provider comparison includes explicit credit arithmetic.
Migration checklist: Netlify to a static host
The following is a rehearsal checklist, not a report of a completed migration. Work on a temporary domain first and retain the current site through cutover.
Use the downloadable static-site migration fixture to exercise local static-export checks. It checks the fixture only; it is not evidence of a live Netlify or DanubeData deployment, form delivery, DNS cutover or TLS provisioning. Follow the included README and run your own site checks as well.
1. Inventory the dependencies
Review netlify.toml, _redirects, _headers, build plugins and environment settings. Search the application for Netlify endpoints and SDKs. List forms, authentication, functions, edge functions, image handling, scheduled work and any CMS webhooks. Record what must move, be replaced or remain on a separate service.
Separate build-time variables from browser-visible configuration. A value embedded in JavaScript is public; do not copy server secrets into a frontend environment setting.
2. Reproduce the static build
Use the same source commit, runtime version and dependency lockfile. Record the build command, working directory and output folder. With a static export, confirm the generated files contain the routes you expect. If the project requires request-time server code, choose a runtime host or redesign that part before proceeding.
3. Deploy without changing production DNS
On DanubeData, start from the Static Sites product page and choose Git, CLI or ZIP. For ZIP, package the built output at the expected archive root. Set the build/output settings to match the project. Use the temporary site address to inspect the result.
4. Check real URLs and external state
- Load the homepage and refresh a nested route directly.
- Request a missing page and a missing JavaScript file; confirm the intended status and body.
- Check redirect status codes, query strings, slash behaviour and caching headers.
- Test images, fonts, downloads, canonical URLs, robots rules and the sitemap.
- Submit a harmless test form and verify receipt, storage and spam controls.
- Check login, logout and a protected page if authentication exists.
- Verify intended preview access controls and inspect browser/network errors.
- Check analytics and consent behaviour without assuming a host change configured them.
5. Cut over domains and verify TLS
Record the old DNS values. Lower TTL ahead of time if appropriate, then add and verify the custom domain using the new host's instructions. Use its displayed record values; do not assume every apex domain can use an ordinary CNAME. After the change, check both apex and www, HTTPS, certificate coverage and redirects from more than one network.
6. Keep a rollback path
Keep the old deployment and its settings available until traffic and application checks pass. DNS rollback is not instant while caches expire. If forms or another write path moved, decide how new submissions will be reconciled before reverting. Rolling back static files does not roll back external data.
Location and performance need separate checks
European hosting can be a requirement, but it does not by itself make an application compliant. Inventory logs, forms, analytics, processors, retention and third-party assets. A German origin does not control a script that sends visitor information elsewhere.
For speed, test the same output from your audience's regions, with warm and cold caches recorded. Compare build duration separately from page load. We have not measured provider latency or completed a hosted migration for this article, so the old 20–50 ms versus 100–150 ms estimates are not used.
Which alternative should you choose?
For repository documentation, start with GitHub Pages and its policy. For large static traffic, evaluate Cloudflare. For Next.js runtime features, evaluate Vercel. For a frontend and API in one workspace, compare Render. For directory-first publishing, try Surge. For static output hosted in Germany with a team plan, compare DanubeData.
Use the migration checklist to test the choice before changing the domain. View DanubeData Static Sites plans and deployment options, or ask about a specific migration requirement.