One platform, not a bundle of products
A single data model, a single session and a single place to configure. Modules are enabled; they are not integrated with one another.
How it is built
Frame ingestion
TCP, UDP and HTTP receivers per protocol family. Frames enter a queue and are processed asynchronously, so a reporting peak does not translate into lost positions.
Normalisation
A translator per protocol converts the manufacturer's frame into a single data model. That is what lets a rule or a report behave identically with any certified device.
Event engine
Rules are evaluated over the normalised stream, not over periodic database queries. A geofence entry is detected the moment the position that crosses it arrives.
Layered storage
Recent positions live in hot storage so the map and today's reports answer fast; history moves to cold storage without losing queryability.
Multi-tenant isolation
Each company has its logical space. Queries carry the tenancy filter at the data layer, not at presentation, so an interface bug cannot expose another tenant's data.
API and webhooks
The same service layer the interface uses exposes the public API. There is no functionality reachable from a screen that does not exist through the API.
Security and continuity
We do not use your operation's information for anything other than providing the service. You can export your full database at any time and, if you decide to leave, we hand it over in an open format with no penalty and no retention.
- Encryption in transit with TLS 1.2 or above on every endpoint
- Encryption at rest for the database and the backups
- Two-step authentication and sessions with configurable expiry
- Permissions by module and action, evaluated on the server
- Audit log of access, changes and commands sent
- Daily backups with periodic restore testing
- Redundant infrastructure across several availability zones
- 99.9% availability target measured monthly