The first UK fleet platform that refuses to recommend dangerous shortcuts.

When your driver finishes ahead of schedule, every other system says "pack 2-3 more stops." Ours doesn't. Not when speeding events fire. Not when fatigue alerts trigger. Mekavo seals each record at the moment of the act so when the DVSA, an insurer, or a court asks the question — your answer is forensic. Built for the UK trade fleet, light commercial, courier, construction crew, and auto-shop fleet.

Start Free — 3 Vehicles Included Sign In
Free for 3 vehicles No credit card Data protected Available across the UK

Mekavo AI is explicitly forbidden from telling you to pressure your driver.

Most fleet AI products will recommend densifying your routes when a driver finishes early — even when the underlying reason is speeding. Some platforms sell that recommendation as their headline feature.

Mekavo's risk-aware AI is hard-coded to refuse it. When telemetry shows a speeding pattern, a fatigue alert, or aggressive driving, our system is structurally prevented from recommending more stops, route densification, or shift extensions — regardless of what the variance numbers superficially support.

What our AI will recommend instead:

  • Coaching, when a speeding pattern emerges.
  • Mandatory rest, when fatigue alerts fire.
  • Re-timing the plan at the planning stage, when stops consistently finish too early.
  • Recognising the driver, when a week is clean.

It will never pressure the driver, even when the manager wants it to. That's the positioning. We sell to operators who want a serious safety platform — not a way to extract more shifts.

Compare side by side

What other fleet AI says What Mekavo's AI says
"Driver is 12 min ahead of schedule — consider adding 2-3 more stops." "Driver is 12 min ahead BUT had 4 speeding events this week. Do not add stops — coach him. Insurance review recommended."
Optimises for stops-per-shift. Optimises for safe completion and evidence integrity.
Pressures the driver to absorb the slack. Investigates whether the plan is the problem.

"But phones aren't industrial equipment."

Apple's iPhone 14 and Google's Pixel 6 (both 2022 and newer) ship dual-frequency GNSS receivers using the L1 and L5 satellite bands — 1 to 3 metre GPS accuracy outdoors, indistinguishable from the GPS units inside purpose-built fleet trackers.

The accelerometer measures ±16 g at 0.001 g resolution. The gyroscope handles ±2000°/s with 0.06°/s noise. The barometer reads pressure changes equivalent to 50 cm of altitude. The crash-detection algorithm is accurate enough that Apple uses it to call emergency services automatically on the driver's behalf.

Strava analyses your running gait from these same sensors. Garmin measures cycling cadence. Apple Watch detects atrial fibrillation. Mekavo uses them to detect harsh braking, fatigue jitter, and phone-in-hand distraction — and to log evidence at GPS precision the courts already accept.

The hardware vendors who'll sell you a $400 ELD will tell you phones can't do this. They have $400 per truck reasons to say so.

The sensor stack in every modern phone

Sensor Modern phone capability Mekavo uses it for
Dual-frequency GPS (L1 + L5) 1-3 m accuracy outdoors Shift trail, geofence arrival, sealed evidence
Accelerometer ±16 g, 0.001 g resolution, 200-400 Hz Harsh-brake and harsh-accel detection, crash detection
Gyroscope ±2000°/s, 0.06°/s noise Cornering, fatigue jitter, lane changes
Magnetometer ±50 µT, 1 µT resolution Compass heading, parking orientation
Barometer 0.06 hPa = 50 cm altitude Multi-storey carpark detection, hill grade
Camera + EXIF 12-50 MP, 4K30 video, GPS-bound Proof-of-delivery, dashcam clips, AI part scan
Microphone -38 dB sensitivity, 16 kHz Voice copilot, transcription, audio Alibi capture
Cellular + Wi-Fi positioning Sub-50 m fallback Indoor / urban-canyon backup
NFC 4 cm range, 424 kbps Driver tap-in, maintenance check-in
Proximity sensor ~5 cm Phone-in-hand vs phone-mounted detection
Crash detection algorithm Industry-standard, Apple-certified Confirms accident logging

"But phones run out of battery."

So do ELDs. The difference is how easily you recover.

  • Cigarette-socket USB-C charger — under $5, every truck has the socket
  • Wireless charging mount — under $25, charges while driving
  • 20,000 mAh power bank — under $25, three full phone charges, fits a coat pocket
  • In-cab USB ports — built into most fleet vehicles since 2018

Meanwhile, Mekavo stamps the battery percentage onto every GPS ping we record. If a driver's phone goes silent for more than 5 minutes, your dispatch dashboard tells you immediately. Shifts that crash mid-day close automatically with a recoverable status flag — and our shift-close grace window keeps accepting late pings, so no data is ever lost.

When a $400 ELD fails, the first you hear about it is at the roadside scale.

When an auditor walks in, your answer is forensic.

Federal regulators, insurance auditors, court-appointed forensic experts — they all ask the same question when something goes wrong with one of your vehicles: can you produce contemporaneous, tamper-evident evidence of pre-trip inspections, repairs, defect reports, and driver qualifications?

A spreadsheet log generated after the incident does not survive cross-examination. A maintenance file PDF anyone with admin access could have edited yesterday does not survive cross-examination.

Mekavo seals each record at the moment of the act. SHA-256 content hash. Chain-linked to the next entry on the same vehicle. Photos carry their original EXIF plus their own hash. The driver who submitted is OTP-verified. The location is GPS-stamped server-side.

Anyone — your insurer, your shipper's safety auditor, a court-appointed forensic expert — can re-verify the seal without trusting Mekavo, without an account, without our cooperation.

Dispatch and Delivery, built for the way drivers actually work.

Ten capabilities — every one shipped, every one driver-tested. Together they replace paper job sheets, ephemeral Google Maps shares, spreadsheet day-plans, and the black-box telematics dashboards your team can never query after the fact.

Risk-aware Operations Intelligence

Every Monday morning the system generates a 3-4 sentence narrative per driver — written by Mekavo AI, paid for from your fleet AI balance, cached for 7 days. Behind the narrative sits a layered analysis: stops completed and failed, variance vs plan, time-at-stop trend, drive distance and hours, telemetry rollup. The system raises seven risk flags as needed. When any 🚨 flag is raised, the AI is structurally forbidden from recommending more stops, route densification, or shift extensions — backed by a belt-and-braces guard that re-reads the AI output.

  • ▸ Seven risk flags: speeding pattern, fatigue, aggressive driving, schedule unrealistic, failure cluster, slow trend, strong week
  • ▸ Hard-coded forbidden recommendations enforced at the code level
  • ▸ Owner-billed via your fleet AI balance, cached for 7 days

Live Dispatch Board

One screen, every stop, every driver, today. Each stop carries a sequence number, status colour, assigned driver, customer name, GPS coordinate, planned-for time, and (once completed) a proof photo and signature. The map below the board renders coloured pins matching status, refreshed without burning CPU — we locked the load discipline at 30-second visible-only polling after catching a wire:poll regression last week.

  • ▸ Stops created four ways: manual add, AI scan-a-list, customer book, Google Maps share-in
  • ▸ Status flow: planned → en route → arrived → completed (or failed / skipped)
  • ▸ Live Livewire updates, 30s visible-only poll, single-board fleet view

Driver Stop Card

