A few people use the app
Nothing important depends on it, and it's enough that only your colleagues can open it. On Business and Enterprise you can restrict a published app to workspace members, or to specific people and groups.
If you're fine with your apps running in Lovable's cloud and your own people checking what gets published, Lovable Enterprise covers a lot: SSO, SCIM, audit logs, publishing controls, SOC 2 Type II and ISO 27001. Taking the app into Fabrika makes sense when you want it running in your own cloud account, the data outside Lovable Cloud, and a person reviewing every change before it goes live.
This page is for IT and leadership in a company where people already build in Lovable and an app has become something the company depends on.
Updated 28 September 2026
We checked the details about Lovable on lovable.dev and docs.lovable.dev. Plans change; the sources are listed under the table.
IT decides who can publish and where each app runs, in Lovable's cloud.
The app runs in your account on Cloudflare or Zerops (AWS on request). A person reads every change.
Whether you can keep building in Lovable after the takeover, we're testing right now. Ask us.
On the left, you stay in Lovable and use its Enterprise plan. On the right, the app starts in Lovable and we take it over into your own cloud account on Fabrika.
| Question | Lovable Enterprise | Lovable + Fabrika |
|---|---|---|
| Who builds | Lovable Enterprise Anyone in the company, in Lovable's chat editor with a live preview. | Lovable + Fabrika The app starts in Lovable. After the takeover you carry on in Claude Code or Cursor, or we develop it for you. Whether you can keep building in Lovable itself, we're verifying right now; ask us. |
| Where apps run | Lovable Enterprise Lovable Cloud by default. Deploy on AWS or Azure is in private preview. | Lovable + Fabrika Your own installation on Cloudflare or Zerops, or AWS on request, in a cloud account registered to your company. The app has no public address. |
| Where the data lives | Lovable Enterprise In Lovable Cloud, in the region you pick (EU, US or Asia Pacific), or in your own Supabase project. | Lovable + Fabrika We decide it together: move the data to a database in your cloud account, run Supabase in your account, or leave it where it is for now. |
| Sign-in | Lovable Enterprise Workspace SSO through SAML 2.0 or OIDC. Enterprise promises apps “behind your SSO”. | Lovable + Fabrika The platform's single gate: company account via OIDC (Google, Microsoft Entra, Okta), or a password for outside people. No SAML. |
| Users and records | Lovable Enterprise SCIM provisioning and audit logs on Enterprise. | Lovable + Fabrika No SCIM. Roles per app in one place. Sign-ins are logged, changes to access and roles are kept, every deployment is recorded. |
| Publishing | Lovable Enterprise Publishing controls on Enterprise: external publishing can be limited to admins and owners. By default, editors and above can publish. | Lovable + Fabrika Nothing reaches production without our review. We agree with you to take down the copy published on lovable.app. |
| Who reviews changes | Lovable Enterprise Automated security scans before publishing, deep scans on demand, scheduled scans on Business and Enterprise. Reading the code of each change is up to you. | Lovable + Fabrika A person from Contember reads every change before it goes live, and you get a report on what went out. |
| Certifications | Lovable Enterprise SOC 2 Type II and ISO 27001, GDPR support, and AIUC-1. | Lovable + Fabrika Fabrika holds no certification of its own. For IT, we've written up what the platform handles and answers to a security questionnaire. |
| If you leave | Lovable Enterprise The code syncs to GitHub and is yours. The Lovable editor can't be self-hosted. Hosting, sign-in and moving data out of Lovable Cloud are up to you. | Lovable + Fabrika Code, data, domains and the cloud account are yours. The system keeps running without us, and the next person picks it up from Git. |
| How you pay | Lovable Enterprise Enterprise pricing is volume-based, through Lovable's sales team. Business starts at USD 50 a month. | Lovable + Fabrika A one-off takeover and setup, then monthly operations priced by the number of apps. You get the price in an offer after the first call. A Lovable plan, if you keep one, is separate. |
Lovable details are as of 28 September 2026, from lovable.dev and docs.lovable.dev. Lovable changes its plans often; check the current pages before you decide.
Sources, checked 28 September 2026
Often. Here's when we'd tell you to stay in Lovable.
Nothing important depends on it, and it's enough that only your colleagues can open it. On Business and Enterprise you can restrict a published app to workspace members, or to specific people and groups.
Lovable Enterprise has SOC 2 Type II, ISO 27001, SAML, SCIM and audit logs. If your procurement asks for these from the vendor, Lovable has them and Fabrika doesn't.
Lovable Cloud lets you pick the region (EU, US or Asia Pacific), and on Business and Enterprise your workspace data isn't used to train Lovable's models.
Enterprise gives IT publishing controls and automated scans. If you have a person who reads changes before they're published, you may not need a review service.
When the app runs part of the company and you want it held by you, not by a tool. The whole takeover is described in From Lovable to production.
The app runs in a cloud account registered to your company, so we're your only supplier. The data can leave Lovable Cloud; what happens to it we decide together.
Automated scans and a person who understands what a change does are two different things. On Fabrika, someone from Contember reads every change before it goes live.
The code is in your Git. The next change can come from Claude Code, Cursor, your developer or your agency, and it goes through the same review.
One app from Lovable, another from Cursor, a third from a freelancer. On Fabrika they share one sign-in, one set of roles and one way into production.
What we know today, from Lovable's documentation. Nothing more.
We take the code from the repository Lovable creates. Lovable exports to GitHub, but it can't import an existing repository back. We don't need access to your Lovable account.
Lovable Cloud can export the database (up to 15 GB, an export file of at most 5 GB, once every 24 hours). Then it goes to your cloud account, into Supabase run in your account, or stays where it is for now.
We make small changes, connect the app to the platform's sign-in and roles, and deploy it on Cloudflare or Zerops. Then we agree with you to take down the copy published on lovable.app, so no second version runs outside review.
Today you can carry on in Claude Code or Cursor, or we develop the app for you. Whether you can keep building in Lovable, we're verifying right now; ask us where it stands.
The full walkthrough, including Supabase and older React and Vite apps, is on From Lovable to production.
Worth knowing before you decide. If any of this is a hard requirement, Lovable Enterprise may be the right answer.
Lovable supports SAML 2.0 and OIDC for workspace sign-in and SCIM provisioning on Enterprise. Fabrika connects company accounts through OIDC only and has no SCIM.
Lovable lists SOC 2 Type II, ISO 27001 and AIUC-1. Fabrika holds no certification of its own.
Lovable Enterprise has audit logs your security team can read. Fabrika records sign-ins, access changes and deployments, but it isn't an audit product.
Lovable scans before publishing and on demand, and lists integrations with Wiz and Aikido. Our review is done by a person.
People who don't write code build in a chat with a live preview, in one product, with self-serve plans you can start today.
It gives IT real controls: SSO, SCIM, publishing controls, audit logs and automated scans. What it doesn't do is read each change for you and decide whether it does what it should. On Fabrika, a person does that before every deployment.
We're verifying it right now, ask us. Lovable syncs with GitHub in both directions, so the road is there, but we want to test it on a real app before we promise it. Today you can carry on in Claude Code or Cursor, or we develop the app for you.
Lovable says Lovable Cloud supports regional hosting in the EU, US and Asia Pacific and data stays in the region you select. On Fabrika the data sits in a cloud account registered to your company. If you need it in the Czech Republic, Zerops is a Czech company with a data centre in Prague.
No. For IT, we've written up what the platform handles and how a change gets into production on Security, and answered a typical security questionnaire.
Not necessarily. Lovable is where the app starts. Fabrika is where it runs once the company depends on it. Whether you keep a Lovable plan afterwards depends on where you'll keep building.
No. Leaving the data where it is can be the first step: Fabrika handles sign-in, deployment and change review, and the data stays managed where it is today. We decide together when, and whether, to move it.
Lovable Enterprise is priced by volume through their sales team. On Fabrika you pay a one-off takeover and setup, then a monthly fee by the number of apps, never per user. Servers are paid directly to Cloudflare or Zerops. You get the figures in the offer after the first call. More on Pricing.
From lovable.dev and docs.lovable.dev, checked on 28 September 2026. The sources are listed under the table. If you spot something out of date, write to sales@contember.com.
Half an hour is enough. We'll look at what the app does and where the data is, and tell you whether Lovable Enterprise is enough or a takeover makes sense.