One command between dist and a link.
Most hosts want a project created, a repo connected and a build configured before they'll serve files you have already built. harvis takes the folder. The first deploy needs no account at all — you get a URL back, plus a private claim link if you decide to keep it.
Where frontend developers reach for this
Showing someone a branch
Quicker than explaining how to run it locally, and it works on their phone, which is where half the feedback comes from anyway.
The thing that isn't worth a project
A reproduction for a bug report, a pen that outgrew the pen, a demo for a talk tomorrow. None of them deserve a permanent entry on a platform.
Hosting that doesn't assume a repo
No commit, no workflow file, no Git provider to connect. Version control stays a choice you make for your own reasons rather than a prerequisite for a URL.
From a folder to a link
- 01
Build the project
npm run build, or whatever your setup calls it. Everything harvis needs is in the output folder — dist, build, out, _site, the name is the only thing that varies.
- 02
Deploy the folder
npx harvis deploy dist. Nothing to install and no login for the first one; you get a live URL and a private claim link straight back.
- 03
Claim it if you're keeping it
The claim link attaches the site to a free account, where you can set the subdomain, redeploy over the same address, or delete it.
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.
- Komut satırıThe main one: npx harvis deploy <dir>, no install and no account for the first deploy.
- MCP sunucusuGive your editor's agent a deploy_site tool and it publishes what it just built without you leaving the editor.
- HTTP APIFor your own scripts and CI, with a published OpenAPI contract behind it.
- Dosya bırakWhen the terminal is on the other machine and the folder is on this one.
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 frontend developers
Does client-side routing work after deploying?
Yes, for the common case. harvis falls back to your entrypoint HTML for paths that aren't files, which is exactly what a history-mode router needs for a direct visit to a deep link like /settings to resolve.
How is this different from Vercel or Netlify?
Those are built around connecting a repo and running your build on their servers, with a project to configure first. harvis takes output: you build locally or in your own CI, run one command against the folder, and get a link — no project setup, and no account until you want to keep the site.
Which frameworks are supported?
All of them, once they've built — the CLI can't tell React output from Hugo output, because by then both are plain files. The only thing that varies is which folder to point at, and there's a per-framework guide covering that.
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.