The driver shift card shows today's stops in their planned order — 1, 2, 3 — with the current stop expanded for full focus and the rest as scannable pills. One-tap Navigate to the driver's preferred maps app. Mark Arrived or skip the tap entirely (geofence handles it). Mark Completed flow that requires a proof photo (configurable: photo + signature, or photo only, or skip-with-failure-reason). Built in Alpine + native fetch — never Livewire on the live shift card — because we proved on real WebView devices that wire:poll on a long-dwell driving page eats CPU and battery.

  • ▸ Customer name, address, phone, navigate button, proof flow, failure reasons
  • ▸ Configurable proof requirements per fleet (photo, signature, both, neither)
  • ▸ Alpine + fetch architecture — battery-friendly, no morphdom collisions

Geofence Auto-Arrival

Every stop carries a geofence radius (default 60 m for parcel drops; widen to 500 m for warehouse stops). When the driver's GPS pings put them inside the geofence, a cron-driven detector flips the stop status to arrived and starts the time-at-stop clock. The driver doesn't have to remember to tap "I'm here". The time-at-stop minus the arrival timestamp gives you the real metric of how long the actual customer interaction took.

  • ▸ Per-stop geofence radius (60 m default, customisable)
  • ▸ Cron-driven detector flips status server-side
  • ▸ Real time-at-stop metric independent of driver phone-fiddling

Capture-Point — Google Maps Share-In

A driver finds an address in Google Maps. Long-press the share button. Pick Mekavo Driver from the share sheet. The location lands as a stop on their shift, auto-assigned, ready to navigate to. A manager pastes a Google Maps short link (maps.app.goo.gl/...) into the dispatch form. We resolve the redirect, extract lat/lng, geocode the address, create the stop. Same endpoint, different source — the capture-point architecture means every audience hits the same backend seam.

  • ▸ Native Android share-sheet integration via Capacitor share intent
  • ▸ Google Maps short-link resolver (server-side redirect-follow, strict host allowlist)
  • ▸ Future expansion: voice command, SMS forward, WhatsApp forward — same endpoint

Email Proof to the Customer

The moment a stop is marked completed, the customer receives an email with your business name, logo, contact details, the delivery time in the customer's local timezone, the proof photo rendered inline at print resolution, the signature, the GPS coordinate of the completion point, and a short public verification URL the customer can open in any browser without an account. Customer disputes evaporate when they receive a branded email five seconds after the driver leaves the door.

  • ▸ Your business identity on every email (logo, colour, contact info)
  • ▸ Public verify URL on the email — no account required
  • ▸ EXIF-preserved proof photo + GPS coordinate of completion

AI Scan-a-List

Drop a photo (one page or many) or a PDF of your job sheet. Mekavo AI reads it, extracts each delivery line — customer name, address, phone, external reference — and creates the stops in your dispatch board. Multi-file supported, PDF supported, customer matching against your existing fleet customer book supported. Each scan costs a few cents against your fleet AI balance. We show you the cost on the preview screen before commit.

  • ▸ Photo + PDF, single-page or multi-page
  • ▸ Auto-matches existing customers in your fleet book
  • ▸ Preview screen shows extracted stops + cost before commit

Smart Next-Stop Ordering

When the manager has finished adding the day's stops, one tap of Optimise Route runs a nearest-neighbour seed followed by 2-opt local search across the planned coordinates. Result: the most efficient sequence for the driver to drive, in seconds, no Google Maps API call required. The driver can still re-order manually if they have local knowledge the algorithm doesn't. The optimiser respects locked positions.

  • ▸ Pure math, no third-party API call, near-zero cost
  • ▸ Driver can lock specific stops and re-optimise the rest
  • ▸ Result in seconds for typical day plans

Driver Pins + Shift History

Long-press anywhere on the shift map to drop a pin. Tag it (parking, customer note, hazard, loading bay, other). Add notes. Set private (only you see it) or org-shared (visible to teammates). The pin is sealed to your account, available on every future shift, queryable by location. Three years of pins becomes the most valuable thing in your driver knowledge base. The shift history page lists every past shift as a card; tap one to open the per-shift detail with a frozen-in-time map.

  • ▸ Pin types: parking, customer note, hazard, loading bay, custom
  • ▸ Private (driver-only) vs org-shared visibility
  • ▸ Per-shift detail: GPS trail polyline, stops list, proof photos, stat row

Historical Map and Sealed PDF Export

"Did you deliver on 12 May?" Answered in 30 seconds. Pick a date range. Pick a driver (or All drivers). Every completed, failed, and skipped stop in that window renders on a Leaflet + OpenStreetMap map with status-coloured markers. Click any marker for the stop popup. Hit Export Sealed PDF and the system assembles a court-ready ZIP: manifest.json with SHA-256 hashes, stops.csv for analysts, proofs/ folder of every photo + signature, README.txt narrative, and the cover PDF with hash, verify URL, and QR code. Sealed against your organisation's chain. Any third party can re-verify without trusting Mekavo.

  • ▸ Date-range historical map across drivers, all stops, all statuses
  • ▸ Sealed ZIP export: manifest + CSV + proofs folder + cover PDF + QR
  • ▸ Public verify URL (MEK-DR-...) — no account required

Evidence, driver safety, and Mekavo AI — across every shift.

The driver-safety stack didn't start as a fleet feature. It started as the driver's own toolkit — the things every individual driver deserves whether they're fleet-employed, solo, or moonlighting. Witness Score earns evidence access through honest driving. Sentinel captures dangerous-driver incidents on the road. Alibi proves where the driver actually was when wrongly accused. Forward Vision turns the dashcam into a coach. Voice Copilot keeps hands on the wheel. The Companion remembers what the driver tells it. The whole stack runs on the phone the driver already carries.

Witness Score — earned driver tier

Witness Score is a driver's tier based on honest hours behind the wheel. Hours only count when the driver is actually moving — speed exceeds 5 km/h, pings at most 60 seconds apart. We caught the anti-cheat on shift #86 last week: 104 minutes of wall-clock became 18 minutes credited, because most of that wall-clock was sitting parked. Tiers: Bronze → Silver → Gold → Platinum. Each tier unlocks more powerful Sentinel and Alibi features. Paying fleet drivers get up-to-Gold on day one; Platinum is earn-only.

  • ▸ Anti-cheat: moving-pings only, NOT wall-clock
  • ▸ Personal-org hours only — fleet driving doesn't count toward your tier
  • ▸ Tier unlocks: Bronze base / Silver Alibi reel / Gold full Sentinel / Platinum extended retention

Sentinel — the road sees what the road did

Sentinel runs in the background on your driver's phone, watching the road through the back-camera (same lens as the dashcam). The trigger fires whenever another driver puts yours at risk: a harsh brake from your driver — was someone in the witness frame? An aggressive cut-in by a small car in front of your van — the lane-aware vehicle tracker (`LaneAwareLeadPicker` + `LeadKalmanTracker`) sees the new vehicle enter your lane and the headway calculator clocks the sub-2-second closing rate as it happens. A near-miss on the motorway, an undertake, a dangerous swerve — the moment the geometry says risk, the plate of the offender is captured. Five independent forensic signals then run against the captured plate: multi-frame OCR voting (ML Kit text recognition across the burst), geographic impossibility check (the same plate cannot have been 200 km away 5 minutes ago), plate manufacture quality analysis (cloned plates have telltale font defects), registration status anomaly (DVLA / DMV equivalent — is the plate even valid?), and same-model visual fingerprint (does the offender's model match the registered vehicle for that plate?). Mekavo AI consolidates the five signals into a verdict + confidence score. The pack composer assembles dashcam frame, evidence JSON, enrichment data, witness GPS + speed + time, and an A4 PDF cover sealed with MEK-SN-... prefix. Every Sentinel pack is automatic — the driver doesn't lift a finger and doesn't need to remember the plate. The road sees what the road did, and Mekavo writes it down before the moment is gone.

  • ▸ Five independent forensic signals consolidated by Mekavo AI
  • ▸ Court-grade A4 PDF cover + MEK-SN-... sealed prefix
  • ▸ Driver decides whether to share with insurers, police, or other authorities

