Backbone. The layer between machine fleets and the physical world.

01 // WHAT WE DO

Deploy

01 Engineers in your depot. Weeks, not quarters.

Standardize

02 One spec. One gate per service. Their liability.

Orchestrate

03 Machine to machine. Exceptions to you.

02 // THE STACK

Four layers and one boundary.

Layer 01

The physical world.

Your fleet, your depots, your city. Robotaxis, delivery fleets, shuttles: riders or goods, the vehicles need charging, cleaning, maintenance, staging, and recovery every single day. Nothing here gets replaced. It gets connected.

The boundary

Published events only.

Pulse listens to what your systems already emit. No new hardware on the vehicle, and the driver stack stays sealed, always. This dashed line is the design's first promise.

charger.fault.raisedenergy.session.closedwork.order.closedrecovery.case.closedrelease.granted

Full event taxonomy and data-governance notes shared on request

Layer 02

Pulse. The control layer.

Events come up, decisions go down. Pulse assigns every vehicle its next required action, machine to machine; the assignment lands in your dispatch and your stack drives. Your team stops chasing status and starts commanding exceptions.

Pulse operator command center, the real product

Layer 03

The service network.

Independent providers of charging, wash, maintenance, and recovery, certified once against one published standard per service. That standard is the SLA every operator inherits. They execute and carry the liability. Your capacity grows without new real estate.

Layer 04

Neutral oversight.

For the platform above the operators: one read-only pane, apples to apples across markets. Three numbers: human share of cost, depot throughput, cost per in-service mile, computed against rate inputs each operator supplies. Every view runs under scopes the operator grants and can revoke. Nothing flows down. Operators use the same pane as their own proof of performance.

Pulse network oversight, the real product, fictional operators

One night, narrated · tap to step

03 // READS AND COMMANDS

What Pulse reads. What Pulse commands.

The boundary is not a slogan; it is an interface. Reads come from events the operator publishes; commands run under scopes, revocable API grants from the party that owns each interface: the operator for its fleet, the provider for its own infrastructure.

Reads // published events only

Nothing inside the vehicle.

The interface

Vehicle state events your stack already publishesSTATE OF CHARGE, LOCATION, FAULT FLAGS
Charger telemetryOCPP SESSION EVENTS
Provider job statusWORK ORDER OPEN / CLOSED
Depot floor eventsBAY OCCUPANCY, LANE STATE
Licensed driver? The operator publishesNOTHING REQUIRED FROM THE SEALED DRIVER STACK UNLESS ITS PLATFORM OPTS IN
No event bus? An adapter closes the gapTELEMATICS FEED OR CHARGER-SIDE OCPP AS THE INGEST SPINE

Commands // owner-granted scopes

Nothing without authorization.

The interface

Next-action assignments to your dispatchYOUR STACK DRIVES, ALWAYS
Charger sessions booked and sequencedOCPP COMMANDS
Provider work orders dispatchedCERTIFIED-PROVIDER DISPATCH
Recovery and retrieval dispatchESCALATION SCOPE
Staging release recommendationsOPERATOR PRE-AUTHORIZES BY POLICY OR CONFIRMS PER RELEASE. PULSE EXECUTES

04 // THE OPERATORS

Built by insiders.

The team that ran the ground game for the giants now builds the layer that runs it for everyone.

Ex-Waymo // Operations

AV depot operations, learned inside the fleet that defined them. Our operations leadership ran the ground game at Waymo before building it for everyone else.

Ex-Uber // Engineering

Dispatch engineering at global scale. The systems that route millions of trips taught us how machines should hand work to machines.

The founders

A 60K-vehicle network, built from zero across 22 markets. At MAX we held the CTO, CGO, and President seats: we built the technology that ran the network, not just the business on top of it. Depots, chargers, drivers, uptime, the balance sheet, the battery-swap stations: we carried all of it.

60K+Vehicles operated

22Markets

12Years running fleets

The product starts on the ground because we did.

05 // THE DEPOT, LIVE

Inside it. Then above it.

One depot runs itself. Then the city takes over, and every empty mile back to base becomes a short hop to the nearest service. Shorter is money.

Diagram, not footage

06 // WHERE YOU FIT

Find your seat on the stack.

AV platform

You sit above it.

More revenue miles, less deadhead, depot capacity without capex. Run the network or license the driver into fleets you do not operate: every deployment gets the same certified floor, and one read-only pane shows every operator and market on your network.

You are here: oversight, standing on every floor

Fleet operator

You own the middle.

Pulse embeds in your depot in weeks and runs the loop, whether you run fifteen vehicles or fifteen thousand. Certify your ground once against the published standard and work routes to it: your lots and depots can become certified capacity on the network, at your choice, and you keep your systems, your data, and your platform relationships.

You are here: the world + the control layer

Service provider

You join the network.

Certify once against the standard. Work routes by proximity and certification, never a price auction, and demand compounds with every fleet that joins the stack. Booked, scheduled load you can plan against, not walk-in traffic.

You are here: the service network

Build the driver and run your own fleet? You hold both seats.

07 // THE FILM

Every Mile in Service.

A minute thirty-eight, storyboarded below. One depot turns its fleet through the night and releases it, vehicle by vehicle, as inspections pass under the operator's standing release policy.

F01 · 00:06 A vehicle publishes one event: low charge, 40 miles out.

F02 · 00:14 Pulse books the bay, the charger, and the wash before arrival.

F03 · 00:34 The floor sequences itself. Machines hand off to humans and machines.

F04 · 00:58 Deep night. The work continues in the dark, on schedule.

F05 · 01:14 Dawn. Inspections pass, vehicles release. Every mile in service.

08 // WHY NOW, WHY IT COMPOUNDS

The ground game is the binding constraint.

In 2023 the public robotaxi fleets were pilots; by 2026 they are opening new cities every quarter. Every launch, robotaxi, shuttle, or delivery, needs the same floor: chargers online, bays sequenced, providers held to standard. Building that floor once per operator is the industry's slowest, most duplicated work.

The graph learns

Every published event teaches the operating graph. Depot N+1 inherits what depot N learned about cycle times and sequencing, so it opens faster and runs cheaper. The graph learns process behavior only: aggregated, non-attributable, never anyone's records, never anything from inside the vehicle.

Single-tenant walls

A vertically integrated operator learns from one fleet: its own. A neutral layer learns across every fleet that joins, and no operator's data changes hands. That is the part no one can build alone.

09 // THE STANDARD

Every operator. One gate.

Onboarding

Weeks, not quarters. Week one, map the events your systems already publish. Week two, grant scopes and shadow-run the floor. Week three, the first supervised hands-off shift. Your engineers point the event stream, grant the scopes, and set the release policy; our forward-deployed engineers carry the rest, and in a first-fleet market, certification of your existing local vendors runs alongside those same weeks. Nothing to rip out, nothing new to buy.

The spec

One standard per service, written to be held in the open. Response time, turnaround, quality checks: versioned and auditable. Providers stay certified only while they hold it. The standard is the floor; your contracts can sit above it.

Liability

Providers execute and carry the liability. Backbone owns no depots, vehicles, chargers, or vendors; it orchestrates across them. Liability for each job sits with the certified provider who executes it.

The layer between machine fleets and the physical world.