Services
What we build, run, and rescue.
Five things, done by senior engineers. Each one says what it covers, what you end up owning, and how it is bought. If your problem is not on this page, say so on the call and we will tell you whether it is ours to solve.
01 / Pillar
SaaS product development
We design and build multi-tenant products: data model, application, billing, and the admin side that keeps them running.
We take a product from a data model on a whiteboard to something paying customers use every day. That means multi-tenancy, roles and permissions, billing, the admin back office you will live in, and the operational work that keeps it upright after launch. We build in small increments with tests and CI from the first commit, so you see working software every week instead of a status report.
What you get
- An architecture and data model documented in your repository
- A multi-tenant application with role-based access and an admin back office
- Automated tests and a CI pipeline running on every commit
- Staging and production environments, with deploys and rollbacks written down
- A handover pack: runbook, credentials, and how to change things without us
02 / Pillar
DevOps and cloud operations
Pipelines, environments, and infrastructure set up so a deploy is routine and a rollback is one command.
We set up the path from a commit to production and make it boring. Pipelines, separate staging and production, infrastructure written down as code, backups you have watched being restored, and alerts that reach a person rather than an inbox nobody opens. We work with the cloud you are already on rather than moving you to ours.
What you get
- CI/CD pipelines with separate staging and production
- Infrastructure defined as code, in your repository
- Backups with a restore we have run in front of you
- Monitoring, logging, and alerting that reaches a person
- A runbook for the routine jobs: deploy, roll back, restore, rotate keys
03 / Pillar
SLA maintenance and support
A retainer that keeps software patched, monitored, and answered for, with response times written down.
A monthly retainer that keeps software patched, watched, and answered for, whether we built it or not. Response times sit in the agreement by priority, so you know what a P1 buys you before you need it. Each tier includes engineering hours for the small changes that would otherwise queue up behind a quote.
What you get
- Response times per priority, in writing
- Dependency and security patching on a schedule
- Uptime and error monitoring, with alerts reaching a person
- Included engineering hours each month for small changes
- A monthly report: uptime, incidents, patches, hours used
04 / Pillar
Modernization and rescue
For systems that still earn money but nobody wants to touch. We stabilise first, then modernise in steps you can pause.
For systems that still earn money but nobody wants to touch. We read the code, the data, and the infrastructure before proposing anything, then stabilise what is actively breaking, then modernise in steps you can stop after any one of them. The system stays live throughout, and every step has a way back.
What you get
- A written audit of the code, data, and infrastructure
- A stabilisation pass before any rewrite is discussed
- Tests around the parts that cost money when they break
- A staged migration plan, priced step by step
- The system live throughout, with a rollback at every step
05 / Pillar
Our own products
We run our own SaaS, rentiQ, on the same stack and the same discipline we sell, M-Pesa integration included. The lessons come back into client work.
We run our own SaaS on the stack and the discipline we sell. rentiQ is a property management platform for the Kenyan market, live in early access, built and operated by the same engineer who does the client work. It reconciles M-Pesa rent against invoices, which means we have shipped a payments integration that has to be right about somebody else's money. Running it is how we know what year three of a product costs, not just the first sprint: the migrations, the support load, the invoice from the cloud provider.
What that proves
- rentiQ: a property management platform for Kenya, live and taking real use
- A production M-Pesa integration, reconciling real rent against real invoices
- Built and operated by the same engineer who ships client work
- Running costs, migrations, and support load we have paid for ourselves
Next step
Tell us which one you need.
Bring a product to build, infrastructure to tidy, a system that has outgrown itself, or software that needs someone to answer for it. If we are the wrong studio for it, we will say so on the first call.
The first call is free and takes 30 minutes. We reply within one business day.