Hosting for the way you actually code now
Hosting for vibe coders. Deploy as a tool call from Claude Code, Cursor, or Windsurf, with everything an app needs already wired up. Honest about what it isn't.
Read post →Blog
Notes from building it.
Deploys, MCP tooling, recovery contracts, performance fixes, and the trade-offs we hit while building Percher. Subscribe via RSS.
Your app, with the lid off
Percher's new Topology view is a live map of everything that makes your app run, including the parts Percher manages for you. It is also an MCP tool, so your assistant reads the same map you do.
Read post →Inside the node bypass: why cold builds got five times faster
Percher stopped using Nixpacks as the default for Node and Bun and wrote its own multi-stage Dockerfile generator. Cold builds went from a minute or two down to about twenty seconds. Here is the design and the trade-off.
Read post →From prompt to URL in 90 seconds
What "publish my app" actually does when you say it to an assistant with hosting tools. Walkthrough of the loop, the failure case, and the parts of the old workflow that disappeared.
Read post →Why we built MCP-first hosting
Deploys, logs, env vars, and rollback should be callable from the same place the code is being changed. That is the practical reason Percher is built around MCP.
Read post →The agent recovery contract
Percher errors include a typed nextAction so assistants can recover from deploy failures without parsing prose or guessing the next tool call.
Read post →Self-hosting fonts fixed a 7-second first paint
A Percher app had fast server responses but a blank page for seven seconds. The culprit was a blocked Google Fonts request, not the app server.
Read post →