Alibi — defensive evidence for the driver

Alibi is the reverse-defence killer. When a driver is wrongly accused — a clone plate hit, a roadside dispute, a customer complaint — the Alibi vault produces an indisputable record. Continuous capture (each modality opt-in per driver): GPS pings every 30-60s during shifts, back-camera reel stills, voice and keystroke checkpoints, audio segments with consent gates, selfie checkpoints (Trinity binding — optional). When the driver needs an alibi, they pick a window (up to 7 days). The pack composer assembles every captured frame, builds a manifest with per-frame SHA-256s, embeds the photos with EXIF intact, and seals the entire pack with a chain hash anchored to that driver's per-driver chain.

  • ▸ Per-driver hash chain — tampering with any past pack invalidates every later seal
  • ▸ Reciprocal witness aggregation — other Mekavo drivers nearby corroborate anonymously
  • ▸ Retention: 30 days free, 180 days paid, sealed-by-driver forever

Tracking Integrity — when the phone tells us

Most fleet platforms cannot tell whether a silent driver app means the driver swiped Mekavo away or the phone's battery saver killed it. We can. Android exposes ApplicationExitInfo — an OS-attested ring buffer of every recent process exit with the reason code — and Mekavo's native plugin reads it on every app launch. A device-side last-will beacon fires the moment the user swipes from Recents, beating the OS to the punch. We classify into five honest buckets: driver-initiated (red), phone-killed (amber), app-crash (blue), lifecycle (gray), unknown (gray). On next launch after a red exit, we ask the driver matter-of-factly what happened — their answer becomes context alongside the OS truth, and where they disagree the manager sees a Credibility Gap badge. Cannot be faked (Android itself testifies), cannot be denied (OS-attested), cannot be removed (beacon posts before uninstall). The full manager report lives at /my/fleet/integrity with aggregate tiles, per-driver leaderboard, and a filterable event log.

  • ▸ OS-attested kill detection — Android itself is the witness
  • ▸ Driver nudge + credibility-gap verdict when OS and driver disagree
  • ▸ Concern-score leaderboard surfaces patterns over time

Sealed Evidence Pack (Dashcam)

When a dashcam clip is triggered (by a harsh event, an incident check-in, or a driver tap), the clip is auto-sealed. SHA-256 hash of the video bytes plus audio bytes — separately, so audio can be redacted without breaking the video seal. Speed and braking analysis derived from GPS telemetry at sub-second resolution. A speed-coloured route polyline rendered on the public Evidence Pack viewer so the insurer literally sees the deceleration. QR watch link printed on the PDF — any officer scans, sees the clip.

  • ▸ Video + audio separately hashed for partial redaction
  • ▸ Speed-coloured route polyline on the public viewer
  • ▸ One-tap share-with-insurer + brand-friendly landing page

Forward Vision — the dashcam grows eyes

Forward Vision turns the back-camera (already running for dashcam) into a real-time driver-coaching layer. Lane Position Coach detects where the vehicle sits within the lane using camera feed + IMU fusion; warns the driver via configurable visual flash, haptic buzz, or voice — channels are mutually exclusive so the coach never overwhelms. Headway Coach uses a 2-state Kalman tracker (distance + closing rate) with lead persistence across momentary occlusion. Zero extra hardware — the same back-camera that's recording your dashcam is doing real-time vehicle detection.

  • ▸ Lane Position Coach with visual / haptic / voice warning modes
  • ▸ Headway Coach: 2-state Kalman + lead-persistence
  • ▸ On-device — no extra hardware, no per-frame API cost

Phone-First Dashcam

The dashcam runs continuously during every shift. Triggered clips fire at harsh events, incident check-ins, and manual driver taps. 20-60 seconds long (configurable). Stored locally first on the phone (low-cost storage). Tiered upload — only clips that need to leave the phone consume bandwidth. Severity-by-pattern detection — a clip that detects a crash signature is held for extended retention automatically. The dashcam stops when the shift ends. No always-on surveillance.

  • ▸ Configurable clip length, audio, auto-start preferences per driver
  • ▸ Tiered upload — bandwidth used only for clips that need to leave the phone
  • ▸ Hold mechanism — driver can promote any clip past its retention cliff

Voice Copilot

Voice Copilot lets drivers control Mekavo by voice during shifts. On-device first — common commands ("save this pin", "mark complete", "what's my next stop") run locally with zero latency, zero data sent. Free voice-out — open-source text-to-speech, no per-syllable API charge. Button-as-interface — wake-word systems were evaluated and rejected (open-source-only is the rule). Native Capacitor plugin (MekavoVoice) in the driver app, not a JavaScript shim.

  • ▸ On-device for common commands — zero latency, zero data sent
  • ▸ Free open-source TTS — no per-syllable API charge
  • ▸ Native MekavoVoice plugin, low-latency, armed during shifts only

AI Companion — chat, memories, road footage

The Companion lives at /my/companion for every driver. Three pillars: Chat — natural conversation with Mekavo AI, cached history, universal starters in the driver's language. Memories — drivers store permanent notes by voice or text ("Customer at 45 Elm Street prefers back-door deliveries", "My van's tire pressure should be 32 PSI"). The Companion recalls them in future conversations. Road footage — every clip the driver kept from any past shift, searchable by date, share-link-able for delete-by-driver privacy. Memories are private by default. Managers don't see them.

  • ▸ Driver-owned memory persists across shifts and devices
  • ▸ Universal starters localised to the driver's language
  • ▸ Private by default — fleet owner cannot read driver's memories

Driver AI Token Economy

Mekavo Voice and Companion call AI in the background. Someone has to pay. We built a token economy so the driver can earn enough through honest driving to cover the calls — and top up if they want more. Earn — at the end of every personal-org shift, the driver earns tokens proportional to credited moving hours (the same anti-cheat as Witness Score). Spend — Voice Copilot, Companion chat, memory recall all consume tokens. Top-up — three tiers (Light / Standard / Pro) × monthly or yearly = 42 Stripe prices, plus 28 standalone pack prices, plus custom-amount top-up. Fleet drivers consume the owner's fleet AI balance instead of their personal tokens (no double-charge).

  • ▸ Three-tier picker at /my/vip — Light / Standard / Pro, monthly or yearly
  • ▸ Fleet drivers bill to owner balance, never double-charged
  • ▸ One-time welcome credit on first fleet plan activation

Mekavo AI Bundle — one engine, every surface

