UNCLASSIFIED
UNCLASSIFIED
SHIELD/ATLAS  /  NATO DIANA / Allied / Coalition
NATO DIANA · NATO C-UAS CoE · Allied / Partner-Nation MoDs

Same chassis. STANAG-aligned messaging. No separate fork.

SHIELD | ATLAS lines up with the three things NATO DIANA, the NATO Counter-UAS Centre of Excellence, and partner-nation MoDs keep asking industry to deliver: dual-use deep tech, deployable at scale, and multi-national interoperable. The platform that serves a US Army brigade is the same platform that serves an allied formation — same code, same adapters, different cookies.

Civilian emergency management and military C2 from one chassis. DDIL-native by architecture, not feature flag. $93/node on commodity hardware. UNCLASSIFIED ceiling today — classified pathways via standard cooperative-R&D vehicles.

DIANA's three asks → ATLAS architecture

Ask 1 · Dual-use deep tech

One chassis, two missions

Civilian fire/flood/MCI response and military C2 on the same code. Not a defense product with a civil mode bolted on, not a civil platform with mil pretensions — one product, two doors, one operations log.

Ask 2 · Deployable at scale

Commodity hardware, $93/node

Designed for the contested, disconnected, low-bandwidth conditions allied units face on the eastern flank, in the Sahel, and across the Indo-Pacific. DDIL-native architecture, not a fallback mode.

Ask 3 · Multi-national interop

STANAG-aligned, not US-only

Nine adapters including Cursor-on-Target, Link 16-compatible VMF, AFATDS, TITAN. The same translation layers that speak to US C2 spines align with NATO common operating picture and partner-nation systems.

Easy integration — three steps, real endpoints

Every endpoint below is live on this server. Hit them. The data is real ADS-B + sensor fusion, UNCLASSIFIED, no auth required for the public picture.

Step 1 · Read the manifest

What's available, what version, what envelope

One JSON document describes the partner-facing API surface, schema versions, and supported translation protocols. Stable contract.

curl https://secureassure.app/api/partners/manifest
Step 2 · Subscribe to the live picture

Server-Sent Events — or pull, your choice

Same envelope whether you stream or poll. Works in any HTTP-capable stack — no proprietary client, no SDK lock-in.

curl -N https://secureassure.app/api/live-feed/stream     # push (SSE)
curl    https://secureassure.app/api/live-feed/tracks     # pull (snapshot)
Step 3 · Translate to your C2 protocol

CoT / Link 16-compatible VMF / GeoJSON — pre-translated, no work on your side

Don't want to write a translator? We've already done it. Same air picture, the wire format your stack speaks.

curl https://secureassure.app/api/live-feed/tracks/cot       # Cursor-on-Target XML
curl https://secureassure.app/api/live-feed/tracks/link16    # Link 16-compatible VMF
curl https://secureassure.app/api/live-feed/tracks/vmf       # raw VMF
curl https://secureassure.app/api/live-feed/tracks/geojson   # GeoJSON FeatureCollection

Full WebXR / Unity / browser consumer sample (drop-in JavaScript): /api/partners/sample-client.js. JSON Schema for the track envelope (versioned): /api/partners/schema.

Adapter compatibility — what speaks what

ProtocolDirectionStatusEndpoint / notes
Cursor-on-Target (CoT) Out Live /api/live-feed/tracks/cot · XML, TAK-native
VMF / Link 16-compatible Out Live /api/live-feed/tracks/link16, /api/live-feed/tracks/vmf
GeoJSON Out Live /api/live-feed/tracks/geojson · web mapping, Cesium, MapLibre, ArcGIS
Server-Sent Events (push) Out Live /api/live-feed/stream · native browser, native Node, Unity via polyfill
REST snapshot Out Live /api/live-feed/tracks · works anywhere HTTP works
AFATDS / TITAN Out Alignment intent Translation layer present in live-sensor-feed.ts; certification path is FMS/cooperative-R&D vehicle
NATO Friendly Force Information (FFI) / NFFI Out Roadmap VMF and CoT are the present interop spines; NFFI gateway scoped, not yet shipped
NATO SECRET / mission-network ATO Roadmap Not held today; UNCLASSIFIED ceiling. Path is cooperative R&D or DIANA consortium with a host-nation accreditation sponsor

Engagement vehicle — honest reality

What we are: ISS LLC (DBA SecureAssure), US-domestic SDVOSB-pending prime. Dr. Terry Flood, CWO 131A (Ret) — Army targeting / EW / fires / intel. CAGE 9VKK3, UEI C7YDV3P8EHL7. Pflugerville, Texas.

What that means for allied engagement: three viable pathways —

What we do not pretend to be: we do not hold NATO SECRET ATO. Coalition operational use today is the UNCLASSIFIED ceiling. We won't bid that we have something we don't have.

Why this matters now

Counter-UAS is a NATO-wide priority and the NATO C-UAS Centre of Excellence in Souda Bay is the locus. The same Soldier-as-Sensor acoustic / RF / radar fusion that the US C5ISR Center and Army SBIR (A23-010) are pursuing is what allied formations on the eastern flank and southern flank are asking for — at a price that makes deploying it across a battalion or a border post realistic.

The platform exists, runs, and is reachable from any standards-compliant client today. We are not asking for funding to build — we are asking for the partner-nation pilot, the DIANA Challenge slot, the cooperative-R&D vehicle to scale.

Next step for allied evaluators

Hit the endpoints above with curl from your own network — the answer comes back in seconds. Then reach out and we'll book a live walkthrough on your timezone.

Contact partners@secureassure.app Full evaluation surface One-page brief

Doctrinal references this page is grounded in: NATO DIANA charter (2021); NATO C-UAS Centre of Excellence mission statement; STANAG 5527 (CoT alignment); STANAG 5516 (Link 16); ADP 3-0 (Operations); JP 3-30 (Joint Air Operations). Pages cited live in docs/agent-memory/topics/partners.md and docs/agent-memory/topics/grants.md.

PRESENCE
⚠ SANDBOX / TRAINING MODE — Live read-only data. Write commands are inhibited (train as you fight, missile button safed).