What deploying usually takes
To get feedback on a prototype, it has to be on the web. The standard route runs through infrastructure: initialize a Git repo, push to GitHub, connect the repo to a Vercel project, then deploy — or install the Vercel CLI and keep it and its login state current.
That setup earns its keep on a long-lived project. For showing a client a layout or checking a landing page on your phone, it's a lot of machinery for one URL.
Deploying from the editor
The Vercel integration in Kerf Pro skips that setup. There's no terminal involved and no branch to commit to: once your Vercel account is linked, Kerf deploys the current workspace itself.
How it works
- Connect. Authenticate with Vercel once.
- Select. Choose which Vercel project maps to your local folder.
- Ship. Click the Deploy button in the Kerf toolbar.
Kerf uploads the folder's HTML, CSS, and JS to Vercel and shows the live URL when the deploy finishes.
Where it fits
To be clear: this isn't a replacement for a CI/CD pipeline in a large team. If you work in a monorepo with complex build steps and dozens of contributors, keep using your Git-based workflow.
For solo builders and prototypes, the point is iteration speed: make a visual change, save, deploy, and send the URL, all from the same window.