Your developer or agency builds. We run it and carry the SLA.
Whoever you hire keeps writing your apps. Sign-in, access and keys are held by the platform in your cloud account. We review every change and answer for operations under an SLA, including bugs in your developer's code.
Not through your supplier. You hire the developer yourself.
Nothing goes live that we haven't gone through.
Code, data, domains and the cloud account are in your company's name.
Who answers for what?
You decide, your developer or agency builds, and we hold the platform and operations. When an app stops working, you call us, not the developer.
You
- Decide what gets built and who gets into which app
- Hire the developer or agency, with your own contract
Your developer or agency
- Writes and develops the apps to your brief
- Uses the tools they know. If they use AI, it runs on your own plan
- Sends every change to Git
Contember
- The platform in your cloud account, on Zerops, or on AWS on request
- A single way in and sign-in with your company account (OIDC)
- Roles, keys, separate test and production
- Watching for errors and outages, patching the platform
- Operations under the SLA, including fixing bugs in your developer's code
How does a change from your developer get into production?
Your developer doesn't deploy on their own. Nothing reaches production except through Git and our review.
The developer builds
On their own computer, from the code and your brief.
The change goes to Git
With an author, a time and a description. Nothing gets copied onto the server by hand.
We review it
Permissions, data handling, anything that could open a door that should stay shut. If something needs fixing, we tell the developer.
Deployment and report
The version goes live and you get a report of what changed and what we checked. If it widens anyone's access, it first waits for your approval.
What changes for your developer or agency?
You can send this part to whoever builds for you.
“How to build for clients without being on call forever?”
What you no longer handle
- Servers and patching them
- Sign-in, roles and passwords built into every app
- Being on call when an app is down
- Fixing bugs in production. Under the SLA, we do that
What stays with you
- Building the apps and developing them further
- Your tools, including AI through your client's own plan
- Your contract with the client
What's new
- Changes go live only through Git and our review, with feedback on what to fix
- Sign-in, roles and keys are handled by the platform, not the app code
- An introduction to the platform and the building rules at setup
What if only one agency can change your system today?
Usually there's no bad intent: the system grew for years and every change waits until the people who wrote it have time.
New apps go straight onto Fabrika
They run in your cloud account, with review and operations on our side. The same agency can build them.
We take over an existing app
If it's code that can run outside the tool it was built in, we make small changes and deploy it to Zerops.
How a takeover works →A larger, older system
A big system the whole company runs on is a job for our Services: taking it over and modernising it step by step.
Services →What you need from the agency
For a takeover we need the source code and access. Whether the agency hands them over depends on your contract with them; on the scoping call we'll tell you exactly what to ask for.
When isn't Fabrika for you?
-
Your agency already runs operations and an SLA that suit you.
There's no point paying for operations twice.
-
The app lives in Bubble or a similar no-code builder.
We can't get the code out, so we can't take it over. It can serve as the brief for a new app.
-
Your developer needs to deploy without review.
On Fabrika every change goes through us. That's the point.
-
All you want is hosting.
For servers without change review and an SLA, there are simpler services.
What companies ask us
Who owns the code?
You do. The code, the data and the domains live in a cloud account in your company's name. We act as administrators there, and you can take that access away from us at any time. The platform is open source, so you're not tied to us either.
Who picks up the phone when an app isn't working?
We do, under the SLA in your contract with us, including bugs in code the agency wrote. The fix goes to Git like any other change, so your developer knows about it. The contract sets out what the SLA covers and the response times.
What if the agency shuts down or stops replying?
The apps keep running in your account and we keep operating them. Another developer, another agency or we can take over development, because the code is in Git and the building rules are the same for everyone.
What is it built with? Does our developer have to use AI?
Ordinary code: TypeScript and React on standard web technologies. Whether your developer uses AI is up to them, and we don't train anything on your data. If they work in something else, tell us on the scoping call.
Do we have to start with the kickstart week?
No. With your own developer you start straight with setting up Fabrika: the platform in your account, the building rules and an introduction. The kickstart is optional.
How much does it cost?
A one-off setup, which is usually not large, then a monthly fee for operations and change review based on the number of apps, never per user or per hour. You get both in the offer after the scoping call. Your developer you pay as you do now.
Start with half an hour on what you have. Bring your developer along.
Tell us who builds for you and what's already running. After the call you get an offer, or we tell you that you don't need Fabrika.