The customer’s most common fear before adopting any command platform is lock-in. A system is bought for years, and a year later it turns out that the map module is outdated, the communications provider has changed its terms, and one cannot be replaced without the other. We design AGATA so that this scenario is impossible by architecture, not by promise.
A bus instead of a monolith
The platform is built on a single data bus and a common access rights model. The communications, maps, tasks, logistics, and control modules do not know about each other directly: they publish and read events on the bus according to an open specification. Any module can be replaced with an equivalent, including one from a third-party manufacturer, without stopping the others.
Each module exchanges data only through the bus.
What this gives the customer
Three things. The data belongs to the customer and is exported in open formats. Modules are connected as they become ready, and the customer does not pay for what they do not use. A technology partner connects their device or module without our involvement at every step: the specification is open, and the environment is shared.
Centralization is not hidden. It ensures quality and accountability, not lock-in to a supplier.
Darlein Defense representative
What it costs the team
Modularity is more expensive than a monolith at the start: a bus specification, event versioning, compatibility tests for every module. We consider this the right price. A platform that cannot be developed in parts becomes outdated as a whole.
The readiness of each module is reported separately and honestly. Nothing is shown as ready until it has passed testing.
