Your company builds its own apps now. Who answers for them?

You do, as leadership. Fabrika is a platform and a team that let you know what runs in the company, who has access to it, and that every change was reviewed before it went live.

Your people or your suppliers keep building the apps. They just do it along one path, where the platform enforces the rules and we review the changes.

What's happening with apps in companies today?

Important processes run in spreadsheets, and data gets copied between them by hand. A capable colleague can now build an app with AI in a few days, and it often works. The company starts relying on it before anyone asks who will look after it.

90 %

“We're 90 percent done. Finish the rest for us.”

That's what companies bring to developers now. The rest is authorisation, a data model, migrations, deployment, logging and GDPR. Developers say that isn't ten percent of the work, it's most of it.

Lupa.cz, 2026 ↗
5 %

of IT leaders know what's running

Only 5 % of IT and security leaders know which AI-built tools run in their production. In a company without an IT department, often nobody knows.

Retool, survey 2026 ↗
22 %

have already had an incident

In the same survey, 22 % of IT and security leaders said an AI-built tool had already caused an incident.

Retool, survey 2026 ↗
“…the development of applications critical to how the company runs and grows may rest on one irreplaceable person.”
An employee who built two company apps with AI herself, translated from Czech Lupa.cz, 2025 ↗

What does it mean for you as leadership?

“So the key question is who will take responsibility for the resulting 90/10 patchwork.”
A reader under the article, translated from Czech Lupa.cz, 2026 ↗

You answer for apps nobody ordered

An app your people built themselves falls under the same rules as software you buy. As soon as it holds personal data of employees or customers, GDPR applies, including reporting a breach to the authority within 72 hours. It doesn't matter that it started as someone's side project.

What if the person who built it leaves?

An app built with AI is often known only to its author. When they leave, nobody knows where it runs, where the code is or how changes get in. With an agency it's the same, only bigger: one supplier can change the system, at their price.

Do you know what's running?

Which apps exist, what data they hold, who has access and whether they can be reached from the internet. Without that overview you can't answer for anything, and nobody will hand it to you unless someone is asked to keep it.

The Czech Cyber Security Act (NIS2)

Medium and large companies in listed sectors, among them parts of manufacturing, transport and healthcare, may fall under Act No. 264/2025 Coll. Whether you do is worth checking.

If you do, Decree 410/2025 Coll. puts duties directly on top management even in the lower regime (Section 4): complete training, provide the resources for security, and demonstrably keep up with how the security measures are being met. The company also has to set security requirements for developing and maintaining its systems (Section 3). The apps your people build are exactly that kind of development.

The rules can reach you indirectly too. Regulated companies must address in their supplier contracts, among other things, change management and an exit strategy (Section 3(5) and Annex 2), so they may ask the same of you as their supplier.

This isn't legal advice. Whether and how the act applies to you is best assessed with your lawyer.

How does Fabrika solve it?

You don't have to slow your people down or ban AI. You give them one path where the rules hold. Fabrika is the platform your company builds its own apps on, and the Contember team behind it.

01

The platform enforces the rules, not each app on its own

People sign in with their company account. Roles and permissions are set per app, in one place. The apps have no public address; the only way in leads through the platform. Sign-ins, access changes and deployments are recorded.

02

We review every change before it goes live

Nothing gets into production without our review. Each version comes with a report of what changed and what we checked. We keep the platform patched without you having to ask.

03

Everything belongs to the company

The apps run in your own installation, in a cloud account in your company's name, with Cloudflare or Zerops, or AWS if you prefer. The code, the data and the domains are yours, and the system keeps running without us.

04

One supplier

The cloud account is registered to your company, so the only supplier you deal with for Fabrika is 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, and which change goes out and when. Those are decisions for the company, not for the platform.

The technical detail for your IT →

How do you get onto Fabrika?

It always starts with setting Fabrika up: the platform in your cloud account, the rules for working with AI, and a short training. The first app then gets onto it one of three ways.

01 Kickstart

Starting from scratch

We build the first app on one of your processes together with the person who'll build the next ones. It usually takes a week. It's optional; you don't have to start this way.

How the kickstart works →
optional
02 Takeover

Someone has already built an app

In Lovable, Cursor or Claude Code, or you got it from an agency. We take it over, make small changes and deploy it. One condition: it has to be code that runs outside the tool it was made in.

Taking over an existing app →
depends on the app
03 Your developers

You have developers or an agency

They keep building, only on Fabrika. Operations, change review and the SLA sit with us, and your contract is with us directly.

Fabrika for your developers →
ongoing

What will it cost?

You won't find numbers here, because it depends on what you have and what you want to build. What we can tell you is what the price is made of and when you'll know it.

one-off

Setting up Fabrika

The platform in your cloud account, the rules for working with AI, a short training. With a takeover, also the changes to your app; with a kickstart, building the first app. It's usually not a big item.

monthly

Operations and review

Depends on how many apps you run and how often you deploy. Not on the number of users, and not on hours worked.

before we start

When you know the price

It's in the offer you get after the scoping call, before anything starts. Then it doesn't move.

Not part of our price: cloud usage, which you pay according to actual consumption, and your own AI plan.

How the pricing works →

When is Fabrika not for you?

We'll say it on the call too, but it's better you know up front.

Off-the-shelf software covers the process

If a boxed product does what you need, take it. Fabrika makes sense where the box doesn't fit.

One person uses the spreadsheet and nothing is on fire

Then leave it. A spreadsheet is fine until several people depend on it or the data starts getting copied by hand.

The app is clicked together 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, by your person or your supplier. If you want one large system delivered turnkey, that's different work. We do it too, just not as Fabrika.

Custom development →

A one-off audit is enough for you

We don't check an app once. We review every change for as long as you use Fabrika.

What owners and directors ask us

Do we need our own IT?

No. A capable person who knows your processes and will build with AI is enough, or the developer or agency you already work with. The platform enforces the rules and we review the changes. If you do have IT, we'll work with them directly.

How much of our time will it take?

The scoping call is half an hour. In a kickstart, the person who'll build your next apps spends the week with us, and the people who know the process join at the start. In a takeover we mostly need whoever built the app. After that it depends on how much you want to build.

What if the person who builds our apps leaves?

The apps stay where they are and keep running. The code is in Git, the rules are in the platform, and we've seen every change during review. The next person picks up where the last one stopped, and we help them find their feet.

We don't fall under NIS2. Does this concern us at all?

Possibly indirectly. Regulated customers have to address change management and an exit strategy with their suppliers, so they may ask it of you. And GDPR applies to every app with personal data. Whether you fall under the act is best checked with a lawyer.

Isn't off-the-shelf software cheaper?

If you can find one that fits, yes. Fabrika is for processes a box won't cover, and for the apps your people are building anyway. You pay for apps in production, not per seat, so the price doesn't grow with headcount.

Who answers when something goes wrong?

We do for the platform and for the change review; the exact commitments are in the contract. When something breaks, we help find out what happened in the app, fix it, and put together the documents for any report you have to file. Who gets which role, and what a person does with data they're allowed to see, stays with you.

Won't this just be another vendor 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.

Can we bring our IT or our lawyer to the call?

Please do. Security and contract questions are best answered right away. For IT, the details of what the platform handles are on the security page.

Start with half an hour on what you have.

Tell us what runs in spreadsheets, what your people have already built and who looks after it today. We'll tell you whether and how it would work on Fabrika. Bring your IT along if you like; security questions are best answered right away.