Technology
Before you sign, you want to know three things: where your data goes, what each call costs and how you leave.
These three pages are a data sheet, not a brochure. They are written for whoever is evaluating the product from IT or technical management, and every answer comes with enough detail to check it.
The risks, one by one
What worries you about a new supplier, and the short answer.
| What you fear | What you get |
|---|---|
| A variable cost that grows with your usage | Routing (Valhalla), optimisation (VROOM), the base map (Planetiler) and the tile server run inside the installation. No per-call cost for map APIs and no third-party API key. |
| Your staff's positions in a third party's hands | Positions and calculated routes are not sent to anyone, because there is no one to send them to. Staff telemetry is purged automatically after 60 days. |
| Permissions nobody controls | 52 permission codes resolved in four layers, three separate identities and isolation per organisation. |
| Not being able to take your data with you | Full asynchronous export of 22 resources, in NDJSON, with a manifest and the SHA-256 hash of every file. |
| An API nobody documents | Swagger and ReDoc generated from the code and accessible with no key. The limits of each resource are declared in the API itself. |
What isn't there is in writing too: the API does not create or modify work orders and does not emit outbound events. You'll find that on the API page, not in the small print.
Last updated:
And if you prefer the full detail, it's published.
All 25 chapters of the functional document, openly available, plus the API reference with no key required. Your IT team can review them before the evaluation session.