Before every release
Every change is reviewed and tested before it is released, whether a person or an agent wrote it.
How we work
We build platforms, join primes' teams and take over existing systems.
Agencies and authorities hire us for platforms that stay in service for a decade or more; air traffic management (ATM) primes, for engineers who already know their domain; owners of existing systems, to keep them running and extend them.
01 / Build and run
We build a platform, then maintain and support it through its service life.
- Who it suits
- EU agencies and international bodies, national authorities and investigation bodies that need a platform to stay in service for a decade or more.
- How it starts
- A first conversation, then an RFI or a tender. The work usually runs under a framework contract.
- What we commit to
- The team that builds the platform maintains and supports it. We deploy it where you need it: on your premises, in the cloud, or on a network with no outside connection.
02 / Team extension
Our engineers inside your team.
- Who it suits
- ATM primes and OEMs that need engineers on their codebase who already know air traffic control software.
- How it starts
- A call about the codebase and the roles. Screening comes first, and CVs are shared under NDA.
- What we commit to
- Engineers who already know air traffic management software, working to your process, in your codebase.
03 / Support and evolution
Taking over a platform someone else built.
- Who it suits
- Owners of a system that has to keep running after the original team has moved on.
- How it starts
- A conversation about the platform, then a look at the code and at how it is deployed today.
- What we commit to
- Service continues while we take the platform over; then we extend it in small, tested releases.
04 / Team shape
Small teams that own a platform end to end.
One team per platform.
The same team designs, builds, deploys and supports the platform, so the people answering a support call know why the code is the way it is.
Our engineers work with AI coding agents every day. Agents help with rebuilds and upgrades of long-lived platforms, and what they write goes through the same review, tests and release process as any other change.
05 / Delivery practice
How a change reaches a release.
Small and frequent
TOKAI is updated every few weeks, and EMCIP had 88 releases after going live.
Security
We are certified to ISO/IEC 27001:2022 for software development, and written policies cover supply chain, patching, incident reporting, staff screening and segregation of duties.
The details, on Trust →06 / Support after release
Support after release.
- Who answers
- An engineer from the team that maintains the platform.
- How fast
- Response times by severity, set in each contract.
- Where it runs
- On your premises with remote updates, in the cloud, or on a closed network.
- What changes next
- Agreed with the users; on TOKAI, through its change control board and user group.
The local installation at MUAC went very smooth, and consecutive software updates are performed remotely and very quickly.
07 / Next step
Pick the one that fits.
We need a platform built and run for yearsEmail us about build and run →
We need ATM engineers in our teamEmail us about team extension →
We need to qualify you as a supplierSupplier qualification →
Who else will ask, and what they'll want
- ProcurementCompany details, certification and references, on Trust.
- IT securityCertification facts and written policies, on Trust.
- Your engineering leadThe systems behind each model, in Work.