Your developer or agency builds. We run it and carry the SLA.
Whoever you hire keeps writing your apps. We run the platform in your cloud account, review every change before it goes live, and answer for operations under an SLA. If a bug in your developer's code shows up in production, we fix it.
Bring your developer or agency along, if you like.
Operations and the SLA aren't arranged through your supplier. You hire the developer yourself.
Nothing goes live that we haven't gone through first.
Code, data, domains and the cloud account are in your company's name.
Who answers for what?
There are three parties on Fabrika and each holds its own part. 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
- You own the cloud account, the code, the data and the domains
- You decide what gets built and who builds it
- You hire the developer or agency and have your own contract with them
- You decide who gets into which app and with which role
- Your contract for operations and the SLA is with us
Your developer or agency
- Writes the apps and develops them to your brief
- Builds with the tools they know. If they use AI, it runs on your own plan
- Sends every change to Git
- Doesn't deal with servers, sign-in, platform patches or being on call
Contember
- The platform in your cloud account, on Cloudflare or Zerops, or AWS if you prefer
- A single way into the apps and sign-in with your company account (Google, Microsoft, Okta)
- Roles, keys and passwords, separate test and production environments
- Review of every change before deployment, with a report
- 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 to production on their own. Every change goes to Git, someone on our side goes through it, and only then is it deployed. Nothing reaches production any other way.
The developer builds
On their own computer, working from the code and your brief, with the tools they know. If they use AI, it runs on your own plan.
The change goes to Git
Every change has an author, a time and a description. Nothing gets copied onto the server by hand.
We review it
Before deployment we go through what changed: permissions, handling of data, 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 leaves a record. You get a report: what changed and what we checked.
What do you get out of it?
You pay your developer for what they build. Servers, monitoring and patches are no longer something you have to sort out with them.
One place to call
When an app isn't working, you call us. We find out what happened and fix it, even when the bug is in your developer's code. You don't have to track them down on holiday.
A contract directly with us
Operations and the SLA are agreed between you and us, not through your supplier. You hire the developer or agency yourself, and if you ever replace them, the platform and operations stay as they are.
The next developer picks up where the last one left off
The apps are ordinary code in Git, and the rules for building are the same for everyone. Whoever comes after the previous developer starts from the same code and the same rules.
You know what went live
Each version comes with a report of what changed and what we checked. You can see what's running even if you don't read code.
What changes for your developer or agency?
This is the part you can send to whoever builds for you. It's written to them.
“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 separately into every app
- Being on call and the phone ringing when an app is down
- Fixing bugs that show up in production. Under the SLA, we do that
What stays with you
- Building the apps and developing them further
- The tools you're used to, including AI through your client's own plan
- Your contract with the client for building and development
What's new
- Code lives in Git and goes live only through our review
- Sign-in, roles and keys are handled by the platform, not by the app code
- An introduction to the platform and the building rules when Fabrika is set up
- Feedback from our review on what to fix before deployment
What if only one agency can change your system today?
There's usually no bad intent behind it. A system grows for years, the people who wrote it understand it, and every change waits until they have time. Depending on what you have, there are three ways forward.
New apps go straight onto Fabrika
The next apps are built in your cloud account, with change review and operations on our side. The same agency can build them. The difference is that everything runs on your side.
We take over an existing app
As long as it's code that can run outside the tool it was built in. We go through it, make small changes and deploy it to Cloudflare or Zerops.
How a takeover works →A larger, older system
A big system the whole company runs on is usually a job for our Services: taking over the older system and modernising it step by step.
Services →What you need from the agency
For a takeover we need the source code and access. Whether and how the agency hands them over depends on your contract with them. We can't settle that for you, but on the scoping call we'll tell you exactly what to ask for.
When isn't Fabrika for you?
Better to say it up front than on the call.
-
Your agency already runs operations and an SLA that suit you.
Then 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 of it, so we can't take it over. It can serve as the brief for a new one, though.
-
Your developer needs to deploy to production on their own, without review.
On Fabrika every change goes through us. That's the whole point.
-
All you want is hosting.
For servers without change review and without an SLA on the apps, there are simpler services.
What companies ask us
Who owns the code?
You do. The code of the apps, the data and the domains live in a cloud account in your company's name. We act as administrators in it, and you can take that access away from us at any time.
Who fixes a bug in code the agency wrote?
We do, under the SLA. When a bug shows up in production, you don't have to chase whoever wrote the code. The fix goes to Git like any other change, so your developer knows about it.
Who picks up the phone when an app isn't working?
We do. We answer for operations under the SLA in your contract with us. What exactly the SLA covers and the response times are set out in the contract.
Who do we have a contract with?
For building, with your developer or agency, as before. For the platform, operations and the SLA, directly with us. You choose the developer and you pay them.
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 the development. 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?
The apps are ordinary code: TypeScript and React on standard web technologies. Whether your developer uses AI is up to them. If they do, it runs on your own plan and we don't train anything on your data. We're happy to advise on the provider. 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 or agency you start straight with setting up Fabrika: the platform in your account, the building rules and an introduction to the platform. The kickstart is optional.
How much does it cost?
A one-off setup of Fabrika, which is usually not large, then a monthly fee for operations and change review based on the number of apps. You get both in the offer after the scoping call, before anything starts. You never pay per user or per hour. Your developer's work you pay to them, 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. We'll go through what would change for you and for them, and after the call you get an offer. If it turns out you don't need Fabrika, we'll say so.