Lovable update, applied to your business

Lovable keeps your workspace's AI processing in the EU

Published October 5, 20262 min readLire en français

In short

Enterprise workspaces can have their AI requests processed by providers located in the European Union. The setting covers both building and AI features in published apps, but some models and features are unavailable and credit usage increases.

What changes for you

  1. 01Enterprise workspace admins and owners can enable the setting.
  2. 02EU providers process AI requests during building and in published apps.
  3. 03Some models and features are unavailable, and the workspace uses more credits.

3 concrete examples

Example

E-commerce and marketplaces

The problem

You want requests from your online shopping app's AI features to be processed in the EU.

How the update helps

The setting would route those requests to EU providers, subject to the models and features available there.

Example

Services and SMBs

The problem

Your team wants AI requests handled in the EU while building its app.

How the update helps

An Enterprise workspace admin or owner could enable EU processing for the building phase.

Example

Operations teams

The problem

You want EU processing to cover both building your tool and using its AI features after publication.

How the update helps

The workspace setting could cover both uses, with higher credit consumption and some features unavailable.

How to use it

  1. Step 1As an admin or owner, open your Enterprise workspace settings.
  2. Step 2Go to Privacy & security.
  3. Step 3Enable EU inference.

Who it’s for, who it isn’t

For you if

  • Enterprise workspace admins and owners.
  • Teams that want AI requests processed by EU providers.

Not for you if

  • Workspaces without an Enterprise plan: the described option does not apply to them.
  • Teams unwilling to increase their credit consumption.

Karim’s take

This option first serves Enterprise teams that must keep their workspace's AI processing in the European Union, both while building and in published apps. The trap: switching it on without planning for higher credit usage and for the models and features that are not available in the EU. With a client, I would first list the AI features in their tools and check that they remain available before enabling it.

FAQ

Who can enable this setting?

Admins and owners of Enterprise workspaces can enable it in the workspace's privacy and security settings.

Does it cover published apps too?

Yes. While enabled, it covers AI requests during building as well as requests from AI features in published apps.

Which models are unavailable, and how many extra credits are needed?

The source says some models and features are unavailable in the EU and the workspace uses more credits. It does not identify them or specify the increase.