Phase 1: Discovery, Requirements & Architecture Blueprint
Assemblies, WebForms pages and WCF contracts are mapped into a dependency graph and migration risk register.
Three pillars. Twelve focused engagements.
DevNord migrates business-critical .NET Framework, WebForms and WCF applications to supported .NET 8/9 on modern cloud infrastructure. AI-assisted dependency mapping, strangler-fig extraction and automated Playwright QA make every step reversible.
This is the service-specific architecture we design and operate. Inspect any node to see its role, the engineering or QA control around it, and how risk is contained.
Tap any node to inspect it.
Hover over a node to inspect it.
Node inspectorSelect any component to see what it does, which control protects it and how we hand it over.
An indicative 12-week cadence for a full engagement. The exact calendar, milestones and price are fixed in your EUR (€) or SEK (kr) proposal after discovery.
Indicative cadence — finalised in your fixed-scope proposal
Assemblies, WebForms pages and WCF contracts are mapped into a dependency graph and migration risk register.
An anti-corruption proxy is deployed and the first .NET 8/9 service takes traffic from one bounded context.
Characterisation tests protect legacy behaviour while exploratory UAT and Playwright verify each extracted journey.
Weighted routing completes the cutover; IIS configuration, CI definitions and multi-cloud IaC are handed to your team.
Every engagement runs with the same operating model: senior squads, transparent ownership and written evidence at every gate.
Two-week sprint cadence with demoable increments and a written decision log.
Transparent Git repository ownership — repositories land in your organisation from day one.
Infrastructure-as-code (Terraform or Bicep) for every environment, reviewed and reproducible.
Fixed-scope proposals in EUR (€) or SEK (kr), with capped B2B consulting retainers when scope is still emerging.
Bilateral NDA signed before source code, architecture data or credentials are shared.
The fastest safe route off .NET Framework is rarely a rewrite. DevNord maps assemblies and data ownership, then places a strangler-fig proxy in front of the monolith. Individual capabilities move to .NET 8/9 services in containers, each protected by characterisation tests before it receives production traffic.
For Nordic and European B2B teams we default to EU-region services across major cloud platforms, managed identity and infrastructure-as-code. Proposals are fixed scope in EUR (€) or SEK (kr) and include a rollback plan for every slice.
Your .NET Framework application still runs the business, but it is anchored to end-of-life runtimes, Windows-only hosts and a web of WCF/WebForms coupling. Hiring gets harder, dependencies age, and deployment windows grow longer each quarter.
We start with a two-week Blueprint Audit that maps assemblies, endpoints and data ownership. Then a strangler-fig proxy routes individual capabilities to new .NET 8/9 services running in containers, each protected by characterisation tests before it takes traffic.
Move to .NET 8/9 LTS with a clear runway, current C# tooling and a hiring pool that still exists.
Weighted routing and rehearsed rollback mean a bad release is a traffic shift back, not an incident.
Independent services, automated QA and self-serve environments collapse multi-week releases into days.
These are service-specific, reviewable assets — not status reports. Your team owns each one.
Still unsure? Write to us at [email protected] — we reply in plain language, without a sales script.
Yes. We commonly keep the WebForms front end behind the strangler proxy while replacing backend capabilities first, then migrate screens incrementally to React or Razor once the API layer is stable.
We wrap them in an anti-corruption layer that exposes a clean, versioned API to new services. The legacy contract stays untouched until its consumers have moved.
No. The strangler approach runs modernisation in parallel with your roadmap. We agree a small, protected slice of capacity and sequence extractions around your release calendar.
Microsoft Azure is often a short path for deep .NET estates, but we design target architectures across Azure, AWS, Google Cloud, and private cloud environments based on your existing contracts, data residency needs and skills — never on licence preference alone.
Start with the 2-week Blueprint Audit. You receive a dependency map, target architecture and sequenced extraction plan you can act on — whether or not you continue with DevNord.