Is deploybase hosted in Europe?

Updated

Yes. deploybase describes itself as "European static site hosting and functions," and its own tagline is "Live in minutes on European infrastructure." Both parts of a project — the static site and any serverless function — run on that European infrastructure, and the public URLs reflect it: sites are served from *.sites.deploybase.eu and functions from *.fn.deploybase.eu.

What "hosted in Europe" covers here

deploybase splits a project into two deployable pieces, and both are described as running on European infrastructure:

Piece Example URL Notes
Static site my-site.sites.deploybase.eu Built output (HTML, assets) served from the .eu hostname
Serverless function signup-my-site.fn.deploybase.eu Each function gets its own hostname; functions are in beta on paid plans

A documented build of a sample site (eu-check, a site with one function) shows the full chain in one deployment: the site went live at eu-check.sites.deploybase.eu and its function scan at scan-eu-check.fn.deploybase.eu, 32 seconds after the push.

Why the domain structure matters

The .eu suffix is not just branding — it is the visible signal of where the workload sits. If your reason for asking is data residency or European latency, the practical checks are:

  • Residency: the site and its functions are both on European infrastructure, so you are not splitting a project across regions.
  • Latency: European visitors hit European endpoints for both static assets and function calls, rather than crossing to another continent.
  • Compliance framing: "hosted in Europe" is a hosting statement, not a certification. If you need a specific legal or regulatory guarantee (for example a particular data-processing agreement), confirm that directly with deploybase — the public material does not spell out those terms.

How to verify it for your own project

  1. Deploy a site (upload a folder, push from Git, or have an MCP-capable agent do it).
  2. Check the URL you get back — it should be on *.sites.deploybase.eu.
  3. If you add a function, check that it lands on *.fn.deploybase.eu.
  4. Add your own domain when ready; the underlying hosting location does not change with a custom domain.

Who this matters for

  • Teams with a European data-residency or procurement requirement.
  • Sites whose audience is mostly in Europe and where round-trip latency to the origin matters.
  • Anyone migrating from Netlify or Vercel who wants the same workflow (branch previews, instant rollback, Git push deploys) on European infrastructure — deploybase notes you can bring your settings with you.

One caveat to keep in mind: functions are in beta and tied to paid plans, so if your Europe-hosting question is specifically about serverless functions, plan for that rather than assuming parity with the static hosting tier.