Stop Fixing Breakdowns. Start Preventing Them.
Baylitx pairs custom edge-compute gateway hardware with a real-time telemetry routing engine — turning passive vehicles into sovereign data nodes. Independent repair shops get live diagnostic streams and deliver proactive, trust-driven service before breakdowns happen.
Rev D gateway node · ESP32-S3 · 26-pin chassis intercept · no OBD-II dependency
The independent bay — not the dealership.
Family shops, multi-bay independents, and specialist garages. The businesses that service most of the cars on the road, using the least of the data those cars produce.
Vehicle data got locked up.
Repair got reactive.
Modern vehicles generate a continuous stream of chassis health data. Almost none of it reaches the shop that actually services the car. The result is an industry that waits for failure — and drivers who only hear from their mechanic once something has already broken.
Dealership data monopolies
OEM diagnostic lockouts route the most valuable information away from the bays doing the majority of the work.
Proactive independent care
One non-invasive node per vehicle turns the shop's customer base into a monitored fleet with a shared source of truth.
The same shop. A different conversation.
Work you scheduled
Trends surface days or weeks ahead of failure, so the vehicle arrives on an appointment instead of a tow truck.
Evidence, not claims
The driver sees the same telemetry the technician does, in plain language, before approving any work.
Customers who stay
A live relationship with the vehicle gives the shop a reason to reach out — and a reason to be trusted.
Photography on this page is third-party stock used for layout purposes and does not depict Baylitx customers, staff, or hardware. Replace with licensed or first-party imagery before launch.
One system. Two halves that need each other.
A custom edge-compute node reads the chassis bus directly; a real-time routing engine turns that stream into decisions a shop and a driver can both act on.
We start where the data actually is.
Not the restricted OBD-II port — the chassis bus itself, intercepted with a 26-pin harness that installs without splicing a single wire.
Inspect either half.
Toggle between the physical intercept and edge-compute layer, and the platform and API architecture it feeds.
Chassis CAN intercept
Custom Rev D gateway nodes and a 26-pin intercept harness bypass the restricted OBD-II port to read raw chassis telemetry directly off the bus.
Edge intelligence & processing
Low-latency firmware parses, filters, and structures high-frequency CAN bus streams on-device, then transmits securely over cellular or a local SoftAP link.
Non-invasive deployment
Engineered for fast installation in customer vehicles with no wire splicing and no voided factory warranties — so a shop can roll units across its whole customer fleet.
Service bay dashboard
Shop owners and lead technicians get a real-time overview of customer vehicle health — automatically turning incoming DTCs and sensor trends into high-margin repair orders.
Plain-English driver portal
Translates complex fault codes and CAN bus telemetry into clear, visual health reports for car owners — full transparency, and long-term trust in the shop.
Cloud & API infrastructure
A high-throughput backend — FastAPI, Supabase data pipelines, automated SMS alerting — paired with a responsive React/Vite frontend for instant telemetry rendering.
Fifteen minutes, no splices, no warranty risk.
The intercept harness sits inline with the factory connector. Nothing is cut, nothing is soldered, and the vehicle returns to stock the moment the node is removed.
That matters commercially as much as technically: a shop can deploy across a customer fleet without asking anyone to accept a modification to their vehicle.
Infrastructure for the market that already does the work.
Independents service the majority of vehicles on the road while OEM diagnostic lockouts siphon off the revenue. Baylitx sells the missing layer — and charges for infrastructure, not for anyone's data.
Market size and independent-share figures as supplied by Baylitx. The gap between the two bars above is the company's entire thesis: the shops doing most of the work have the least access to the data the work depends on.
A majority market with a data deficit
Independent shops service over 70% of on-road vehicles but lose revenue to OEM diagnostic lockouts — a structural disadvantage, not a service-quality one.
Recurring revenue per service bay
High-margin recurring software revenue priced per service bay, complemented by infrastructure tolling on telemetry routing. Baylitx monetizes the pipes — explicitly not user data resale.
Right to Repair, and the demand for receipts
Policy momentum on Right to Repair converges with consumer demand for transparent vehicle ownership. Open telematics is the infrastructure both trends require.
Hardware moat, open-source gravity
Custom edge hardware and a proven chassis intercept are hard to copy; open schematics and developer-first docs pull the aftermarket ecosystem toward the standard.
Sold per bay. Deployed per vehicle.
Every shop that adopts Baylitx brings its own customer fleet with it — the hardware footprint grows through the shop relationship rather than through consumer acquisition spend.
Photography on this page is third-party stock used for layout purposes and does not depict Baylitx customers, staff, or hardware. Replace with licensed or first-party imagery before launch.
Real hardware. Real buses. Real vehicles in the bay.
This is hard tech with a short feedback loop: high-baud-rate bus multiplexing, real-time edge streaming, and desk-to-vehicle hardware validation. Schematics are open, documentation is written for the person who has to build against it, and the firmware and platform teams sit at the same table.
Problems that don't have a library for them.
High-baud-rate hardware bus multiplexing. Real-time edge streaming on constrained silicon. Firmware that has to survive a real vehicle's electrical environment, not a bench power supply.
You will write code in the morning and watch it run on a car in the afternoon. The loop between a decision and its consequence is measured in hours.
Three ways in.
Embedded firmware engineer
Own the node: parse and multiplex high-frequency CAN traffic on constrained silicon, and make it survive a real vehicle's electrical environment.
- ESP32-S3, FreeRTOS, C / C++
- CAN protocol parsing & RS485
- Desk-to-vehicle validation loops
Full-stack platform engineer
Turn raw telemetry into a product two very different users trust: the technician in the bay and the driver reading their car's health report.
- FastAPI, Supabase pipelines
- React, Vite, Tailwind CSS
- Real-time streaming & SMS alerting
Open-source contributor
Bring your own vehicle, your own bus, your own weird edge case. Contribute decoders, harness variants, docs, and dashboards to the shared standard.
- Open hardware schematics
- Decoder & DBC contributions
- Developer-first documentation
Open by architecture, not as a marketing posture.
Open hardware schematics and developer-first documentation are how an aftermarket standard actually gets adopted — and how a shop verifies exactly what the box in their customer's vehicle is doing. Hardware and software synergy is the product; the openness is what makes it durable.
Photography on this page is third-party stock used for layout purposes and does not depict Baylitx customers, staff, or hardware. Replace with licensed or first-party imagery before launch.
To build absolute trust between drivers and independent repair shops — turning reactive breakdown service into proactive, long-term care.