Technologies we take on
For IT and operations managers handing over an existing system: we look after software built on anything from VB6 to .NET 10, and the testing, release and monitoring practice that keeps it safe to change. Each page covers what tends to go wrong, the realistic options, and how we approach the work.
Microsoft platform
From Classic ASP and Web Forms to ASP.NET Core on .NET 10.
- .NET Framework to modern .NETSupport for .NET Framework applications and staged migration to current .NET.
- ASP.NET Core and modern .NETSupport and development for ASP.NET Core applications on current .NET.
- ASP.NET Web FormsSupport for Web Forms applications and page-by-page migration to ASP.NET Core.
- Classic ASPSupport, hardening and staged migration for Classic ASP sites on IIS.
Databases and data access
SQL Server and the code that talks to it.
Cloud and hosting
The servers and services the application runs on.
Web front ends and Node.js
From jQuery and AngularJS to React and TypeScript.
- AngularJSRoute-by-route migration from AngularJS 1.x to Angular, React or Vue.
- Knockout and jQuery front endsStabilising and gradually replacing large Knockout, jQuery and Kendo UI front ends.
- React and TypeScript front endsSupport for React front ends, and new React screens added to older systems.
- Node.jsUpgrades, package security and support for Node.js services and functions.
Desktop and office
Access, Excel and VB6 systems that outgrew their tools.
Engineering practice
What makes a system safe to change: tests, releases, monitoring, integration and AI.
- APIs and systems integrationREST APIs, single sign-on, file and message integrations for existing systems.
- Automated testing with PlaywrightBrowser and integration tests added to existing systems, run on every release.
- Build and release pipelinesAutomated build, test and release in Azure DevOps or GitHub Actions.
- Production monitoringError tracking, performance monitoring and logs with Sentry, New Relic and Seq.
- Large language models (Claude and others)Claude and other LLMs built into existing systems, tested and kept within budget.
Vendor support on 12 November 2026
Once support ends, the vendor stops issuing security fixes. The software keeps running, but each new vulnerability stays open.
Not on the list?
We take on other stacks when we can do the work properly. Tell us what the system is built on and we will say plainly whether we are the right people.