TOKAI and RAT
Installed at air navigation service providers' premises and updated remotely, with support for each installation. Since version 4 shipped in November 2025, we have released an update every few weeks.
Read the case study →Capability 04
Deployment and long-term operation
Installed on your premises, in the cloud or on a closed network, then supported and upgraded by one team through its service life.
The problem
Most of the work comes after the first release.
Safety software often stays in service long after the contract that paid for it. It has to install where the client needs it: in their own data centre, in the cloud or on a closed network, where every update has to be carried in. Then it has to be patched, upgraded and supported for a decade, through new regulations, new operating systems and new people on both sides.
That work needs people who know why the code is the way it is.
What we support
Installed on site, carried into closed networks, deployed on Kubernetes.
ASMT
Containerised services that install on closed networks, where each update is carried in. We released version 6 in July 2026.
Read the case study →EMCIP
Deployed on Kubernetes behind single sign-on, with 88 releases after go-live.
Read the case study →The local installation at MUAC went very smooth, and consecutive software updates are performed remotely and very quickly.
The support from JLG is very competent and quick. It’s the best support from any IT company I have worked with.
What it runs on
Standard components, documented with every release.
- Java services and Angular web applications
- PostgreSQL
- Containers on Kubernetes
- Single sign-on through Keycloak
How we would approach yours
Decide where it runs before deciding how it is built.
- Agree where it runsYour premises, the cloud or a closed network, settled before the architecture.
- Package for that placeContainers and installation steps that work offline as well as online.
- Make releases routineSmall, regular releases, delivered remotely where the network allows and carried in where it does not.
- Write it down as you goRelease notes and technical documentation with every version.
- Keep it currentOur engineers work with AI coding agents every day. Agents help with rebuilds and upgrades of long-lived platforms, and every change, written by a person or an agent, goes through the same review, tests and release process.
A typical engagement
Build and run, or take over and keep running.
- Model
- Build and run, or support and evolution of a platform you already have
- Team
- A product team that designs, builds, deploys and supports it
- Support
- Hours and response times as agreed in the contract
- After launch
- Regular releases and support from the same team
Next step
Tell us what you need.
Need a platform built and run?
Installed where you need it, then supported through its service life.
Contact usWho else will ask, and what they'll want
- IT securityCertification facts and written policies, on Trust.
- Your legal teamWhat we sign under Part-IS and NIS2, on Trust.
- ProcurementCompany details, certification and references, on Trust.