Software Maintenance and Application Support Services

Our software maintenance services keep web apps, mobile apps, APIs, websites tied to an application, and AI systems working, secure and current. A month includes fixes, security patches, upgrades, monitoring and a report you can read in five minutes. It starts with an access handover and a written review.

Six years on one clinic's live site · 48-hour response in the client's own words · 5.0 on Clutch

SOFTWARE MAINTENANCE

What software maintenance services are

Software maintenance services keep live software working, secure and current after launch. They cover bug fixes, security patches, framework and platform upgrades, monitoring and backups, changes for new operating systems and app store rules, and a set number of hours for improvements, reported every month. Metwaves maintains web apps, mobile apps, websites tied to an application, and AI systems, including code that another team built.

01

Corrective

Bugs and incidents

For exampleA booking form that fails on one browser is fixed and released

You see it inA ticket with the cause and the fix

02

Adaptive

Changes in the OS, browser, framework or a third-party API

For exampleAn Android app updated for Google Play's new target API level

You see it inRelease notes

03

Preventive

Patches, dependency updates, backups tested by restore

For exampleA library with a known vulnerability updated before anyone exploits it

You see it inThe monthly report

04

Perfective

Small improvements

For exampleA slow report rewritten so it loads in seconds

You see it inHours used against the plan

WHEN TO CALL US

Signs you need a software maintenance partner

Most maintenance work starts with one of these. Red ones put the business at risk now.

Open issues on your software
  • The developer who built it has gone

    Nobody is sure how to deploy it, or where the passwords are.

  • Security patches are months behind

    Known vulnerabilities stay open in libraries anyone can look up.

  • The framework is out of support

    Xamarin support ended on May 1, 2024, and nothing patches it now.

  • Google Play says the target API level is too old

    Updates are refused until the app targets the current level, and new users on newer Android versions stop seeing it.

  • Bugs pile up and nobody owns them

    A spreadsheet of issues with no priority and no dates.

  • You pay every month and cannot see what was done

    No report, no tickets, no release notes.

Application support and maintenance services we provide

Eight kinds of work, usually bundled into one monthly plan.

Bug fixing and incident response

Problems triaged by severity, fixed in a branch, tested and released.

Security patches and dependency updates

Libraries and frameworks kept current, known vulnerabilities closed first.

Framework and platform upgrades

Moves to supported versions of .NET, Node.js, React or Angular, planned and tested.

Mobile app maintenance

New iOS and Android versions, store rules and crash monitoring. More below.

Monitoring, backups and hosting care

Uptime and error alerts, and backups we prove by restoring them.

Small improvements each month

A set number of hours for the changes your team asks for.

Takeover of code another team built

A review before any promise. How it works.

AI and machine learning model support

Monitoring answers and retraining models on new data, as we do for BioBuild's engine.

How application maintenance services work day to day

Requests, alerts and scheduled work all go through the same route: triage, a fix in a branch, a test, a release and a line in the monthly report.

How support works day to day: requests from your team, monitoring alerts and scheduled work are triaged by severity, fixed in a branch, reviewed and tested, then released with a rollback ready; every change appears in the monthly report, and a quarterly review decides what to upgrade, replace or retire
  • Where work comes from
  • The route every change takes
  • Agreed with you
Nothing is changed directly on the live system. Every fix goes through a branch, a test and a release you can see in the monthly report.

Support levels and response times: what to agree in writing

We agree response times in each contract instead of selling fixed tiers. These are the terms to settle with us or with any other provider.

Support terms, to agree in writing
  • Hours covered

    Which hours, in which time zone, and what happens outside them

    From ____ to ____, time zone ____
  • Urgent response time

    How fast someone starts on a problem that stops your business, and how you reach them

    Within ____ hours
  • Normal response time

    How fast a non-urgent bug or question gets an answer

    Within ____ working days
  • What counts as urgent

    A written definition, so nobody argues about severity during an outage

    Definition attached to the contract
  • Hours for changes

    How many hours a month the plan includes, and the rate beyond them

    ____ hours a month, then ____ an hour
  • Reporting

    What the monthly report shows: issues, fixes, releases, hours and risks

    Sent on day ____ of each month
48 hours

or less to answer any request on the urgent care engagement, confirmed by the clinic's founder in a verified Clutch review. It is the response time we can show in public.

TAKEOVER

Taking over software another vendor built

We review before we promise. The first weeks produce a working build, a review and a fixed list of fixes.

Keys to collect first

