Built an app? We'll host it for you.

Flat monthly pricing, no usage meters. Free is €0 (three apps, each sleeps after 20 minutes idle and wakes on the next request). Paid plans are €3, €12, and €29 per month. There is no per-GB bandwidth bill and no token meter, so a busy weekend doesn't turn into a surprise invoice.

percher_doctor is the recovery hub. It reads the deploy and runtime logs, classifies the failure (build error, health-check timeout, missing env var, out-of-memory, crash loop) and returns a structured next action your assistant can act on: set the missing variable, fix the offending line, retry, or roll back. The crash-to-fix loop stays inside the assistant.

No. bunx percher publish works straight from your terminal with nothing else installed. MCP is the upgrade: once your assistant can call publish, logs, env, and rollback as tools, you stop switching tabs. The CLI is the foundation and works on its own.

Yes. Set runtime = "docker" in percher.toml and Percher builds your Dockerfile untouched. Otherwise bunx percher init detects the framework (Next.js, Vite, FastAPI, Django, and more) and writes the config for you, so most apps never need a Dockerfile at all.

If it needs one, opt into the managed PocketBase sidecar with [data] mode = "pocketbase": SQLite, authentication, and S3-compatible file storage in a single container, reachable through POCKETBASE_URL. Prefer your own backend? Point DATABASE_URL at any external Postgres.

Yes, on any paid plan. bunx percher domains add yourdomain.com prints the DNS records to set, and the certificate is issued automatically through Let's Encrypt. Free apps run on a name.percher.run subdomain.

The simplest route needs no store at all: add a web manifest and a service worker and your app becomes an installable PWA — it opens full-screen from the home screen and works offline. For many apps that's enough. To go further into the actual App Store or Google Play, you wrap your Percher app in a thin native shell (a TWA for Play, or a tool like Capacitor for both) while Percher keeps serving the web app and its backend. You bring the developer account and submit it; Percher doesn't publish to the stores for you. The guide explains the setup.

Read the guide →

For the apps most people build here, yes: every app gets a real HTTPS link, daily backups, logs, and one-click rollback. What it doesn't have is the heavy guarantees a paid product needs. It runs in one region, so a rare outage there means downtime with no automatic backup region. There's no uptime guarantee (an SLA), and it isn't audited for formal standards like SOC 2 or HIPAA. So it's a great home for personal projects, an app for your family or club, internal tools, or a small-business site, but not for a paid SaaS that customers depend on.

You're not locked in. Every deploy is git-backed and your data exports as a tarball at any time, so the same app and its database move elsewhere without a rewrite. We also publish a shutdown commitment on the "If Percher shuts down" page.