How it works, in detail

Deploying your first site, pointing your own domain at it, wiring it to your agent, and where your data actually sits.

Connect your agent over MCP

Mint a token, paste one block of configuration, and your coding assistant can create sites, deploy them, attach domains and read the status without you opening a dashboard.

Read article

Deploy your first site

Two ways in, a repository or a folder of built files, and what happens after you hand it over.

Read article

Point your own domain at it

One CNAME record, and the certificate is our problem. Why root domains are not supported, and what to do instead.

Read article

Where your data lives

Which company does what, in which country, and the two places where the honest answer is more complicated than "all of it is in the EU".

Read article

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.