You built the site. We put it on the internet.

Hand over a repo, or a folder of built files. We build it, keep it in Germany and serve it on your own subdomain, certificate included. Your coding agent can do the whole thing over MCP without opening a dashboard.

Join the waitlist

European vendors underneath. Plain MCP on top.

BunnyBuddy WorksHankoAstroGitHubMCPClaude CodeCursorVS Code
#_

The site is done. Shipping it is the part that stops you.

You did not set out to learn build pipelines, DNS records, certificates and CDN configuration. That is a second skill standing between your work and anyone seeing it, and the risk of getting it wrong is public and sometimes expensive.

  • No build pipeline to write
  • No CDN dashboard to learn
  • No certificate to request or renew
  • No git required on the upload path
  • No account with four separate vendors

Two doors in. Pick whichever you have.

Connect a GitHub repo and we build it for you on every push. Or upload a folder of already-built files, with no repository, no commit and no git at all, which is what you want when an agent made you files rather than a project.

#_

Three steps, and two of them are ours

A repository or a folder of files, built, then served from a global network

01. You hand it over

Point us at a GitHub repo, or upload a folder of built files. That is the whole of your side of it.

02. We build it and serve it

Your site is built, stored in Germany and served from a global network so it loads quickly wherever someone opens it. Builds sometimes wait their turn, and when yours is waiting the page says so rather than spinning.

03. It goes live and stays live

You get a working address straight away. Point your own subdomain at it when you are ready: we show you the one record to add and sort out the certificate ourselves. Push a change and it goes out again on its own.

Tell your agent, not a dashboard

The whole feature set is exposed over MCP, the open standard your coding assistant already speaks. Give it a token and it can go from a repo to a live URL, attach a domain and read back the status, without you opening the product at all.

#_

You are still the one who decides

An agent cannot install a GitHub App on your account or paste a record into your DNS. Those stay yours, they are the only two things we ask for, and we say exactly what to do in plain words. Everything else it can handle.

#_

Every company that runs your site is European

Your site is hosted and served without AWS, Google Cloud, Cloudflare or Vercel, and everything we store sits in Germany. The delivery network is worldwide on purpose, because that is what makes the site fast: what stays in the EU is every company we depend on and every copy of your data we hold. Your source code stays wherever you already keep it, which is your call and not part of our stack.

#_

Bunny, Slovenia

Hosting, storage and the database. Your files sit in Bunny's German region and are served from a global network so the site loads quickly everywhere.

#_

Buddy Works, Poland

The builds. You never configure it, you never see it, and you never need an account with it. We name it because it is a good company, not because we have to.

#_

Hanko, Germany

Sign-in, with a passkey or a code to your email. No password to choose and none for us to lose.

Your own subdomain

Point a subdomain at us with one CNAME record and we handle the certificate. Root domains like example.com are not supported, because most DNS providers cannot CNAME them: send www at us and redirect the root yourself.

Redeploys on push

Connect a repo and every push to the branch you chose rebuilds and republishes on its own. Nothing to run and nothing to remember.

Roll back to any deploy

Uploaded a bad build. Pick an earlier deploy from the history and it goes back out. We keep the archive so you do not have to rebuild it.

A failed build changes nothing

If a build breaks, the deploy stops and your live site stays exactly as it was. Nothing goes down while you work out what happened.

Status in plain words

You are told what is happening and what went wrong in ordinary language. A build log you have to decipher is not a report, it is a shrug.

Delete it just as easily

Tear a site down and its hosting goes with it. No support ticket, no lingering resources you forgot you were paying for.

Fifteen tools your agent gets, in full

This is not an API with an assistant bolted on afterwards. The MCP server was how the product was built, so an agent can do every single thing the dashboard can do.

Mint a token in settings, paste one block into Claude Code, Cursor or VS Code, and these are the tools it can reach.

See how to connect it
  • 1

    ping

    Check that the connection and the token are wired up correctly.

  • 2

    deploy_requirements

    Ask what is still missing before a site can be created, and get back a checklist rather than a failure.

  • 3

    validate_repo

    Confirm a GitHub repository exists and that we can read it.

  • 4

    provision_site

    Create a new site from a repo: hosting, build pipeline and the first build.

  • 5

    upload_site

    Create or update a site from a folder of built files, with no repository involved.

  • 6

    deployment_status

    Read where a deploy has got to, including which file it is on, and the address once it is live.

  • 7

    redeploy_site

    Send the last upload out again, without re-uploading anything.

  • 8

    rollback_site

    Put an earlier deploy back on the live site.

  • 9

    list_deployments

    Read a site's deploy history, most recent first.

  • 10

    list_projects

    Read every site in a workspace.

  • 11

    teardown_site

    Destroy a site and its hosting for good. Irreversible, so it insists on being told twice.

  • 12

    add_domain

    Attach your own subdomain and get back the exact record for you to add at your DNS provider.

  • 13

    list_domains

    Read every domain on a site, whether DNS has propagated and whether the certificate is issued.

  • 14

    remove_domain

    Detach a domain and free the name up again.

  • 15

    recheck_domain

    Check a domain's DNS and certificate right now instead of waiting for the next sweep.

