Application Maintenance and Support Services in India: costs, delivery models and data rules

Application maintenance and support services in India start at roughly ₹68,000 or $1,000 per month for business-hours cover with an eight-hour response, ₹1,60,000 or $2,500 for 24 by 5 cover with a four-hour response, and ₹3,40,000 or $5,250 for 24 by 7 cover with a one-hour response and a named engineer. Indian clients are invoiced in rupees with GST.

This article covers what those tiers actually include, the delivery models available from an Indian partner, how IST cover maps onto UK, US and Gulf working hours, and the data residency and incident reporting rules that apply to anyone operating production systems for Indian users.

What does application maintenance and support cost in India?

Our published tiers are the clearest reference point. The Essential plan is ₹68,000 or $1,000 per month: business hours in IST, eight-hour response, ten hours of work included. Standard is ₹1,60,000 or $2,500 per month: 24 by 5 cover, four-hour response, twenty-five hours included. Enterprise is ₹3,40,000 or $5,250 per month: 24 by 7 cover, one-hour response, sixty hours included and a named engineer. Applications with AI components add ₹40,000 or $750 per month for evaluation runs, cost monitoring, prompt regression and re-indexing. Everything is listed on the pricing page and described in full under software maintenance and support.

Annualised, Essential is about ₹8.2 lakh a year and Enterprise about ₹41 lakh. Those are the retainer figures only; a realistic budget adds an upgrade allowance and a change budget on top, which is the same arithmetic anywhere in the world. Indian clients receive GST invoicing in rupees; international clients are billed in US dollars. Model API usage, where an application has AI features, is paid through your own provider accounts rather than marked up through us.

Rate arbitrage is the usual reason buyers look at India, and it is real, but it is not the whole argument. Indian engineering rates sit well below US and UK equivalents for comparable seniority, as set out in our comparison of software development pricing in India versus the US. What changes the calculation for maintenance specifically is continuity: a support relationship is worth what the retained knowledge is worth, and cheap capacity with high turnover is expensive in the second year.

One caution on comparing quotes. Indian vendors price very differently from each other, and a figure well under the entry tier usually means a shared first line with no named engineer, no patching commitment inside the retainer and no out-of-hours cover. That can be a perfectly rational purchase for a low-risk internal application. It is not comparable to a plan with reserved hours and a response target, and putting the two side by side in a spreadsheet produces the wrong decision.

Delivery models available from an Indian partner

Four shapes cover almost everything buyers actually purchase. The right one depends on where your users are and how much of the system your own team still understands.

About half our work is paired with internal teams, with documented handover, so the fourth row is less unusual than it sounds. It is often the correct answer for a company that has the engineering capability but not the headcount to run a rota, which is the single hardest thing about support for a team under twenty people.

What does IST cover actually buy you?

United Kingdom and Europe

IST is four and a half hours ahead of UK time in summer and five and a half in winter, so an Indian weekday shift covers the entire UK working day with several hours to spare at the start. This is the easiest overlap in the world for support: an incident raised at 09:00 in London lands in the middle of an Indian afternoon, and work done overnight in IST is ready before the London team logs in.

United States

IST is nine and a half to ten and a half hours ahead of US Eastern time. Standard IST hours overlap the very start of the US East working day only, which is why US-facing products usually need the 24 by 5 tier rather than the entry tier. Eazyware is headquartered in Bengaluru with studio presence in New York and London, and we work across IST, UK and US East hours; what that means practically is a scheduled overlap window, not a claim that everyone is awake at once.

Gulf and Asia-Pacific

The Gulf sits an hour and a half behind IST, giving near-total overlap, and Singapore two and a half hours ahead, which still leaves most of a shared working day. For these markets an Indian support partner behaves like a local one for practical purposes, which is why so much Gulf enterprise support is already delivered from Indian cities.

Data residency, DPDP and incident reporting

If your application processes the personal data of people in India, the Digital Personal Data Protection Act, 2023 applies to you regardless of where your company is registered. The practical maintenance consequences are access control, purpose limitation, retention rules and the ability to action deletion requests, all of which belong in the support contract rather than in a policy document nobody reads. The glossary entry on the DPDP Act 2023 covers the obligations, and what Indian companies must do works through them in more depth.

Incident reporting is the rule most often missed by teams new to operating in India. CERT-In, the national computer emergency response team, requires organisations to report specified cyber incidents within six hours of noticing them, and to keep logs within Indian jurisdiction. The directions are published by CERT-In, and a support contract that does not name who detects, who decides and who files against that clock is not compliant in practice however good the engineering is.

Residency itself is a design decision rather than a support decision, but maintenance is where it is enforced. Ask where primary data, backups, logs and any AI model traffic physically sit, and make the answer a contractual term. Both major cloud providers offer Indian regions, and several sectors, notably banking and insurance, carry their own stricter rules. The data residency entry sets out the vocabulary you need for that conversation.

Sectoral regulators add a further layer. Banking, insurance and capital markets estates carry outsourcing and audit obligations from their own regulators on top of the general rules, and those obligations flow down to whoever maintains the software. If you operate in a regulated sector, bring the compliance team into the vendor conversation at the shortlist stage rather than after selection, because a support contract that fails a regulatory review is renegotiated from a weak position.

How to judge a domestic partner against a global one

• Ask who holds the knowledge, by name. Global firms rotate staff more; that is the trade for their bench depth.
• Check the overlap window in writing. Cover hours in IST mean nothing until they are mapped to your users' clock.
• Confirm the invoicing currency and GST treatment. Indian entities should get rupee invoices with GST; international clients, dollars.
• Ask where logs live. Residency, retention and the six-hour reporting duty all depend on this one answer.
• Test escalation with a scenario, not a diagram. Ask what happened during their last out-of-hours incident.
• Confirm you own everything. Code, infrastructure, credentials, prompts and documentation should be yours throughout.
• Compare three-year totals. A lower monthly rate with high turnover costs more by year two.

When an Indian support partner is the wrong choice

There are cases where the honest answer is no. If your data cannot legally leave a specific jurisdiction, and the contract cannot be satisfied by an Indian-region deployment with access controls, that is a hard constraint and no amount of process solves it. Some public sector and defence-adjacent work falls here.

If your users are entirely US Pacific and you need a sub-hour response during their working day, an IST-based team is working nights to serve you, and night rotas have a quality cost that shows up in month six. Buy local first-line cover and use an Indian partner for depth and engineering rather than for the pager. And if the requirement is two hours of work a month, a retainer of any size is the wrong instrument; pay for time and materials until the volume justifies a plan.

What a real engagement looks like

A university running fifteen-year-old student and finance systems moved to a supported, incrementally modernised estate without a rewrite, described in the university ERP modernisation case study. The support arrangement that followed mattered as much as the engineering: academic calendars create hard freeze windows, admissions creates seasonal load, and the team that fixes something in October needs to remember it in July. Continuity, not rate, is what made that work. Our delivery base for engagements like this is Bengaluru, with on-site time as the programme needs it.

Related reading

Outsourcing development to India: what has changed covers the wider commercial picture, and the page on working with an AI development company in Bangalore explains how we run engagements from the city. If you want a straight answer on which tier your estate needs, send us the inventory and we will tell you.

Indian delivery is cheaper per hour and better on overlap for most of the world, but the number that decides a support contract is how long the same engineer stays on your system.