Electronic Logging Device · 49 CFR Part 395

Compliance you can prove, not just claim.

OM ELD is a heavy-truck logging platform engineered to the letter of FMCSA Appendix A — and verified byte-for-byte against FMCSA's own file validator. Tamper-evident by design. Built to run when the signal doesn't.

Book a demo See the platform
Passed the FMCSA File Validator Append-only records Works fully offline
Built to spec
Appendix A checksums ASCII output file Web Services + Email transfer Self-monitoring · 7 malfunctions EN · ES · SR
The difference is the foundation

Most ELDs store your logs. Ours refuses to let anyone quietly rewrite them.

0
records ever edited in place — every correction is a new, linked entry
2×
certified transfer methods: FMCSA Web Services and encrypted S/MIME email
100%
of duty capture runs on-device — sync is a follow-up, never a dependency
1-tap
roadside DOT inspection mode — transfer or display, no fumbling
The platform

Everything a fleet needs. None of the guesswork a driver dreads.

The same capabilities the big names list — done with the precision an audit actually requires.

Roadside in one tap

A dedicated DOT inspection mode shows the officer 8 days at a glance, or transfers the certified file over Web Services or email — always in English, exactly as the rule demands.

4.9.1 · 4.10.1

Tamper-evident logs

An append-only chain: the original never disappears. Edits and carrier proposals are new entries the driver approves — the inspector sees both the mistake and the fix.

§395.30 · Append-only

Runs dark, syncs later

A native background service on the phone keeps recording through dead zones, OEM battery killers and locked screens. When the network returns, everything catches up — idempotently.

Offline-first core

Self-monitoring, always on

Seven malfunction and six diagnostic checks run continuously — power, sync, positioning, data transfer. Red and amber indicators surface the moment something drifts, not at audit time.

4.6 Monitoring

Carrier portal that respects the driver

Safety staff propose corrections from the web — but the record only changes when the driver accepts on the phone. Full audit trail, no back-door edits, roles that map to real jobs.

Portal · roles

Location without a data plan

An on-device directory of every U.S. town over 5,000 people turns coordinates into “2mi ENE of Marietta, GA” — offline, because a roadside stop rarely has bars.

4.4.2 · Offline geo
How it's built

Three decisions the market's ELDs won't make.

Compliance isn't a checkbox we ticked. It's the shape of the system.

01 / TRUTH

Append-only. No exceptions.

There is no UPDATE and no DELETE path to a duty record — the database itself forbids it. An edit is a new record that supersedes the old one; the original stays, forever, in the chain.

events table → UPDATE denied
events table → DELETE denied
edit = append + supersede
02 / RESILIENCE

The phone is the source of truth.

A thin native core — Kotlin foreground service, Swift CoreBluetooth with state restoration — owns the recording. The cloud is a mirror, not a lifeline. Lose signal for a day and nothing is lost.

native core → journal → canonical store
sync → dual-layer idempotent
offline = normal operation
03 / PROOF

Verified against FMCSA's engine.

Our output file passed FMCSA's own File Validator — structure, section order and every checksum — before a single record left the lab. “Compliant” isn't a promise here. It's a test result.

file check → DEA9 ✓
line + event checks → match
submission → File Received
Where we pull ahead

The same category. A different class of engineering.

Capability OM ELD Typical ELD
Record integrity Append-only chain, edits preserved Editable records, history varies
Offline operation Full capture on-device Partial · cloud-dependent
Data transfer Web Services and S/MIME email Often a single method
Roadside handoff One-tap DOT inspection mode Manual navigation
Compliance evidence Passed FMCSA File Validator Self-attested
Driver languages EN · ES · SR, switch at runtime English-only, commonly
One record, three people

Driver, carrier and inspector — each sees exactly what they should.

Driver · in the cab

Simple by design

  • Big duty buttons; automatic driving detection
  • Live hours-of-service timers and warnings
  • Certify the day with a real signature
  • Correct a missed status with a required note
Carrier · in the office

Oversight, not override

  • Fleet view of hours and readiness
  • Propose an edit — the driver still approves
  • Register vehicles and manage roles
  • Generate certified output files on demand
Inspector · at roadside

Nothing to explain

  • 8-day graph-grid, English, read-only
  • Transfer over Web Services or email
  • Every edit and its original, side by side
  • Checksums that validate on the spot

See the ELD built like it'll be audited.

Book a 20-minute walkthrough. We'll run a real inspection, transfer a real file to FMCSA's validator, and show you the record no one can quietly rewrite.

Book a demo Explore the platform