Safe, because it has to be.Fast, because now it can be.
The platform handles security, not whoever built the app: company sign-in, access and keys kept out of the code. It's open source and runs in your own cloud account. A new app takes a few days with AI, and your people can edit it themselves in their own Claude or ChatGPT.
No public address. Everyone comes in through the platform's sign-in.
2
AI builds inside
Built with AI on your company's own AI plan, within the platform's rules.
3
Keys held apart
The cloud platform holds passwords and keys. Each app sees only its own.
4
A record
Sign-ins, access changes and deployments: who, what and when.
5
Reviewed changes
We go through every change before it goes live.
1
One way in
No public address. Everyone comes in through the platform's sign-in.
2
AI builds inside
Built with AI on your company's own AI plan, within the platform's rules.
3
Keys held apart
The cloud platform holds passwords and keys. Each app sees only its own.
4
A record
Sign-ins, access changes and deployments: who, what and when.
5
Reviewed changes
We go through every change before it goes live.
Changes to an app? Just ask your Claude or ChatGPT.
No programming needed. Much like in Lovable, only inside the apps your company allows, and nothing goes live without a person. Connect it to Fabrika once and sign in with the company account.
1
Say what you want
For example “add an invoice number to orders”. The AI changes the app's code.
2
Try it on a test copy
Within a few minutes the change is on a test copy, away from live use, so you can click through it first.
3
A person lets it go live
Someone on your side approves it and we review it, the same day if that's what we agree. A change that widens access also waits for your approver.
New: apps on Zerops, and we're still verifying the whole flow in real use.
PPetra from salesConnected to Fabrika
9:12
In the Orders app, add an invoice number to each order and show it in the list.
9:13
Should the number be required, or can it stay empty until the invoice is issued?
9:14
Empty until it's issued. Only accounting can fill it in.
9:17 · fabrika · deploy_stage
Done. I added the field, only the Accounting role can edit it, and it's on the test copy at orders-stage.northwind.example. Try it and tell me when it's good.
9:23
Works. Send it on.
9:23 · fabrika · create_pull_request
I've asked for approval. It gives Accounting a new permission, so your approver confirms it too. It goes live once a person approves it.
10:04 · approved by Jana Nováková · live
Write a message…
What gets made, and how fast
One asks, another approves: holidays, trips, small purchases.
Estimate: A day or two
Contracts, vehicles, equipment, certificates. With deadlines and reminders.
Estimate: A day or two
Trips and work done, entered on a phone instead of paper.
Estimate: A day or two
Approval rounds and matching. Purchase requests work the same.
Estimate: Two or three days
Enquiries, offers, deals. Your sales steps, not a hundred fields.
Estimate: Two or three days
Hours by project, straight into billing.
Estimate: Two or three days
Order status, documents and requests for your clients.
Estimate: Four or five days
From intake to delivery, with statuses and history.
Estimate: Four or five days
People, machines or dates against commitments.
Estimate: Four or five days
Anything that lives in spreadsheets, e-mail and people's heads, in any industry. Built with you in the kickstart, a small app takes a day or two, a bigger one the week. Nine examples out of many.
helpdesk
bookings
complaints
inspections
onboarding
board reporting
shift handovers
asset register
purchase requests
training records
stock counts
visitor log
helpdesk
bookings
complaints
inspections
onboarding
board reporting
shift handovers
asset register
purchase requests
training records
stock counts
visitor log
The list has no end. We pick your first app together on the scoping call.
Your people are already building apps. Who's watching what runs?
With AI, a capable colleague builds a working app in a few days. What makes it safe for customer data doesn't come from the AI: sign-in, permissions, deployment, reviewed changes and someone to keep it running.
AI made writing software cheaper. It didn't make owning it cheaper.
90 %
“We're 90 percent done. Finish the rest for us.”
The rest is authorisation, data model, migrations, deployment, logging and GDPR. Developers say that's most of the work.
“I've seen AI coding. But who's going to maintain it here?”
Unmanaged, an app becomes shadow IT that ends when its author leaves. On Fabrika we handle operations, patches and the review of every change, and the code and data stay with your company.
The platform keeps the rules. Here's what that means in practice.
Sign-in, permissions, outgoing e-mail and error reports live in the platform, once for all your apps. Four situations from everyday work.
More access only after a person says yes
Someone in HR asks the AI to let assistants export candidates too. The deployment stops and the approver sees one plain line: the role HR assistant gains exporting candidates. Until they say yes, the app runs as before.
Applies to a new permission, public form, outside address or e-mail sender. Taking access away goes through on its own.
Unusual steps, such as direct database queries, are flagged.
The platform reads the change itself, not what the AI says about it.
On by default in production, set per environment. Every decision is recorded.
On top of that, our team reviews every change before it's deployed.
console.northwind.example/approvals/01a16386
A deployment waiting for approval. Each line says in plain words what would change.
Every e-mail your apps send, in one place
Every e-mail an app sends through company mail is recorded: who, to whom, when. A rule like “hold anything this app sends outside our domain” makes those messages wait for someone to release or drop them.
Rules per app and recipient domain: send, hold or drop.
Apps never get the login to your mail service.
Bulk e-mails can carry one-click unsubscribe.
Applies to apps running on Zerops.
console.northwind.example/mail
One gate and one company login for every app
Your people sign in with the company account they already have. A partner gets an invitation and sees only their firm's data. Remove someone in one place and their access ends in every app within minutes.
One gate checks every request and refuses anything the app hasn't declared.
Whoever runs an app hands out its roles, no IT ticket.
console.northwind.example/people
When something breaks, the error reports itself
A nightly job fails at 2 a.m. By morning the error is in the console, grouped, tagged with its version and stripped of passwords, keys and request contents.
Apps report errors on their own, no setup per app.
The platform regularly checks that each app responds.
Alerts for new, returning or spiking errors.
console.northwind.example/operations/errors
A few more things the platform takes care of
Public forms without a CAPTCHA vendor
A form on your website feeds an app without opening it to the internet. Bot protection runs in your installation and only listed sites can send. On Zerops.
A record of every deployment
Each version goes live from an exact point in Git, with who started it: a colleague, an AI agent or a trigger.
Testing kept apart from live use
Each environment has its own data, keys and address.
In your own cloud account
In your company's name on Zerops, AWS on request. Code, data and domains are yours. AI runs on your own plan.
For technical people: how it works under the hood
The request path, what apps declare in code, how approvals read a change. For your IT or developer.
Each starts with a setup, usually a small job: the platform in your cloud account, rules for working with AI, a short training. Each ends the same: apps in your account, every change reviewed by us.
01Kickstart
We build the first app with you
For companies starting from scratch. The person who'll build your next apps works with us all week.
Mon we map the process
Tue–Thu we build the app
Fri live
optional · one week
02Takeover
You bring an app you already have
From Lovable, Cursor, Claude Code, a freelancer or an agency. Small changes hand sign-in, keys and deployment to the platform, and the app moves to Zerops with its data. It has to be code that runs outside its tool, so Bubble apps are out.
The business quietly runs on an app someone built, nobody manages access, and it ends when its author leaves. We take it over with its data and your person keeps developing it.
With no capacity for development, the only safe answer is no. On Fabrika every app runs under the same rules: one sign-in, permissions and a record of every deployment.
Show us a process you want to turn into an app, or an app you already have. We'll tell you which way in fits and what it involves, or say plainly that we're not the right match. Bring your IT along.
