Service 07 · Monitoring and support, day and night
Custom software maintenance: warranty, follow-up and taking over existing code.
Three months of warranty after every fixed-price delivery, then maintenance by the people who wrote the code. And if the code comes from elsewhere, a review before we take it over.
First conversation free.
Warranty, maintenance, takeover: three moments in the life of software
- 01
Right after delivery. Three months of warranty: proven, documented and reproducible defects are fixed at no extra cost.
- 02
The years that follow. Fixes and small changes as they come, by the team that wrote the code: nobody bills you for rediscovering it.
- 03
Code that came from elsewhere. An Access database, an Excel workbook that became critical, an application nobody knows how to maintain any more: we take it over before it stops along with the one person who understands it.
What the warranty and maintenance cover
Every fixed-price delivery is covered by three months of warranty. After that, maintenance goes through a managed services contract, priced according to how critical your application is: fixes and small changes as they come are part of it, along with continuous monitoring, security patches, encrypted nightly backups and on-call support for critical incidents.
Larger changes, a new workflow or a new line of business, are priced on request, at a fixed price or by the working day. Every month, a report tells you what happened, what we did and what remains to be done.
The warranty, plainly
- Three months after every fixed-price delivery
- Proven, documented and reproducible defects
- Fixed at no extra cost
- Details in our terms of sale
Three contract levels
Essential, Standard or Premium, described on the managed services page; the monthly order of magnitude, application maintenance included, is published on the pricing page.
Taking over existing code without breaking everything at once
- 01
The review. The code and the hosting: what exists, what is fragile, what costs money. You receive a readable report.
- 02
Taking it over for maintenance, or a step-by-step rebuild. Screen by screen, module by module, without stopping everything.
Software we wrote, and that we host
The measurements come from our instruments, each with its date.
- Machines tracked for the application of security patches
- 39PatchMon patch manager (internal console)
- Backup integrity checks over the last seven days
- 7 out of 7Dedicated backup server (Proxmox Backup Server)
Measurements taken on 5 September 2026, values recorded by our own instruments.
Before handing over your software
What exactly does the warranty cover?
Every fixed-price delivery is covered for three months: proven, documented and reproducible defects are fixed at no extra cost. Beyond that, changes and routine maintenance go through the managed services contract. The details are in our terms of sale.
Can you take over software you did not write?
Yes, it happens often. We start with a review of the code and the hosting: what exists, what is fragile, what costs money. You receive a readable report, then we move on to taking it over for maintenance or to a step-by-step rebuild.
What happens if we part ways?
You leave with the source code and its documentation, an export of your data in open formats, and access to the services we were running on your behalf. We prepare the handover with the provider who takes over.
How much does maintenance cost?
It goes through the managed services contract, priced in a quote according to how critical your application is, application maintenance included. The monthly order of magnitude is published on the pricing page.
Timelines, quotes, code ownership, end of contract: the answers are in the FAQ.
Quoted per project. Price ranges are published on the pricing page, along with what makes a budget vary.
Software to keep alive
Software to maintain, or to take over?
Tell us about your software, who wrote it and where it runs. We will tell you what we take over, in what order, and at what price.
Reply within 24 working hours, from a founder.