The crew · Montpellier, France · since January 2024
Eight people, and the stack they hold up.
A team this size is not judged on its headcount, but on what it carries in production and what it publishes. Both are below, then the names.
- Headcount
- eight people
- Head office
- Montpellier, France
- Founded
- January 2024
- Engagements
- embedded 12 months and up · audit and architecture · open source support
- Published code
- close to 15,000 lines of Rust, including one crate on crates.io
- Network
- France Digitale (member)
Production
What the team runs in production.
Nothing on this list is a declared skill: every name runs either at a client under contract or inside the product we build.
- Machine layer
- Talos LinuxKubernetesKubeVirtOpenTofuArgo CD
- Storage and data
- Rook-CephMinIOCloudNativePGPostgreSQLTrinoApache IcebergKafkaAirflow
- Network, identity, secrets
- CiliumEnvoy GatewayIstioKeycloakOpenBaocert-manager
- Inference
- KServevLLMNVIDIA GPU OperatorLeaderWorkerSet
- Operations
- GrafanaPrometheusOpenTelemetry
At the Montpellier computing centre, fourteen applications are described in a single repository and continuously reconciled: the repository carries the expected state, the cluster conforms to it, and any drift shows up in a log rather than in an engineer's memory. The infrastructure there is cut into six modules — bastion, cluster config, compute, network, security, Talos. Under the distributed GPU inference chain, which combines KServe, LeaderWorkerSet and NVIDIA's GPU operator, the operating system is immutable, storage is replicated by Ceph, databases are driven by CloudNativePG and secrets live in OpenBao. ▪
Inside the data platform of a national banking group, engineers from the team have been embedded for more than twelve months, on the client's tooling and processes: reproducible deployments, infrastructure as code, end-to-end observability.
We build Hyperfluid, an internal cloud of twenty services that our clients install on their own side. The product describes itself on its own site; here it counts as evidence. Eight people only hold a catalogue of twenty services by going all the way down the stack — down to the operating system and down to the protocols.
Publications
The team writes the clients for the components it runs.
You only operate well what you understand. When the client library for a critical component does not do what operations require, we write it.
| Repository | Size | What it solves |
|---|---|---|
| talos-rust-client | 8,316 lines of Rust, 14 files | A gRPC client for Talos Linux, with mTLS by default and a typed API generated from the official protos. Published on crates.io, under MIT OR Apache-2.0. |
| trino-rust-client | 6,374 lines of Rust, 45 files | A Trino client taken over from prusto in December 2024: Presto support removed, the spooling protocol added. Apache-2.0. |
| Ferris Key | contribution and sponsorship | An authentication and identity management server written in Rust, maintained upstream. Apache-2.0. |
The people
Who the crew is.
Management
Roch Dardie
Founder · joined in 2024
He has run the company since it was founded and is the publication director of this site. He is also the person who answers the number published in the footer.
Engineering
- Martin Moreira De Jesus Engineer ⟨spécialité⟩
- Pauline Contant Engineer ⟨spécialité⟩
- Alexis Langlet Engineer ⟨spécialité⟩
- Charlotte Lewis Engineer ⟨spécialité⟩
- Kalil Pelissier Engineer ⟨spécialité⟩
- Héloïse Rigaux Engineer ⟨spécialité⟩
- Mateo Fernandez Engineer ⟨spécialité⟩
Specialisms marked ⟨spécialité⟩ will be filled in by the people concerned themselves.
Crew alumni
Method
What is written down before we start.
We sell the time of engineers employed by the company. Everything else follows from that.
- Engineers on our payroll
- The people assigned to your order are named in it, with their role and their workload; the assignment is discussed before signature. Delivery is not subcontracted to an unnamed third party.
- Rotation in writing
- No replacement on our initiative without written notice and an overlap period between the two people. Keeping a named person until the end of the engagement requires a continuity clause, also written down.
- Skills transfer
- What we build is documented in your repositories and in your working language. That is the counterpart of a long embedded engagement: your teams have to be able to carry on without us.
- What you keep
- The code, the described infrastructure and the documentation are yours on delivery. On the components we publish, the licence protects you even if the company disappears.
- On-call
- Embedded engagements carry none. Covered hours, response targets and resolution targets belong to a support contract, where they are written down component by component.
- Five percent
- Five percent of the value of every new contract goes to the engineering team. A public commitment since 1 July 2024, never withdrawn.
Where we come from
Montpellier, January 2024.
The company was founded in Montpellier in January 2024 and has not moved. It has been funded by its own revenue, with no outside investment: nobody on the outside is waiting for a curve from it.
It is a member of France Digitale. It supports a few technical communities and open source projects in its region and its field, because it depends on them directly. ▪
- Professional network
- France Digitale
- Communities and projects we support
- Sunny Tech · PolyCloud · Ferris Key
Two pages that continue this one