Eurobase loves Lovable: how to run your Lovable app on a European backend
Nothing is loaded from YouTube until you press play. When you do, the video comes from YouTube (Google) and they can see that you watched it.
Lovable is a great product. It helps people everywhere create amazing apps by describing what they want, and a lot of those people have never set up a backend in their life. That is exactly why the default matters.
By default, Lovable saves your data in Lovable Cloud or in Supabase. Both are great products. But Lovable Cloud is built on Supabase, and Supabase is a US company running on AWS, so neither is 100% EU owned and operated. If you are building for European users, that is a question your customers or your DPO will ask sooner or later. We wrote about why an EU region is not the same thing as EU jurisdiction in "Our Data Deserves a Better Agreement".
So we made a guide on how to set up your Lovable project to use Eurobase as its backend. It takes about 6-7 minutes, and Eurobase makes it really easy for you: the console has a Connect → Lovable page where every value is already filled in for your project. You mostly copy and paste.
Prefer to watch? I recorded the whole setup, start to finish. It is the video at the top of this page. There is also a shorter reference version of these steps on the Lovable integration page.
Before you start
You need a Eurobase project. Sign up (free, no credit card), create a project, and open Connect → Lovable in the console. Keep that tab open next to Lovable; the six steps below are the same six steps you see there.
1. Stop Lovable from creating its own backend
In Lovable, go to Connectors → Cloud → Manage my agent's permissions and set Enable Cloud to Ask each time. If Lovable asks later whether it should enable Cloud, decline. Without this step, the first "add a login" prompt puts your users on Lovable Cloud.
2. Copy the environment values
Connect → Lovable shows three lines for your project. Copy them into your Lovable project:
- ▸
VITE_EUROBASE_URLis the address of your project, for examplehttps://my-app.eurobase.app - ▸
VITE_EUROBASE_PROJECT_IDis your project id - ▸
VITE_EUROBASE_PUBLIC_KEYis your public key, it starts witheb_pk_
Only the public key ever goes into Lovable. Never paste a secret key (eb_sk_) into Lovable or any other app builder. Anything that needs a secret belongs in an edge function.
3. Add the Eurobase skill
The skill teaches Lovable how to use @eurobase/sdk correctly: the right method signatures, row-level security, file privacy, and where secrets belong. Copy SKILL.md from the Connect page into Project settings → Knowledge in Lovable. If you are a workspace owner or admin, you can add it to your workspace skills instead, and then every project can use it.
4. Connect the Eurobase MCP server
This lets Lovable see your tables and create new ones. In Lovable, go to Connectors → + → MCP server and enter:
- ▸Server URL:
https://mcp.eurobase.app/mcp - ▸Authentication: Bearer token
The Connect page has a button that creates the token for you. It is a project token with Developer access, so Lovable can work in this one project and nothing else.
5. Allow your app's URLs
A Lovable app runs on several addresses: two for the preview, one for the published app, one for its shareable preview, and maybe your own domain. Paste your Lovable editor URL and your published URL into the Connect page and click Add to allowed URLs. The console works out all of the addresses and adds them to the allowed CORS origins and redirect URLs. Wildcards like *.lovable.app are not accepted, because anyone can publish there.
6. Start building
Copy the first prompt from the Connect page. It tells Lovable to use the Eurobase skill and to use Eurobase instead of Lovable Cloud. Add what you want to build, and send it.
That's it. From here on you work in Lovable the way you always do, and auth, database, storage, realtime and functions run on Eurobase.
What you get
- ▸Your data stays in the EU. Eurobase is operated by an Estonian company and runs on Scaleway in France. No US provider in the path.
- ▸GDPR tooling is already there. One-click DSAR export, the Article 30 report and the audit log come with every project, including Lovable ones. Here is how that works.
- ▸Real Postgres. Tables that Lovable creates are normal Postgres tables with row-level security. You can open them in the console's SQL editor at any time.
Try it
- ▸Sign up free and open Connect → Lovable
- ▸Watch the video walkthrough
- ▸Not sure how exposed your current stack is? Take the 60-second sovereignty check
If you get stuck anywhere, write to us. We would love to see what you build.
— Stefan