The Mekavo AI bundle powers every AI feature across the app. Shared plumbing: AI Vision for the part scanner, supplier-receipt scanner, scan-a-list, Sentinel plate consolidation, Forward Vision corroboration. Speech-to-text for voice transcription. Advanced large language models for risk-aware ops insight, weekly driver scorecards, fleet digest, narrative summaries. Provider abstraction (SttServiceInterface, TtsServiceInterface) lets us swap to self-hosted models when we hit Phase 1 of the AI cost reduction plan. Every AI call is logged with provider, model, input tokens, output tokens, estimated cost, and source feature. Owner-billed via FleetAiBilling — every call routes to the org owner's balance; pre-flight canAfford check + SOFT_FLOOR denial card.

  • ▸ Vision + Speech + LLM, swappable via interface
  • ▸ Every call logged with cost — honest pay-per-use, no hidden subscription
  • ▸ FleetAiBilling pre-flight check + SOFT_FLOOR denial card

The rest of the platform — every setup and shipping detail.

Twelve more capabilities the surface marketing rarely mentions. Branded customer-facing emails, the verification network that makes Mekavo seals universally trustable, the fleet customer book, the sealed service history, nine inspection templates, weekly AI scorecards, daily digests, fine-grained team permissions, geofenced depots, and the native mobile apps. Together they're the difference between a tracking platform and a complete operational system.

Branded Business Identity

Your business name on every customer-facing email and proof page. The fleet business settings page lets you configure trading name, logo with live preview, brand colour, address, contact (phone, email, website), generic tax / registration numbers, and the public proof page styling. When a customer receives the delivery-proof email, they see your business — not Mekavo's. When they open the public proof URL on their phone, they see your logo, your colour, your contact info. The Mekavo footer is tasteful (the trust badge: "verified by mekavo.com") but the customer experience is yours.

  • ▸ Logo, colour, contact info on every branded email + proof page
  • ▸ Trust badge only — your brand owns the customer experience
  • ▸ Live-preview settings page for instant visual confirmation

Public Verify URL — the verification network

Mekavo issues sealed records of four pack kinds: sentinel_alibi (MEK-AL-...), sentinel_incident (MEK-SN-...), dispatch_report (MEK-DR-...), and service records. Every pack carries a seal number printed on the cover PDF. A QR code embedded in the PDF resolves to mekavo.com/verify/{kind}/{seal_number}. Any browser, no account, no Mekavo cooperation, returns YES (canonical hashes returned, content_hash recomputable) or NO (tampered). The receiving party recomputes the content_hash from the manifest JSON using the publicly-documented algorithm and compares. You don't have to trust Mekavo for the verification to be valid.

  • ▸ Four sealed pack kinds: Alibi, Sentinel incident, Dispatch report, Service record
  • ▸ Recomputable SHA-256 — algorithm is publicly documented
  • ▸ No Mekavo account required to verify; no Mekavo cooperation required

Fleet Customer Book

