Any echelon, any authorized network
On October 20 the Marine Corps published a message directing organizations at all echelons to give authorized personnel their own Maven Smart System accounts. The enterprise license behind it took effect October 1. It covers every command and organization, reserves included, on any network a Marine is cleared to use. Before that, the license covered specific commands on the secret network only. Commands are to name an implementation lead, and an updated implementation plan is coming.
The numbers behind the decision are large. About 5,500 Marines used the system in the month before the service's August summit, and the Corps has moved its situation reports onto a Maven application. Across the department, a senior official said in September that users grew from about 50,000 in January to more than 100,000. The deputy secretary directed in March that it become a formal program of record, and an Army colonel was named program director in August with command-and-control integration as the charge.
Why the enterprise layer is winning
Maven earned this. The CSIS explainer describes a map-based interface that fuses drone video, synthetic aperture radar, ground radar, signals intelligence, and documents, built with Palantir as the prime software integrator. Central Command's 2024 deployment drew on 179 data sources. Drew Cukor, the program's first chief, has said that before these tools, analysts spent about 3 percent of their time analyzing data and 97 percent gathering it.
One platform across the Joint Staff, the combatant commands, and now every Marine echelon is a real gain. A staff that used to assemble the picture by hand gets it fused, and a decision that used to wait on a briefing can be made from a shared screen. That is good for the force, and it is good for anyone building beneath it, because a common enterprise layer gives the edge a place to send what it knows.
The picture starts below the network
A fused picture is only as good as what reaches it. Much of what a battalion knows begins with a patrol, an observation post, or a drone crew at the far end of the weakest link. When the link is up, their reports flow. When it is jammed, out of range, or switched off for emissions control, the team keeps observing and the reports wait. They wait in notebooks, on voice nets, and in memory, and they are entered later with the time, the source, and the sensor reconstructed from recollection.
The department sees this. The Marine summit's agenda included a working session on edge and tactical systems. The enterprise command-and-control office the Pentagon floated earlier this year would combine Maven Smart System with Edge Data Mesh in one program. Access at any echelon is the first step. Giving the lowest echelons something that works when the account cannot be reached is the next one.
What a disconnected team layer adds
First, data captured at the source with provenance. EdgeLance runs on the hardware the team carries and records each observation, detection, and report on the device at the moment it happens: who or what produced it, when, where, from which sensor, and, when a model was involved, which model. The entry is signed and written to the mission record. Nothing has to be reconstructed later.
Second, sync on reconnect through open standards. The team's devices share state over their own mesh while cut off. When a path to higher returns, EdgeLance is designed to exchange what the unit chooses to release via open standards such as Cursor on Target, the message format the TAK ecosystem already uses. An enterprise platform that accepts those standards receives reports that arrive late but complete, each with its original time and source.
Third, continuity when reachback is gone. The map, the tasks, and the AI run locally on open-weight models sized to the device, so the team keeps working through the outage. In internal testing, a node cut off from every peer kept its mission functions and reconciled when links returned.
What this is and is not
EdgeLance has no integration, partnership, or endorsement relationship with Palantir or with the Maven program, and this post claims none. It does not do what Maven does. It has no theater picture, no multi-intelligence fusion, and no targeting workflow at echelon. It is the layer for the stretch of ground where an enterprise account cannot be reached, and its job is to make sure that what happened there arrives upstream intact.
Enterprise platforms winning at echelon is the right outcome. The more people who rely on the fused picture, the more it matters that the data feeding it was captured cleanly at the source and can be traced to it. An earlier post covers how the two layers are funded, and another covers how detections reach TAK as standard messages. The platform page shows the team layer end to end, and the trust capabilities explain how the record is signed.