.NET support and maintenance services

.NET support resolves issues affecting current operations, while .NET maintenance keeps the application healthy over time through planned technical work. Most established applications need both.

There is no single fixed price for .NET support. The cost reflects the current state of the codebase and the level of coverage required. Occasional requests involving a well-documented codebase usually require less engineering time than recurring production issues or strict response expectations.

After the initial discussion and any necessary review, UKAD provides an estimate based on the expected workload. Monthly agreements typically start from 20 engineering hours, while occasional requests can be handled on an hourly basis. Larger upgrades and migrations are scoped separately, with responsibilities and costs agreed in advance.

Yes. UKAD provides SLAs (Service Level Agreements) with response times based on incident severity and the agreed coverage hours. Critical production issues receive the highest priority, with specific targets documented in advance.

The SLA also defines how an incident is escalated and how progress is communicated. Resolution time depends on the cause and complexity of the issue, but the team works to restore affected functionality without unnecessary delay.

Yes. We first review the available codebase, infrastructure, documentation and deployment process, then agree access, responsibilities and initial priorities with your team.

If documentation is incomplete, the handover can begin with a focused technical review and knowledge recovery. A straightforward transition can often be completed within one to two weeks, while larger or poorly documented systems may require a longer handover.

Yes. UKAD works with established .NET Framework applications, including Web Forms and ASP.NET MVC solutions. This can cover both the codebase and the way it is hosted and released.

When the existing setup becomes too costly or platform limitations slow further development, our legacy application modernisation services provide a gradual path forward. Improvements can be planned in stages without requiring a complete rebuild.

Yes. A complete rebuild is not always necessary. UKAD can modernise a legacy .NET application in stages, starting with the components that carry the greatest technical risk or maintenance burden. This allows the existing platform to remain operational while improvements are introduced gradually.

The first stages may focus on framework upgrades or selected architectural changes. Where cloud migration is part of the plan, workloads can move to Microsoft Azure or AWS. Each stage is planned and tested separately to reduce the risk associated with replacing the entire solution at once.

UKAD follows an ISO/IEC 27001:2022-certified information security framework. Access to repositories and technical environments is limited to assigned team members, while confidentiality requirements and ownership terms are documented in the relevant NDA and service agreement.

UKAD can work within your existing repositories and infrastructure, allowing your organisation to retain control over source code, permissions and project assets. Additional security requirements can be agreed during onboarding to align with your internal policies.

Yes. Individual specialists can join your existing team through staff augmentation, or a dedicated engineering team can take responsibility for an agreed area. The setup depends on what you want to retain internally and where additional capacity is needed.

The team follows your established tools and communication routines, working directly with internal developers and product managers. Roles and access levels remain clearly defined.