Software rarely breaks the day support ends. It just stops getting safer.
Most businesses run on .NET they haven’t looked at in years: a customer portal on .NET 8, a pricing engine on .NET Framework, a WCF service nobody dares to touch. They keep working, so nobody budgets to update them, until a security audit, a cyber insurer or a new integration asks which version they are on. On 10 November 2026, .NET 8 and .NET 9 stop receiving security patches. Version 4.6.2 of .NET Framework follows in January 2027.
At vi-tech, we build new .NET applications and bring existing ones up to date without stopping the business that depends on them. We design the architecture, write clean C#, build the APIs that connect your systems and move them to .NET 10, the long-term release supported until November 2028. Then we add what modern .NET makes possible: faster pages, cloud hosting that scales, offline-ready apps for people in the field and AI assistants that work inside your own software, with your own permissions.
3x
3yrs
800bn
58%
more likely to suffer a cyber incident: organisations still running end-of-life software, according to an insurer’s claims data.
of security patches for .NET 10, the long-term support release, running until November 2028.
package downloads from NuGet, the library ecosystem behind .NET, across more than 478,000 packages.
of developers who use ASP.NET Core want to keep using it, and almost one in five web developers surveyed already does.
New software, old software made new, and everything that connects them.
Six things we deliver on .NET, from the first line of code to the patch that keeps it safe five years later.
Six layers inside every .NET application we ship.
Screens are what people see. These six layers decide whether the software is fast, safe, easy to change and still supported in five years. Tap a marker to look inside.
Most systems don’t need a rewrite. They need a plan and a steady hand.
Big-bang rewrites are where budgets and good intentions go to die: two years of work, a frozen roadmap and a weekend cut-over everyone dreads. We take the slower road that finishes sooner. We put a modern .NET front door in front of the old system, move one feature at a time behind it and keep both running side by side, so every step goes live on its own and can be rolled back if it misbehaves. The business never stops, and the old code quietly retires.
Side by side
Yours
In slices
features move one at a time, each one live and tested before the next begins
old and new run together, so there is no weekend cut-over to survive
clean, documented code and pipelines that your team or any partner can take over
Secure by default
Security checks in every build, dependencies kept current and Microsoft’s monthly .NET patches applied on schedule.
Fast by design
Load testing, caching and performance budgets set before launch, so pages and APIs stay quick as you grow.
Tested before it ships
Automated tests around the code that matters, so changes go out on a Tuesday afternoon, not a Saturday night.
Six stages from first code review to software that keeps improving.
We read your code before we quote for it, then ship working software every two weeks.
Where are you starting from?
A new product, an ageing system, a move to the cloud and an AI feature each start in a different place. Here is where we would usually begin.
Platform
Web & APIs
Apps
Power BI Desktop · Power BI Service · Report Builder · Power BI Embedded · Mobile apps
Lakehouse · Warehouse · Data Factory · Real-Time Intelligence · OneLake
DAX · Power Query (M) · Tabular Editor · DAX Studio · Direct Lake
Data
Entity Framework Core · SQL Server · Azure SQL · PostgreSQL · Cosmos DB · Redis
Cloud & DevOps
Azure · Docker · Kubernetes · GitHub Actions · Azure DevOps · OpenTelemetry
AI
Microsoft Agent Framework · Microsoft.Extensions. AI · Azure OpenAI
Mid-ocean, an app that needs the internet is an app that doesn’t work.
Software for vessels has to run on a satellite link that drops, queue its changes and sync the moment the signal returns, and be simple enough for an engineer at the end of a twelve-hour watch. Our maritime team includes a Master Mariner who has served as a Salvage Master, so we build for those conditions from day one. We write offline-ready .NET apps for planned maintenance, inspections, crew records and ship-to-shore reporting, connect them to your ship management system and bring the ageing Windows tools many fleets still rely on up to date.
Also building for logistics, finance, manufacturing, healthcare, energy and professional services.
Three ways in. One team accountable for the outcome.
.NET code & risk review
Build or modernise
Support & patching
A fixed-price, two-week review of your code, versions, dependencies, security and hosting, with a clear upgrade path and an estimate you can budget against.
New applications, APIs or staged upgrades, delivered in two-week sprints by one team, from architecture to release.
Monthly .NET and package updates, monitoring, fixes and small features on a monthly plan, with version upgrades planned ahead.
Best for
estates that have grown messy
Best for
new reporting or a fresh start
Best for
teams without in-house BI specialists
