Astro hosting in Europe

Push an Astro site and it builds in Paris and goes live on Bunny.net's CDN. Your astro.config stays as it is: no adapter, and the settings are already filled in.

Your pages in, your addresses out.

The Astro step of a real build of a small blog on deploybase, with its domain swapped for example.com. Astro writes every page as a folder with an index.html in dist, and each one answers at its clean address, with or without the trailing slash.

Pages of an Astro blog built on deploybase and the addresses they are served at after one build: seven pages built in 11.60 seconds, 28 files uploaded.
An Astro blog astro build 7 pages in 11.60 s
  • src/pages/index.astro example.com/
  • src/pages/about.astro example.com/about
  • src/pages/blog/index.astro example.com/blog
  • src/pages/blog/[...slug].astro example.com/blog/{slug}
  • src/pages/projects/[...slug].astro example.com/projects/{slug}
  • src/pages/rss.xml.ts example.com/rss.xml
3 images optimised · 3709 kB → 17 kB sitemap-index.xml created at dist 28 files uploaded to the CDN

Your astro.config stays as it is.

The same blog's config, domain swapped. Nothing in it is there for us; the one line to check before you go live is site.

astro.config.mjs
  1. // @ts-check
  2. import { defineConfig } from 'astro/config';
  3. import mdx from '@astrojs/mdx';
  4. import sitemap from '@astrojs/sitemap';
  6. export default defineConfig({
  7. site: 'https://example.com', Set it: the sitemap and RSS need it.
  8. integrations: [mdx(), sitemap()], Runs in the build, as on your laptop.
  9. markdown: {
  10. shikiConfig: {
  11. theme: 'github-dark',
  12. },
  13. },
  14. }); No adapter, no output: 'server'.

How long a build takes here.

The median build on deploybase, from build start to live, across every framework and every team. Counted on 25 September 2026.

Mean, pulled up by a few long builds
78 s
Builds timed
1,641
Builds that succeed
81.5 %
Time limit per build
15 min Free, 30 min paid

Failed builds are left out of the times: they measure how long we took to give up. There is no figure for Astro alone yet; at our size it could point at one customer. The live numbers are on /open.

What Astro does here that we cannot yet.

  • On-demand rendering everywhere With @deploybase/adapter-astro (beta, paid plans) on-demand pages run on your deploybase address, branch previews and custom domains. Responses are not cached at the edge yet. A live site sleeps after 30 minutes without visitors (during the beta that window is shared capacity, and it can drop to about 2 minutes when full), and the first request after that waits several seconds for the server to start.
  • Your Node version Builds run Node 24. We do not read .nvmrc or the engines field yet.
  • A build cache Nothing carries over between builds, so Astro installs and optimises every image again each time.

Questions about Astro on deploybase.

Something else? Write to support@deploybase.eu. A person answers.

Does deploybase run Astro server rendering?

Yes, in beta on paid plans, for Astro 7. Install @deploybase/adapter-astro, add adapter: deploybase() to astro.config.mjs, and set output: 'server' or export const prerender = false on a page. Prerendered pages come from the CDN; on-demand pages, API routes, actions and server islands run on a function in Paris. It works on your deploybase address, branch previews and custom domains. On the Free plan the build still succeeds as a static site: on-demand routes answer 404 and the build log says why.

Astro guide
Do I need an adapter?

Not for a static site: Astro's static output needs no adapter. For on-demand pages, use @deploybase/adapter-astro. Remove any other: a leftover @astrojs/node or @astrojs/vercel either fails the build or fills dist with server files that publish as an empty site.

Which package manager does the build use?

The one your lockfile names: pnpm, Yarn or npm, or the packageManager field in package.json if it is set. With a lockfile, dependencies install with install scripts switched off. Image optimisation with sharp still works: the build on this page shrank a 3709 kB photo to 17 kB.

How is an Astro site cached?

Files under /_astro/ carry a hash in their name, so they are cached for a year. HTML is cached at the CDN and checked by the browser on every visit, and a new deploy clears it.

What does a build cost?

Build minutes. Free includes 200 a month, Starter 1,000, Pro 3,000 and Scale 10,000, and a failure on our side or a build you cancel never counts. The median build on deploybase takes 40 seconds.

Pricing

Other frameworks

All frameworks and their defaults

Put your Astro site live.

Create a team on the free plan and connect the repository. The settings are already Astro's.

Start free Talk to the founder