Deploy your Vue app
The official create-vue scaffold (Vite under the hood) builds to a single dist folder with everything the browser needs. Hand that folder to the CLI and it's live.
- 01
Install dependencies
Run "npm install" once after cloning or scaffolding with "npm create vue@latest".
- 02
Build the app
Run "npm run build". Vite compiles and minifies your components into plain HTML, CSS, and JS in the "dist" folder.
- 03
Deploy it
Run "npx harvis deploy dist" from your project root. No config and no login for this first deploy — you get a live URL immediately, plus a private claim link to attach the site to a free account whenever you're ready.
Deploy Vue with one command
Build your project, then hand the output folder to harvis. No account needed for the first deploy — you'll get a live link and a private claim link to manage it later.
npm run build npx harvis deploy dist
Prefer dragging files instead of a terminal? Build the project, then drop the output folder here and publish it the same way.
Vue deploy questions
I'm using Vue Router in history mode. Will deep links work?
Yes. harvis falls back to index.html for any path it doesn't recognize as a file, which is exactly what history-mode routing needs for a direct visit to a route like /about to resolve correctly.
Does this work for a Vue app built with the older Vue CLI (not Vite)?
Yes — Vue CLI's "npm run build" also writes static output, just to a "dist" folder by default too. Point the CLI at whatever folder your build config actually writes to if you've customized it.
Is deploying a Vue app to harvis actually free?
Yes, no card required. Free limits are 500 files and 50 MB per site, which covers a static Vue build with plenty of room. Published sites don't expire — they stay live until you delete them.
Can I use my own domain with the deployed Vue site?
Every site gets a free harvis.dev address, and you can pick your own subdomain from the dashboard after claiming it — my-app.harvis.dev instead of a random one. Pointing a domain you already own (like mystore.com) at the site isn't supported yet.
How is this different from deploying Vue to Vercel or Netlify?
Vercel and Netlify are built around connecting a Git repo and running your build on their servers, with a dashboard to configure it. harvis skips all of that: you build locally (or in your own CI), run one CLI command against the output folder, and get a link — no project setup, and no account needed until you want to keep the site.
Deploying something else?
The recipe is the same everywhere — build it, then npx harvis deploy the output.