Morpheus Key, OBD-II, and operational WhatsApp

It is the Karvia OBD-II device. It plugs into the vehicle diagnostic port and streams engine telemetry, GPS location, and operational signals to the web dashboard and to Morpheus AI. The device is sold as the Morpheus Key; the Pro subscription covers continuous monitoring per device.

It is plug and play. Connect it to the OBD-II port, usually under the steering column. No professional installation and no extra wiring. On most vehicles it takes less than 30 seconds. Install it only in the vehicle OBD-II port you are authorized to use.

Vehicles with an OBD-II port — typically gasoline models from 1996 onward. Exact compatibility depends on make, model, and the protocol each unit exposes. We confirm the fit during the demo or when you pair each vehicle.

Engine and operating telemetry (OBD PIDs and signals), diagnostic trouble codes, GPS location, speed, and events relevant to vehicle health. On the Pro subscription the dashboard shows near real-time diagnostics (dozens of PIDs depending on protocol), Vehicle Health Score, fuel consumption, and predictive alerts.

The device can be purchased outright or provided under a loan (comodato) agreement, depending on the commercial terms. Under a loan agreement, Karvia keeps ownership while the contract is active. It must be used only in authorized vehicles and in the OBD-II port. Exact terms are confirmed at signup or during the demo.

Soft-launch (English / US checkout): Morpheus Key from $199 USD ($149 at 5+ devices). Karvia Pro from $49 USD/device/month (volume down to $35). Free plan for up to 2 vehicles — see /en/pricing and /en/shop. Mexico list prices are in MXN at /pricing ($399 Pro / $1,799 OBD). English shop checkout charges USD via Stripe (US); Spanish shop charges MXN (Mexico).

It is the Karvia copilot. It reads telemetry and incidents and turns them into actionable context. It runs mainly through operational WhatsApp and the web dashboard Actions inbox (Acciones). Recommendations are operational guidance and do not replace a certified mechanic or a shop diagnosis.

Karvia sends alerts and recommendations by WhatsApp (Twilio) when a number is linked, and into the Actions inbox (Acciones) on the web dashboard; email follows your preferences. The loop is Detect → Alert (WhatsApp or inbox) → Act → Verify with vehicle signals. You can mute or re-enable alerts with control phrases on WhatsApp when your account allows it.

WhatsApp is the operational channel for alerts and context. Fleet managers use the web platform (dashboard, Actions inbox, live GPS, maintenance). There is no native Karvia app on the App Store or Google Play.

Sending an alert is not enough. Karvia records the recommendation and the follow-up, then confirms with OBD readings and fault codes (DTCs) that the issue is actually resolved. You close incidents with evidence instead of an "alert sent" timestamp.

Yes. Diego (operations), Héctor (engine), Elena (documents), and Andrés (driving) work as a team on the same conversation. You ask on the dashboard or WhatsApp; if the topic changes, the next one continues without you repeating the context. Details: /en/copilotos.

They are Karvia’s copilot team. Diego sees the fleet (health, alerts, location). Héctor reads the engine and builds the maintenance plan (operational guidance, not a shop diagnosis). Elena watches policies and papers. Andrés gives a driving tip. One conversation, four jobs. See /en/copilotos.

On OBD/GPS monitoring, your unit’s history (trips, fault codes, service logs), and statistical baselines for that vehicle. DTCs are labeled with an SAE J2012-style catalog; preventive intervals are class-oriented heuristics. Karvia is not a NOM compliance engine and does not index OEM manuals as source of truth. Norms such as NOM-167 (OBD verification) or NOM-068 (federal physical-mechanical condition) apply to the vehicle, verification center, or permit holder — we help you operate and document; we do not issue a dictamen (official finding) or hologram. Guidance is operational and does not replace a shop diagnosis.

Both. Fixed thresholds cover idle (~5 min), harsh brake/accel, battery voltage scales, fuel anomalies, operating-hours windows, and documents. In parallel, Morpheus and the OBD monitor learn each unit’s normal behavior (~30-day windows, z-score style deviations) and adjust predictive-signature confidence. You can also define custom alert rules. On brakes: today that means driving stress / inspection recommended — not pad thickness in mm or certified remaining useful life.

Creation and delivery (Actions inbox, email, and WhatsApp per preferences) are automatic. Karvia does not run a human NOC that approves each alert before it fires. Your team runs the loop in Actions and WhatsApp: acknowledge, resolve, or dismiss alerts (Morpheus/OBD, documents, geofences, place visits, trip insights, custom rules, and more), confirm findings with telemetry (e.g. battery), and use the copilot for context. After acknowledgment, the system can re-check OBD data and close Detect → Verify when the condition is gone.

Yes. With a Morpheus Key plus the Pro subscription you get live location, route history, and geofences with entry and exit alerts (including schedules when configured). Alerts land in the dashboard and, depending on the event and your settings, by email or WhatsApp.

Light and mid-size commercial fleets — from a handful of vehicles to operations with dozens of units — that need less unplanned downtime and a clear detect → act → verify loop. Individual vehicles can also start from the shop or the limited free plan.

GPS answers "where is it". Karvia adds a team: Diego (operations), Héctor (engine), Elena (documents), and Andrés (driving). WhatsApp recommendations and close-out with engine readings and fault codes. The map is part of the control center, not the whole product. See /en/copilotos. For ELD / hours-of-service claims, see the Standards section below.

No. Karvia is monitoring and operations software (web dashboard + WhatsApp). We are not a Unidad de Verificación (verification unit) and we do not issue holograms, constancias, or NOM dictámenes. Norms such as NOM-167 (OBD/emissions verification where applicable) or NOM-068 (federal physical-mechanical condition) apply to the vehicle, an accredited verification center, or the permit holder. We help you operate and document; the authority or UV issues the legal act.

