Payload System Architecture

Explore the services, applications, infrastructure, and job flows that make up the Payload ecosystem.

Ecosystem

click any subsystem for detail
Dump Truck industry · services Built inside the industry. New industries define their own services.
Dump Truck

{{ sys.name }}

{{ sys.role }}

{{ sys.tagline }}

{{ sys.rel }}

Payload Exchange

Foundation Industry-agnostic

The shared job, marketplace, telemetry, and orchestration layer. It belongs to no single industry — it serves all of them. Payload services own their user-specific experience; the Exchange owns the shared truth about jobs.

Service pattern

not every product has every part
{{ h }}
{{ row.name }}
{{ cell.text }}

Industry layer

Dump Truck · Live

Dump Truck is an industry implementation running on Payload — not the definition of Payload itself. Future industries reuse the same Exchange.

{{ c }}

External integrations

Future

The Exchange is designed as a platform: third-party construction, TMS, logistics, and fleet software could eventually post jobs, discover jobs, and claim capacity.

Job marketplace

supply and demand meet in the Exchange
Customer
Demand
creates jobs
Exchange · Job Marketplace
Jobs can exist without an assigned driver or organization.
{{ c }}
claims jobs
claims + posts jobs
Driver
Supply
Dispatch
Supply + Demand

Job revisions & approval

{{ step.n }}{{ step.label }}

Explicit approval on both sides prevents silent job changes.

Money boundaries

Exchange → Driver
Payload can invoice the customer, collect payment, and pay out the owner-operator quickly — earning a transaction fee (currently directionally ~10–15%).
Exchange → Dispatch → its drivers
The Exchange pays the dispatch company for the job. What that company pays its employees or contract drivers is internal and decoupled from Exchange job revenue.

Job execution

“Deliver gravel to a construction site at 2:00 PM.”
Step {{ activeStep.n }} · owned by {{ activeStep.owner }}

{{ activeStep.label }}

{{ activeStep.detail }}

Anchor step scheduling

One step must happen at a fixed time. The Exchange arranges the surrounding schedule around it.

{{ row.time }} {{ row.label }} {{ row.note }}

Industries

each industry defines its own job types on the shared Exchange

Dump Truck

Live

The implemented industry. It defines its own job types, vehicle configurations, and supply-chain concepts on top of the shared job model — an implementation running on Payload, not the definition of Payload itself.

Job types
{{ j.name }} {{ j.scope }}

{{ j.body }}

{{ b }}
Vehicle types
{{ v.name }}
{{ v.body }}
Industry concepts
{{ d.title }}
{{ d.body }}

Shared job shapes

every industry implements its own

An open job exists in every industry — book a driver for a period of time at a work site. But each industry's open job is its own job type: a Dump Truck open job books a truck configuration, while an Excavating open job would book different equipment and different on-site work. The Exchange holds the shared model; the industry defines the specifics.

Conceptual future industries

examples only · not implemented
{{ f }}
own job types
{{ statusPrefix }} {{ statusLine }} Live Active development Planned