A contact who knows your platform
No front desk, no ticket number to explain three times over. The person who answers has access to your infrastructure and knows what runs on it.
The company
Engineers who operate what they build.
Obicorp started from a simple observation: technical projects rarely break in the middle, they break at the seams — between whoever writes the code, whoever deploys it and whoever hosts it. We chose not to create those seams.
What we do
We design, host and evolve application platforms. In practice that covers four disciplines we practise together rather than separately: hosting containerised infrastructure, securing it, deploying it through GitOps and building the business applications that run on it.
That scope isn’t a list of services stacked up to look complete. It’s a chain: an application is designed knowing where it will run, deploys there automatically, and is operated with the same tools that built it.
How we work
We listen to the business first. Real constraints — volumes, seasonality, regulatory obligations, in-house skills, budget — dictate the architecture. A technically elegant solution your team can’t operate is a deferred failure.
We write down what we do. Infrastructure is described as code, decisions are explained, procedures are documented. This isn’t bureaucracy: it’s what makes you independent of us, and what lets us act fast when something breaks at three in the morning.
We say what we think. If your needs don’t justify Kubernetes, we’ll say so. If a product on the market already covers 90% of what you want built, we’ll tell you to buy it. A technical partner is judged as much on the projects they save you from as on the ones they invoice.
What we don’t do
We don’t do paid search marketing, brand design or digital strategy consulting. We don’t resell licences we can’t operate. And we don’t take on work we already know will be delivered below the standard we consider acceptable.
When a need falls outside our scope, we say so — and we point you elsewhere when we know someone serious.
What we commit to
No proprietary lock-in
We build on open foundations — Docker, Kubernetes, Git, PostgreSQL, Linux. Your platform stays something another team could take over, and we would help with that handover if you decided on it.
The right level of complexity
We turn down architectures designed to impress. An unnecessary cluster is a permanent operations bill for a problem you don't have.
What gets done gets written down
Infrastructure described as code, runbooks documented, changes traced in Git. What we know about your platform is written somewhere, not only in our heads.
Frequently asked questions
Working with us
What size of organisation do you work with?
Mainly small and mid-sized companies, and in-house technical teams needing reinforcement on infrastructure or hosting that is genuinely looked after. We work both as the sole provider and alongside an existing team.
Do you take one-off work or long-term engagements?
Both. An infrastructure audit, a migration or a scoped development are one-off engagements. Hosting and managed operations run over time, with a contractually defined service level.
Do you work remotely?
Yes, as almost all infrastructure work does today. Scoping sessions and review meetings can happen on site if that suits you.
How does an engagement start?
With a technical conversation and no commitment, where you describe your context and constraints. We come back with an honest opinion — including when that opinion is that you don’t need us.
Let's talk about your infrastructure
Migration, redesign, taking over an existing setup or starting from scratch: tell us your context and we'll come back with a first technical opinion — no strings attached.