Decision guide

Percher or Lovable?

Lovable and Percher are not really competitors — they sit at different layers of the stack. Lovable is an AI app builder: you describe what you want in a chat, and it generates a React + Vite + Supabase project plus a preview URL you can share — and on paid plans, custom domains and real deployment. So this isn't a hosting comparison; both can host. The pattern this page is about is the bridge: build in Lovable, host on Percher. People do this when they want the Lovable build experience but want hosting on infrastructure separate from the AI builder — your own domain, runtime logs, per-deploy rollback, flat per-account pricing that doesn't depend on builder token usage, and EU data residency. Percher is the second host you keep code on once Lovable has done the building part — best fit for personal projects, not for monetised SaaS or anything that needs a formal uptime SLA.

Who Percher is for

Percher is built for personal apps — projects you build for yourself or your close circle. It is notpositioned as production-grade or enterprise hosting today: there is no uptime SLA, no formal compliance attestation, and a single region in Germany. If you're shipping a monetised SaaS, an app for paying customers, or anything that needs an SLA, Lovable or a higher-tier provider is the safer choice. Percher may grow into that space; it is not there now.

At a glance

When Percher is the better choice

• You want hosting separated from the AI builder — different vendors, different bills, different reliability domains. Lovable's hosting works; this is about keeping it untangled.
• Your daily AI assistant is Claude Code, Cursor, or Windsurf rather than Lovable's chat, and you want operational tools (publish, logs, env, rollback, doctor) accessible to that assistant via MCP.
• You want flat per-account hosting cost decoupled from AI builder token usage. On Percher the hosting bill is €0 / €3 / €12 / €29 per month regardless of what tools you use to write the code.
• Your hosting must stay in the EU for data-residency reasons. Percher runs in Germany only; Lovable's hosting is US-based.
• You want full operational visibility — runtime logs, build logs, deploy history, metrics — tuned for diagnosing live-traffic issues, not just preview-iteration.

When Percher is the wrong choice (and Lovable fits better)

• You're still in the prototype phase and want the AI to write the code, not just host it. Lovable is excellent for that part; Percher doesn't build apps for you.
• You haven't written any code yet and a chat-based AI builder is the fastest path from idea to running preview.
• You want one vendor handling both the build experience and the live hosting, with the in-chat workflow staying intact across milestones — Lovable's bundled hosting is well-tuned for that.
• You're invested in Lovable's chat-based workflow for non-developers — designers, founders, PMs spinning up internal tools — and the production-host split would add friction.
• Your team's review loop is happening inside Lovable (in-chat preview, branch-style versions, comment threads on prompts) and moving to Percher would split that workflow.

Migrating from Lovable

The migration path is straightforward because Lovable lets you sync the project to GitHub. Once your Lovable project is in a repo, clone it locally, run `bunx percher init` to detect the Vite framework (Lovable scaffolds Vite + React by default), and `bunx percher publish` builds and deploys it. The Vite app ships as `runtime = "docker"` with a multi-stage build (Bun stage compiles, slim Caddy stage serves the static bundle) — `init` scaffolds the Dockerfile and Caddyfile automatically.

Your Supabase backend keeps working unchanged. Copy the Supabase URL and anon key from Lovable's env vars and re-set with `bunx percher env set VITE_SUPABASE_URL=...` and `bunx percher env set VITE_SUPABASE_ANON_KEY=...` — Percher auto-forwards any `VITE_*` env var to the build, so the values reach your client bundle without further configuration. Custom domain moves with a one-time DNS update. The app stays connected to the same Supabase project; only the host changes.

# 1. In Lovable: sync your project to GitHub
# 2. Clone the repo locally:
git clone https://github.com/you/your-lovable-project
cd your-lovable-project
bunx percher init            # detects Vite, scaffolds Dockerfile + Caddyfile
bunx percher env set VITE_SUPABASE_URL=https://xxx.supabase.co
bunx percher env set VITE_SUPABASE_ANON_KEY=eyJ...
bunx percher publish         # build + deploy
bunx percher domains add yourdomain.com

FAQ

Try Percher in under a minute

Free plan, no credit card. Bring any Node, Bun, Python, or Docker app.

Bringing an existing app? See recommended setup or the migration walkthrough above.