Frameworks · Updated 10 November 2026 · 10 min read

Where to host a Gatsby site in Europe in 2026

Q: Which folder do I deploy for a Gatsby site?

public. After a successful gatsby build, Gatsby puts everything the site needs in the public folder at the root of your project, including the HTML for each page, minified files and transformed images.

Six European places to put a Gatsby build, what happens to SSR, DSG and Gatsby Functions on each, and what you'll pay.

View as Markdown

Most Gatsby sites are fully prerendered, so any host that runs gatsby build and serves the public folder will do. Eurobase builds and serves that folder from Git at a flat €10 or €20 a month and leaves room for an API or server code later, statichost.eu documents a ready Gatsby configuration and has a free plan, and Clever Cloud serves it as a Static application billed by the second. If your pages use server-side rendering or Deferred Static Generation, you need a running Node server instead, which Sliplane or Coolify on Hetzner can give you.

Gatsby hosts in Europe at a glance

Platform	Company	Serves a static Gatsby build	SSR and DSG	Starts at
Eurobase	Warsaw, Poland	Yes, as a Static site	Not documented	Free, then €10 a month + VAT
statichost.eu	Stockholm, Sweden	Yes, with a Gatsby example config	No	Free for 1 site, then €9 a month
Clever Cloud	France	Yes, as a Static application	Not documented	Free credits, then billed per second
Codeberg Pages	Codeberg e.V., Berlin, Germany	Yes, built in CI	No	Free for open-source projects
Sliplane	Berlin, Germany	Yes, in a container	Yes, if you run a Node server	€9 excl. VAT
Coolify on Hetzner	Open source, on a German host	Yes, on your server	Yes, if you run a Node server	Free software, servers from €5.49 a month excl. VAT

Prices come from each provider's own page as of 10 November 2026.

What to check before you move a Gatsby site

Which rendering modes you use. Static Site Generation is Gatsby's default and needs no server after the build. Deferred Static Generation and server-side rendering, set per page since Gatsby 4, need a server that keeps running after the build.
Gatsby Functions. Gatsby leaves these serverless endpoints to an adapter, which wraps them for the platform you deploy to. Its only official adapter is gatsby-adapter-netlify, so on a European host you'd usually turn those endpoints into a separate API.
Build time and memory. Large Gatsby sites with many images take a while to build. Compare each host's build limits with how long gatsby build takes on your machine.
Node.js and package manager. Gatsby 5 needs Node.js 18 or later. Check that the host's build image has a version your lockfile accepts.
404 pages and redirects. Gatsby builds your src/pages/404.js as 404.html, but the server still has to send missing paths there. Redirects you define in Gatsby also need a host or adapter that applies them.

1. Eurobase

Eurobase's V8 isolate runtime has no Gatsby support, so a Gatsby repository goes into a container project. Pick Static site rather than Web service, point the build command at the build script in your package.json and enter public as the Output directory. Eurobase runs the script and serves the result with NGINX, on European infrastructure run by Scaleway, a French provider. Each build has 4 vCPU, 6 GB of memory and up to 20 minutes. Code can live on GitHub, GitLab, Codeberg, Forgejo or Gitea, and a coding agent can ship the site through the Eurobase MCP server or CLI.

Best for: prerendered Gatsby sites that might later sit next to an API, a function or a server-rendered app in the same workspace.
Price: the Free plan covers 2 projects. Paid workspaces cost €10 a month on Starter or €20 on Pro, + VAT, and members don't add to the bill. Eurobase doesn't bill for usage today. Once a limit is reached, further work is refused, apps on V8 isolates and Functions wait for the monthly reset, and static sites and containers stay online.
What it lacks: Eurobase doesn't suggest Static site for Gatsby, so you set the type and folder by hand. A missing path gets index.html back, not Gatsby's 404.html, and its docs don't cover Gatsby Functions, SSR or DSG. Only npm and Yarn 1 lockfiles build. Pull requests get no preview deployments, and neither ISO 27001 nor SOC 2 has been awarded yet, as both are still underway.

Read Deploy a static site and Containers and static sites for the settings.

2. statichost.eu

statichost.eu, run from Stockholm, hosts static sites and nothing else. Its guides give a ready Gatsby configuration: a node:22 build image, npx gatsby build as the command and public as the folder to publish. It pulls code with plain git clone from any provider, can roll back at once, and states that its whole stack sits on infrastructure owned by European companies.

Best for: a fully prerendered Gatsby blog, docs or marketing site.
Price: the Hobby plan costs nothing and covers a single site with 10 GB of bandwidth and 100 minutes of builds. Starter at €9 a month lifts that to unlimited sites, 500 GB and 5,000 build minutes, and Professional is €49 a month. VAT isn't mentioned on the pricing page.
What it lacks: any server rendering. Its Gatsby guide warns that API routes and server-rendered pages won't work, and branch preview links are still marked as coming soon.

