Four engagements, described in enough detail to be checked.
Full case studies are being written. In the meantime these are honest summaries, and the offer on the contact page stands: we will walk your engineers through a real repository before you commit any money.
-
01
20+ PB
A geospatial lakehouse moved from Azure to GCP
Twenty petabytes of geospatial data for a United States client, moved between clouds with no freeze on delivery. The team kept shipping throughout.
The migration was the visible part. The work that mattered was re-architecting storage tiers and query patterns so the running cost after the move was lower than before it, rather than the same bill in a different currency.
Handed back with the runbook written, the on-call rotation staffed, and their engineers able to operate it without us.
-
02
13
One platform across thirteen motorsport disciplines
Rehz Racing Software is the operations layer a national motorsport body runs its events on, covering thirteen disciplines from rally to drag racing on a single system.
Five roles touch the same event and none of them want the same view of it: officials, technical staff, entrants, organisers and stewards. Most of the design work went into keeping one system legible to all five rather than shipping five systems that disagree by Sunday.
Circuits do not reliably have signal. Everything on the trackside side of the product had to work with the network down and reconcile once it came back, which shaped the data model more than any screen did.
Entry handling, licence checks, timing and result publishing now run through it, and the paper it replaced is not missed.
-
03
1987
Four decades of a rally team, finally legible online
Arka Motorsports has been building and running cars since 1987, with a national rally championship record and a workshop that does engine work, dyno tuning and ECU calibration for manufacturer-backed teams.
None of that was visible. The brief was to put four decades of results, capability and partnerships in front of the people who commission that work, without the site turning into a scrapbook.
Built to the same budget as everything else here: no framework, no third-party requests, and quick on a phone at a service park with one bar of signal.
-
04
2.0.1
Open source charge management turned into a product
A charge point management system customised for the Indian market, built on an open source OCPP core rather than from nothing.
The market has peer to peer operators that the upstream project did not model, so the ownership and settlement layers were ours. The protocol layer stayed upstream, which is why it still takes upstream fixes.
It publishes reliability reporting that comparable operators do not, which was a commercial decision before it was a technical one.
Client names, team composition and the tool stack are available under NDA on a call. Ask for them.