Lovable × OpenBerth

Lovable hosting on your own server

Lovable builds the app. OpenBerth puts it online — on a server you own, under your own domain. One connector, two minutes, every Lovable project ships somewhere you control.

  • Live in 30 seconds
  • Your domain
  • No per-app bills
Quickstart

Connect Lovable in under a minute

Lovable supports custom MCP servers in project Settings. No CLI, no JSON file — paste a URL and an auth header.

  1. Open your Lovable project → Settings → Integrations → MCP.
  2. Click Add custom MCP server and paste the values below.
    Custom MCP server
    Name  OpenBerth
    URL   https://yourdomain.com/mcp
    Auth  Bearer bt_your_api_key
  3. Enable the connector. Then in any chat ask: “deploy the current project to my OpenBerth server.” Lovable hands the build off to OpenBerth and you get a live URL.

Replace yourdomain.com with your server’s URL and bt_your_api_key with an API key from your workspace’s People page.

What you can do

Ask Lovable, OpenBerth handles it

Ship in one sentence

Ask the AI to deploy and it does. Real HTTPS URL in seconds, no dashboard tab-hopping.

Iterate in a sandbox

Push live edits to a sandbox berth. Promote when it's right, throw it away when it isn't.

Roll back any release

Every deploy is versioned. One command (or one ask) and you're back to the last good build.

Manage secrets in plain English

Set, list, rotate, delete — your env vars stay on your server, never in the chat transcript.

Why your own server

OpenBerth handles hosting, so you handle creating

It's yours. Forever.

Your apps live on a server you own. Nobody else holds your code, your domain, or your customer data.

No surprise bills

Pay your server's flat monthly fee. Ship one app or a hundred — the price doesn't change.

Built for real apps

Databases, file uploads, background jobs, custom domains. The boring stuff that makes a website feel like a real product.

Every AI ships to one place

Lovable, Cursor, Claude, Gemini — they all push to the same dashboard. One place to see what's live.

FAQ

Common questions

  • Why host Lovable apps myself instead of on Lovable's hosting?
    Three reasons: you own the data and traffic logs, there are no per-app fees, and everything you build with AI lives in one place — Lovable apps next to anything you ship from Cursor or Claude, all in one dashboard.
  • Do I need to redeploy on every Lovable edit?
    No. Use a sandbox berth — Lovable can push live edits to it, and you promote to production when it looks right. The sandbox is a separate URL so you don't break the live version.
  • What about custom domains?
    OpenBerth wires up Caddy with automatic Let's Encrypt certs. Point a CNAME to your server, run `berth domain add app.example.com`, done.
  • Can Lovable see my server's API key?
    Yes — you're pasting a Bearer token into the connector form. Treat it like any third-party integration: rotate it from your OpenBerth People page if you stop using Lovable.
  • Does Lovable's free tier support custom MCP servers?
    No — custom MCP servers are a paid-plan feature on Lovable. The free tier ships with prebuilt connectors only. If you're on a paid plan, OpenBerth slots in like any other custom server.

Ready to ship from Lovable?

Stand up a server in minutes, paste the snippet above, and your AI tool can deploy on its own.