Independent engineering. Bangalore, India.
Engineering for systems that have to work.
We design, build and test software for businesses where downtime is expensive and an auditor eventually asks how it works.
Clarity in the architecture.
Confidence in the outcome.
The short version
Most software problems are not technology problems.
They are problems of clarity — nobody agreeing what the system is supposed to do, or what happens when it does not. The technology decisions follow from that, and they are usually the easy part.
So we start by getting the question right, then build the smallest thing that answers it properly. That tends to produce systems that are cheaper to run, easier to change, and considerably less frightening to deploy.
What we do
Four areas. Most engagements touch more than one.
Product and platform engineering
Systems designed to be maintained, not just delivered. APIs, services, internal tools and the infrastructure underneath them.
Explore this serviceData and integration
Getting information out of the places it is stuck and into the places it is useful — across systems that were never meant to talk to each other.
Explore this serviceQuality and assurance
Test coverage, automation and the evidence that a release is safe. The work that decides whether a system ships or sits in review.
Explore this serviceTechnical advisory
A second opinion with its hands in the code. Architecture reviews, build-versus-buy calls, and honest assessments of what a project actually needs.
Explore this serviceHow we work
Three commitments we do not negotiate on.
The engineer you meet builds it
No handover from the people who scoped the work to a team you never met. We stay small so that stays true.
Evidence, not demos
Anything can be made to work once. We ship the tests, the failure modes and the numbers that show it works repeatedly.
Everything is yours
Source, documentation, infrastructure, working files. Nothing proprietary in the middle, and no reason you cannot take it in-house tomorrow.
Where we work
Environments where getting it wrong is expensive.
- Banking and financial services
- Insurance
- Regulated and audited environments
- Companies with systems older than their engineers
The common thread is not an industry. It is that someone has to sign their name against the system working.
In development
A product, built out of the work we kept repeating.
The assurance side of our work turned out to be the part clients valued most and the part that generalised. We are building it into a platform, currently in private development with a small number of design partners.
Tell us what you are trying to build.
A short call is usually enough to work out whether we are the right people for it. If we are not, we will say so and point you somewhere better.