Find out if anyone wants it before you build it.
The first version of a company is a page and a way to hear from the people who want what's on it. harvis hosts the page for free and collects the signups itself, so the experiment costs an afternoon instead of a stack.
Where founders reach for this
The waitlist
One page, one email field. Add the form attribute and every address lands in your dashboard — no email platform to open an account with before you can find out whether anyone cares.
Docs and changelog beside the app
Whatever the product itself runs on, its documentation is static HTML. Deploy it as its own site so fixing a typo in the docs never waits on an app deploy.
Pages you'd rather not put on the main site
An investor one-pager, a pricing experiment, a page written for a single customer. Each gets its own address and stops existing when you delete it.
From a folder to a link
- 01
Put the page up
A template, something you wrote, or something a model produced. It's a folder with an index.html in it either way, and that's a complete deploy.
- 02
Collect the signups
Add harvis-form="waitlist" to the form. Submissions show up in the dashboard immediately; export the CSV once you have somewhere to send them.
- 03
Keep shipping to the same address
Redeploying replaces the site in place and the URL doesn't change, so rewriting the headline for the fourth time costs one command and breaks no links.
Pick how you drive it
All of these publish the same way and produce the same site. The only difference is what you already have open.
- Command linenpx harvis deploy from wherever the page lives, with no project to create on a dashboard first.
- MCP serverYour coding agent publishes the page itself and reads the live URL back to you, which keeps the loop inside the editor.
- I-drop ang mga fileBefore there's a repo or a build, the browser is genuinely enough.
Put something online and see
The first deploy needs no account: drop a folder in and a live URL comes back, along with a private claim link if you decide to keep the site.
Put a site onlineQuestions from founders
Is it really free while I'm still figuring out whether this works?
Yes, and there's no card and no trial that turns into a bill. The free limits are 500 files and 50 MB per site, which covers a landing page and a docs build comfortably, and sites don't expire — the page stays up until you take it down.
Can the waitlist live on my own domain?
Not yet. You get the subdomain you claim — waitlist.harvis.dev, say — rather than a domain you own. For a validation page that's usually fine, but it's worth knowing before you plan the real company site around it.
What happens when the product is real and the traffic grows?
Nothing you have to do. Publishing is free, and if a month outgrows the free limits the account moves onto the nearest paid step — from $5 — then back down when the traffic settles. Bandwidth and SSL are never metered.
Do I need an account?
Not for the first deploy. You get a live URL and a private claim link; the claim link attaches the site to a free account when you want to choose its subdomain, redeploy over it, or delete it.
What can harvis not host?
Anything that needs code running on a server: PHP, Node, Python, a database, or a page rendered at request time. harvis serves the static files you upload and collects submissions from forms on them. A JavaScript front end talking to an API hosted elsewhere works normally.
What does it cost?
Publishing is free — 500 files and 50 MB per site, no card, and sites that do not expire. If a month outgrows the free limits the account steps onto the nearest paid step, from $5, and steps back down when usage does. Bandwidth and SSL are never billed.
Is someone else's job closer to yours?
The product underneath is the same — these pages just start from a different problem.