We send this list to the outgoing vendor for you.

  • Source code and its history
  • Cloud and hosting accounts
  • Domains and DNS
  • App store accounts
  • Third-party API keys
  • Any documentation
  1. 1

    Build and deploy it ourselves

    We rebuild and deploy the software from the repository to prove nothing is missing. This is where most surprises appear.

  2. 2

    Review the code, security and hosting

    Libraries out of support, known vulnerabilities, backups that were never tested, and the parts of the code that change most.

  3. 3

    A fixed list of fixes, ranked by risk

    Written up at a fixed price, so you decide what to fix first.

  4. 4

    Monthly support, reviewed every quarter

    The plan starts, and each quarter we look at what to upgrade, replace or retire.

When we take over

  • Only the previous developer knows how to deploy.
  • Accounts and keys sit in someone's personal email.
  • Nobody knows which libraries are out of date or vulnerable.
  • Backups exist, but nobody has restored one.
  • Fixes are made directly on the live server.

After the review

  • The software builds and deploys from your own repository.
  • Accounts, domains and keys are in your company's name.
  • A ranked list of risks, with a fixed price for each fix.
  • Backups restored and tested on a schedule.
  • Every change goes through a branch, a test and a release.

Mobile app maintenance services: staying in the stores

A mobile app needs work every year even if nothing in it changes, because Apple and Google change the rules and the operating systems. The same plan covers optimisation and integration: faster start-up, lower battery use, new payment or login providers. Rules checked on Google's and Apple's developer sites in November 2026.

  1. May 1, 2024

    Xamarin support ended

    No more fixes. The way out is a supported framework; see cross-platform app development.

  2. April 28, 2026

    Apple: Xcode 26 and the iOS 26 SDK

    Uploads to App Store Connect must be built with Xcode 26 or later.

  3. August 31, 2026

    Google Play: Android 16, API level 36

    New apps and updates must target API level 36. Existing apps must target API level 35 to stay available to new users on newer Android versions.

  4. Every year

    New iOS and Android versions

    We test on the new versions before they reach your users, then watch crash rates and reviews.

WEBSITES

Website maintenance services for sites tied to your software

If your site is a brochure on WordPress, a website-care plan is usually cheaper than us, and we will say so.

We maintain websites with custom code, online booking or a link to your application, where an update can break something a care plan would not notice. For a rebuild, see CMS development.

What a website plan with us covers

  • Updates to the CMS, plugins, frameworks and server
  • Backups, and a restore test on a schedule
  • Uptime and error monitoring
  • Security patches and certificate renewals
  • Content and layout changes on request
  • Search engine work where it is agreed, as on the clinic site

CASE STUDY

Six years of support for a clinic's live website

We built the website for Epic Urgent and Family Care, a walk-in clinic in Palatine, Illinois, before it opened, then supported it from February 2016 to February 2022.

Each month brought search engine work, layout changes on request and a progress report by email. In the founder's words on Clutch: “Very responsive to our email and text messages with turn around time of 48 hrs or less.”

Read the full case study >

  • EngagementFebruary 2016 to February 2022
  • TeamTwo to five people
  • Response48 hours or less to any request
  • ResultsOnline appointment requests up 25%; first-page rankings for 70% of target keywords within the first year

Also supported: BioBuild's material recommendation engine, live since January 2025 and retrained every quarter on real project outcomes.

How we start

Five steps from the first call to a plan that runs itself.

  1. 1

    Access handover

    Code, accounts and keys moved into your company's name, with access for us that you can remove.

  2. 2

    Review

    We build and deploy the software ourselves, then review the code, security, hosting and backups.

  3. 3

    Fix list at a fixed price

    Risks ranked, each with a fixed price, so you decide what to fix first.

  4. 4

    Monthly support

    Fixes, patches, upgrades and agreed hours, with a report you can read in five minutes.

  5. 5

    Quarterly review

    What to upgrade, replace or retire next, before it becomes urgent.

What software maintenance costs

We price a monthly plan after the review. These factors move it most.

high impact

Size and age of the code

A small, recent app on current libraries costs less to keep than a large one that has not been updated in years.

high impact

Response time and hours covered

Faster responses and longer hours mean someone has to be ready.

medium impact

Number of apps and environments

Each app, store listing and environment adds checks and releases.

medium impact

Changes you want each month

Keeping software running is one cost; improving it is another.

medium impact

Security and compliance needs

Healthcare and financial data add reviews and records.

low impact

Third-party integrations

Each outside API can change under you, so each needs watching.

Ways to work with us

Every plan starts with the review, so the price matches your software.