3. Clever Cloud

A Static application on Clever Cloud runs your build, then serves the files with Static Web Server or Caddy on pico, its smallest instance size. Its docs don't name Gatsby among the generators it builds on its own, so you put gatsby build in CC_BUILD_COMMAND and /public in CC_WEBROOT. A sws.toml file with page404 set to 404.html gives you Gatsby's error page.

Best for: a Gatsby site whose backend or database already runs on Clever Cloud.
Price: it depends on how large and how many instances you run, metered per second. Signing up brings free credits and asks for no card.
What it lacks: a Gatsby guide, and a plain monthly figure for a Static application on its pricing page.

4. Codeberg Pages

Codeberg is run by Codeberg e.V., a non-profit based in Berlin. Its Pages service publishes static files at username.codeberg.page or on a domain you own. Gatsby needs a build step, so you'd run it in Forgejo Actions and deploy the output from there. You can set your own 404 page, redirects and rewrites.

Best for: docs and project sites of open-source projects already hosted on Codeberg.
Price: free.
What it lacks: a home for closed-source sites. A repository website must be public, and Codeberg exists for free and open-source projects. Nothing server-side runs there.

5. Sliplane

Sliplane GmbH, a Berlin company, bills you per server and lets you fit as many containers on each one as it can carry. Your framework is picked up automatically, or you supply a Dockerfile or a finished image. Gatsby documents SSR and DSG as fully supported with gatsby serve, a Node process you could keep running in a container here, started with -H 0.0.0.0 so it accepts outside traffic.

Best for: Gatsby sites with DSG or SSR pages, built by people who are at ease with containers.
Price: €9 excl. VAT for its smallest server, which has 1 vCPU, 1 GB of RAM and 20 GB of storage. You can try a demo server free for 48 hours.
What it lacks: a Gatsby guide. Gatsby's CLI reference also presents gatsby serve as a way to test the production build before you deploy, so load-test it with your own traffic first. Sliplane has US and Singapore regions too, so check the region before you create the server.

6. Coolify on Hetzner

Coolify is open-source and free to self-host. It builds each commit from a Git host, GitHub, GitLab and Gitea included, ships it to any server it reaches over SSH, and renews Let's Encrypt certificates for your domains. On a Hetzner server it can serve the static public folder or keep gatsby serve running for SSR and DSG pages.

Best for: developers who want their own server and the smallest monthly bill.
Price: Coolify itself is free when you host it. On Hetzner, a CPX02 is listed at €5.49 a month excl. VAT in Helsinki or €6.49 in Falkenstein and Nuremberg, yet on 10 November 2026 those entry plans couldn't be ordered.
What it lacks: support. Updates, backups and a server that falls over at night are your job.

How to choose

Run gatsby build locally and check whether any page exports getServerData, defers its build or calls a Gatsby Function. If none do, your site is fully static.
For a static site, go with Eurobase when an API or a coding agent is in the plan, statichost.eu when you want the Gatsby settings filled in for you, Clever Cloud when the rest of your stack is already there, or Codeberg Pages for an open-source project.
For SSR or DSG pages, pick Sliplane or Coolify on Hetzner and run a Node server, or turn those pages back into static ones.
Move Gatsby Functions to a separate API before you switch hosts, then copy environment variables and point your domain at the new host.

For more static hosts, see static site hosting in Europe. Leaving Netlify? Read European Netlify alternatives and the guide to move from Netlify.

Frequently asked questions

Which folder do I deploy for a Gatsby site?

public. After a successful gatsby build, Gatsby puts everything the site needs in the public folder at the root of your project, including the HTML for each page, minified files and transformed images.

Can I host a Gatsby site for free in Europe?

Yes, as long as the build is static. One site fits statichost.eu's Hobby plan, the Eurobase Free plan takes 2 projects with hard limits, and Codeberg Pages costs nothing for open-source work. Clever Cloud starts you off with free credits.

Do Gatsby SSR and DSG work outside Netlify?

They can, but you supply the server. Gatsby's docs say both need a running Node.js server and are fully supported with gatsby serve, and the only official adapter is for Netlify. Container hosts such as Sliplane, or your own server with Coolify, can run that process. Static-only hosts can't.

What happens to Gatsby Functions when I leave Netlify?

They won't run on a static host. Rewrite each endpoint as a small API on a platform that runs server code, and call it from the site by URL.

Does Gatsby still need Node.js to build?

Yes. Gatsby 5 dropped Node.js 14 and 16 and needs Node.js 18 or later. Eurobase builds with Node.js 20, 22 or 24, and the statichost.eu Gatsby preset uses a node:22 image.