Practical prep path (not a stamp): (1) In Actions (Acciones) close alerts and review “why it fired.” (2) Keep service logs and documents (registration card / plates) current. (3) In Reports → NOM prep (or Actions) export the Inspection packet — it includes a NOM prep map with gaps and linked evidence; take it to your UV or internal audit — it is not a dictamen. (4) Ask the copilot (web or WhatsApp) “Am I ready for NOM-068?” or “prepare inspection”: it uses the compact map and tells you what still needs documenting. NOM-167: OBD/DTCs are informational. NOM-001: upload expiries you enter. The UV/authority issues the legal act.

NOM-068 requires the unit to be in proper physical-mechanical condition and verified as required; maintenance and logs are the operator’s duty. NOM-167 (where it applies) uses onboard diagnostics (OBD/SDB) in environmental verification. Karvia reads OBD/GPS telemetry and stores history/logs. From Actions you can export an operational evidence packet with a NOM prep map (gaps and linked evidence — not a compliance score), explicitly labeled as not a dictamen — it does not replace the official inspection or the UV’s legal act.

Fault codes are labeled with an SAE J2012-style catalog; OBD PID/mode language aligns with the SAE J1979 / ISO 15031 diagnostic protocol family — that is protocol vocabulary, not “Karvia is SAE-certified.” We do not claim ISO 20078 (ExVe) certification today; OEM data via ExVe is a future path separate from aftermarket Morpheus Key.

No. Harsh-braking or “brake stress” alerts are operational coaching (inspection recommended) from telemetry and driving events — not pad millimeters or certified remaining life. A measurable wear model would need dedicated sensors (e.g. high-rate IMU) and calibration against real measurements; until then we do not offer TTF.

Not as the Karvia product. Morpheus Key uses Geometris hardware (whereQube family) for OBD/GPS telemetry into the web dashboard and WhatsApp. Geometris does offer platforms (e.g. whereQube ENG) designed for U.S. ELD when paired with third-party hours-of-service (HOS) software registered with FMCSA — that is a hardware+app electronic log stack, not Karvia. Karvia does not produce ELD/HOS logs, is not an FMCSA-listed ELD provider, and is not a NOM-087 (Mexico driving-time/rest) compliance product. Operating hours and geofences are internal controls; they do not replace legal driver logs or SICT audits.

Available now: this FAQ with honest language on NOM, SAE, ELD, and brake pads; in Actions you can see why an alert fired (fixed rule vs baseline) and export an operational evidence packet with a NOM prep map, labeled as not a dictamen; the copilot summarizes gaps via web/WhatsApp. Later (not available yet): informational OBD prep with UV partners; brake-wear estimates only with hardware/calibration and published error; OEM data via ExVe for selected fleets; declared weight/config fields (NOM-012 educational). At no step does Karvia become the UV.

It is a prep and operational-evidence tool — not a compliance stamp. It helps you document maintenance, OBD faults, documents, and operations (evidence packet with NOM prep map / Actions) for themes such as NOM-068 (federal phys-mech) or NOM-167 (OBD verification where applicable), and track registration-card/plate expiries you enter (NOM-001 — customer-entered dates). NOM-194 (safety devices on *new* light vehicles) is an OEM go-to-market duty, not the SaaS. NOM-012 (weights/dimensions) is not something we certify; educational tips use existing fleet/usage data (declared weight fields later). NOM-034 is road signing (infrastructure), out of scope. NOM-236 (light phys-mech) was cancelled in 2022 — do not treat it as current source of truth. Karvia is not an ELD or a NOM-087 product. The authority or UV issues the legal act.

Identification and contact details, vehicle data (including VIN and OBD data where applicable), GPS location, speed and driving patterns, and copilot query history. We do not request sensitive data categories. Full detail is in /en/privacy.

Karvia operates under Mexican data protection law (registered in Mérida, Yucatán). You can request access, rectification, cancellation, or objection (ARCO rights) by writing to soporte@karvia.mx; we respond within 20 business days. You may also escalate to the Mexican data protection authority (INAI) where applicable.

Cloud infrastructure (Google Cloud), AI models for the copilot (Gemini / Vertex AI), WhatsApp messaging via Twilio when you enable it, and payment processors when you buy hardware or a subscription. The current list is in the privacy policy (/en/privacy).

We protect access and data with TLS in transit, encryption at rest where infrastructure applies, JWT authentication (no demo tokens in production), secrets in cloud Secret Manager, a CORS allowlist, auth rate limits, role-based access (RBAC) in the dashboard, telematics/payment webhooks that reject invalid signatures in production, and secret scanning on code changes. No system is fully invulnerable — report incidents to soporte@karvia.mx. Detail in /en/privacy.

Book a 30-minute demo at /en/book-demo to review your operation with real numbers, or buy and pair Morpheus Keys from /en/shop. You can also compare plans at /en/pricing and see the Detect → Verify loop at /en/fleet.

The Pro subscription is month to month. You can cancel from the dashboard or by contacting support, under the terms in effect when you signed up. Hardware purchases and loan agreements are governed by the terms of service.

Shipping is free within Mexico, usually 3 to 7 business days. For deliveries outside Mexico, contact the team and we will confirm options and timing before you order.

Email soporte@karvia.mx. Karvia is based at C20 235 609, Fracc. Altabrisa, Mérida, Yucatán, Mexico. For commercial conversations use /en/book-demo or /en/contact.