APIs and services
Back ends for web and mobile clients, as we ship on .NET.
We have no published Java build. Our enterprise back ends are .NET and Node.js, and we say plainly where that differs from Java before you commit.
Back ends for web and mobile clients, as we ship on .NET.
Moves from older releases to JDK 21 or 25.
Years of records migrated with no loss, as on the Norwegian platform.
Codebases left by another vendor, documented before anything changes.
Illustration. A dashed outline marks where the technology would sit. We have no published build on it.
A new release ships every March and September. Long-term support releases get years of Oracle support.
Sources: Oracle Java SE Support Roadmap for support dates, OpenJDK for release dates, checked 2 November 2026. JDK 27 went to general availability on 15 September 2026.

The same job on a different stack: a failing enterprise rebuild finished on .NET and Angular with years of legacy data migrated.

A project taken over from a failed vendor and a team grown to more than 60 developers, on Node.js and .NET.
.NET
AWS
Azure
Docker
Kubernetes
AngularJDK 25, a long-term support release that went to general availability on 16 September 2025, with Oracle Premier Support to September 2030. JDK 21 has Premier Support to September 2028.
No. We say so on the first call and show the nearest work, which is enterprise back ends on .NET and Node.js.
We have taken over abandoned projects on .NET and Node.js and documented them first. We would apply the same method and tell you where Java differs.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes on your system and the JDK it runs. No sales pitch.