Deploy
Deploy Any Framework with Zero Configuration
deploybase auto-detects your framework, sets the right build command and output directory, and deploys to EU infrastructure. Connect your Git repository, push your code, and your site is live on a global CDN — built on Scaleway Paris, delivered via Bunny.net across 100+ PoPs. We support 8 frameworks out of the box, from Astro to static HTML. No YAML files, no build pipelines to configure, no US data transfers.
Last updated: April 2026
Astro
Content-focused framework with island architecture. Outputs zero JavaScript by default — ideal for blogs, docs sites, and marketing pages that need fast load times.
Deploy guideHugo
The fastest static site generator. Builds thousands of pages in milliseconds with no Node.js dependency. Perfect for documentation sites, blogs, and content-heavy projects.
Deploy guideSvelteKit
Full-stack framework with adapter-static for pre-rendered sites. Component-driven development with minimal boilerplate and built-in routing.
Deploy guideVite
Lightning-fast build tool for vanilla JS, React, Vue, and Svelte projects. If your framework uses Vite under the hood but isn't listed separately, select Vite.
Guide coming soonNext.js
React framework with static export support. Use next export or output: 'export' in next.config.js to generate a fully static site deployable on any CDN.
Guide coming soonGatsby
React-based static site generator with a rich plugin ecosystem. GraphQL data layer for pulling content from CMSs, APIs, and local files at build time.
Guide coming soonJekyll
Ruby-based generator that powers millions of sites. Mature ecosystem with extensive theme and plugin support. Markdown-first content authoring.
Guide coming soonStatic HTML
No framework needed. Upload plain HTML, CSS, and JavaScript files directly. deploybase serves them from the CDN with automatic TLS and custom domains.
Guide coming soonBuild Configuration Reference
Every framework has sensible defaults. deploybase auto-detects your framework from your repository and pre-fills these values. Override any setting in your project configuration if your setup differs.
| Framework | Build Command | Output Dir | Install | Docker Image |
|---|---|---|---|---|
| Astro | npm run build | dist | npm install | node:24-alpine |
| Hugo | hugo --minify | public | — | hugomods/hugo:0.139.0 |
| SvelteKit | npm run build | build | npm install | node:24-alpine |
| Vite | npm run build | dist | npm install | node:24-alpine |
| Next.js | npm run build | out | npm install | node:24-alpine |
| Gatsby | npm run build | public | npm install | node:24-alpine |
| Jekyll | jekyll build | _site | bundle install | jekyll/jekyll:4 |
| Static HTML | echo done | . | — | alpine:3.23 |
How Deploying on deploybase Works
Auto-Detection Sets the Right Defaults
When you connect a Git repository, deploybase scans your project files
to identify the framework. It looks for astro.config.mjs, hugo.toml, next.config.js, svelte.config.js, Gemfile, and other
framework-specific markers. Once detected, the build command, output
directory, and install step are pre-filled automatically. You never need
to write a build pipeline definition, a Dockerfile, or a CI
configuration file. According to our internal data, 92% of projects
deploy successfully on the first push with auto-detected defaults — no
manual configuration needed.
If your project uses a custom setup — a monorepo with a non-root directory, a different package manager, or a post-build step — you can override every default in your project settings. The auto-detection is a starting point, not a constraint.
From Git Push to Live Site
The deployment pipeline has three stages, and most sites complete all
three in under two minutes. First, deploybase clones your repository
into an isolated Kubernetes pod — each build runs in its own container
with no shared state. Second, it runs your install and build commands
inside a framework-specific Docker image (e.g., node:24-alpine for Node.js frameworks, hugomods/hugo:0.139.0 for Hugo). Third,
the built output is uploaded to Bunny.net storage and served through their
CDN with 100+ global points of presence.
Every deployment is an immutable snapshot. Promoting a previous
deployment to production takes seconds — no rebuild required. Branch
previews are created automatically: push to a feature branch and get a
unique CDN-backed URL at {branch}-{slug}.previews.deploybase.eu. The default
branch auto-promotes to production. Non-default branches create or
update preview URLs.
What We Build and What We Don't
deploybase is purpose-built for static sites. If your framework outputs
HTML, CSS, JavaScript, and assets at build time, we handle it. This
includes static site generators (Hugo, Jekyll, Gatsby, Eleventy),
content-focused frameworks (Astro), and frontend frameworks with static
export (Next.js with output: 'export', SvelteKit with adapter-static). We don't do server-side rendering, edge
functions, or serverless compute at the CDN layer. Vercel and Netlify
are better choices if your architecture requires those capabilities —
and we say that on our comparison pages.
What we offer instead is simplicity and compliance. A JAMstack architecture — static frontend calling a separate API — gives you full control over your backend while deploybase handles the hosting. Your source code, build artifacts, and access logs stay on EU infrastructure. No data crosses the Atlantic, not even billing data. For EU companies that need verified GDPR compliance for their web properties, that combination matters.
Framework Auto-Detection
Push your repo. deploybase identifies your framework, sets build defaults, and deploys. No config files to write.
Branch Preview URLs
Every feature branch gets a unique CDN-backed preview URL automatically. Share with your team before merging.
Instant Rollback
Every deployment is an immutable snapshot. Re-point production to any previous build in seconds — no rebuild needed.
EU Data Residency
Builds run on Scaleway Paris. Sites delivered via Bunny.net CDN (EU-headquartered). No US infrastructure in the chain.
Flat EUR Pricing
No per-seat fees. No overages. Pro plan includes 5 members for €19/month total. Proper EU VAT with B2B reverse charge.
Global CDN Delivery
100+ Bunny.net PoPs across Europe, North America, Asia, and beyond. Wildcard TLS via DNS-01 ACME. 99.99% uptime SLA.
Frequently Asked Questions
Which frameworks does deploybase support?
deploybase supports 8 frameworks out of the box: Astro, Hugo, Next.js (static export), SvelteKit (adapter-static), Vite, Gatsby, Jekyll, and plain static HTML. Each framework is auto-detected from your repository, with build command and output directory pre-filled automatically. You can also use any framework with a custom build command.
How does framework auto-detection work?
When you connect a Git repository, deploybase scans your project files (package.json, config files, Gemfile) to identify the framework. It then pre-fills the build command, output directory, and install step with the correct defaults. You can override any of these settings if your project uses a non-standard configuration.
Can I use a custom build command?
Yes. While deploybase auto-detects your framework and sets defaults, you can override the build command, output directory, install command, and root directory (for monorepos) in your project settings. Any command that produces static HTML output will work.
Where are my sites hosted?
All builds run on Scaleway infrastructure in Paris, EU. Built sites are delivered globally via Bunny.net CDN with 100+ points of presence across Europe, North America, Asia, and beyond. Bunny.net is EU-headquartered (Slovenia). No data is processed through US infrastructure — not even billing data, which is handled by Vatly, a European Merchant of Record.
Not sure which platform to use? Compare deploybase to Vercel, Netlify, and other platforms. Looking for inspiration? See what you can build and host.
Deploy your first site in under two minutes
Free plan includes 1 site, 100 GB bandwidth, custom domains, and automatic TLS. No credit card required.