Monthly plan with set hours

Software your business relies on every day: agreed response times, monitoring and hours for changes.

Pay per request

Stable software that needs occasional fixes, estimated request by request.

Fixed-price review and fixes

The takeover review and each fix on the ranked list, at a fixed price.

Dedicated developer

A large application with steady change, with one developer who knows it, monthly.

Technology we support

The technologies in our live case studies, plus PostgreSQL and Neo4j. Older versions are welcome: upgrading them is part of the job.

ASP.NET Core
ASP.NET Core
.NET
.NET
Node.js
Node.js
Python
Python
React
React
Angular
Angular
React Native
React Native
Swift
Swift
Kotlin
Kotlin
SQL Server
SQL Server
MongoDB
MongoDB
MySQL
MySQL
Microsoft Azure
Microsoft Azure
AWS
AWS

How to choose a software maintenance company

Six questions to ask any provider, us included, and what a good answer looks like.

AskWhat a good answer looks like
What are your response times, in writing?Urgent and normal, with the hours they apply to.
Can I see a sample monthly report?It should show issues, fixes, releases, hours used and risks.
Who holds the accounts and keys?You should. The vendor gets access you can remove.
Have you taken over code another team built?Ask what they found and what they fixed first.
What happens if we leave?The notice period and a handover of code, accounts and documentation.
Do we need 24/7 on-call cover?If you do, ask every vendor for it in writing. We agree hours per contract and do not advertise round-the-clock cover, so a provider built around 24/7 support may suit you better.

When maintenance is not enough

Sometimes the right move is to rebuild, upgrade or add to the software.

Application modernizationWhen patching an old system costs more than moving it.
Web application developmentNew features or a new app, from the team that keeps it running.
CMS developmentWhen the website itself needs rebuilding.
.NET developmentUpgrades from .NET Framework and older .NET versions.
Mobile app developmentNew iOS and Android apps, or a rebuild of one that cannot be saved.

QUESTIONS & ANSWERS

Software maintenance: frequently asked questions

Straight answers on cost, response times, takeovers and what happens if you leave. If you don't see an answer to your question, you can send us a message from our contact form.

They keep live software working, secure and current: fixing bugs, applying security patches, upgrading frameworks, adapting to new operating systems and store rules, and making small improvements, with a report of what was done.

Updates, backups, security patches, uptime checks and small content or layout changes. For a site tied to your software, they also cover the application behind it.

It depends on the size and age of the code, the response time and hours you need, and how many changes you want each month. We price a monthly plan after the review.

Yes. We collect the code and accounts, rebuild and deploy it ourselves, review it, and give you a ranked list of fixes at a fixed price before the monthly plan starts.

We agree response times for urgent and normal issues in each contract. On the urgent care engagement, the clinic's founder confirmed on Clutch that we answered within 48 hours or less.

Support answers and fixes issues as they come. Maintenance keeps the software current so fewer issues come. Most plans include both.

Yes: yearly updates for new iOS and Android versions, Apple's and Google's build rules, crash monitoring and store releases.

You keep everything: code, accounts, documentation and the history of what we changed. We agree the notice period and the handover steps in the contract.

Ask for response times in writing, a sample monthly report, who holds the accounts and keys (you should), a takeover they have done, and the handover terms if you leave. The questions on this page go into more detail.

INSIGHTS & NEWS

Discover IT Industry Insights and Technology Trends

Nikit Nandan    Nikit Nandan November 17, 2026
Is .NET 8 Still Safe to Run After November 2026?

Support for .NET 8 and .NET 9 ended on November 10, 2026. What that means for apps still on them, how risky it is, and how to plan the move to .NET 10.

Learn More >
Microsoft Technologies 5 min read
Nikit Nandan    Nikit Nandan November 12, 2026
Top AI agent development companies for small and mid-sized businesses (2026)

Nine AI agent development firms a small or mid-sized business can shortlist, with Clutch figures, minimum budgets and the weaknesses their own clients name. Published by Metwaves, which is not ranked.

Learn More >
AI Development 9 min read
Nikit Nandan    Nikit Nandan November 12, 2026
Enterprise AI Agent Platforms Compared (2026)

An architecture review of the four big enterprise AI agent platforms: where each one reasons, acts, finds its data and connects to outside agents, what it costs, and when a custom build is the better choice.

Learn More >
AI Development 9 min read

Let’s build your idea!

Let us help you with free analysis & estimate. Our product expert will contact you within 12 hours.

 All your information is kept confidential and protected by NDA.