About
Four people, one long argument about state.
Ardent started in 2019 in a rented room above a bike shop in Bristol, mostly as an excuse to stop maintaining other people's dashboards.
We spent the previous decade on call for systems nobody fully understood. The pattern was always the same: a service that had quietly accumulated five layers of retry logic, three caches, and a manager process that nobody could name the owner of. When it broke, the incident was not really about the bug. It was about the fact that no one could say what the system was supposed to do.
So we build the opposite: few moving parts, explicit state, and failure that announces itself. We would rather ship a tool that does one thing and tells you when it stops doing it than a platform that does everything and hides its confusion.
How we work
- Every feature ships with the sentence that explains it to an operator at 3am.
- If a design needs a diagram to be understood, the design is the problem.
- We keep a written decision log for each product, public to customers who ask.
- No telemetry, no licence checks, no phone-home. You can run us air-gapped.
Who we are
- Mara Ellison — storage and query engine. Previously databases at a payments company.
- Tomas Reiner — delivery and scheduling. Wrote the first version of Relay in a weekend, spent two years making it correct.
- Priya Nandakumar — discovery and inventory. Came from network operations, which explains the obsession with diffs.
- Sam Okonjo — everything that touches a customer. Documentation, support, and the occasional hard conversation about scope.
Where we are
Bristol, UK. We work in the office three days a week and answer email the other two. If you are nearby and want to argue about event sourcing, the coffee is decent.
Write to hello@brigghouse.com.