For Lovable users
The prototype works. You want a live URL on your own domain, predictable monthly cost, and the freedom to keep iterating from whichever assistant you prefer — with hosting on infrastructure separate from the AI builder.
Who Percher is for
Percher is for personal apps — projects you build for yourself or your close circle. It is notpositioned as production-grade or enterprise hosting today: no uptime SLA, no formal compliance attestation, single region in Germany. If your Lovable app is heading toward a paying customer base, Lovable's own production hosting or a higher-tier provider is the safer choice.
Lovable is excellent at one specific thing: turning a chat conversation into a working React + Vite + Supabase project, with an immediate preview URL you can share. For going from idea to running app in an hour, very little else compares. Lovable also ships its own paid hosting on top of that — so this isn't about Lovable lacking a host.
The reason to bring Percher into the loop is keeping the build vendor and the live-URL vendor separate. Different bills (one for AI tokens, one for hosting). Different reliability domains. Freedom to swap the AI tool later (Claude Code / Cursor / Windsurf all work via MCP) without touching where the app actually runs. Flat per-account pricing that doesn't move with builder token usage. EU data residency if you need it. That's the trade — not a feature Lovable lacks.
bunx percher publish picks up the new state.The actual migration is shorter than this paragraph. Lovable does most of the work by already exporting your project as a standard npm package; the rest is environment variables and a domain.
# 1. In Lovable: sync your project to GitHub
# 2. Clone it locally
git clone https://github.com/you/your-lovable-project
cd your-lovable-project
# 3. Generate percher.toml (init detects Vite + scaffolds Dockerfile + Caddyfile)
bunx percher init
# 4. Re-set your Supabase env vars (auto-forwarded to the build via the VITE_ prefix)
bunx percher env set VITE_SUPABASE_URL=https://xxx.supabase.co
bunx percher env set VITE_SUPABASE_ANON_KEY=eyJhbGc...
# 5. Build and deploy
bunx percher publish
# 6. Custom domain (one DNS update — the CLI prints the records)
bunx percher domains add yourdomain.comThree to five minutes end to end, including the DNS propagation wait. The Vite project ships as runtime = "docker"with a multi-stage build — a slim Bun image compiles the bundle, a slim Caddy image serves it. The result is a ~30 MB runtime image with instant cold starts and automatic SSL via Let's Encrypt.
name.percher.run right away, or bring your own domain on any paid plan. No platform-branded subdomain you have to live with.bunx percher logs streams runtime logs; bunx percher logs --build shows the build log of any deploy. Build a failed deploy log on the same view that your live one is on.After the migration, you're not locked into any specific AI tool. The Lovable chat-driven flow still works (sync to GitHub when ready, redeploy). Claude Code, Cursor, and Windsurf all work via Percher's MCP server — publish, logs, env, rollback, and ~37 other operations become native tool calls inside the assistant. Pick whichever fits the moment.
No — that's actually the whole point of the pattern. Build in Lovable, host on Percher. Keep using Lovable's chat to iterate on the app, sync to GitHub when you have a milestone, and re-deploy with `bunx percher publish`. The two layers stay independent: Lovable handles the build-by-chat experience, Percher serves the live URL.
Nothing — it stays exactly where it is. Supabase is reached over HTTPS from your client bundle; Percher's outbound proxy routes the request. Copy `VITE_SUPABASE_URL` and `VITE_SUPABASE_ANON_KEY` from Lovable's env vars and re-set them on Percher. The `VITE_*` prefix auto-forwards to the build container, so the values are baked into your bundle on the next deploy. Auth, RLS, edge functions — all unchanged.
Add your new Percher URL to Supabase Authentication → URL Configuration → Site URL and Redirect URLs. Without that, OAuth callbacks and email confirmations come back to the wrong domain. Every other Supabase auth feature works unchanged.
Yes. You keep the code (it's a standard Vite + React project on GitHub) and the Supabase backend. If Percher turns out not to be the right fit, you can deploy the same code somewhere else without lock-in. Percher is hosting, not a platform you build inside.
No, and we're not trying to build one. Percher is dedicated hosting for personal apps; the AI builder layer is Lovable's strength. The intended pairing is: Lovable (or Claude Code, or Cursor, or Windsurf) for building, Percher for hosting. The two roles stay separate.
Not today, and we're upfront about it. Percher runs in a single region in Germany, has no formal uptime SLA, and isn't certified against SOC 2 or HIPAA. It's a great fit for personal apps, internal tools, projects you build for yourself or your close circle — not for a monetised SaaS or anything where downtime has contractual consequences. If you're building something you intend to sell access to, Lovable's own production hosting or a higher-tier provider is the right call. We may grow into the production-grade space over time, but the platform isn't positioned there now.
Free plan, no credit card. Five commands and your project has a real URL.