Astro hosting on European infrastructure.

Deploying

Connect the repository once and slew detects Astro, fills in the build, and deploys dist/ on every push. Or build locally and ship the folder:

$ slew deploy dist
Live at https://your-project.slew.cloud

Every pull request gets a preview URL that updates per push and expires after 7 days — send it to a client instead of a staging login.

When you outgrow static

Add Astro's Node adapter and your project becomes a server app: it runs as a real Node process on slew with env vars, live logs, health-checked zero-downtime deploys, and scale-to-zero when idle. Same project, same push, no platform migration — which is the part most European static hosts can't do.

Numbers without a banner

Every site includes cookieless analytics measured from CDN logs at the edge: pageviews, unique visitors, referrers and countries, with no script to add and no consent banner to show. For an Astro site that exists to be fast, not shipping an analytics script is the point.

Frequently asked

Which Astro modes work?

Static output deploys as files. SSR with the Node adapter runs as a server app. Hybrid rendering follows the adapter: prerendered pages are static files, the rest hits your server.

Do content collections, image optimization and the usual toolchain work?

Builds run your project's own build command in a clean Linux container, so anything that works in `astro build` works here — including Astro's build-time image optimization. Deployed sites additionally get the platform's /_slew/image endpoint for on-demand resizing at the CDN edge.

What does it cost?

A static Astro site fits the free plan (3 projects, 50 GB). Paid plans are flat euros — €9, €24, €99 — with no build-minute meter and no per-seat fees.

Where does my site physically live?

Storage and servers at Hetzner in Germany, CDN and DNS at Bunny in Slovenia, company incorporated in the EU. No US parent, no CLOUD Act exposure.