Quick start
Most people never touch a terminal. You tell your AI assistant to publish, and it does the rest.
Percher is built to be driven by an AI coding assistant that can see your project and use tools: for example Claude Code, Cursor, Windsurf, or an AI client connected to Percher. You can ask it to publish in plain words; you do not need to understand the commands it runs.
Publish this project to Percher. Read https://percher.app/docs/quick-start first. If you cannot access the project files or run Percher tools, tell me how to connect you instead of guessing. Before the first deploy, confirm the public app name with me. Keep secrets out of source code and return the live URL when the deploy is healthy.
Changed something and want the live version updated? Say “Publish my latest changes to percher.app.” It's the same flow.
What happens next
- 1Make sure your assistant can act. If it can edit this project and run terminal commands, it can use the Percher CLI. If you are in a chat-only client, connect Percher first at percher.app/connect. A normal chat with no project or Percher access cannot publish safely.
- 2The first time, you sign in. Your assistant opens a browser window (or hands you a link). Click approve. That's a one-time step, and after that it just works.
- 3It sets everything up for you. No config file knowledge or server choice is required. Your assistant detects the app type, shows you the public name, and handles the technical details.
- 4You get a link back. A couple of minutes later your assistant hands you a real web address like
your-app.percher.run, already secured with HTTPS. Share it with anyone.
That's the whole thing. Your app is live at your-app.percher.run with SSL, builds, and a health check, typically in about 2 minutes.
Before you share the link, open it once and check the main flow. New apps are public unless you explicitly add password or Percher-account protection.
Prefer to run it yourself? Percher also ships as a CLI, with no global install needed. Run it with bunx (Bun) or npx (Node). One command does login, config, and deploy:
# One command does everything: login, config, deploy cd my-app bunx percher publish # Granular control (only when you need to isolate a single phase): bunx percher login bunx percher init bunx percher push