Two engineers who couldn’t stop seeing the same problem.
InfraXcode began as a conversation between colleagues, not a business plan. It still runs the way that conversation did: one standard, no handoffs.
Nassim & Messaoud · Paris
- 2022
- Founded
- Paris
- Based
- Bootstrapped
- Independent
- AI-native
- Since 2022
- €1M
- In R&D
It started with a shared desk and a nagging feeling
2018 · Bouygues Telecom
A shared desk
Two engineers on the same programme: SDN, automation, QA. Over 30,000 routers automated, and the hardest part was never the code.
2018 to 2022 · Consulting
The search for an exception
Telecom operators, banks, cloud providers. Everyone agreed infrastructure had become software. Nobody managed it that way, and nobody could test a change before it went live.
2022 · Paris
Built from scratch
No more waiting for someone else to fix it. One company, one standard: the one missing on that rollout.
“If infrastructure is being software-ized, we need to manage it like software rather than only buying more software tools.”
One team, one standard, and tools
we built ourselves
The company grew around the work rather than the other way round.
Paris
Nassim and Messaoud work out of Paris, close to the clients they answer to. The automation engineers we recruit and train work alongside them, on the same team and to the same standard. Nothing is subcontracted.
The clients we answer to
Telecom operators, banks and cloud providers: the same rooms the two of them came from. Work reaches us through people who have seen us deliver.
One wall kept coming back: no safe way to try an infrastructure change before it went live. Nobody was going to build that for us, so we did.
They generate and review configuration, reproduce multi-vendor behaviour without a physical lab, and prove a change is safe before it touches anything you run. Used in-house, not sold as products. When we commit to a date, this is part of why we can.
The two engineers who started InfraXcode
Both are still in the work, alongside the engineers on every project.
Whichever of them scopes your system answers for it.
A network automation engineer. Four years inside other people’s organisations, in telecom, banking and cloud, automating the operations nobody had time to fix.
He takes the first conversation himself. He would rather spend a week understanding your system for free than name a price he cannot hold.
Scoping, the price that holds, and the date it lands on.
An SDN and network-QA engineer. He left the 5G programme with one conclusion: writing automation is easy, testing it at scale is where every team struggles.
He leads our research, with a Columbia University researcher alongside him, and owns the tooling that proves a change is safe before it ships.
Architecture, research, and the engine we test on.
AI is the muscle. The engineer owns the decision, the context, and the judgment.
AI-native since 2022, with €1M of our own money in R&D on the methods and tooling behind it: how we brief it, how we review what it produces, how we prove its work is safe.
Nothing reaches your production because a model suggested it. Human-in-the-loop is not a setting we can switch off.
Human-in-the-loop, alwaysTalk to us
Got questions about how we work? Just ask.
No form to fill in and no pitch waiting. Write to one of us and you get an answer from the person who’d do the work.
Get in touch