Maintenance & technical support
An application evolves along with its users, its dependencies, and its technical environment. NuWide provides ongoing support to correct, maintain, secure, and update whatever needs to be addressed.
LaunchA delivered and documented version
ObservationUsage, feedback, technical issues
MaintenanceUpdates, maintenance, analysis
Correction · EvolutionWhat needs to change, and why
ValidationVerified and approved prior to delivery
New versionDelivered, tracked, then monitored
A web product lives on
After an application goes live, its environment changes, even when the code itself remains unchanged. Keeping track of these changes allows you to incorporate them at the right time, rather than simply having to adapt to them.
New behaviors and standards.
Updated libraries and components.
New versions, end of support.
Operating systems and Services.
New ways to use the tool.
Volumes are on the rise.
Changing traffic patterns.
New processes to implement.
Evolving users and roles.
Demands that are growing.
Three types of maintenance
These three dimensions complement one another. The ones that apply to your project, and their exact scope, are defined together in the contract.
Correct behavior that no longer matches the expected functionality, or address an identified incident.
Scheduled technical tasks, when they fall within the scope: updates, checks, and maintenance of dependencies or the environment.
Evolve the application to accommodate new use cases or business needs, while remaining consistent with the existing architecture.
What NuWide can do
Each layer may fall within the scope of maintenance, depending on the project and the scope of work entrusted to NuWide. Support covers the agreed-upon layers, without implying continuous monitoring of the entire system.
Visual regressions, compatibility, responsiveness, and user experience where applicable.
Business logic, APIs, processing, and general operations.
Database and operational integrity, depending on the technical scope.
Frameworks, libraries, and technical components.
Identify performance issues and optimize where necessary.
Updates, configuration, and resolution of issues identified within the managed scope.
Systems, services, and runtime environments, when managed by NuWide.
Beyond corrections
Maintenance isn’t just about stepping in when a problem arises. It keeps the system functional and ready to evolve.
Continuity
Design → Development → Infrastructure → Maintenance: Maintenance is an extension of engineering rather than an addition to it.
Maintaining an application that you designed yourself—or took the time to understand—helps prevent gaps between its development and its operation.
Having NuWide maintain your application is always a choice: no maintenance is required once development is complete.
Systems, services, databases, reverse proxies: the runtime environment is also evolving. Depending on the contract, maintenance may cover both the infrastructure and the code.
Back in the day
An application that is fast and secure upon delivery can evolve in either direction. Monitoring them over time allows us to take action based on actual findings.
Performance can gradually deteriorate without any visible changes. The goal is to identify performance issues and optimize as needed, based on metrics.
A secure application today must continue to be maintained tomorrow. No system is immune to vulnerabilities: maintenance reduces exposure and addresses issues identified within the managed scope.
Tracking & traceability
Maintenance requests are tracked in the NuWide client portal: everyone knows what has been requested, what is in progress, what has been completed, and what is awaiting approval.
The request user journeys
Incidents, questions, updates, security, or hosting—all with up-to-date status information.
Areas for improvement are noted, discussed, and then planned.
Approve a delivery or request a change.
Project messages and documents all in one place.
Actions and decisions remain available for review.
How does the request process work?
The terms of service are defined in each project’s contract. Significant changes to the live site are approved before being deployed.
The need or problem is described.
NuWide analyzes the context, impact, and scope.
Corrections, adaptations, or updates as needed and approved.
Technical and functional testing.
The change has been delivered and tracked.
What kinds of projects?
Not all websites require an extended maintenance contract. A simple website may only need minimal support, while a business platform often warrants more comprehensive support.
Maintain an existing site
NuWide can take over maintenance of a project it did not develop, following a preliminary analysis. This step identifies what can be maintained as-is, what needs to be fixed first, and the risks to be aware of.
Frequently asked questions
Corrective maintenance addresses behavior that no longer aligns with expected functionality. Preventive maintenance reduces future risks through planned actions. Evolutionary maintenance adapts the application to new uses or needs. The scope of each project is defined in the contract.
Yes, after a preliminary analysis: architecture, code, dependencies, environment, available documentation, and risks. This analysis helps determine what can be maintained as-is, what needs to be fixed first, or whether a complete overhaul would be more appropriate.
It depends on the scope. Application maintenance covers the code, dependencies, and operation of the application; infrastructure (server, system, services) falls under an administration service when entrusted to NuWide. The two can be combined or handled separately.
Not always. Some updates can be automated depending on the environment; significant changes are tested and validated before being deployed to production.
Each request is described and then categorized based on context, impact, and effort. Development begins after the request is approved and, when necessary, after a quote is accepted. Requests, communications, approvals, and documents remain accessible in the NuWide client portal.
No standard turnaround time is guaranteed by default. The terms of service, including any turnaround times, are specified in each project’s contract.
These are included when the maintenance or infrastructure service calls for them. In such cases, the data to be backed up, the frequency, the retention period, and the restoration procedure are specified in writing for the project.
No. No connected system can be guaranteed to be incident-free. Maintenance reduces risks, allows identified problems to be addressed sooner, and limits the impact of an incident when it occurs.
Your maintenance
Let’s talk about your application, its architecture, and the level of support it actually needs.