Gravital Cloud

Early access

GeoStream

Real-time location infrastructure, private by default and multi-tenant, to build into mobile apps and backends.

  • Instant StreamingLive streaming with guaranteed order
  • Strict opt-inLocation off by default and revocable at once
  • 1:1 · 1:N · N:NLive sessions for any topology
  • Multi-tenantPer-customer isolation and zero coordinates in logs

Service status

Checked from our server. Documentation, contracts and the developer console are on the GeoStream portal.

Operational Last check: 21:55

Open the GeoStream portal

Documentation

Everything you need to integrate GeoStream, organized by topic. The full documentation, the contracts and the developer console live on the GeoStream portal.

  • Get started

    From zero to your first location.

    • Create your account in the portal console with your email and a one-time code.
    • GeoStream is in early access: sign-up on the console may be limited for now.
    • Create an organization and a project.
    • Generate an API key with the minimum permissions you need; it is shown only once.

  • How it is consumed

    The journey of a location, end to end.

    • Your server creates a tracking session with the API key.
    • Your server issues a device token for the person or team sharing their location.
    • The device turns sharing on and sends up to 50 samples per batch; each sample gets its own result: accepted, duplicate, stale or rejected.
    • Your server reads each member's latest position when it needs it and closes the session when done.

  • Authentication and security

    Two credentials with different roles.

    • The API key is server to server: it creates sessions, issues tokens and reads positions. It never goes in an app.
    • The device token is the only one that can send locations; ingestion with an API key is rejected.
    • Operations that create resources accept an idempotency key: retrying returns the same result.
    • Errors follow the problem+json format with a stable code. There is no CORS: the API is used from servers.

  • Per-organization configuration

    Policies each customer tunes.

    • Optional rejection of simulated positions, off by default.
    • Optional position history with a configurable retention period. Without it, live positions are ephemeral and are not stored.
    • Several active API keys at once: create a new one and retire the old one without cutting service.

  • Deployment and operations

    How it is offered today.

    • GeoStream is offered as a hosted Gravital Cloud service, in early access.
    • Its health status is public: it appears above and you can check it on the portal.
    • There are no packages or installers to host it yourself yet.

  • Versions and downloads

    What is published today.

    • API contract: OpenAPI v1, still a draft, published on the portal.
    • Service version: no public version yet.
    • Packages, builds and installers: not published yet.
    • SDKs for apps: not published yet.
Read the full documentation on the portal

What it does

  • Live sessions one-to-one, one-to-many and many-to-many.
  • Private by default: location sharing starts off and only the person can turn it on.
  • High-efficiency streaming with guaranteed ordering and minimal mobile data usage.
  • Instant revocation: whoever loses permission stops receiving at once.
  • Strict per-customer isolation, with no coordinates or tokens in logs.
  • Ready for open maps: positions are shown on OpenStreetMap, with no dependency on proprietary map providers.

How it works under the hood

See how GeoStream ingests and distributes live coordinates while protecting each person's privacy.

1. Explicit consent and session creationPrivacy by default No device transmits its position until the person voluntarily turns sharing on.
  1. Your backend creates an isolated session inside its tenant space via the control REST API.
  2. The mobile device receives a scoped token, but coordinate emission stays off until the person explicitly enables it.
  3. Publishers and subscribers are defined for one-to-one, one-to-many or many-to-many topologies.
2. Real-time streaming and distributionSynchronization · Mobile Optimized Real-time distribution with guaranteed ordering and minimal mobile data usage.
  1. Positions arrive over the network optimized and compressed to preserve mobile data.
  2. The engine validates sequence order, drops duplicates, and orders updates deterministically.
  3. Authorized subscribers receive live updates immediately, while coordinates and tokens are never written to log files.
3. Hot revocation and clean teardownInstant cutoff Access control over who can view a location is enforced live on active connections.
  1. When a delivery finishes or the user turns sharing off, permission is revoked on the server.
  2. The engine immediately halts emission to any subscriber that lost authorization without waiting for a reconnect.
  3. Session resources are released while preserving strict per-customer isolation.

Use cases

  • Last-mile delivery tracking

    In GravitalPay, buyers watch the courier live on OpenStreetMap only while their order is on the way, with the position rounded to protect privacy.

  • Fleet and field crew coordination

    Monitor active field technicians or couriers on a central dispatch view using one-to-many sessions.

  • Temporary peer location sharing

    Embed time-bounded live location sessions into mobile apps without building streaming infrastructure from scratch.

Status

  • Live status, documentation, contracts and the developer console are on the GeoStream portal.

Explore the rest of the Gravital Cloud ecosystem

See all products