Deploy Your Astro Site to EU Infrastructure
Astro is the content-focused web framework that ships zero JavaScript by
default. deploybase auto-detects your Astro project, runs npm run build, and deploys the dist output to a global
CDN — built on Scaleway Paris, delivered via Bunny.net across 100+ PoPs. No
build pipeline to configure, no adapters required for static output, no US data
transfers. Your Astro site goes from Git push to live URL in under two minutes.
Last updated: April 2026
Deploy Astro in Three Steps
Connect your repository
Link your GitHub, GitLab, Bitbucket, or Codeberg repository.
deploybase detects astro.config.mjs and identifies your
project as Astro automatically. The build command (npm run build), output directory (dist), and install step (npm install) are pre-filled — no manual configuration needed.
Push your code
Push to your default branch to trigger a production deployment, or push to any feature branch for an automatic preview URL. deploybase clones your repository into an isolated container, installs dependencies, and runs your Astro build. Real-time build logs stream in the dashboard so you can watch the build progress.
Your site is live
The built output from dist/ is uploaded to Bunny.net
storage and served via their global CDN. Your site gets a .sites.deploybase.eu URL immediately — add a custom domain with automatic TLS whenever you're
ready. The entire process typically completes in under two minutes for a
standard Astro project.
Astro Build Configuration
These defaults are auto-detected when deploybase identifies an Astro project. Override any value in your project settings.
| Setting | Default Value | Notes |
|---|---|---|
| Build command | npm run build | Runs astro build via package.json script |
| Output directory | dist | Astro's default static output location |
| Install command | npm install | Use bun install or pnpm install if preferred |
| Docker image | node:24-alpine | Node.js 24 LTS on Alpine Linux |
| Output mode | static | Astro's default — pre-renders all pages to HTML |
What You Get with Astro on deploybase
Branch Previews for Every PR
Every feature branch gets a unique CDN-backed preview URL at {branch}-{slug}.previews.deploybase.eu. Review design
changes, content updates, or new Astro components before merging.
Previews are created automatically on push — no configuration needed.
Share the URL with your team or clients for feedback on the exact
build that will go to production.
Instant Rollback Without Rebuilding
Every Astro deployment is an immutable snapshot stored on the CDN.
Spotted a broken link or a content error after deploying? Re-point
production to any previous build in seconds. No rebuild, no waiting
for npm install and astro build to run again. This
is especially useful for content-heavy Astro sites where builds can take
longer as your page count grows.
EU Data Residency by Architecture
Your Astro source code is cloned and built on Scaleway infrastructure in Paris. Build artifacts are stored in Bunny.net's EU-origin storage. Sites are delivered globally via 100+ CDN PoPs, but the origin data never leaves the EU. No AWS, no GCP, no Azure in the chain. For EU companies shipping documentation sites, marketing pages, or client projects with Astro, this means verifiable GDPR compliance without additional legal review.
Global Performance from EU Origin
Astro's zero-JavaScript output is already fast. Pair that with Bunny.net's global CDN — 100+ points of presence across Europe, North America, Asia, and South America — and your visitors get sub-100ms response times worldwide. Automatic TLS certificates via DNS-01 ACME. Custom domains with wildcard support. 99.99% uptime SLA from an EU-headquartered CDN provider.
Why Astro and deploybase Are a Natural Fit
Astro is the fastest-growing framework for content-driven websites, with over 50,000 GitHub stars and 1.25 million weekly npm downloads. It ranked #1 in developer interest and satisfaction in the State of JavaScript 2024 survey. The reason is simple: Astro outputs static HTML by default, shipping 90% less JavaScript than comparable React or Next.js setups. Pages load faster, crawlers index them immediately, and there's no hydration overhead to worry about.
deploybase complements that philosophy. We do one thing — static site hosting — and we do it on EU infrastructure with flat EUR pricing. No per-seat fees, no bandwidth overages, no US data transfers. Your Astro blog, documentation site, or marketing page gets the same global CDN delivery as any large platform, but with a compliance story your legal team can actually verify. If you're comparing options, see how deploybase compares to Vercel or Netlify for static hosting.
Frequently Asked Questions
Does deploybase support Astro SSR (server-side rendering)?
deploybase is built for static sites. Astro's default output mode is 'static', which works perfectly — your site is pre-rendered to HTML at build time and served from the CDN. If you need on-demand SSR (output: 'server' or 'hybrid' with server-rendered pages), you'll need a platform that runs a Node.js server like Vercel or Netlify. For most content sites — blogs, docs, marketing pages, portfolios — static output is the right choice and the fastest option.
How does deploybase detect my Astro project?
deploybase scans your repository for astro.config.mjs (or .ts, .cjs) and checks for 'astro' in your package.json dependencies. Once detected, it pre-fills the build command (npm run build), output directory (dist), and install step (npm install). You can override any of these defaults in your project settings if your setup differs.
Can I use Astro with React, Vue, or Svelte components?
Yes. Astro's island architecture lets you use components from any framework — React, Vue, Svelte, Solid, Preact, or Lit — in the same project. These components are rendered to static HTML by default. Add a client:* directive (client:load, client:visible, client:idle) to hydrate specific components with JavaScript. deploybase builds the project the same way regardless of which UI frameworks you use.
Do I need to configure anything for Astro Content Collections?
No. Content Collections are processed at build time by Astro's build pipeline. deploybase runs npm install and npm run build in a Node.js container — your collections, MDX files, and data sources are all resolved during the build step. The output is static HTML in the dist directory, which deploybase uploads to the CDN automatically.
What about environment variables in Astro?
deploybase supports environment variables per project, encrypted at rest and injected at build time. Astro exposes PUBLIC_* variables to client-side code and keeps other variables server-side only. Set your variables in the deploybase dashboard under Project Settings → Environment Variables. They're available during the build process just like in local development.
Deploy your Astro site in under two minutes
Free plan includes 1 site, 100 GB bandwidth, custom domains, and automatic TLS. No credit card required.