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.

Data sovereignty means that the spatial intelligence you receive through Vangrid stays within the jurisdictional and organizational boundaries you define. Vangrid is designed from the ground up to support nation-state grade sovereignty requirements — not as an add-on, but as a core architectural property.

​
What data sovereignty means in Vangrid

Sovereignty in Vangrid operates at three levels: Node level — Edge nodes process data locally and transmit only derived, signed outputs. Raw sensor data never crosses jurisdictional boundaries. Network level — Your API key can be scoped to specific geographic regions. Queries outside your authorized regions are rejected, not silently filtered. API level — All data returned to your application is tagged with the originating region and epoch. You can audit exactly what entered your systems and from where.

​
Geographic access controls

When you onboard, Vangrid configures your API key with one or more authorized regions. A region is a named geographic boundary (e.g., a country, a state, or a custom polygon). 
# Query is scoped to your authorized region automatically
curl -X POST https://api.vangrid.io/v1/spatial/query \
  -H "Authorization: Bearer your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "aoi": {
      "type": "Polygon",
      "coordinates": [[[...coordinates...]]]
    }
  }'
If your AOI extends outside your authorized region, the API returns a 403 Forbidden with: 
{
  "error": "region_not_authorized",
  "message": "Your AOI intersects regions not authorized for this API key.",
  "unauthorized_regions": ["region_us_ca_north"]
}

​
Data residency

For enterprise and defense customers, Vangrid offers dedicated data rail configurations where:
  • Processing and aggregation occur within a specific country or jurisdiction
  • No query metadata or results are replicated outside the authorized region
  • Cryptographic provenance records are stored within the same jurisdictional boundary
Data residency configurations require a custom enterprise agreement. Contact hello@vangrid.io to discuss your requirements.

​
Compliance considerations

Vangrid’s architecture is designed to support compliance frameworks that require:
  • Data not leaving a defined geographic perimeter
  • Audit trails for all data access (available via your account dashboard)
  • Cryptographic proof that data has not been tampered with in transit
If you operate under specific regulatory requirements (e.g., ITAR, national data protection laws), share those requirements when you contact Vangrid. Sovereign deployment configurations are available for qualifying customers.