Your page, online in one sentence.
The one-pager, the portfolio, the event invite. If it opens in your browser from a folder, it works here — and your first ten are free, forever, without a card.
Files, served fast, nothing else.
A site here is just your files: HTML, CSS, images, and whatever JavaScript you put in the page. There is no build step and no framework to declare. Drop in a Tailwind or Alpine link from a CDN and it still works, because nothing has to be compiled first.
That’s also why it’s the free part: a site is files behind a web server, which costs us almost nothing to serve. You get ten of them free, forever, without a card.
A site is one thing you put online — a page and whatever sits beside it. Three or four sub-pages still count as one, and adding more of them later is free, because we count a site when you create it and never look again. Ten separate things is more than most people put online in a year; if you do outgrow it, Grow takes you to 500.
Updates work the same way as the first deploy. Ask again and the new version replaces the old one at the same address, usually before you’ve switched tabs.
Is this the right thing for what you made?
It comes down to one question: does anything need to happen on our side after the page loads?
Yes — a static site
Landing pages · portfolios · one-pagers · documentation · wedding and event pages · link-in-bio pages · a chart you generated · anything you’d otherwise email as a zip.
Nothing has to run. The files are the whole thing, and that’s what makes them free.
No — you want an app
If it needs to save what visitors type, take a payment, send an email, or check who someone is, then something has to run on our side after the page loads.
That’s an app: €4 a month with a database included, and your agent can move your files across without starting again.
An app that saves things →- framework preset
- build command
- output directory
- node version
- FTP
- cPanel
- cache headers
No settings, because there are none.
Not simplified for beginners — genuinely absent. There is no build command field to leave blank, which is why your agent can do this without stopping to ask you something you'd have to look up.
- minification
- CDN config
- deploy hooks
- DNS records
- SSL certificates
- redirect rules
- server updates
The one convention: your page is index.html at the top of whatever you send, and your agent handles that. The static site page has the detail if you’re curious.
The usual ones.
Can I use my own domain?
Yes, on Grow — as many domains as you like. Your agent tells you the one record to add at whoever you bought the domain from, then sets up the certificate itself. On Starter you get an agenthost.eu address, which is a real, shareable link with HTTPS — just not your name.
How fast is it?
Fast enough that a page like this isn’t the thing making it slow. Files are served directly with compression and caching already on — there is no performance setting for you to get wrong either.
Can I password-protect it?
Better than a password: name the email addresses allowed in, and only those people can open it. Nothing to share, nothing to leak, and you can take someone off the list later. That’s the client preview page →
What if I want to change it later?
Ask your agent. Every deploy keeps the previous version, so “put the old one back” also works.
Do I need a GitHub account?
No. Your agent sends the files straight to us. If you happen to keep your project in git that’s fine, but nothing here requires it.
Ask your agent to publish it.
Ten static sites free forever, no card, and the first one live in about a minute.