Frameworks · Updated 10 November 2026 · 8 min read

Where to deploy a Vite app in Europe in 2026

Q: Where do I put API keys in a Vite app?

Not in VITE_ variables. Vite writes their values into the JavaScript your visitors download. Keep secret keys on a server or in a function, and call it from the browser. On Eurobase, the same project can run that code on V8 isolates or as a Function.

Eurobase, statichost.eu, Clever Cloud, Scalingo and Bunny.net compared for a Vite build: who runs it, how deep links work, who the company is and what it costs.

View as Markdown

A Vite app is usually a folder of built files, so almost any host can serve it. The real differences are who runs vite build, whether deep links like /settings survive a refresh, and who the provider is. Eurobase builds Vite apps from Git with no settings and keeps a path open to server code, for €10 or €20 a month flat. statichost.eu suits a purely static build on a fully European stack, Clever Cloud and Scalingo fit teams that already run their backend there, and Bunny.net suits apps with readers worldwide, if you script the upload.

Vite hosts in Europe at a glance

Platform	Company	Who builds it	Deep links to index.html	Starts at
Eurobase	Warsaw, Poland	Eurobase, detected from `vite`	Built in	Free, then €10 a month + VAT
statichost.eu	Stockholm, Sweden	statichost.eu, from any Git provider	A `_redirects` rule you add	Free for 1 site, €9 a month for more
Clever Cloud	France	Clever Cloud, from `CC_BUILD_COMMAND`	Not documented	Free credits, then billed by the second
Scalingo	Strasbourg, France	Node.js buildpack, served by Nginx	A `try_files` rule you add	€7.20 a month for 256 MB, excl. VAT
Bunny.net	Ljubljana, Slovenia	You, locally or in CI, or its CLI	404 rewrite or `spa: true`	$1 monthly minimum, 14-day trial

Prices are from each provider's own page, checked on 9 and 10 November 2026. Bunny.net's figures are in US dollars.

What to check before you pick a host

Client-side routing. A React or Vue router handles paths in the browser. The host must answer an unknown path with index.html, or a refreshed deep link returns 404.
The `base` setting. Vite's docs say to set base to the subpath when a site lives under one, such as /<REPO>/ on GitHub Pages.
Variables baked into the bundle. Vite replaces import.meta.env values at build time, and its docs warn that VITE_ variables must not hold secrets. Secrets belong in server code, so check whether the host can run some next to your app.
`vite preview` isn't a server. The Vite docs say it's for checking the build locally, not for production. On a host that runs Node.js, something else has to serve dist.
Who the provider is. A data centre in Europe tells you where the files sit, not which country's law reaches the company running it. The EU region vs EU company page covers the difference.

1. Eurobase

Eurobase finds vite 6.1.0 or later in your lockfile, builds the app and runs it on V8 isolates with the Cloudflare Vite plugin, which it adds during the build. Static files and any server code share one address, and unknown paths go to index.html without a rule. For redirects and headers, put _redirects and _headers files in Vite's public folder. Public values such as VITE_API_URL go in Build as variables, not secrets.

If you'd rather serve the bundle from a container, pick Static site in a container project: Eurobase runs your build script, serves dist with Nginx and sends unknown paths to index.html. It pulls code from GitHub, GitLab, Codeberg, Forgejo or Gitea, and agents can ship through the Eurobase MCP server or CLI.

Best for: Vite apps that may need an API route, a function or a SQLite database later, on European infrastructure run by Scaleway, a French provider.
Price: a Free plan with 2 projects, then Starter at €10 and Pro at €20 a month + VAT for the whole workspace. There are no usage charges today: work over a limit is refused, apps on V8 isolates and Functions stop until the monthly reset, and containers and static sites keep serving.
What it lacks: preview deployments, servers outside Europe, managed Postgres, and KV, R2, Durable Objects or queues for server code. Its ISO 27001 and SOC 2 audits haven't finished, so it holds neither certificate today.

Start with Deploy a static site, and see the Workers runtime for server code limits.

2. statichost.eu

