Your company builds its own apps now. Who answers for them?
You do, as leadership. With Fabrika your people keep building and you know what runs. Sign-in, access and keys are held by the platform, whoever wrote the app.
AI-built apps already run in companies, often with nobody looking after them.
“We're 90 percent done. Finish the rest for us.”
The rest is authorisation, a data model, migrations, deployment, logging and GDPR. Developers say that's most of the work.
Lupa.cz, 2026 ↗of IT leaders know what's running
IT and security leaders who know which AI-built tools run in their production.
Retool, survey 2026 ↗have already had an incident
That's how many IT and security leaders say an AI-built tool has already caused one.
Retool, survey 2026 ↗Leadership answers for them, even if nobody ordered them
The same rules as bought software
With personal data of employees or customers inside, GDPR applies, including reporting a breach within 72 hours, side project or not.
The author leaves, the knowledge goes too
Nobody else knows where the app runs or where the code is. With an agency it's the same, only bigger: one supplier changes the system, at their price.
Without an overview you can't answer for anything
Which apps exist, what data they hold, who has access, whether they're on the internet. Nobody keeps that list unless asked to.
The Czech Cyber Security Act (NIS2)
Medium and large companies in listed sectors, such as parts of manufacturing, transport and healthcare, may fall under Act No. 264/2025 Coll.
If you do, Decree 410/2025 Coll. puts duties on top management even in the lower regime: training, resources for security and following how the measures are met (Section 4). It also requires security rules for developing your systems (Section 3), and that includes the apps your people build.
Not legal advice. Check with your lawyer whether the act applies to you.
NIS2 and the apps your company builds itself →One path where the rules hold
Fabrika is the platform your company builds its apps on, and the Contember team behind it. No need to ban AI.
The platform enforces the rules
Company sign-in, roles per app in one place, no public addresses. Sign-ins, access changes and deployments are recorded.
We also review every change before it goes live
Each version comes with a report of what changed and what we checked. We keep the platform patched without you asking.
Everything belongs to the company
Your own installation in your company's cloud account, usually on Zerops, AWS on request. Code, data and domains are yours. The platform is open source and runs without us.
One supplier
For Fabrika you deal only with us. The AI runs on your own plan, and we don't train anything on your data.
What stays with you
What the apps do and for whom, who gets which role, which change goes out and when.
Three ways onto Fabrika
Starting from scratch
We build the first app on one of your processes with the person who'll build the next ones. It usually takes a week.
Someone has already built an app
In Lovable, Cursor, Claude Code or at an agency. We take it over if it's code that runs outside the tool it was made in.
Taking over an existing app →You have developers or an agency
They keep building, on Fabrika. Operations, change review and the SLA are ours, under a contract with us.
Fabrika for your developers →What will it cost?
No numbers here: it depends on what you have and what you want to build.
Setting up Fabrika
The platform in your cloud account, rules for working with AI and a short training, plus the takeover changes or the first app. Usually not a big item.
Operations and review
Depends on how many apps you run and how often you deploy. Not on users or hours.
When you know the price
In the offer after the scoping call, before anything starts. Then it doesn't move.
Not in our price: cloud usage, paid by actual consumption, and your own AI plan.
How the pricing works →When is Fabrika not for you?
Off-the-shelf software fits
Then take it. Fabrika makes sense where the box doesn't fit.
One person, one spreadsheet, nothing on fire
Leave it until several people depend on it or data starts getting copied by hand.
The app lives in Bubble or a similar builder
We can't take that over. It can serve as a brief and we build the app again.
Nobody on your side will build or commission apps
Fabrika assumes apps get made on your side. A turnkey system is different work; we do that too, outside Fabrika.
Custom development →A one-off audit is enough for you
We review every change for as long as you use Fabrika, not once.
What owners and directors ask us
Do we need our own IT?
No. A capable person who knows your processes is enough, or your developer or agency. If you have IT, we work with them directly.
How much of our time will it take?
Half an hour for the scoping call. In a kickstart, your future builder spends the week with us; in a takeover, mainly whoever built the app.
What if the person who builds our apps leaves?
The apps keep running and the code is in Git, so the next person picks up with our help.
We don't fall under NIS2. Does this concern us at all?
Possibly through your customers. Regulated companies must agree change management and an exit strategy with suppliers (Annex 2 of the decree), so they may ask it of you.
Who answers when something goes wrong?
We do for the platform and the change review, as the contract sets out. When something breaks, we help find the cause, fix it and prepare documents for any report you must file.
Start with half an hour on what you have.
Tell us what runs in spreadsheets and what your people have built. We'll tell you whether it fits Fabrika. Bring your IT or your lawyer along.