Founded in 2022, still run by engineers, and organised so the people who design a system are the people who carry the pager for it.
Why we exist
OrbitWren was founded on a stubborn belief: the hardest part of software is not writing it, it's keeping it honest as it grows.
We started as four engineers who had spent a decade watching well-funded programmes ship systems that worked in a demo and fell over in contact with real users. The pattern was always the same: distance between the people making architectural decisions and the people living with the consequences.
The structure has not changed since. Small senior pods, no hand-off layer, and an expectation that every engineer can explain the business reason for what they are building.
We write our own evaluations, publish our benchmarks internally, and will tell you when a model is the wrong answer to your problem. Roughly a third of the proofs of concept we run end with a recommendation not to proceed — we consider those the profitable ones.
Bias to production
A demo proves nothing. We optimise for the day the system meets real traffic, and we design backwards from it.
Measure or don't ship
Every claim we make about a system has a dashboard behind it. If it isn't measured, we don't assert it.
Own the boring parts
Migrations, backfills, on-call, documentation. The unglamorous work is where trust is actually built.
Say the hard thing
We would rather lose a scope than let you build the wrong system. Roughly a third of our proofs end in a recommendation not to proceed.
One team, one place, and client work that spans time zones rather than offices.
Perth
55B Tuckfield Way, Nollamara 6061 · Australia
Engineering, delivery and client work
UTC+8A short conversation with an engineer, not a sales qualification call. If we're the wrong people for it, we'll say so and point you somewhere better.