Fleet governance, safety, compliance and reporting, without a hardware rip-and-replace.
Fleet Shield applies JEGASEC's operational-data philosophy to fragmented fleet and telematics environments: it consolidates operational data from compatible telematics systems into a secure governance, safety, compliance and reporting layer, without requiring organisations to replace their entire hardware environment. It is a secondary product; JEGASEC's flagship is Continuity.
What Fleet Shield does
Fleet Shield is a vendor-neutral, secure fleet-telematics middleware platform built for local councils, utilities, contractors and other organisations accountable for how their vehicles are used, particularly those running mixed or legacy fleet environments. Fleet Shield is being developed to consolidate data from compatible telematics systems through validated API, secure file-based and custom integrations, and turn that feed into the safety, compliance, and emissions reporting these organisations are accountable for, in one place instead of stitched together across spreadsheets and separate vendor tools. The goal is gradual deployment alongside what's already running, not a disruptive, fleet-wide replacement. See "Integration readiness" and the "Product validation roadmap" below for exactly what's built today versus what's still in development.
- Vendor-neutral ingestion architecture under development: see the validation roadmap below
- Fleet mapping, status and alert workflows
- Driver-behaviour alerts: harsh braking, acceleration, speeding, idling
- Geofencing and restricted-zone compliance
- Emissions & energy reporting across diesel, petrol, and EV fleets
- Per-vehicle safety scoring
- Registration and service-due compliance tracking
- Fleet utilisation and operational-efficiency reporting
- Auditable decision trails for safety and compliance reviews
- Reduced dependence on a single telematics vendor
Integration readiness
No public integrations have yet been listed. Integrations will be published after technical validation. If you run a specific telematics system today, tell us about it and we'll confirm what's realistic for your environment before any commitment is made.
Integration methods we realistically plan to support:
- REST API: Direct, authenticated API integration for telematics platforms that expose one.
- Secure file import: Structured file-based import (e.g. CSV/JSON export) for systems without a live API. (internal engineering prototype, exercised against synthetic test data only; not yet available to customers or publicly validated)
- Scheduled data import: Periodic batch import on a set schedule, for lower-frequency reporting needs.
- Custom connector: Purpose-built connector for a specific provider or legacy system, scoped per engagement.
- Approved manual upload: Manual, validated upload for low-volume or one-off data sources.
Product validation roadmap
An honest picture of what's actually working today, what's being actively validated, and what's still ahead, rather than presenting an early-stage product as more mature than it is.
- Simulated fleet dashboard with live map, vehicle list and status
- Vehicle map and status workflow
- Driver-behaviour alert demonstration: harsh braking, acceleration, speeding, idling, geofencing
- Reporting prototype: emissions, utilisation, per-vehicle summary
- Account and organisational model: multi-tenant orgs, MFA-protected admin login
- Controlled product demonstrations for prospective partners
- Secure CSV telemetry import: internal prototype
- Field validation and normalisation
- Duplicate-record detection
- Import error reporting
- First authorised representative dataset: not yet obtained
- Pilot deployment process: documented, not yet run with a real partner
- First provider-specific connector: not yet started
- Published, validated telematics integrations
- Automated customer onboarding
- Unrestricted self-service signup
- Production service commitments (uptime/SLA)
- Expanded emissions and compliance modules
- Enterprise support tiers
JEGASEC is seeking fleet operators and technology partners to validate telemetry ingestion, reporting workflows and controlled pilot deployment. We don't yet have confirmed design partners. If you'd like to be one of the first, get in touch.
Commercial structure
Fleet Shield is priced per vehicle for smaller, straightforward fleets, and quoted individually for larger, integration-heavy or government deployments so the commercial model reflects the actual scope of work. Fleet Shield is currently available through controlled demonstrations, design partnerships and approved pilot deployments, not open self-service signup.
Per-vehicle pricing for live map, alerts, compliance and reporting on straightforward fleets, accessed via an approved demonstration or pilot during the current controlled beta.
Based on fleet size, data sources and system complexity.
Available by quotation for organisational deployments.
Pilot, annual subscription, invoicing and purchase-order arrangements available.
Request an organisational quotePremium options may include custom integrations, implementation support, advanced reporting, migration assistance, priority support and tailored governance workflows, scoped per engagement.
See Fleet Shield in context
The clearest way to evaluate Fleet Shield is to see it against your own fleet, telematics environment and reporting requirements. We'll walk through the platform, discuss what a pilot or integration would realistically involve for your organisation, and answer questions about deployment, data handling and commercial terms directly.