Controla costos de mantenimiento, cumple con inspección vehicular, y toma decisiones con datos reales. Software profesional de gestión de flotas — gratis para empezar.
Gratis para 3 vehículos
Sin tarjeta de crédito
Datos protegidos
Usado en más de 20 países
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.
▸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
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.
▸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
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
"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 — offensive evidence against dangerous drivers
Sentinel runs in the background on your driver's phone. The harsh-event detector fires when the driver's accelerometer registers a harsh brake, harsh accel, harsh cornering, or a near-miss. Sentinel asks: was there another vehicle in the witness frame? If yes, five forensic signals run against the offender's plate: multi-frame OCR voting, geographic impossibility check, plate manufacture quality analysis, registration status anomaly (DVLA / DMV equivalent), same-model visual fingerprint. Mekavo AI consolidates the 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.
▸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
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
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: Vision for the part scanner, supplier-receipt scanner, scan-a-list, Sentinel plate consolidation, Forward Vision corroboration. Whisper for voice transcription. Anthropic API 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 + Whisper + Anthropic API, swappable via interface
▸Every call logged with cost — honest pay-per-use, no hidden subscription
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.
▸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.
▸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.
▸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
Todo lo que necesita tu flota
Control de Inspección Vehicular
Alertas automáticas de vencimiento de inspección vehicular. Nunca pierdas una fecha límite para ningún vehículo de la flota.
Reporte de Daños
Los conductores reportan daños con fotos desde el celular. Sabes qué pasa antes de que el problema crezca.
Registros Digitales
Se acabó el papel perdido. Mantenimientos, inspecciones y documentos — todo digital, accesible desde cualquier lugar.
Gestión de Conductores
Quién maneja qué. Quién dañó qué. Quién está disponible. Toda la responsabilidad en un solo panel.
Vista General de la Flota
Todos los vehículos de una vez — placa, estado, conductor, costos acumulados. Decisiones rápidas con datos reales.
Historial de Mantenimiento
Cada reparación, cada repuesto, cada taller — registrado. Cuando vendas el vehículo, el historial completo está ahí.
PA
Hecho para Flotas Panameñas
De Ciudad de Panamá a David, de Colón a Chitré — Mekavo ofrece gestión de flotas profesional para empresas panameñas. Ideal para logística del Canal y distribución.
Diseñado para tu sector
Transporte de Carga y Logística
Flotas de camiones, contenedores y logística del Canal. Controla costos por ruta y mantenimiento preventivo.
Construcción
Volquetas, retroexcavadoras, camionetas. Verificaciones diarias y control de costos en obra.
Entregas y Última Milla
Motos y carros de reparto. Minimiza tiempos de parada y maximiza entregas. Ideal para PedidosYa, Uber Eats.
Transporte de Pasajeros
Diablos rojos, Metro Bus, taxis, Uber e InDriver. Costo real por vehículo y control de mantenimiento.
Sector Público y Municipal
Flotas gubernamentales y municipales. Transparencia, reportes y control de gastos públicos.
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.
Construido para los reguladores con los que las flotas panameñas realmente lidian
Un control ATTT en ruta, una revisión técnica reprobada en un centro autorizado, una inspección MITRADEL tras un accidente laboral con vehículo de la empresa — todas exigen lo mismo: prueba contemporánea y a prueba de manipulación de la inspección pre-operacional y la asignación del conductor. Mekavo sella cada registro en el momento de la captura.
ATTT
Autoridad del Tránsito y Transporte Terrestre
Marco regulatorio del transporte terrestre, autorizaciones para transporte comercial de carga y pasajeros, registro vehicular y la red de Centros de Inspección Vehicular.
PNP/Tránsito
Dirección Nacional de Operaciones del Tránsito (Policía Nacional)
Fiscalización en ruta, control de licencias de conducir y aplicación del reglamento de tránsito.
MITRADEL
Ministerio de Trabajo y Desarrollo Laboral
Aplicación del Código de Trabajo y la Ley 51 de 2005 (Riesgos Profesionales) — incluye operación de vehículos y responsabilidad personal del empleador.
COPANIT
Comisión Panameña de Normas Industriales y Técnicas
Normas técnicas para vehículos comerciales, criterios de revisión técnica y reglamentación que los centros aplican.
DGI
Dirección General de Ingresos (Ministerio de Economía y Finanzas)
ITBMS sobre operaciones de flota, facturación electrónica, deducción de gastos operativos y depreciación de vehículos comerciales.
Los operadores deben asegurar la aptitud para circular a diario; la revisión técnica cubre la aptitud periódica. Mekavo sella cada inspección pre-operacional con fotos, geolocalización, kilometraje e identidad del conductor. El sello es verificable independientemente — ATTT, MITRADEL o peritos judiciales pueden reverificar sin confiar en el operador.
CANCELACIÓN DE AUTORIZACIÓN ATTT / RETENCIÓN
La detección en ruta de revisión vencida, autorización ATTT expirada o un defecto mecánico crítico lleva a la retención inmediata. ATTT puede cancelar la autorización tras reincidencias. Las investigaciones MITRADEL pueden derivar en responsabilidad personal del empleador después de un accidente laboral con vehículo.
● En investigaciones MITRADEL y demandas civiles ante los juzgados panameños, la exigencia estándar es la bitácora de inspección pre-operacional emparejada con el plan de mantenimiento. Una bitácora completada después del hecho no resiste el contraste pericial. Un registro sellado en SHA-256 con fotos vinculadas por EXIF y la identidad del conductor verificada por OTP sí — y la reverificación es independiente del operador.
Precios sencillos para flotas
Empieza gratis. Escala a medida que creces.
Aún no hay precios locales para PA — se muestran precios del Reino Unido como referencia. Puede haber precios locales al registrarse.
Regístrate gratis. Elige tu sector — configuramos automáticamente las plantillas de inspección correctas.
2
Agrega vehículos y conductores
Agrega los vehículos de tu flota, invita a conductores y gestores. Asigna vehículos a conductores.
3
Inspecciona, reporta, mantén el cumplimiento
Los conductores hacen controles diarios desde su móvil. Los defectos se detectan al instante. El panel de cumplimiento muestra el estado de tu flota.
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.
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.
