Web console
The administrative surface: boards, register, logbook periods, reports, settings, super-admin controls.
PLATFORMPlatform
One core. Four surfaces. No integration tax.
Vectis is a single multi-tenant application, not a suite of acquisitions. Bookings, the register, logbooks, telematics events and AI all read and write the same tenant-scoped record, so there is no nightly sync to reconcile and no field that means two different things in two products.
The platform at a glance
Development fixture figures, not approved for publication.
01How data moves
From an OBD port to an FBT assessment
One path, fully automatic. Each stage is independently observable, and each can be replayed without touching the stages around it.
| # | Stage | What happens |
|---|---|---|
| 1 | Device check-in | The in-vehicle device opens an encrypted session and streams position, ignition, movement, voltage, accelerometer and signal data. |
| 2 | Event persistence | Records are validated, decoded and stored against the vehicle, then queued for the stages that follow. |
| 3 | Trip detection | Ignition-off plus a debounce window closes the trip, guarding against the trip-splitting that modem power-saving can otherwise cause. |
| 4 | Road enrichment | The finished trip is snapped to road geometry, matched to per-segment speed limits and analysed for compliance severity. |
| 5 | Journey creation | The trip becomes a logbook journey awaiting classification as business, private or home-to-work, on web or in the driver's app. |
| 6 | Assessment | Classified journeys roll into business-use percentage, then into statutory, operating-cost and mileage-rate assessments for the FBT year. |
02Surfaces
Four ways in, one set of rules
Driver apps
iOS and Android. Book, check out, capture the handover, start and classify journeys.
API access
The same capabilities the apps use, with tenant scoping and entitlement checks applied server-side.
Partner integrations
Marketplace applications from partners, each installed with its own scoped credentials and granted data access.
03Identity & integration
It has to fit the systems you already run
Enterprise identity is table stakes: five supported providers, automated directory provisioning, just-in-time user creation, group-to-role mapping, break-glass accounts and enforcement modes you can stage rather than flip.
- Microsoft Entra ID, Okta, Auth0, Google Workspace, generic OIDC
Email-domain routing to your identity provider, discovery-endpoint configuration and role mapping from group claims.
- Directory provisioning
Users and groups created, updated and deactivated from your directory over SCIM 2.0, with an auditable attribute mapping.
- Partner marketplace
Install integrations from the Vectis marketplace, grant each one only the data scopes it needs, and receive webhook events.
ProviderStatus
Microsoft Entra IDConnected
Domain example-council.govt.nzRouted
Directory provisioningActive · 214 users
EnforcementSSO required
Break-glass accounts2 · audited
ROLE MAPPING
FLEET-ADMINS → Fleet Administrator · FINANCE-FBT → Finance Administrator · default → Driver
Bring your technical questions.
Walkthroughs cover tenancy, data handling, entitlements, identity and integration. Detailed technical documentation goes out on request, once we know who we are talking to.