deploy next.js

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-nextjs
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. we build it and run it as a server. you never touch the machinery. runs on the free tier too — your one free app can be a server; it naps after a quiet spell and wakes on the next visit. $13/mo lifts the one-project cap and keeps apps always awake.

how we know it's next.js

• next in the dependencies of your root package.json

what happens when you push

• your build script runs, then your start script
• pnpm, yarn and npm are all fine: the lockfile decides which one runs
• monorepo workspaces install correctly: member packages are picked up from pnpm-workspace.yaml or the workspaces field
• PORT is set to 8080 in the environment. next start picks it up on its own

sharp edges

• set output: "standalone" in your next config. the build ships the standalone server and will not start without it
• keep the scaffold build and start scripts in package.json
• no lockfile means a plain install instead of a locked one. commit your lockfile

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.