statichost.eu is a static-only host based in Stockholm. It fetches your repository with a standard git clone, so any Git provider works, builds it with a preset or any Docker image you name, and publishes the output. Its FAQ says no layer of the stack, DNS and CDN included, relies on a US cloud. For a Vite router, add /* /index.html 200 to a _redirects file in the output folder.

Best for: a Vite build with no server code, where a fully European supply chain matters more than features.
Price: one site is free on Hobby, within 10 GB of traffic and 100 build minutes. For €9 a month, Starter lifts the site limit and includes 500 GB, then €1 per 10 GB. Professional, at €49 a month, raises that to 1 TB and adds a performance CDN.
What it lacks: server code on its listed plans, and automatic preview links for branches, which its docs put on the roadmap.

3. Clever Cloud

Clever Cloud's Static runtime serves a folder with Static Web Server, or with Caddy when your project has a Caddyfile, on its smallest instance size, pico. It runs the build itself for generators it detects, such as Astro, VitePress and Nuxt. Plain Vite isn't one of them, so put your build in CC_BUILD_COMMAND and point CC_WEBROOT at /dist.

Best for: teams whose API and database already live on Clever Cloud and want the frontend next to them.
Price: per-second billing, after free credits that need no card.
What it lacks: a documented index.html fallback for client-side routes.

4. Scalingo

For a Vite build, Scalingo's docs on static-only apps offer two routes: an Express server that serves dist, or the Nginx buildpack as the last buildpack, with try_files $uri $uri/ /index.html =404; in nginx.conf and web: bin/run in the Procfile.

Best for: a Vite frontend deployed next to a Heroku-style backend on a French platform.
Price: €7.20 a month excl. VAT keeps a 256 MB container running, or €8.64 excl. VAT if it sits in the SecNumCloud region. You can test it free for 30 days first.
What it lacks: a ready path for static builds. You write the buildpack list and the Nginx rule, and pay for a running container.

5. Bunny.net

Bunny.net is a CDN run by BunnyWay d.o.o. in Ljubljana. Its docs list Vite among the frameworks it can host from Bunny Storage, served through Bunny CDN. With the Bunny CLI, a sites block in bunny.jsonc sets the build command, the dist folder and spa: true to serve index.html for unknown paths. Without the CLI, enter /index.html as the storage zone's 404 file and turn on the rewrite of 404 to 200.

Best for: a Vite app read on several continents, built in your own CI.
Price: a $1 monthly minimum, and CDN traffic from $0.01 per GB in Europe and North America on its 119-location standard network. You can try it for 14 days without a card.
What it lacks: a free plan. Its storage regions also include Asia, the Americas, Africa and Australia, so pick a European one when you create the storage zone.

How to choose

Pick Eurobase if the app talks to an API you'd like on the same platform, or an agent does your deploys.
Pick statichost.eu if the build is purely static and you want no US provider anywhere in the chain.
Pick Clever Cloud or Scalingo if your backend already runs there and one bill matters more than setup time.
Pick Bunny.net if your users are spread worldwide and you already build in CI.

The static site hosting comparison covers hosts for plain HTML and generator sites. For Vite-based frameworks with server rendering, see React Router, SvelteKit, Nuxt or Astro.

Frequently asked questions

Why does my Vite app return 404 when I refresh a page?

Your router works in the browser, but on refresh the server looks for a real file at that path and finds none. Tell the host to answer unknown paths with index.html: Eurobase does it for Vite apps already, statichost.eu takes a _redirects rule, Scalingo needs a try_files rule, and Bunny.net needs spa: true or a 404 rewrite.

Can I host a Vite app for free in Europe?

Yes. Eurobase's Free plan covers 2 projects within fixed limits, statichost.eu hosts 1 site at no cost, and Clever Cloud starts you on free credits. Bunny.net and Scalingo offer trials rather than free plans.

Where do I put API keys in a Vite app?

Not in VITE_ variables. Vite writes their values into the JavaScript your visitors download. Keep secret keys on a server or in a function, and call it from the browser. On Eurobase, the same project can run that code on V8 isolates or as a Function.

Do I need a CDN for a Vite app?

Usually not when your audience is mostly in Europe and the files are served from Europe. Bunny.net and similar CDNs start to pay off once many visitors load the app from other continents.

Can I use GitHub Pages or Netlify from Europe?

You can, and Vite's deployment guide covers both. They're run by companies outside the EU, so read EU region vs EU company and the GitHub Pages alternatives or Netlify alternatives if that matters for your contract.