When we use Rust.
Where tolerances are tight. Components that need to respond within a predictable time, not just be fast on average; parts of a system under constant load; processing engines where a production error carries a high cost.
Some things that elsewhere are discovered by trying do not compile here: it is a cost paid while writing rather than afterwards.
This is where it pays off: a component that needs to last, hold up, and make few mistakes.
The technologies we work with
The technologies we work with
When we do not use it
When we do not use it
When the thing to build is simple and changes often. Writing in Rust takes more time, and that time pays back only if the component lasts. For a service that will be rewritten in six months, it is an expense with no return.
It is also a technology with limited availability in the Italian market: if part of your system is written in Rust, you have to allow for the fact that finding someone to maintain it later is not immediate. That applies to us as much as anyone else.
What we have used it for
What we have used it for
[REDACTED]
ScalePrediction Markets
Prediction market — order-matching engine.
3 yearsActive
BuildEmbedded & IoT
Mechit — control software for driving simulators.
3 yearsActive
The way we work is the same across technologies: peer review before release, separate environments, and automated pipeline checks. How we work