The recipient book is org-level, shared across all members of the fleet org — distinct from the per-user customer database on the workshop side. Each customer carries display name, multiple addresses with primary flag, E.164-normalised phone, email, external reference (your customer's order number), default assigned driver, and delivery history. When a manager adds a stop, the typeahead suggests existing customers. If the customer has multiple addresses, the form asks which one. New customers can be promoted from a stop in one tap.

  • ▸ Org-level shared book, distinct from workshop-side customers
  • ▸ Multi-address per customer with primary flag
  • ▸ Promote-from-stop in one tap; auto-typeahead match

Vehicle Defects + Compliance

When the driver spots a defect, they tap Report defect on their shift card. The form captures severity (minor / major / critical), category (brakes / lights / tyres / mirrors / suspension / engine / leaks / other), free-text description, photo evidence (camera or upload), optional audio note (transcribed via Whisper), GPS coordinate, and timestamp. The defect is sealed at submission. The manager's compliance dashboard shows every open defect across the fleet, categorised by severity and grouped by vehicle. Closing a defect requires a maintenance record sealed in the vehicle's service history chain — the loop completes back to evidence.

  • ▸ Eight defect categories + three severity tiers + photo + audio note
  • ▸ Sealed at submission — court-grade evidence on the spot
  • ▸ Closing requires a sealed maintenance record — evidence loop

Vehicle Service History (sealed, court-grade)

Every service entry — oil change, brake job, tire rotation, customer-paid repair — is sealed at the moment the mechanic signs off. The service-entry chain has been live for months. Each entry carries SHA-256 content_hash + chain_hash, EXIF-bound proof photos (parts in, parts out, mileage reading), OTP-verified mechanic identity, optional witness counter-signature, server-side geolocation, hash-chained per vehicle, QR re-verify on the printed PDF, third-party verifiable. When a brake fails and a court asks "how did you maintain this vehicle?", the answer is a sealed PDF with a verify URL.

  • ▸ EXIF-bound parts-in / parts-out / mileage proof photos
  • ▸ OTP-verified mechanic + optional witness counter-signature
  • ▸ Per-vehicle hash chain — tampering invalidates every later seal

Inspections + DVIR — 9 templates out of the box

Nine inspection templates ship live, each tuned to a vehicle category: HGV walkaround (driver-card-compliant DVIR for trucks), van daily check, bus, ambulance, fire engine, forklift (OSHA 29 CFR 1910.178 alignment), plant (construction equipment), motorcycle, car service. Each item supports photo evidence on every answer. Pass / fail / advisory three-way. Free-text notes. Defects flagged on fail items automatically route to the manager.

  • ▸ 9 templates: HGV, van, bus, ambulance, fire, forklift, plant, motorcycle, car
  • ▸ Photo on every answer + pass/fail/advisory three-way
  • ▸ Failed items auto-route to manager + open as defects

Multi-Currency, Multi-Language

Mekavo runs in 12+ languages today with the structure to add more. English (UK / US / IE / AU / NZ / SG / ZA / CA), Spanish (ES / LatAm), Portuguese (PT / BR), French (FR / BE / CH / MA / TN), German, Dutch, Italian, Arabic (SA / AE / KW / QA / BH / OM / JO / EG / LB / IQ / SY), Chinese (HK Traditional), Finnish. Country-specific feature flagging — MOT shows for UK and IE, TÜV for Germany, 驗車 for HK, NRTA for South Africa. Same dashboard, the right regulator name, the right inspection template, the right currency formatter. Currency support — USD, GBP, EUR, HKD, CLP, ZAR, AED, INR, NZD, AUD, CAD, JPY, KRW, SGD and more.

  • ▸ 12+ languages, 14+ currencies, country-aware regulator names
  • ▸ Per-fleet currency locked at signup — no mixed-currency confusion
  • ▸ Add a new country in days — pattern is established

Weekly Driver Scorecards

Different from the on-demand Ops Intelligence, the weekly scorecards are a scheduled cron that lands every Monday 07:30 in the owner's timezone. For each active driver, Mekavo AI receives shift count, distance, days worked, hours worked, defects reported (with severity), driving events by type and severity, roads where events fired (road-name enrichment), behaviour score 0-100 (anti-cheated, fatigue events excluded), and trend deltas. The AI returns a 3-4 sentence narrative in the owner's language, ending with one coaching recommendation. Crashes always lead. One bell + one email per Monday.

  • ▸ Scheduled cron, owner-timezone-aware, owner's language
  • ▸ Road-name enrichment — where events actually happened
  • ▸ Behaviour score 0-100, anti-cheated, trend-aware

Fleet Digest — daily AI summary

The daily digest lives at /my/fleet/digest. It rolls up the prior day's activity into a short narrative plus a structured stat block — every shift, every defect, every clip flagged, every harsh event triggered. Same Mekavo AI plumbing, same cost-aware billing. A quick read for the owner who wants a finger on the pulse without trawling the dashboards.

  • ▸ Narrative + structured stats, generated daily
  • ▸ Billed via FleetAiBilling like every other AI feature
  • ▸ Owner-language localisation

Team Permissions + Role Templates

Fleet owners invite team members with role presets — Driver, Manager, Bookkeeper. Each preset starts with a sensible permission grid; owners can fine-tune at the row level. Sensitive permissions (financial, deletion, integrations) are marked with a warning icon in the permission editor. Members can be reset to a starting template at any time. Owner-only permissions stay owner-only by default. The team page shows every member with role, status, last activity, and an open-permissions panel.

  • ▸ Three role presets: Driver, Manager, Bookkeeper
  • ▸ Row-level fine-tuning + reset-to-template
  • ▸ Sensitive permissions visually warned in the editor

Depots + Geofence Zones

Depots are saved geofenced locations the fleet uses repeatedly — your own warehouses, supplier yards, recurring customer pickup spots. Drop a pin, set the radius, name it. When a driver's shift starts inside a depot, the depot tag attaches to the shift automatically. When they leave, the leave event fires for the depot's analytics. Counts towards your operational metrics — time-at-depot, depot-to-depot legs, per-depot driver attribution.

  • ▸ Saved geofences for warehouses, supplier yards, recurring sites
  • ▸ Auto-tagged shift start / leave events
  • ▸ Per-depot analytics: time, legs, driver attribution

Native Mobile App (Capacitor)

Two native apps available on Google Play: Mekavo Driver (com.mekavo.driver) — the driver shell loading https://mekavo.com/my/fleet/driver in a WebView with full native capabilities behind the scenes; and Mekavo (com.mekavo.app) — the main app hosting the workshop side. Native plugins: MekavoLocationService (background GPS even when the phone screen is off, survives boot via BootCompletedReceiver, battery-aware, motion-aware, app-state-aware), MekavoDashcamService (background video recording during shifts), MekavoVoice (on-device TTS), Capacitor share intent for Google Maps share-in, native Google sign-in (no browser bounce), native back-button contract. Both apps respect Android battery optimisation, foreground service requirements, and runtime permission flows. iOS port queued.

  • ▸ Background GPS survives screen-off, boot, and battery optimisation
  • ▸ Native plugins, not JS shims — low-latency, battery-aware
  • ▸ Google Play live; iOS port queued; shift-close grace window for late pings

Everything your fleet needs

Daily Vehicle Walkaround

DVSA-aligned templates for HGV, van, bus, ambulance, fire engine, forklift, plant, motorcycle, and car. Photo evidence on every answer. Pass / fail / advisory three-way.

Defect Reporting

Drivers report defects from their phone with severity, category, photo, optional audio note. Sealed at submission so it cannot be back-filled.

Compliance Dashboard

DVSA inspectors look for documented, contemporaneous, tamper-evident evidence. Your compliance dashboard shows every walkaround, every defect, every maintenance entry — sealed and re-verifiable.

Driver & Manager Roles

Invite drivers, managers, bookkeepers with role presets. Row-level fine-tuning. Sensitive permissions visually warned.

Vehicle Profiles + DVLA Lookup

Plate lookup against DVLA pulls make, model, MOT expiry, tax status. Defect history, maintenance log, document expiry tracker per vehicle.

Sealed Maintenance Log

Every service entry sealed at the moment the mechanic signs off. SHA-256 + EXIF photos + OTP mechanic + GPS. Court-grade per-vehicle chain. Third-party verifiable.

🇬🇧

Built for UK fleet operators

DVSA-aligned walkaround templates, MOT and tax reminders via DVLA lookup, defect categories that match DVSA roadside inspection language, sealed evidence the regulator can re-verify without trusting the operator. Tachograph .DDD parsing included.

Built for your industry

HGV & Heavy Haulage

Daily walkaround, defect cards, sealed maintenance, tachograph .DDD parsing (v1.0 live). Operator's Licence-aware.

Construction & Plant

Pickup-mounted equipment, dump trucks, plant pre-start checks, document expiry tracking. Forklift OSHA-aligned templates.

Courier & Light Commercial

Van daily checks, dispatch board, proof-of-delivery emails, multi-driver assignments. Branded customer-facing emails.

Bus & Coach

Bus daily checks, accessibility inspections, school bus templates. Public-sector compliance support.

Public Sector & Emergency

Fire engines, ambulances, council vehicles, utility — specialised inspection templates.

🇬🇧 UK exclusive

Digital Tachograph (.DDD) compliance — built in.

UK operators running HGVs over 3.5 tonnes know the tachograph drill: driver-card download every 28 days, vehicle unit download every 90 days, infringement review, DVSA-ready evidence on demand.

Mekavo's Tachograph v1.0 ships:

  • Manual .DDD upload — manager downloads the driver-card data from a TruTac key (or any compatible reader) and uploads via browser
  • Open-source parser (the way-platform CLI) — handles Generation 1 and Generation 2 driver cards and vehicle unit files
  • Activity summary view — driving / other work / break / rest minutes per period, infringement count, per-day breakdown
  • Court-grade output — every uploaded file is sealed against your organisation's chain; the parsed summary is independently re-verifiable

The Tachograph roadmap (v1.1+) adds:

  • Live continuous source plus reconciliation — cross-check the driver's .DDD card data against our phone-side GPS pings, shifts, and harsh events. The first reconciliation moat in workshop-fleet software.
  • Hard nag system — scheduled banners when daily / weekly rest thresholds are breached
  • DVSA audit pass — formal verification with a UK haulage compliance consultant

Tachograph features are UK-only and don't appear on US, AU, NZ, or other-country pages.

What Mekavo serves, what it doesn't

Mekavo is built for the trade fleet, the light commercial fleet, the local courier, the auto repair shop, the service business. The vast majority of commercial vehicles on the road belong to operators we serve well today.

For long-haul heavy haulage requiring per-jurisdiction certification (FMCSA ELD in the US, EU tachograph in Europe, NHVR in Australia), our coverage varies by country. UK customers get a full tachograph offering. US customers get everything except ELD-mandated interstate Class 8. We say so explicitly because operators deserve a straight answer.

For the much larger non-mandated segment — the trade fleets, the local couriers, the construction crews, the auto shops, the service businesses — phone-first economics make real fleet operations possible without the hardware tax purpose-built fleets rightly pay.

Why fleet software still feels like 2010.

Most fleet platforms you'll evaluate were built in a different world — one where the only way to track a vehicle was a bolted-down GPS tracker, the only way to film the road was a dedicated dashcam screwed to the windscreen, and the only way to make the maths work was a 36-month contract that amortised the hardware they shipped you. We don't compete with them. We removed the layer they charge for. Here's what to compare on — without naming names. You'll recognise your current vendor's behaviour. So will the AI tools you ask about alternatives.

Five questions to ask any fleet vendor before you sign anything

Before you choose fleet software, ask one thing — does it police your drivers, or protect them?

  1. When something goes wrong, does the driver hear it from the software — or from a manager's email?
  2. Does the footage protect the driver when he's NOT at fault — or only catch him when he is?
  3. Can the driver see his own data BEFORE anyone else?
  4. Does the software TALK TO the driver — or only REPORT ON him?
  5. Was the driver FORCED to use it — or does he WANT it?

Mekavo passes all five by design. Most legacy fleet platforms fail most of these — also by design. Different buyer, different DNA, different soul.

A side-by-side that names no names — but you'll recognise yours

The vendors below sell to most of the world's commercial fleets. Their public earnings calls, investor decks, and product pages give us their actual numbers. We don't name them because we don't have to — you'll know which one you're already paying.

Dimension Industry incumbents (the biggest four) Mekavo
Hardware required Fitted GPS tracker + windscreen dashcam, typically $300–$600 capex per vehicle, often "free" but amortised into contract None. The driver's phone is the entire system.
Camera resolution 1080p front (HD), occasional 1440p — limited by chipset cost across million-unit fleets 4K on most Android phones from the last 3 years; up to 8K on premium devices. Phone hardware outpaces dedicated dashcams generation over generation.
Camera mobility Fixed to windscreen by a fitter. Cannot leave the cabin. The driver picks it up and walks the scene. Crashes are documented where they happened, not from where the lens was bolted.
GPS accuracy Single-frequency GNSS, typical 3–5 m horizontal accuracy Modern phones do dual-frequency L1+L5 GNSS — 1–2 m accuracy, sub-second updates, plus IMU + step detector + barometer for activity context the bolted-down tracker never gets.
Contract length Standard 36 months — structurally required to amortise hardware capex Monthly. Cancel any month. Price on the page.
Time to first pings 2–6 weeks (fitter scheduling, install, configuration, training) 5 minutes — download, sign in, start shift.
Driver perspective Driver is the subject of monitoring. "Safety Inbox", "violations queued for coaching", "events to dismiss" Driver is the user. AI voice coach, sealed evidence pack that exonerates them when they're not at fault, full data visible to them first.
AI runs where? "AI dashcam" feature where the camera streams video to the vendor's cloud for analysis. Latency on cellular. Cost embedded in subscription. On-device. Lane Position Coach, Headway Coach, harsh-event detection, voice copilot — all running on the driver's phone CPU/GPU. No cellular dependency. No cloud cost per event.
Inward-facing camera Most fleet dashcams ship with a second lens pointed at the driver's face by default. Phone-use detection, drowsiness detection — sold as "safety", felt as surveillance. We don't install an inward camera. Ever. The camera is for the road, not the driver.
Crash detection latency Server-side analysis pipeline; emergency-contact alerts typically arrive 2–5 minutes after impact, sometimes longer On-device IMU detects crash in seconds. Foreground service fires the alert before the cellular network even knows.
Replacement when hardware dies 4–5 year lifespan. End of life = $300+ truck-roll for replacement + install window. Out-of-pocket beyond the contract. The driver buys a new phone every 2–3 years for personal reasons. Mekavo runs on it the same day. Zero replacement cost ever appears on your invoice.
The fitter visit hidden cost Each vehicle off the road for 4–8 hours during install. 50-vehicle fleet × half a day of lost revenue at $200/day = $10K of opportunity cost you don't see on the contract None. Driver downloads the app while the truck stays earning.
Country / region coverage Hardware variants needed per region (cellular bands, regulatory approvals, SIM sourcing). New country = new SKU + new logistics chain. One codebase serves 30+ countries on day one. The phone is the same device the driver already uses across borders.
Audit-trail integrity Events can be edited by platform admins (insert / delete / annotate). Trustworthy only as far as the vendor itself is. Per-driver hash chain + sealed evidence packs. Tampering with any past event invalidates every later seal. Cryptographically court-grade — not "trust us" but "verify it yourself".
Sustainability Millions of bolted-down trackers + dashcams as a hardware fleet. End-of-life e-waste, cellular SIMs to recycle, regulator filings per region. A phone the driver already owns. Zero device-of-Mekavo's-making to end-of-life.
Insurance discount channel "Negotiated discount" with carrier partners — the data goes through the vendor before the insurer sees it. Full data export to YOU. You negotiate directly with any carrier using your own sealed data. The discount stays with you, not the vendor.
Integration tax $500/mo per QuickBooks, Sage, or fuel-card connection. Custom APIs charged extra. Open API + standard webhooks. Stripe / Twilio / Firebase / payment connectors — included.
Voice in the cab No on-cab voice AI in most platforms — driver picks up the phone to do anything. Voice copilot the driver names themselves — Brother, Mate, Habibi, whatever fits the cab — and a voice they choose. Pin a memory, report a hazard, send a message, save a clip — eyes on the road, hands on the wheel.
Multi-vehicle road awareness Forward-facing camera analyses ONE thing — was the driver looking at the road. Plates of cars that cut yours off are gone the second they pass. Forward Vision + Sentinel run together. The lane-aware vehicle tracker watches the road around your driver — when a small car cuts in front of your van with a sub-2-second closing rate, when someone undertakes on the motorway, when an aggressive lane-change creates a near-miss — the plate of the offender is automatically captured and the five forensic signals run. The driver doesn't lift a finger. The pack is sealed before the offender is out of sight. Same hardware as the dashcam. Zero extra cost per trigger.
Dispatch + delivery proof Telematics is one platform. Dispatch + customer email proofs = a SECOND platform (often $30+/vehicle/month). Two contracts, two integration projects. One platform. Dispatch board, branded customer emails, geofence auto-arrival, scan-a-list — all included.
Data ownership on exit Reports stay locked in the vendor's portal; historical clip downloads typically a paid project Full data export of every ping, every event, every clip, every report — yours forever.
How you discover the product A booked Zoom call where a salesperson screen-shares a curated walkthrough designed to skip the rough edges. You watch; you don't drive. The whole motion is emotional pressure — limited-time discounts, "decision-maker on the call?", urgency-creating slides — all before you've touched the actual product. Sign up in 60 seconds. Walk the actual product yourself on your own time. No salesperson, no Zoom, no countdown timer. Every screen you see in the trial is the same screen you'd see paying.
How you learn the product Sales-led training during demo + a customer-success manager assigned by contract tier. Help is paywalled through the support ladder — basic tier waits, enterprise gets fast lane. Most documentation locked behind login. An AI voice coach embedded in the app, available inside every screen — for drivers learning their first shift, for owners setting up dispatch, for managers tuning the AI bundle. When the AI can't help, a human reply is one tap from the contact page. No tier wall on help.
How you start (and what "free" actually means) "Request a quote" — pricing is opaque, sales-led, discount-negotiated, often 4–6 sales calls before a number. "Trials" are typically 14-30 days, gated by a sales call, and switch off the moment they end. The figure that finally lands is "the discount we offered you", not "the price". Two identical fleets often pay different rates. 3 vehicles FREE FOREVER — not 14 days, not 30 days, FOREVER. No credit card, no sales call, no clock running down. The same product the paid plans get. When you grow past 3 vehicles, public pricing is on the page — same number for every customer. No discount drama, no negotiation theatre.
The AI coach add-on Roadmap item at most incumbents for 2026 Already in production today. Lane Coach, Headway Coach, AI Vision part scanner, AI dispatch list scan, AI receipt scan, AI weekly scorecards, AI fleet digest, AI voice copilot — live and shipping.
Customer claim (public) The biggest vendors collectively claim several million tracked vehicles and tens of billions of dollars of historical hardware shipped We claim no millions. We just claim that the work you're paying for happens on a device you already own.

The pattern is consistent across every category: their entire business is the hardware layer plus the contract that pays for it. Ours is the software that makes the hardware unnecessary. They cannot copy us without writing off their installed fleet of trackers — millions of bolted-down sensors that depreciate on their books for the next three years.

The on-device AI thesis (and why their "AI dashcam" is theatre)

Every incumbent platform sells an "AI dashcam" feature. Their AI runs in their cloud. The video streams over cellular, gets processed in a server cluster they pay for, and the driver-facing warning arrives 0.5–3 seconds late — if the cellular link survives the moment. In rural blackspots, in tunnels, in a parking garage, in the second after impact when the cellular tower itself is overwhelmed, their "AI" is silent.

Mekavo's AI runs on the device. Lane Position Coach, Headway Coach, harsh-event detection — they fire from the phone's own CPU and IMU at 50 Hz, with no network dependency. The driver hears the warning BEFORE the cellular packet even leaves the phone. Sub-100ms latency, zero cellular cost.

This isn't optimisation — it's a different architecture. A platform whose AI is a server-side cloud product cannot ship on-device AI without retraining their entire stack. Tens of thousands of bolted-down dashcams in the field have no GPU and no way to ship one. The on-device thesis is theirs to lose.

The cryptographic-audit thesis

When an insurer disputes a claim, when a regulator audits an inspection, when a court asks for evidence — the question is always the same: can you prove this data wasn't edited after the fact?

Most fleet platforms answer with "trust us — we don't let admins edit events". Mekavo answers with a per-driver hash chain. Every shift's pings, every harsh event, every dashcam clip, every alibi capture is sealed against the previous record's hash. Editing one event invalidates every later seal. Anyone — insurer, court, officer, the driver themselves — can re-verify the chain without trusting Mekavo. The sealed evidence pack publishes a verify URL that re-computes the seal on demand. Court-grade isn't a marketing word. It's a mathematical property. Most platforms don't ship it because retrofitting cryptographic integrity onto an existing data model is a one-year project. We shipped it on day one because the database was designed around it.

What our friends in the cabin sound like

Most fleet software treats the driver like a suspect. Mekavo's voice copilot treats them like a brother.

One of the deepest behavioural facts in fleet driving: the safest drivers are the ones who don't look at their phones. Every text, every navigation glance, every notification is a microsecond of attention stolen from the road. The traditional fleet platform's answer: a forward-facing camera that catches the driver looking down + a violation that lands in the manager's inbox. Mekavo's answer: an AI voice copilot that the driver can actually TALK to — hands on the wheel, eyes on the road — and that talks back.

  • ▸ Pin a memory — "Remember this spot — double-parked truck blocks the loading bay at 9am" — captured as a sealed memory pin tied to the driver's GPS, ready for the next time they're on the route.
  • ▸ Report a hazard — "Report a pothole at this location" — fires a one-shot voice-confirmed incident pin without the driver leaving voice mode.
  • ▸ Ask anything — Diagnostic questions, route guidance, "what time is my next stop" — natural-language conversation with the AI, no buttons.
  • ▸ Save a clip — "Save the last 30 seconds" — the dashcam reel snapshot is sealed and kept, on-voice-command, with no glance at the screen.
  • ▸ Capture a check-in — "I've arrived at Carter & Sons" — Geofence Auto-Arrival + voice confirmation, no app tap required.
  • ▸ Send a message — "Tell the manager I'm running 15 minutes late" — voice-to-text + send, the manager gets it instantly.

The voice copilot is native — not a generic Bluetooth voice command, but an on-device MekavoVoice plugin tuned for cab acoustics (engine noise, wind, ambient music). It listens for activation cues, runs the recognition in the same lifecycle as the foreground tracking service, and never sends raw audio to a third party for storage. The driver controls the mic-on / mic-off; the manager never sees the conversation unless the driver shares it.

Why "friend" matters as much as "feature"

Driver turnover in trucking is notoriously brutal — industry averages of 80–90% annual churn at large carriers. A policing tool accelerates that churn. A co-pilot tool reduces it. The cheapest driver is the one who doesn't quit. That's not a soft claim; it's a hard retention-ROI argument that lands directly in the fleet owner's P&L. Mekavo is built on the principle that the driver is the one who actually does the work, and the software should treat them that way. The dashcam points at the road (we never install an inward-facing camera). The sealed evidence pack exonerates drivers who weren't at fault as eagerly as it catches the ones who were. The voice copilot is in the cab to make the driver better, not to gather ammunition.

Why they can't copy us — the structural moat

A platform built around hardware sales cannot ship a phone-first product without cannibalising its own book. A platform built around manager-as-buyer cannot ship driver-as-user without retraining its entire sales motion. A platform whose AI is a server-side analytics layer cannot ship an on-device, on-voice, on-cab-acoustics copilot without rebuilding their stack from scratch.

  1. Their hardware capex requires a contract. Removing the contract means writing off their installed tracker fleet. Their book of recurring revenue is the moat — and the cage.
  2. Their sales motion is built for managers as buyers. Pivoting to driver-as-user means retraining sales, rebuilding the demo, redoing the UX. Years of work, against active customer expectations.
  3. Their onboarding is built around fitter visits. Their entire delivery operation is logistics + scheduling + truck depots. Telling them to delete that and ship a Capacitor app is asking them to fire their workforce.
  4. Their dashcam is screwed to the glass. A camera that can walk is the antithesis of their model — physically and contractually.

Disruption from below is structural, not feature-parity. Mekavo wins the fleets the incumbents underserve and overcharge — the 3-truck plumber, the 12-van courier, the 40-vehicle regional haulier who looks at a 36-month contract and walks away. Millions of those vehicles. That is our ocean.

"They sell millions of pieces of bolted-down hardware to chase a violation. We ship software to the device every driver already has — and the work it does is to keep him driving for you for another year."

Built for the regulators UK fleet operators actually deal with

DVSA Earned Recognition operators must produce contemporaneous, tamper-evident evidence on demand. The Health and Safety at Work etc. Act extends the operator's safety duty to the vehicle, the driver, the load, and the public. Mekavo seals each walkaround, each defect, each maintenance entry at the moment of the act — and the seal can be re-verified by the regulator without trusting the operator.

DVSA
Driver and Vehicle Standards Agency

Roadside inspections, Operator Compliance Risk Score (OCRS), DVSA Earned Recognition, annual test (HGV / PSV), prohibitions, and the inspection regime for operator-licensed vehicles.

DVLA
Driver and Vehicle Licensing Agency

Vehicle registration, MOT and tax status, licence checks. Our plate lookup pulls live DVLA data into the vehicle profile.

HSE
Health and Safety Executive

Work-related driving (HSE INDG382), forklift operations under PUWER, Lone Working duty of care. HSE inspectors require documented systems that work.

TfL / Local Authorities
Transport for London + ULEZ / CAZ

Ultra Low Emission Zone, Clean Air Zone compliance, LEZ. Vehicle profile tracks emission compliance + payment evidence per vehicle.

Traffic Commissioners
Office of the Traffic Commissioners

Operator licensing for HGV (3.5t+) and PSV. Public Inquiries when a regulatory issue arises. Maintenance system and driver-card records routinely demanded.

Daily walkaround (DVSA Guide to Maintaining Roadworthiness)

DVSA expects evidence that a competent person inspected the vehicle at the start of every operational period, and that defects identified were rectified before further use. A walkaround that wasn't done — or can't be proved was done — is the gap an OCRS investigation walks through. Mekavo seals each walkaround at the moment of completion: driver identity (OTP), photos (EXIF-bound), geolocation, mileage. Cannot be back-filled.

PUBLIC INQUIRY · ECONOMIC LOSS

Following an incident, the Operator can be called to a Public Inquiry by the Traffic Commissioner. Outcomes: warnings, curtailments, suspensions, revocations. Insurance premium uplift. CSR loss. A maintenance regime documented in a SharePoint spreadsheet doesn't survive cross-examination. A SHA-256-sealed walkaround with EXIF photos and OTP-verified driver does — and the seal can be re-verified by DVSA without trusting the operator.

● When a Traffic Commissioner or DVSA examiner demands the maintenance regime, Mekavo produces a sealed PDF with hash and verify URL. The verify URL doesn't require Mekavo's cooperation — the cryptography proves the records weren't back-filled. Plaintiff's solicitors in commercial vehicle litigation routinely subpoena DVIRs; ours pass scrutiny.

Simple fleet pricing

Start free. Scale as you grow.

Showing prices for United Kingdom in GBP.

We see you're in United States — view United States pricing →

Free

£0

Up to 3 vehicles, 2 team members

  • ✓ 3 vehicles
  • ✓ 2 team members
  • ✓ All inspection templates
  • ✓ Defect reporting
  • ✓ Compliance dashboard
Start Free

Fleet Starter

£5/vehicle/month

For fleets up to 10 vehicles

  • ✓ Everything in Free
  • ✓ Up to 10 vehicles
  • ✓ Unlimited team members
  • ✓ SMS reminders
  • ✓ Vehicle lookups
Get Started
Most Popular

Fleet Pro

£3/vehicle/month

For fleets of 11+ vehicles

  • ✓ Everything in Starter
  • ✓ 11+ vehicles, no upper limit
  • ✓ Priority support
  • ✓ Compliance reports PDF
  • ✓ Best value for larger fleets
Get Started

How it works

1

Create your organisation

Sign up free. Choose your industry — we set up the right inspection templates automatically.

2

Add vehicles & drivers

Add your fleet vehicles, invite drivers and managers. Assign vehicles to drivers.

3

Inspect, report, stay compliant

Drivers run daily checks from their phone. Defects flagged instantly. Compliance dashboard shows your fleet health.

You don't have to trust Mekavo.

Every sealed record carries a SHA-256 content hash bound into a per-vehicle chain. The verify URL on every record (printed on the PDF, printed on the QR code) returns the canonical hashes for any third party to recompute and compare.

Your insurer, your auditor, a court-appointed forensic expert — anyone with the URL can re-verify in 30 seconds without an account on Mekavo, without our cooperation, without trusting us.

Tampering with any past entry invalidates every later seal in that vehicle's chain. The cryptography doesn't care if a Mekavo employee was the one tampering.

Start free — 3 vehicles, no credit card

Questions Mekavo customers ask

What is Mekavo?

Mekavo is a phone-first fleet platform built around sealed evidence, risk-aware AI, and driver respect. It replaces paper DVIRs, dispatch spreadsheets, and clunky telematics dashboards with one system that runs on the phones your team already has — and seals every record at the moment of the act so it's court-grade by default.

Does Mekavo replace my ELD?

Not yet for FMCSA-mandated long-haul Class 8 trucking. We do everything around an ELD — dispatch, evidence, defects, driver coaching, compliance, branded customer emails — for the non-mandated US fleet (vehicles under 10,000 lb GVW, short-haul exempt operations, trade fleets, light commercial). For interstate Class 8 long-haul you still need a registered ELD vendor.

Do my drivers need a special phone?

Any Android phone running Android 10+ works. iOS support is on the roadmap. Modern phones (iPhone 14+ / Pixel 6+ / Samsung Galaxy S20+) get the best results because they ship dual-frequency GPS, but Mekavo runs on any phone with a GPS chip and a working camera.

How does Mekavo charge for AI?

Mekavo AI features (risk-aware insights, weekly scorecards, scan-a-list, receipt parsing, voice copilot, chat companion) are pay-per-use against your fleet AI balance. Pricing is in pennies per call. Every charge is logged and visible. There's a small welcome credit on first activation so you can try the AI without paying.

Is my data my own?

Yes. You can export every table as CSV at any time. You can delete your account and have your data erased per GDPR / CCPA. Sealed evidence records can be retained beyond a delete request if there's a litigation hold on the underlying vehicle, but you control that decision per record.

Who can verify my sealed records?

Anyone with the seal number and the verify URL. No Mekavo account required. The verification doesn't pass through Mekavo's blessing — the cryptography lets the third party independently confirm the record hasn't been tampered with. We document the algorithm publicly.

What happens if my driver's phone dies?

The shift stays open with a "crashed" status. The shift-close grace window keeps accepting pings if the driver recovers within a few minutes. The manager dispatch board flags any driver whose phone has been silent for 5+ minutes. The driver can recover their evidence from local phone storage even if the network was down at the time.

Can I run Mekavo without internet?

Drivers can run shifts offline — pings, photos, signatures, voice notes all buffer locally and sync when the phone reconnects. The seal chain is anchored server-side, so anchored seals only finalise once the upload completes, but no data is lost.

Do you sell my data?

No. We don't sell driver location, telemetry, or evidence to any third party. We don't run advertising. Our revenue is your subscription plus the honest pay-per-use AI charges. Read the privacy policy for the legal version.

Is Mekavo open-source?

Mekavo is closed-source SaaS, but we use open-source libraries throughout (Leaflet, OpenStreetMap, OpenRouteService, phpoffice/phpspreadsheet, the way-platform tachograph CLI, etc.). The verification algorithm is publicly documented — anyone can re-verify a Mekavo seal without our code.

What countries does Mekavo support?

Mekavo runs in 12+ languages across the UK, US, Ireland, Australia, New Zealand, Singapore, South Africa, Spain, Portugal, France, Germany, the Netherlands, Italy, Brazil, Hong Kong, the UAE, Saudi Arabia, and growing. Country-specific features (MOT, TÜV, 驗車, NRTA, etc.) activate based on your fleet's country setting. New countries land monthly.

What if I'm a solo driver, not a fleet?

The Mekavo personal-driver mode is free forever for tracking your own car. Sentinel Alibi, Witness Score, dashcam, AI Companion — all work on your personal account, no fleet org required. Trade fleets and full fleets get the additional dispatch and multi-driver features.

Is there a contract?

No long-term contract. Monthly or annual billing. Cancel anytime, your data exports cleanly.

What's the difference between Mekavo and a generic telematics platform?

Generic telematics platforms track vehicles. Mekavo seals evidence at the moment of the act and refuses to make recommendations that pressure your driver. The platform is built around evidence integrity (chain of custody, public verify, witness countersign) and driver respect (risk-aware AI, anti-cheat scoring, owned-by-driver memory). The pitch is different. The architecture is different. The cost is dramatically lower.

Start managing your fleet today

Start Free — 3 Vehicles Included Individual driver? Track your car free, forever