Launch the campaign page this afternoon.
A page for a webinar, a launch, or a paid campaign usually has a shorter life than the ticket it takes to get it onto the main site. harvis hosts it at its own address and collects the form on it without a backend, which puts the whole thing back inside the marketing team.
Where marketing teams reach for this
A page the main site shouldn't have to carry
A one-week campaign doesn't need a CMS entry, a template, or a review from whoever owns the corporate site. It needs a URL by Thursday.
The lead form
A static page normally means paying a form service to embed a widget. Add one attribute to your own markup instead and the submissions land in the dashboard, spam-filtered, exportable as CSV.
One page per channel
Deploy the same page twice with different copy and compare what comes back. There's nothing to configure, so a second variant costs another deploy and nothing else.
From a folder to a link
- 01
Get the page from wherever it comes
A designer's export, a template you bought, or an AI chat that wrote the HTML. All three are a folder of files by the time they reach you.
- 02
Turn the form on
Put harvis-form="signups" on the <form> tag. No script tag, no endpoint URL to paste, and nothing for the person filling it in to sign up for.
- 03
Publish it and name it
Drop the folder in the browser or run the CLI, then set the subdomain to the campaign name so the link still reads properly inside an ad.
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.
- 拖放文件No install and no terminal — the folder goes onto the page in your browser and comes back as a link.
- AI 构建器Describe the page you want, get HTML back, and publish it from the same screen when the product shot is all you had.
- 命令行For the one person on the team who would rather type it, and for redeploying a copy tweak in a second.
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 marketing teams
Where do the form submissions actually go?
Into your dashboard, newest first, with spam filtered out and a CSV export whenever you want them somewhere else. The visitor gets a thank-you page you don't have to build.
Can a campaign page use our own domain?
Not yet. Every site gets a harvis.dev address, and you choose the subdomain once you've claimed the site — spring-launch.harvis.dev rather than a random slug. Pointing a domain you already own at it isn't supported, so a campaign that has to live at yourbrand.com belongs on the main site.
Do we need a developer for any of this?
Only to write the HTML, and often not even that — the AI builder writes a page from a description, and turning the form on is one attribute added to a tag that already exists.
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.