Page
Dashboard
One screen, updated live. Asset count, online/offline split, hub status, recent alerts, and the utilization trend — re-rendered in place as events land.
The Platform
One pipeline, from the tag on the asset to the chart on your screen.
Echolo ships the whole stack: hardware, firmware, ingestion, storage, and Fleet — the app your team actually logs into. No duct tape between vendors, no finger-pointing at 3am.
Architecture
Track → Stream → Decide.
Three layers. Each one owned end-to-end by us.
-
01 · Track
BLE tags on the asset.
Small, rugged tags pick up every few seconds. No OBD ports, no VINs, no modems on the asset itself.
- BLE 5 · multi-year battery
- IP67, -40°C to +85°C
- Magnet, screw, or VHB mount
-
02 · Stream
Gateways to MQTT, always.
Wired and PoE gateways relay tag beacons to our MQTT broker. Messages queue locally when the site loses connectivity.
- LTE or ethernet backhaul
- Store-and-forward queue
- Hub health telemetry
-
03 · Decide
Fleet on the other end.
Your team gets live equipment status, hour accrual, hub health, and alerts in a single app — plus on-demand and scheduled reports, without waiting on an integrator.
- Live dashboard + site presence
- Alerts + rule engine
- On-demand + scheduled reports
§ 03 / 08
Meet Fleet
Your equipment, assembled in real time.
One pipeline from the tag on the asset to the chart on your screen. Track, stream, and decide — without waiting on an integrator to wire a CSV export.
- Track. BLE tags + gateways across your sites.
- Stream. MQTT pipeline that doesn't drop messages.
- Decide. Alerts, reports, and hours where you'd expect them.
fleet · live
streaming
Fleet · Web
See every screen,
before you commit.
Real views from inside the Fleet web app — the dashboard, an equipment detail page, location management, and AI-driven fleet rightsizing.
fleet · dashboard
live
Fleet · Mobile
And it goes where the work is.
The same platform, in a technician's pocket. Fleet Mobile turns every phone on the job site into a roaming Bluetooth scanner, shows a sunlight-readable dashboard of your fleet, and lets crews scan a QR code to log hours or close out maintenance — even with no signal.
Inside Fleet
What your team actually uses.
8 pages, 4 platform capabilities, 2 AI helpers — with preventive maintenance and service history at the center. Built for ops leads, site supervisors, and the mechanics who keep it running.
Page
Preventive maintenance
Recurring schedules per asset — every 250 hours, every 6 months, or both. Fleet checks them nightly against live hours and elapsed time, and generates the order the moment either interval comes due.
Page
Maintenance orders
Auto-generated service jobs with a checklist, assignee, priority, and due date. Print the QR label, scan it in the field with no login, record the hour-meter reading, mark it done — every completion writes to service history.
Page
Fleet view
Every asset, sortable and filterable. Drill into a device for hour history, location timeline, and its hub handoffs.
Page
Locations
One page per job site. Equipment transfers between locations are tracked and logged automatically, with full move history per asset.
Page
Hub health
Every gateway's battery, signal, last-seen, and firmware — surfaced the same place you look at the assets they watch.
Page
Alerts & rules
Rules for offline detection, hour thresholds, hub failures. Email + webhook delivery. Badges update via Turbo Streams the moment a rule fires.
Page
Reports
On-demand CSV or PDF — utilization, offline, hours summary. Scheduled deliveries to whichever recipients you pick, on whatever cadence fits.
Power
Hour-meter adjustments
Fix a bad offset in one click. The edit propagates to the ingestion pipeline in milliseconds, and every change lands in the audit log.
Power
Audit trail
Every hour-meter adjustment, every alert ack, every report delivery — stamped, stored, and immutable.
Power
Role-based access
Admins, members, and viewers. Site managers see their yards, execs see the rollup, auditors see whatever you carve out. Email-invited onboarding.
Power
API + exports
REST for queries, webhooks for push, CSV/PDF exports for everything else. No data lock-in — if you can see it in Fleet, you can pull it out.
AI
Daily insights
A written paragraph in your inbox every morning — what happened in the last 24 hours, exceptions first. 30 seconds to read, not a dashboard to hunt through.
AI
Report summaries
Every on-demand or scheduled report lands with a plain-English preamble on top. 'Here's what this report actually says' — before the numbers.
New · Maintenance Orders
From a number to a job someone does.
A continuous hour meter tells you the machine is at 490 hours. Maintenance Orders turn that into a scheduled, assigned, signed-off service — on the record, not on a clipboard.
Shipped
Recurring schedules
Set a rule on any asset — service every 250 hours, inspect every 6 months, or both. Fleet checks each schedule every night against live machine hours and elapsed time, and generates the order the moment either interval comes due.
- Hour and/or time intervals, whichever comes first — a machine that runs hard gets serviced on hours, one that sits all winter still gets its annual
- An optional checklist is copied onto every order it generates — one task per line, the same list each cycle
- Completing an order resets the schedule's baseline automatically, so the next one fires after the next full interval. No manual bookkeeping.
Shipped
Orders, assigned and tracked
Each due schedule becomes an actionable job — a title, a checklist, an assignee, a priority, and a due date. Need ad-hoc work that was never on a schedule? Create a one-off order by hand.
- Status moves open → in progress → completed, with cancel for the jobs that fall away
- Tick checklist items off as you go; record the hour-meter reading at service and any notes on completion
- Owners and members are emailed when an order is generated, and again if it passes its due date unfinished
Shipped
Print it, scan it, done
Print a clean label — a QR code plus the asset and checklist, no app chrome. A tech scans it with the Echolo mobile app, the exact order opens on their phone, they record the hour-meter reading and mark it complete. In the field, with no login.
- The QR loads the right order on a phone — no account, no hunting through a list for "Generator 09"
- The reading comes off the hour meter in front of the tech, not someone's memory of it back at the desk
- Every completion writes a permanent entry to the asset's service history — what got done, when, at how many hours
How an order moves
A schedule is the rule. An order is this week's job.
- Triggers
- An hour interval, a time interval, or both — whichever comes due first.
- Checklist
- Defined once on the schedule, copied onto every order it generates.
- Completion
- Records the hour-meter reading + notes, resets the schedule, writes the service history.
- Plan
- Maintenance Orders are available on the Enterprise plan.
The other half of a continuous hour meter · Why we built Maintenance Orders → · See it in the field →
How we use AI
AI, used where it actually helps.
Two features. Both concrete. Both already shipping. No "AI-powered" sticker over thresholds that have been a solved problem since 1998.
Shipped
Daily insights
Every morning, Fleet writes a paragraph about the last 24 hours — equipment movement, alerts that fired, hour accrual, hub-health changes. Short enough to read with coffee, specific enough to act on.
- In your inbox before 8am — the prior day summarized in a paragraph, not a 20-tile dashboard to go hunt through
- Exceptions first: idle assets, missed check-ins, the rule that fired at 2am — surfaced by name, not buried in a chart
- Same structure every morning, so skimming takes 30 seconds once you know the pattern
Shipped
Report summaries
Every on-demand or scheduled report now carries an AI-written preamble — "here's what this report actually says" in plain language, right above the numbers.
- Shrinks the 9am exec read from five minutes of PDF-scrolling to thirty seconds
- Flags the odd rows by name — "S-09 ran hot three weeks running" — so nobody has to hunt for what's off
- Delivered inline with your existing scheduled report, so it arrives where you already read the numbers
What isn't AI
Not everything is a model — and nothing should be when a threshold works.
- Alerts
- Deterministic thresholds. You set them, the rule engine fires them.
- Rules
- Logic you wrote. No hidden 'AI detected anomaly' on top.
- Hour meter
- Continuous accrual from real telemetry. Not estimated, not smoothed.
- Report data
- Computed from your data. The prose gets AI — the numbers don't.
Built on Claude Haiku via the Anthropic API · Our take on predictive maintenance →
§ 05 / 08
Hardware
Four hubs. Pick the one that matches your site.
We picked the hardware. We own the firmware. We debug it when it breaks. No reference designs glued together with middleware.
BLE Hub · Indoor Echolo G1
The indoor workhorse. BLE 5 + WiFi AP in a single box.
BLE Hub · Outdoor Echolo OLR
The outdoor workhorse. IP54, BLE 5 long-range, zero-config.
BLE Hub · Outdoor Echolo MG5
Brings its own network. LTE-M built in, vehicle or solar power.
LoRa Gateway · Indoor LoRa ILH-85
The long-haul hub. LoRa for the sensors BLE can't reach.
See all the hardware
Or tell us about your site and we'll spec the mix. Talk to the team.
Integrations
Plays nicely with the tools you already run.
API
REST
Full-access JSON API. Paginated, cursor-based.
API
Webhooks
Push events to your stack. Signed payloads, retry with backoff.
API
MQTT
Subscribe to the stream directly if you want the firehose.
Cloud
AWS IoT Core
Bridge to your existing AWS IoT pipeline.
Cloud
Azure IoT Hub
Bidirectional for enterprises already on Azure.
Tool
Manager Plus
Hour-meter feed + asset sync for existing asset management.
On-Premise IoT
For environments where data can't leave the network.
Echolo ships as a fully air-gapped appliance for regulated facilities, classified sites, or anywhere the WAN isn't reliable — or as a hybrid edge that runs locally and syncs to the cloud on your schedule. Same platform either way.
- Scales to
- 1,000+ hubs
- Across
- 10k+ devices
§ 08 / 08
Echolo
Want to see it on your fleet?
Twenty minutes on a call. We open Fleet, go through your equipment types, and tell you what a deployment across your sites would take. The person on the call is the person who writes the code.
Request a demo