When we reach for it
Tight, well-bounded components: parsers, encoders, a hot path that has been measured and found wanting. Rust is at its best replacing one piece of a system rather than the whole of it.
Rust development
Memory safety without a garbage collector, for the small number of components where both correctness and predictable performance are non-negotiable.
When we would argue against it
We will argue against it for a standard web service. Compile times and the learning curve are real costs, and they are paid by whoever maintains the code after us — most teams get more from a boring Go service and the time saved.
What it looks like in delivery
Introduced surgically and behind an interface, so the rest of the system does not have to know. If it cannot be justified by a measurement someone took, it does not go in.
Where this appears on the site
Nothing on this site names it yet
We work in Rust, and no case study or service page currently published on this site prints it in its stack. Rather than describe an engagement you cannot check, this space stays empty until one does. Ask us and we will talk you through it directly.
Working in Rust?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.