Four products we operate, and none of them is a pitch.
This is not a catalogue. Three of these four are not something you can buy from where you are sitting, and we say which. They are here because running software in production for years is a different discipline from delivering a project and leaving, and you are entitled to check that we do the first one.
Availability first, description second
Every product below carries what you can actually do with it today. One of them you can use, one is deployed programme by programme, one is in a closed beta, and one has a release date in the future. Reading that order tells you more than any feature list would.
- You can use it today
UptimeEZ
Operations and monitoring
Monitoring that catches what an uptime check misses: a layout that broke, a database silently returning nothing behind a 200, a certificate that expired, a noindex tag someone left in production. Five layers, each of which has caught a real incident on our own systems.
What it tells you about us. We run this against our own client systems, which means every false alert costs us directly. That is the only reliable incentive to make monitoring honest.
In production, source code public
- Deployed per programme, not self-serve
BougeMaville
Public authorities and institutions
A geolocated field-reporting platform: residents or inspectors report what they see, reports are routed to whoever handles them, and the result becomes statistics an institution can act on. Built for Expertise France, then adapted for the Liège metropolitan area, Welfarm, and an industrial client.
What it tells you about us. The same core has served four organisations with different rules, which is the hard part of a product. Adapting it for Liège is how that authority got a working system during its construction programme rather than after it.
In production, relaunch in 2026
- Not open yet, private beta
Refaudit
Compliance and accessibility
Automated auditing of a website on three axes at once, regulatory compliance, security and accessibility, with the fixes proposed rather than just the problems listed.
What it tells you about us. It is in private beta and we say so. A product page that hides the stage of a product tells you what that vendor will do with a delivery date.
Private beta
- Not available before October 2026
Discoly
Media and online publishers
Google Discover optimisation treated as an editorial discipline rather than a trick: continuous analysis, recommendations, measurement, and editorial A/B testing.
What it tells you about us. A dated release we publish before it happens. You can hold us to it, which is the point of publishing it.
Commercial release October 2026
Three things you only learn by operating, not by delivering
An alert nobody trusts is worse than no alert
We built UptimeEZ because a monitoring tool was producing alerts that were mostly false. The cost of that is not the noise, it is that the real one stops being read. Every layer in that product exists because a specific kind of failure got through a plain uptime check on a system we were responsible for.
A product survives its second client or it was a project
BougeMaville went from one institution to four organisations with different reporting rules and different people handling them. That transition is where most internal tools break, because the first client's rules were written into the code rather than configured. It is also the discipline that makes a tool we build for you survive a change in your own organisation.
Publishing a date is a commitment, and we publish ours
Discoly has a commercial release date on this page before it has happened, and Refaudit is described as a closed beta rather than as something you could try. A vendor's willingness to state the uncomfortable stage of their own product is a reasonable proxy for what they will tell you about your delivery date.
What people ask about this page
- Can I buy any of these?
- UptimeEZ, yes, and its source is public. BougeMaville is deployed per programme rather than sold by the seat, because it has to be adapted to how a given institution routes reports. Refaudit is in private beta and not open. Discoly ships commercially in October 2026 and targets French-language publishers, so it is unlikely to be what you came here for. If you want a straight answer on which of these is relevant to you, ask, and the answer will often be none of them.
- Then why is this page here?
- Because there is a difference between a vendor who delivers projects and leaves, and one who runs software in production and lives with the consequences. Operating our own products is what taught us that a monitoring alert nobody trusts is worse than no alert, that a migration is judged on the restore and not the backup, and that a product survives its second client only if the first one did not hard-code the rules. You are entitled to check that we practise what we sell.
- Does working on your own products take time away from client work?
- It would if we ran them as a growth business, and we do not. They are small, deliberately, and two of the four exist because a client engagement needed them first. What they cost us in attention, they return in judgement: most of what we know about operating software at low headcount, we learned by having to do it ourselves at three in the morning.
- Would you build a product for us?
- That is a real engagement and it is not the same as building an internal tool: a product needs someone to own its direction after we leave, and that person has to exist on your side before we start. We have done it, on fixed fee, with the source code and the operational documentation transferred at the end. What we will not do is start it without that owner identified, because the result would be a system nobody drives.
Twenty minutes, and a straight answer.
Describe what is happening on your side. If one of these products is relevant we will say so, and if none of them is, which is the likely answer, we will say that too and talk about the engagement instead.
Requirements and vendor selection
The business need turned into verifiable acceptance criteria, and someone who reads the quotes on your side of the table.
SituationYour IT department exists
One capability is missing, or one key person just left. Senior reinforcement on a named subject, with an end date.
After the workPost-launch support
Optional, monthly, and it never recreates a dependency. We watch the indicators set at handover.
Who we areThree senior operators
An independent technology firm in Paris since 2019. Being small is the point, not the compromise.