Software maintenance for the system you already run.
When production breaks, know where to report it, who takes the ticket and when you’ll hear back. The Wavect Maintenance SLA pairs ongoing software care with written response targets for your system.
DIRECT ANSWER
The Wavect Maintenance SLA is a written support schedule for an ongoing software maintenance retainer. It sets the systems covered, the working hours and first-response targets by severity. Maintenance also covers agreed patches, bug fixes and small changes.
Best for
- Owners of a production system that can be built and released, and needs a reliable maintainer
- Teams whose developers have moved on to new work and want routine care handled
Consider another approach
- A change of provider that needs access recovery and knowledge transfer first
- 24/7 on-call operations or a contractual uptime guarantee
Start from a system someone can maintain
What routine care includes
Updates and security patches
Keep runtimes, frameworks and libraries on supported versions. Security advisories are triaged and patched in an agreed order of priority.
Bug fixing
Reproduce, fix, test and release defects reported by your team or found in logs and error tracking.
Small enhancements
Minor changes within an agreed monthly budget. Anything larger is quoted separately before work starts.
Monitoring hygiene
Keep error tracking, logs, certificates and alerts useful. Alerts route to a named person during agreed hours.
What does the Wavect Maintenance SLA include?
Critical incident
A core production workflow is unavailable and there is no workable alternative. We acknowledge the ticket, begin triage and agree when you’ll get the next update.
Degraded service
A production workflow is impaired but users can still work. We assess impact and confirm a workaround or the next action.
Routine request
Minor bugs, updates and small improvements enter the maintenance backlog and are scheduled within the agreed scope.
Response clock and reporting
The clock uses the agreed support channel and staffed hours. The monthly report shows ticket severity, first-response times, missed targets and follow-up actions.
Illustrative record: one month of maintenance
Onboard, maintain, review
Onboarding check
We build, test and release the system once in an agreed environment. You receive a version inventory, known risks and a proposed maintenance scope.Ongoing maintenance
A monthly agreement covering the agreed systems, working hours, request channel and response targets per contract.Periodic review
Review what was done, what aged and what keeps breaking. A recurring structural problem becomes a separate modernization or security decision.
Bring access, the version list and the people who report problems
Choose a focused next step
These engagements cover specific needs within this service. Follow the scope that matches your decision.
Recurring monitoring and staffed response, including a separately agreed 24/7 arrangement, belong in Managed Cloud Operations; ordinary maintenance or migration does not activate that coverage.
Ongoing care in existing engineering work
IKB: Wavect worked inside IKB’s Smart City build on infrastructure and devices, handed the platform over to IKB’s in-house team completely, and stayed on as external support for new device integrations, the Grafana stack, field connectivity and manufacturer calls. MyMerch documents a multi-year engagement improving a working Shopify business in targeted steps without a rewrite. Polity documents long-running QA ownership with flakiness reduction and bug triage across services. None of these cases documents 24/7 coverage or an uptime commitment.
Smart City IoT for Innsbruck: extended and scaled the LoRaWAN infrastructure, evaluated and integrated multi-vendor devices, wrote …
MyMerch’s team puts the efficiency gain at ~50%. Fewer delivery errors, improved Shopify conversion, no rewrite.
1.5 years owning QA across seven services and multiple vendors. Quality stayed shippable through every refactor.
These are selected projects, not our full portfolio. We have shipped 100+ products since 2018.
Questions before you start
Scope your maintenance SLA
Describe the system, its stack, who maintains it today and what keeps slipping. Keep credentials and confidential data out of the first enquiry.