What is deploybase?

Updated 2026-10-13

Deploybase is a hosting platform for static sites and serverless functions that runs on European infrastructure. It is aimed at developers and teams who want to ship a site quickly — by asking an AI agent, dragging in a folder, or pushing from Git — and who care about where their data is hosted. You can start free, and pricing is listed in euros.

What you can put on it

Two kinds of things:

Static sites — plain HTML/CSS/JS, or a built output from a framework. In the platform's own example build, a Vite site produced 12 files totalling 181.7 KB.
Serverless functions — code placed in a functions/ directory runs alongside the site, but is served from its own hostname rather than a path on the site.

Functions are currently in beta and available on paid plans, so a free account is enough to try static hosting but not necessarily functions.

The three ways to deploy

Method	What you need	What happens
Ask your AI agent	A Git repository, plus an MCP client such as Claude or Cursor	The agent connects, asks you for one key that only a person can create, builds the repo, and returns the link
Drag and drop	A free account and a folder containing `index.html`	You create a project, choose "Upload a folder", and drop the folder in; the site goes live immediately
Push from Git	A free account and a connected repository (GitHub, GitLab, Bitbucket, Codeberg, Forgejo)	Every push updates the site; every branch gets its own preview link

The drag-and-drop route accepts up to 250 MiB on the free plan and needs no build step or repository. The agent route is the only one that currently requires a Git repository.

How a deploy actually behaves

Production on deploybase is a pointer, not a fixed artifact — which is what makes instant rollback possible. Each deploy produces a new build, and switching production to it (or back) is a pointer change rather than a rebuild.

The platform publishes a real build log from 26 September 2026 for a site called eu-check with one function:

Waited 1.7 s in the queue
Cloned the repository
Built in 13.6 s (tsc --noEmit && vite build, 5 modules transformed)
Uploaded 12 files and bundled 1 function in 7.4 s
Live 32 seconds after the push

The site landed at eu-check.sites.deploybase.eu and the function at scan-eu-check.fn.deploybase.eu. That split is worth noting: the function is not at /scan on the site, it is a separate hostname under fn.deploybase.eu.

Naming and addresses

Every project gets predictable default hostnames:

Site: my-site.sites.deploybase.eu
Function: signup-my-site.fn.deploybase.eu

You add your own domain when you are ready, so you are not forced to configure DNS before you can see the site working.

Forms without a backend

Deploybase includes form handling, so a static page can accept submissions without you writing or hosting an endpoint. This is the usual reason a purely static site would otherwise need a function or a third-party service.

Who it fits

Deploybase is a reasonable choice if:

You want European hosting and euro-denominated, flat pricing rather than per-seat or usage-based billing.
You deploy static output and want branch previews and rollback without extra configuration.
You want to drive deploys from an AI agent through MCP, or you want the lowest-friction path of dragging a folder in.
You are moving from Netlify or Vercel and want to bring your existing settings across.

It is less suited if you need functions on a free plan right now, or if you need a full application runtime rather than static assets plus isolated functions.

Getting started

Create a free account.
Pick a path: paste the agent setup prompt into your MCP client, upload a folder, or connect a repository.
Push or upload — the site goes live on its sites.deploybase.eu link.
Add your own domain when you are ready.

For the agent route specifically, the setup instruction is to fetch and follow https://deploybase.eu/agent-setup, after which the agent connects itself and asks you for a single key that only a person can create.