What it will cost

Every plan starts with a 14 day trial: one site, on a staticsites.eu subdomain rather than your own, with the full set of agent tools. These are the prices we will launch at, published now so nobody has to guess. Nothing is being charged yet, and the waitlist is where we tell you before that changes.

Solo

€12/month

One person, with a handful of things they want online under their own name.

What's included:

  • 5 sites
  • Unlimited custom subdomains
  • 150 GB bandwidth a month
  • 1 seat
  • Free certificates, renewed for you
  • Full MCP access, all fifteen tools
  • Then €0.10 per GB over
Join the waitlist

Studio

€29/month

A small studio shipping client work, where two people need the same sites.

What's included:

  • 20 sites
  • Unlimited custom subdomains
  • 500 GB bandwidth a month
  • 2 seats
  • Free certificates, renewed for you
  • Full MCP access, all fifteen tools
  • Then €0.10 per GB over
Join the waitlist

Agency

€65/month

An agency running client sites, where a slow build costs somebody money.

What's included:

  • 50 sites and up
  • Unlimited custom subdomains
  • 1 TB bandwidth a month
  • 5 seats
  • Free certificates, renewed for you
  • Full MCP access, all fifteen tools
  • Priority builds and priority support
  • Then €0.08 per GB over
Join the waitlist

More than fifty sites

Committed bandwidth, single sign-on, a support agreement and white-label are negotiated rather than listed. Tell us the shape of it and we will quote it.

Request a custom plan
#_

Get it off your laptop

We are opening staticsites.eu to a first group shortly. Leave your email and we will tell you when it is your turn, and what it costs, before you are asked for anything.

Join the waitlist

FAQ

The questions worth answering before you hand us anything, including the ones where the answer is no.

Do I need to know anything about DevOps?
No. There is no pipeline to configure, no CDN to set up and no certificate to request. We ask you for exactly two things a person has to do: install our GitHub App if you are deploying from a repo, and paste one record at your DNS provider if you want your own domain. Both are one screen, and we tell you precisely what to click.
What can I actually deploy today?
Static sites built with Astro, and any folder of already-built files. Static means the pages are built once and then simply served, which covers most personal sites, portfolios, documentation and landing pages. Anything that needs a server running behind it is not supported, and other frameworks are not supported yet. We would rather say so here than let you find out after signing up.
Can I use my own domain?
Yes, as a subdomain: point www.yoursite.com or docs.yoursite.com at us with one CNAME record and the certificate is issued and renewed for you. Root domains like yoursite.com are not supported, because most DNS providers cannot CNAME a root. Send www at us and redirect the root to it at your registrar, which is a setting rather than a project.
Is it really all European?
Every company that runs your site is: Bunny in Slovenia for hosting, storage and the database, Buddy Works in Poland for builds, Hanko in Germany for sign-in. Everything we store sits in Germany. No AWS, no Google Cloud, no Cloudflare, no Vercel. Two honest qualifications. Your site is delivered from servers worldwide, because that is what makes it fast, so the claim is about which companies we depend on and where your data rests, not about EU-only delivery. And if you keep your code on GitHub, that part is yours and sits where you put it.
What is MCP, and how does my agent use it?
MCP is the open standard that lets an AI assistant call tools. Mint a token in settings and paste one configuration block into Claude Code, Cursor or VS Code, and your agent gets fifteen tools: create a site, deploy it, attach a domain, read the status, roll back, tear it down. It can take a project from a repo to a live URL without you opening the dashboard once.
What happens when a build fails?
The deploy stops and your live site stays exactly as it was. Nothing goes down. We tell you what broke in ordinary words rather than handing you a build log to decipher, and you can put an earlier deploy back at any point.
Can I deploy without git at all?
Yes, and it is a first-class path rather than an afterthought. Upload a folder of built files with no repository, no commit and no git involved. That is usually what you want when an agent has produced files for you rather than a project you are managing.
Who is behind this?
Essential Code GmbH, a small company in Austria run by David Wippel. staticsites.eu is built by David and Stefan Rösch. We are new, we have no customers yet, and you will not find invented numbers anywhere on this page.