You already build with AI. We add what production needs.
Someone at your company built a working app with Lovable, Cursor or Claude, and the business now leans on it. On Fabrika the platform holds sign-in, permissions and keys for it, and you can keep editing it in your own Claude or ChatGPT.
The remaining 10 percent
Developers hear this sentence from companies over and over. Behind it are authorisation, a data model that survives the first change of requirements, deployment, logging and GDPR. That's most of the work, not ten percent.
“We're 90 percent done. Finish the rest for us.”
Ready-made in the platform
- Sign-in with your company account (OIDC), or with a password
- Roles and permissions per app, in one place
- No public address: the only way in is through the platform
- Keys and passwords outside the app code
- Deployment from Git, with a record of each one
- Separate test and production
- Errors in one place, with alerts
Taken care of by us
- Reviewing every change before it goes live
- A report with each version
- Patching the platform
- Support for whoever 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 go through the code and make small changes so the platform handles sign-in, permissions, keys and deployment. It stays the same app, runs on Zerops, and the data comes with it.
A scoping call about your app
You show us what you've built and what the company uses it for. Afterwards you get an offer with the scope, the timeline and the price.
Takeover
We set up Fabrika in your cloud account, connect the app to it, move the data and deploy. How long it takes depends on the app, the offer says exactly.
You keep developing it
Your person keeps building with Claude Code or Codex, the way they're used to. If you want us to build the next app with you, you can add a kickstart week.
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.
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.
Does your app run on Supabase or Lovable Cloud?
Lovable apps usually keep their database, sign-in and files in Supabase. We decide with you what happens to it. Each option means different work and a different place for your data.
Move elsewhere
The data moves out of Supabase and the app runs without it.
Run Supabase in your account
Supabase runs in your own cloud account and we look after it.
Leave it where it is
The app runs on Fabrika and connects to Supabase where it runs today.
Not sure? Send us a link to the repository and we'll tell you.
What stays with you
Code, data and domains
Everything runs in a cloud account in your company's name and the platform is open source, so the app keeps running without us. If you ever leave, you take it all with you.
Your own AI
The AI always runs on your own plan, so you know where your data goes, and we train nothing on it. We're happy to advise on which provider makes sense.
What people ask us
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, and only people who sign in with their company account and have a role get in. Afterwards, switch off the old public version in the original tool.
What if people outside the company use the app too?
Parts of the app can be public, a registration form for example, while the rest stays behind sign-in. Outside users sign in with a password.
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 from Cursor or Claude Code the project is a folder on your computer. During the takeover the code gets a repository in your company's name.
Can our person handle it without being a programmer?
If they got an app working with AI, they can keep going. We show them what changed, and 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 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 to show us what they built. If they've gone, we manage without them. After the takeover a colleague or a new developer can pick the app up, because the code is in your company's repository and we've seen every change.
Our IT was handed the app and asked to deploy it. Can you help?
Yes. We deploy it to your cloud account and review every further change. IT keeps access and roles in one place instead of building operations for each app. Details for IT
What do the takeover and running it cost?
The takeover is a one-off sized to the app. Then a monthly fee depending on how many apps you run and how often you deploy, never per user or per hour. You get both in the offer after the scoping call. Servers and the database you pay the cloud provider directly.
Wouldn't a one-off audit be enough?
An audit tells you what's wrong today. But the app keeps changing, and every change made with AI can bring a new bug, so we review each one. If nobody will touch the app again, an audit may be enough.
Show us what you've got.
Half an hour is enough. Show us the app and what the company uses it for, and we'll tell you what the takeover involves, or plainly that we can't take it.