You already build with AI. We add what production needs.
Someone at your company built an app with Lovable, Cursor or Claude, and it works. That's exactly why the business starts to lean on it. What turns a prototype into software you can trust with customer data is still missing: controlled sign-in, permissions, reviewed changes, and someone who keeps it running.
The remaining 10 percent
Developers hear the same sentence from companies over and over. What sits behind it is authorisation, a data model that survives the first change of requirements, deployment, logging and GDPR. That isn't ten percent of the work. It's most of it. Here's who takes care of which part.
“We're 90 percent done. Finish the rest for us.”
Ready-made in the platform
- Sign-in with your company account through Google or Microsoft Entra, or with a password
- Roles and permissions per app, managed in one place
- The app has no public address. The only way in leads through the platform
- Keys and passwords are held by the cloud platform, not the app code
- Deployment from Git, with a record of every deployment
- Separate test and production environments
- Errors collected in one place, with alerts
Taken care of by us
- Reviewing every change before it goes live
- A report with each version: what changed and what we checked
- Patching the platform
- Support for the person who builds
- Help when something goes wrong
Staying with you
- What the app does and for whom
- Screens, forms and the rules of your process
- Who gets which role
- Deciding which change goes out and when
What we do with your app
We take the app over. We go through the code and make small changes so the platform handles its sign-in, permissions, keys and deployment. Nothing dramatic, it stays the same app. Then we help deploy it to Cloudflare or Zerops and the data comes with it.
A scoping call about your app
Half an hour where you show us what you've built and what the company already uses it for. We look at what it's built in and tell you what the takeover involves. Afterwards you get an offer with the scope, the timeline and the price.
Takeover
We set up Fabrika in your cloud account and hook the app up to it: sign-in through the platform, roles, keys, deployment from Git. We move the data over and deploy the app. How long it takes depends on the app; the offer says exactly.
You keep developing it
Your person keeps building it the way they're used to, with AI. Every change goes through our review before it goes live, and each version comes with a report of what we checked. If you'd like us to build the next app with you right away, a kickstart week can be added, but it's optional.
Which apps can you take over?
What matters isn't the tool, it's whether the app is code that can run outside the tool it was built in. If it is, we can take it over.
We take over
- Apps from Lovable, once the code is in Git
- Apps from Cursor, Claude Code or Replit
- Code from a freelancer or an agency
We don't take over
- Apps clicked together in Bubble and similar builders that can't export their code
There the app can serve as a brief and we build it again. A kickstart week is one way to do that, but it's optional.
Does your app run on Supabase or Lovable Cloud?
Apps from Lovable usually keep their database, sign-in and files in Supabase. What happens to it is always a decision we make with you during the takeover. There are three options:
Move elsewhere
The data moves out of Supabase and the app runs without it.
Run Supabase in your account
Supabase stays part of the app and runs in your own cloud account. We look after it.
Leave it where it is
The app runs on Fabrika and connects to Supabase where it runs today.
Each option means a different amount of work during the takeover and a different place where your data lives. We'll go through them on the call.
Not sure? Send us a link to the repository, or show us the app on the call. We'll tell you whether we can take it over.
Got an app from Lovable? Here's how it gets into production →What stays with you
The takeover doesn't take the app out of your hands. It adds the part you'd otherwise have to build and look after yourself.
Code, data and domains
Everything runs in a cloud account in your company's name. The code of the app is yours, and so are the data and the domains.
Your own AI
The AI always runs on your own plan, so you know where your data goes. We don't train anything on your data. We're happy to advise on which provider makes sense for you.
The tool you know
Your person keeps building with Claude Code or Codex, the way they're used to. The difference is that the platform sets the boundaries and we review what goes out.
What people ask us
Do we have to throw away what we have?
No. We take the app over and make small changes so the platform handles sign-in, permissions, keys and deployment. It stays the same app, and the data you already have comes with it.
Will you take over an app built in Bubble?
No, unfortunately. We need code that can run outside the tool it was built in. Apps from Lovable, Cursor, Claude Code or from a developer are fine. Apps that only run inside a no-code builder like Bubble aren't. There, the app can serve as a brief and we build it again, in a kickstart week for example.
Our app is on a public URL right now. Can we make it just for our people?
Yes. On Fabrika the app has no public address. The only way in leads through the platform, and it lets in only people who sign in and have a role in the app. Your people use their company account, they don't have to create a new one anywhere. Once it runs on Fabrika, switch off the old public version in the original tool so it doesn't stay open.
What if people outside the company use the app too?
Parts of an app can be public, a registration form for example, while everything else stays behind sign-in. External users can sign in with a password, your own people with their company account.
We don't use Git. How do we send you the code?
You don't need Git. Lovable and Replit can push the code to GitHub, and with Cursor or Claude Code the project sits in a folder on your computer. We'll agree on the call how you hand it over. During the takeover the code gets a repository in your company's name, and from then on it lives there.
Can our person handle it without being a programmer?
If they got an app working with AI, they can keep going. During the takeover we show them what changed and how the platform works, and afterwards they have our review and support behind them.
Can we keep building in Lovable after the takeover?
We're checking that right now, so ask us how far we've got. What's certain is that after the takeover your person can keep building with Claude Code or Codex. More on apps from Lovable →
The person who built it is leaving. What now?
Ideally start while they're still around, so they can show us what they built and why. If they've already gone, we can manage without them. After the takeover the code is in a repository in your company's name, the app runs in your cloud account and we've seen every change in review. A colleague or a developer you hire can pick it up from there, with the same review and support behind them.
Our IT was handed the app and asked to deploy it. Can you help?
Yes. We take the app over, deploy it to your cloud account and review every further change before it goes live. IT keeps access and roles in one place and doesn't have to build its own operations for each app. The technical details for IT are on the Security page.
What do the takeover and running it cost?
The takeover is a one-off, and its size depends on the app. Then you pay us monthly, depending on how many apps you run and how often you deploy. You get both in the offer after the scoping call, before anything starts. You never pay per user or per hour. Servers and the database are paid separately, directly to the cloud provider based on usage, because the account is in your name. The AI runs on your own plan.
Wouldn't a one-off audit be enough?
An audit tells you what's wrong with the app today, and that's worth something. But the app keeps changing, and every further change made with AI can bring a new bug. We take the app into production and review every further change before it goes live. If nobody is going to touch the app again, an audit may be all you need.
Won't this just be another dependency?
The code, the data and the cloud account are yours, and the system keeps running without us. What you get from us is the review and the support. If you ever stop wanting those, you take everything with you.
Show us what you've got.
Half an hour is enough. Show us the app and what the company already uses it for, and we'll tell you what the takeover involves. If it's built somewhere we can't take it from, we'll say so plainly.