Custom software maintenance: leave it with the provider or bring it in-house?

Custom software does not stop on delivery day. You have to fix what breaks, adapt it when the company changes, and keep everything that makes it run up to date. So the real question is not only “who takes care of it?”, but “will I be free to change my mind later?”.

Who should maintain custom software?

The short answer: whoever can do it properly and over time. That is not necessarily the team that built the software. There are three options: a maintenance package with the provider, a developer in-house, or another provider.

At C-Esium, the choice is yours: optional maintenance, as a monthly package. Because the client owns the code, it can also bring the day-to-day management of the software in-house later, or hand it to another provider.

That freedom exists only because the code belongs to you. With rented software (SaaS), maintenance is the vendor’s: you have no other option. The same applies to a focused project, from AED 40,000 excluding VAT (€10,000 in France): you own its code, so you choose who maintains it.

What does software maintenance cover?

Definitions vary from one contract to another. The three families below are the most common; have them written down in black and white, whoever your provider is.

Technical maintenance is the easiest to neglect: it is invisible until something breaks. Yet as soon as the software holds personal or business-critical data, being able to restore it quickly after an incident matters. Make sure backups are made regularly, that at least one copy is kept in a separate location, and that restoring them is actually tested.

User support (“how do I…?”) is not maintenance in the strict sense, but it comes through the same channel. At C-Esium, after the roll-out, C-Esium Space, the project workspace, becomes the support channel: a screenshot, a few words or a voice message, tracked as a Kanban board, a table or a timeline.

Package, in-house developer or another provider: which option for whom?

These options are not exclusive. An in-house developer can take the small changes while a provider keeps the technical maintenance. What matters is that a named person is responsible for each type of maintenance, and knows it.

What does C-Esium hand over, and what does that make possible?

Bringing maintenance in-house or changing provider is only realistic if you really have the code, the data and the documentation in hand. At C-Esium:

• Ownership. The client owns its software: C-Esium assigns to it by contract all rights to the project code — including the building blocks we reuse from one project to the next — together with the database and the documentation. No per-user licence, no dependence on a software vendor.
• The repository. The code is placed in a Git repository (GitHub or GitLab) in the client’s name, at the latest on delivery.
• The documentation. The technical and functional documentation is delivered with the software.
• The technologies. Standard, widely used web technologies — TypeScript, React, Node.js, PostgreSQL: any web developer can take over the code.
• Skills transfer. C-Esium can train an in-house developer or a third-party provider.

These points answer the three questions a developer taking over asks first: where is the code, how is it organised, and do I know these technologies?

As an option, the code can also be placed in escrow with a trusted third party, for example the APP, the French software protection agency. According to the APP, escrow means entrusting essential elements (software, databases, documents) to a third-party escrow agent so that a beneficiary can access them under the conditions agreed between the parties, in particular if the supplier fails (APP, software escrow, accessed 5 October 2026). The assignment of rights is explained in rent or own your business software.

How do you prepare to bring maintenance in-house?

Bringing maintenance in-house is prepared before the provider leaves, not after. Here is what you need in hand, whoever built the tool:

Then five steps:

1. Choose the profile. A web developer comfortable with TypeScript, React, Node.js and PostgreSQL, employed or freelance. These are widely used technologies, not a proprietary language.
2. Organise the skills transfer. C-Esium can train this developer. Plan a period during which they make their first fixes and small changes before taking over everything.
3. Test the access. An access that has never been used is not an access. The developer taking over must be able to deploy a change from end to end.
4. Restore a backup for real. Restoring to a separate environment is the surest way to check that the backups work.
5. Name the person responsible for technical maintenance. Security updates, dependencies, hosting and backups must each have a name next to them.

When should you keep maintenance with C-Esium?

The maintenance package is often the simplest choice in these situations:

• you have no developer and do not plan to recruit one;
• the software is still being delivered in batches: a complete software takes from 6 months to more than a year, and the team building the next batches already knows the code;
• your requests are too few to fill a job;
• you want a single point of contact for fixes, changes and support.

This choice does not close any door: because the code is yours, you can start with the package and bring maintenance in-house later, once the tool is stable.

When the C-Esium package is not the right option

• You already have a technical team maintaining other tools: giving it this software is often more consistent.
• Your IT policy requires a single provider for all your tools: have that provider take over the software, with a skills transfer.
• You expect permanent on-call cover or guaranteed response times: ask the question explicitly, to C-Esium as to any provider, and have the times written into the contract before you sign.

To find out where and how the software is hosted, read where to host your business software. For the full offer, see the custom internal software page and our 5-step method.

Sources

• APP (French software protection agency), software escrow, accessed 5 October 2026.