Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vangrid.io/llms.txt

Use this file to discover all available pages before exploring further.

Defense and intelligence applications demand more than accurate spatial data — they require provable data provenance, strict control over where data resides and transits, and verifiable chain of custody from sensor to analyst. Vangrid is built for exactly these requirements. Every observation is cryptographically signed at the edge before transmission, data sovereignty boundaries are enforced at the infrastructure level, and raw sensor streams never leave the originating node. The result is a spatial intelligence platform you can deploy in mission-critical environments with confidence that the data you receive is authentic and has not been intercepted or tampered with.

​
Defense-tier capabilities

Cryptographic provenance

Every data point carries a provenance hash encoding node identity, capture timestamp, and observation content. Any alteration to the data invalidates the hash — giving you tamper-evident proof of integrity from sensor to delivery.

Data sovereignty controls

Queries are routed exclusively through nodes within your designated sovereignty boundary. Data does not transit infrastructure outside that boundary unless you explicitly authorize cross-region access.

Edge-computed privacy

Raw sensor streams — imagery, depth data, point clouds — are processed on-device and never transmitted. Only derived spatial features leave the node, enforcing privacy at the hardware layer, not as a software policy.

Access-controlled spatial queries

Fine-grained access controls let you restrict which users, systems, or API keys can query specific geographic zones, data tiers, or provenance-verified datasets.

​
Defense use cases

​
Situational awareness

Vangrid streams continuous ground truth over areas of operational interest, giving analysts and command systems a live, corroborated spatial picture without requiring forward-deployed sensor infrastructure. Because observations are cross-validated by multiple independent edge nodes, the ground_truth_score gives you a quantitative measure of observational confidence for any given area.

​
Border and perimeter monitoring

Define a polygon AOI along a border or perimeter and subscribe to a streaming feed. Vangrid delivers observations as they arrive from edge nodes in the zone, so your monitoring systems receive updates in real time rather than on scheduled imagery cycles.

​
Critical zone surveillance

Establish spatial subscriptions for sensitive zones — installation perimeters, airspace corridors, maritime exclusion areas — and configure alert thresholds based on ground_truth_score and observation type. High-confidence anomalies are surfaced immediately; low-confidence signals are flagged for analyst review rather than silently dropped.

​
Data sovereignty: how residency and access controls work

When you provision a defense-tier Vangrid account, you specify one or more sovereign regions. Vangrid enforces three guarantees within those regions:
1

In-region routing

Your API queries are routed only to edge nodes within your designated sovereign region. No observation data transits nodes or infrastructure outside that boundary.
2

Encrypted transit

All data moving from edge nodes to the Vangrid aggregation layer and from the aggregation layer to your endpoint is encrypted in transit using TLS 1.3. The provenance hash is computed before encryption and verified after decryption, so any interception or modification is detectable.
3

Audit-ready provenance

Every response includes a provenance_hash you can store alongside the response data. At any point you can re-verify the hash to confirm the data has not been altered since delivery. This creates an auditable record of every observation your systems consumed.
Defense-tier access, sovereign region configuration, and advanced access controls are available through a dedicated enterprise agreement. Contact hello@vangrid.io to discuss your requirements and initiate onboarding.

​
Verifying provenance on a spatial response

After receiving a spatial query response, verify its provenance_hash to confirm the payload has not been altered. The following example shows how to perform this verification. 
# Step 1: submit a spatial query and capture the response
curl -X POST https://api.vangrid.io/v1/spatial/query \
  -H "Authorization: Bearer $VANGRID_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "aoi": {
      "type": "Polygon",
      "coordinates": [[
        [34.7818, 32.0853],
        [34.7918, 32.0853],
        [34.7918, 32.0953],
        [34.7818, 32.0953],
        [34.7818, 32.0853]
      ]]
    },
    "max_age_seconds": 60
  }' \
  -o response.json

# Step 2: verify the provenance hash via the verification endpoint
curl -X POST https://api.vangrid.io/v1/provenance/verify \
  -H "Authorization: Bearer $VANGRID_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{
    \"query_id\": \"$(jq -r .query_id response.json)\",
    \"provenance_hash\": \"$(jq -r .provenance_hash response.json)\"
  }"
A successful verification response looks like this: 
{
  "query_id": "q_5a3f1c9d2e7b4806",
  "provenance_hash": "sha256:9e3b1c7f4a2d8605bf1e4d7c2a8f3b9e1c4d7a2f",
  "verified": true,
  "node_count": 214,
  "sovereign_region": "eu-west-1",
  "captured_at": "2026-05-22T11:47:22.304Z"
}
If verified is false, treat the response as untrusted and do not use it in any downstream decision-making. Log the failed verification and contact hello@vangrid.io if you observe repeated failures.

​
Relevant concepts

Cryptographic provenance

How provenance hashes are constructed, what they encode, and how to use them for audit and verification.

Data sovereignty

How sovereign regions work, how routing is enforced, and how to configure access boundaries for your account.

Edge-computed privacy

Why raw sensor streams never leave the node and what this means for operating in sensitive environments.