Skip to main content
Percher is still being built — you can try it out on a free account right now. Create a free account
Percher
No app yet?

Haven't built anything yet? Start with a prompt.

Percher puts your app online. It doesn't build it for you, but the thing you want to host is closer than you think. Describe it to an AI assistant, get a working site or small app back, and publish it here at yourname.percher.run. This page is the fast path from idea to live.

Step 1: Tell an AI what to build

You don't need to write the code. Pick whichever of these you're most comfortable with and describe what you want in a sentence or two:

  • AI app builders (Lovable, v0, Bolt). Describe an app and they generate a working project you can download. Best for something interactive with a few screens.
  • Claude or ChatGPT. Ideal for a single-page site or a small tool. Ask for the files, then save them into one folder on your computer.
  • Cursor or Claude Code (in your editor).For when you want to keep tweaking. They edit the files in place, and once you connect Percher's MCP server they can publish for you too.

One tip that saves trouble later: ask for a static site (plain HTML or a framework that builds to files) or a simple Node or Bun app. Skip platform-specific features like edge functions. The prompt starters below already bake that in.

Step 2: Prompt starters

Copy one, swap in your own details, and paste it into your AI. Each is written so the result publishes on Percher without extra setup.

Personal site / portfolio

A single page about you and your work. The simplest thing to build and host.

Build a one-page personal portfolio as plain HTML, CSS, and JavaScript with no framework. Include a hero with my name and what I do, a projects grid, and a contact section. Keep it a static site I can deploy as-is, no build step.

Link in bio

A tidy page of links for your social profiles.

Build a single-page 'link in bio' site as static HTML and CSS. A round avatar, my name, a one-line bio, and a vertical list of tappable link buttons. Mobile-first, no build step.

Blog

Posts you write in Markdown, rendered as a clean readable site.

Create a blog as an Astro site with three example posts in Markdown, a home page that lists them, and a clean readable layout. Produce static output that's ready to deploy.

Landing page for an idea

One page to explain a product and collect interest.

Build a landing page for [describe your idea] as a static Vite + React site: a headline, three benefit cards, and an email signup form. Keep it a static build with no server.

A small tool or web app

Something interactive that remembers data between visits.

Build a small [todo / expense tracker / habit tracker] web app as a Node app using Express. Store data in a SQLite file. Include a package.json with a start script, and read the port from the PORT environment variable.

A simple API

A few JSON endpoints for another app to call.

Build a small JSON API in Node with Express: two or three endpoints plus a /health route. Read the port from the PORT environment variable and include a package.json with a start script.

Step 3: Publish it

Once you have a folder with your project in it, there are two ways to put it online:

  • Just ask your agent. With Percher's MCP server connected, say "publish this to Percher" and it handles the rest, including the live URL.
  • Or run one command. In your project folder, run bunx percher publish. Percher detects the framework, builds it, and returns the live link.

New to all of this? The quick start walks through it step by step.

Who Percher is for

Percher is for solo builders and personal apps: hobby sites, side projects, internal tools, the small thing you want online today. It runs in one region with no uptime SLA and no compliance certifications, so it isn't the right home for a paid SaaS or anything a customer depends on.

FAQ

Do I need to know how to code?

No. The point of this page is that you describe what you want in plain language and the AI writes the code. You do need to be able to copy files into a folder and run one publish command (or let an MCP-connected assistant run it for you). If a step is unclear, paste the error back to your assistant and ask it to fix it.

Which AI should I use?

For an interactive app, AI app builders like Lovable, v0, or Bolt let you describe it and download a working project. For a single-page site or a small tool, Claude or ChatGPT will write the files and you save them. If you want to keep tweaking, Cursor or Claude Code edit files in place and can even publish for you once Percher's MCP server is connected.

Why do the prompts say 'static site' or 'read PORT'?

Those constraints make the result publish cleanly on Percher. A static site (plain HTML or a framework that builds to files) needs no server. A Node or Bun app needs to listen on the port Percher gives it via the PORT environment variable and have a start script so Percher knows how to run it. Ask for those and the first publish usually just works.

What can't I host here?

Percher is for small, self-contained sites and apps. It runs in one region, has no uptime SLA, and no compliance certifications. It isn't the right home for a paid SaaS or anything a customer depends on. For a hobby site, a side project, or a tool you build for yourself, it's a good fit.

From idea to live URL

Free plan, no credit card. Build something small with AI, then run bunx percher publish.