Where the reviewed products stand
Compare documented control across the named products and routes. Open a review for its plan, region and agreement (this is a selected sample).
0–10 on both axes · Higher and further right means more documented control
Axes average three dimensions each: access, third-party access and exit horizontally; action, continuity and business logic vertically. Fixed 0–10 scale, midlines at 5 (overall grades use separate weights). * Some evidence is unresolved. Marker colors identify companies, not score bands. How to read the map ↗
Permute is included as a reference (it owns this site and is a publisher self-assessment). Its score is excluded from sample averages. Read the Permute review ↗
Vehicle telemetry, driver records and operational mutations have separate permissions and retention. Data access does not establish authority to control equipment or recover every historical observation.
Compare the six dimensions
| Overall control | |
|---|---|
| Data access | |
| Third-party accessibility | |
| External action | |
| Continuity | |
| Data exit | |
| Business logic and customization | |
Product scopes, dates & reviews
Samsara
Fleet management · Checked 2026-10-16
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Read findings and sources ↗Motive
Fleet management · Checked 2026-10-17
Motive Fleet Management / current vehicle master records through v1 Vehicles and an authorized OAuth application, with vehicle-upsert webhooks. Location history, video, ELD/HOS records, remote vehicle controls and freight-visibility products require separate contracts.
Read findings and sources ↗| Customer control | Samsara ↗ | Motive ↗ | Geotab ↗ | Permute ↗ |
|---|---|---|---|---|
| Category | Fleet management | Fleet management | Fleet management | Databases and data platforms |
| Overall control | ||||
| Data access | ||||
| Third-party accessibility | ||||
| External action | ||||
| Continuity | ||||
| Data exit | ||||
| Business logic and customization | ||||
| Assessment scope | Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate. | Motive Fleet Management / current vehicle master records through v1 Vehicles and an authorized OAuth application, with vehicle-upsert webhooks. Location history, video, ELD/HOS records, remote vehicle controls and freight-visibility products require separate contracts. | MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts. | Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed. |
| Assessment checked | 2026-10-16 | 2026-10-17 | 2026-10-17 | 2026-10-12 |
| Read the findings | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ | Detailed review ↗ |
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
Who can connect?
Yes No- Unknown
| Connection method | Customer credentials | Integrator credentials | Provider approval required |
|---|---|---|---|
| Samsara ↗ | |||
| Direct customer fleet API token ↗ | |||
| Marketplace OAuth integration ↗ | |||
| Motive ↗ | |||
| Approved third-party OAuth application ↗ | |||
| Geotab ↗ | |||
| Customer database service-account session ↗ | |||
| Permute ↗ | |||
| Scoped customer REST / TypeScript SDK ↗ | |||
| Permissioned end-user MCP ↗ | |||
A check means the column applies to that route (customer credentials can still require provider approval). Report exports use the customer account without separate API credentials. Open a connection method for its authentication, requirements and last review date.
What each review covers
Samsara ↗
Samsara supports direct customer API tokens and OAuth integrations. Vehicle master records have cursor pagination and an updated-time filter; this review does not equate them with complete telematics history.
Samsara fleet vehicle master-data listing and address create/update APIs, direct customer tokens or OAuth; telemetry/history and fleet-product entitlements are separate.
Motive ↗
Motive exposes vehicle records, creation and updates, with timestamp filtering and upsert notifications. A customer token does not remove the written-consent requirement for distributing a third-party application.
Motive Fleet Management / current vehicle master records through v1 Vehicles and an authorized OAuth application, with vehicle-upsert webhooks. Location history, video, ELD/HOS records, remote vehicle controls and freight-visibility products require separate contracts.
Geotab ↗
MyGeotab exposes customer-authorized records and version-based feeds. Durable checkpoints support recovery only from retained data; default purge settings and full-fleet authorization requirements constrain that recovery.
MyGeotab SDK JSON-RPC / vehicle Device and GPS LogRecord reads, version-based GetFeed synchronization, and Zone geofence create/update. Other telemetry, calculated trips, partner MyAdmin functions, Data Connector and MCP have separate contracts.
Permute ↗
Scoped APIs expose SQL reads, managed records and customer-authored operation code. Customer-built apps are supported, while complete workspace recovery, outbound CDC and minimum-plan access terms remain unresolved.
Permute hosted workspaces / scoped REST and TypeScript SDK access to connected query sources, file datasets, managed database records, operation code and custom apps. Signed enterprise contracts and upstream vendor rights remain separate; no live tenant migration or reliability test was performed.