Deployment
Einride Pod at Ohio
Einride's cabless-by-design autonomous electric freight vehicle: it has no cab or driver position at all (purpose-built, not a retrofit of a cabbed truck), operated by the Einride Driver with remote supervision. Range about 130-180 km, up to roughly 16 tonnes. Approved by NHTSA to operate on US public roads.
Einride Pod by Einride · Operated by EASE Logistics · Catalog entry · 2 sources · not yet field-verified
Recent coverage
- Autonomous freight developer Einride goes public via SPACAgentRecon · 2026-06-18
- Einride goes public and sees strong surge on trading debutAgentRecon · 2026-06-11
- Einride's cabless trucks hit Ohio roads in EASE Logistics trialAgentRecon · 2026-05-18
Machine-readable surfaces
- Markdown mirror: /deployments/einride-ease-logistics-ohio.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/robots/47890b87-4f85-4c95-be1f-99f303bc463a
- Data documentation: /data
- Query this programmatically: Deploy MCP
Footage
Einride's footage of its cabless, electric Pod on a US public road. The cabless Pod is remotely supervised by a human Remote Pod Operator, not unsupervised autonomy.
Einride's cabless electric Pod operating an L4 pilot on Ohio public roads with EASE Logistics (Marysville, OH), remotely monitored, on the ODOT/DriveOhio Truck Automation Corridor.
Key facts
- Operator
- EASE Logistics
- Status
- Cabless L4 pilot on Ohio public roads (DriveOhio corridor), remotely monitored (2026)
- Maturity stage at deployment start
- commercial
Exposure
- Customer segment
- logistics
- Scale tier
- pilot lt10
- Customer
- EASE Logistics
Each exposure value carries its own basis marker. Aggregators report a number; this surface preserves the source class so verification depth travels with the value.
Safety record
No incidents on record for Einride Pod at Ohio.
Only active incidents are counted. Retracted incidents are excluded from this summary but remain reachable at their canonical URLs.
- Trust tier
- Catalog entry · 2 sources · not yet field-verifiedhow tiers work →
- Last updated
- 2026-07-10
- Model
- Einride Pod
- Company
- Einride
- Location
- United States/Ohio
- Operator
- EASE Logistics
- Status
- pilot
- Operator type
- customer deployed
- First seen
- 2026-05-20
- ID
47890b87-4f85-4c95-be1f-99f303bc463a
Timeline
- May 2026First recordedEinride Pod first documented operating at Ohio.
- May 2026created
- Jun 2026field updatedkey facts: unset → Added lifecycle_stage=commercial
- Jul 2026Current status: pilot, reviewedLatest recorded state. New status transitions append here as the deployment-status recorder produces them.
On the deployment map
Einride Pod operates in Ohio. Explore the full verified map:
Sources (2)
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-07-10
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-07-10
Maturity + lifecycle
Maturity stage: commercial
Lifecycle: active
Architectural position
Cohort: truck
Sources by quality tier
- 2
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Einride Pod at Ohio.Common questions
- What is the Einride Pod deployment at Ohio?
- Einride Pod, built by Einride, is recorded as a deployment at Ohio on the DEPLOY registry. EASE Logistics operates the deployment.
- Who operates Einride Pod at Ohio?
- EASE Logistics operates this deployment as a customer of Einride, the manufacturer of Einride Pod.
- When did the Einride Pod deployment at Ohio go live?
- The deployment is recorded as starting May 20, 2026 on the DEPLOY registry. Earlier activity may exist but is not yet sourced.
- Have there been incidents at the Einride Pod deployment at Ohio?
- No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.
Deploy Watch
Track this deployment.
We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.