Data from where the platform cannot see
Most of what an enterprise platform fuses starts with a team on the ground. EdgeLance structures it at capture: typed observations, tracks, tasks, and reports instead of free text and screenshots sent later.
Enterprise platforms
The edge layer for the platforms that run the enterprise.
Enterprise C2 and data platforms have changed how headquarters see and decide. EdgeLance extends that reach to the team that is disconnected, and returns data the enterprise can trust.
Position
Complement, not replacement.
Platforms such as Palantir Maven Smart System, Anduril Lattice, and Shield AI Hivemind are becoming the standard at their layers: enterprise data and targeting, networked command and control, and vehicle autonomy. That is good for the force. A unit should not have to choose between them and the team at the edge.
EdgeLance does a different job. It runs the mission on the devices a small team carries, with no server in the middle, and it treats the enterprise platform as the destination for approved data and the source of approved tasks. Nothing in EdgeLance duplicates enterprise fusion, theater targeting, or flight autonomy.
Division of labor
Two layers, two jobs.
| Enterprise platform | EdgeLance | |
|---|---|---|
| Echelon | Corps, division, operations center | Company, platoon, squad, site |
| Connection | Assumed, with high bandwidth | Intermittent or absent |
| Compute | Cloud and data center | Phones, laptops, a forward server |
| Strength | Fusion across theaters, targeting workflows, analytics at scale | Capture at the source, local decisions, tasking the last asset |
| Record | System of record for the enterprise | Signed mission record on team devices, promoted upward by policy |
What the edge layer adds
Four things an enterprise platform gains.
Provenance on every record
Each item carries its source, time, confidence, device, and the person who approved it. The enterprise receives data it can weigh, not data it has to trust blind.
Continuity when the link drops
The team keeps its picture, its plan, and its tasks when reach-back is gone. On reconnect, the backlog syncs in priority order and the enterprise picture catches up without manual re-entry.
Reach to the last asset
An approved task from the enterprise plan becomes a signed directive to a specific drone, sensor, or team, with an acknowledgement and a result that flow back up.
Exchange
Open standards at the seam.
| Data | Direction | Interface | State |
|---|---|---|---|
| Tracks and positions | Up and down | Cursor on Target (CoT), TAK | Built |
| Tasks and acknowledgements | Down, results up | CoT tasking, signed directives over MQTT | Built |
| Full-motion video and metadata | Up | STANAG 4609, MISB ST 0601, RTSP | Built |
| Imagery and map products | Up and down | NITF 2.1, GeoPackage, GeoJSON, KML | Built |
| Sensor observations | Up | OGC SensorThings, MQTT | Built |
| Mission record and audit events | Up | Signed JSON export, Syslog/CEF | Built |
| Vendor platform APIs | Up and down | Vendor SDKs and data connectors | Planned, with vendor access |
"Built" means implemented and tested in EdgeLance against the open standard. It does not mean tested inside any vendor's environment. What leaves the team is set by the unit's release policy, and every promotion is recorded.
For platform teams
We would like to build the adapter with you.
If you run an enterprise platform and want a disconnected team layer that feeds it, we will bring a working EdgeLance node to an integration session and build against your SDK or data connector.
- Your data model stays the authority. EdgeLance maps to it.
- No shared runtime. Each side keeps working if the other is unreachable.
- Signed releases with a software bill of materials for your security review.
EdgeLance is an independent company. No partnership, integration, or endorsement by Palantir, Anduril, or Shield AI is stated or implied. Product names are trademarks of their owners.
Integration sessions
Bring the interface. We will bring the node.
A working session with your engineers on a real exchange: one track up, one task down, one outage in the middle.