Velantra
The Velantra platform

Five layers. One continuous system.

From the NomadStick installed at registration to the government operator console reviewing live incidents — every layer of the Velantra platform is designed to work together, and to keep working when connectivity fails.

01
NomadStick
In-vehicle hardware

A compact device installed in the vehicle at registration. The NomadStick collects GPS telemetry, runs speed and geo-alert logic locally, delivers bilingual TTS audio alerts to the driver, and queues all trip data for upload. It operates independently of cloud connectivity.

Edge processing — no cloud required for alertsBilingual EN/FR audio (driver-selectable)GPS telemetry collectionOffline queueing — nothing lost without signalSchool zone and geo-alert awareness
02
Edge intelligence
On-device processing

The NomadStick makes real-time decisions without waiting for a cloud response. Speed limit enforcement, geo-alert triggering, compliance state awareness, and violation classification all happen on the device. When connectivity returns, the structured evidence record synchronises intact.

Local speed-limit lookup and enforcementBanded overspeed logic: warning, violation, stunt tiersSchool zone schedule-aware triggeringCompliance state evaluation on deviceGNSS-aware enforcement pause and resume
03
Cloud ingest and storage
GCP Firestore — Montréal

All trips, events, violations, and compliance data flow into a structured Firestore backend hosted on Google Cloud in Montréal. Canadian data stays in Canada. The backend receives queued payloads from NomadStick devices, runs risk scoring, maintains compliance state, and serves structured data to operator and driver surfaces.

Google Cloud Firestore — northamerica-northeast1Canadian data residency — Montréal regionTrip, violation, and event structured storageRisk scoring engine (DN Speeding, Hard Accel, High RPM)Compliance state tracking across all registered vehicles
04
Operator dashboard
Government operator console

Authorised government operators see a real-time view of violations, compliance alerts, device health, and trip evidence across every vehicle in their jurisdiction. The dashboard surfaces structured incident records, not raw telemetry — designed for triage, review, and escalation.

Live violations map and incident tableCompliance driving alertsDevice health and silent device monitoringDriver and vehicle profile linkageRisk scoring and classification
05
Driver portal
Personal driver view

Each driver assigned a NomadStick has access to their own personal portal — trip history, violation evidence, compliance reminders, and risk awareness. Drivers see only their own data. The portal is protective in tone: the blackbox record is as much the driver's defence as it is an operator's evidence.

Personal trip history and route visualisationViolation evidence with location and timestampCompliance status and expiry remindersRisk score and breakdownBilingual — EN/FR
How data moves

From vehicle to dashboard in four steps.

01

NomadStick records

Trip data, speed events, geo-alerts, and compliance state are captured continuously on the device.

02

Edge processes

Violations are classified, alerts are triggered, and evidence is structured — all without cloud connectivity.

03

Cloud receives

On reconnect, all queued data uploads to Firestore intact. No gaps, no overwrites.

04

Operators review

Structured incidents, compliance alerts, and trip evidence appear in the dashboard.

Canadian data residency

GCP northamerica-northeast1, Montréal. Data does not leave Canada.

Offline-first architecture

The NomadStick records and enforces without connectivity. Evidence is never dependent on signal.

Tamper-evident records

Evidence is structured and signed at the edge. It cannot be altered after the fact.

Ready to see the platform in action?