deploy vite
react, vue, svelte, solid, qwik, or vanilla js. built on your machine, shipped as static files.
the whole thing
curl -fsSL https://pushto.host/install | sh # or: brew install mydude-industries/tap/pushto · npm i -g @pushto/cli pushto login pushto init my-vite pushto
that last bare pushto is the deploy. on windows, the install line is irm https://pushto.host/install.ps1 | iex in powershell. live at https://<your-name>.pushto.host with https. the cli builds on your machine and ships only the output. the free tier covers this: one project, live on a pushto.host subdomain.
how we know it's vite
- vite in your dependencies, or a vite.config.js / vite.config.ts at the project root
- a custom start script that runs your own server changes the answer: that reads as a server app, not a static build
what happens when you push
- the cli runs your build locally and ships the dist folder
- served with spa fallback: paths without a file return your index.html, so client-side routing works
sharp edges
- build output must land in dist, the vite default
- uploading source through the dashboard skips the local build and gets a message pointing you back to the cli
deploying from an agent?
claude code and cursor can run all of this for you: connect your agent. the short machine-readable version of this site lives at https://pushto.host/llms.txt.
something off? run pushto doctor, or see all supported frameworks.