Autonomous heavy equipment
Autonomous machines that work alongside people.
mule.bot builds three systems for autonomous heavy equipment. Iron Context knows the job: the sites, the work and the machines, read from public records, training books and the makers' sheets. Hitch is the autonomous system: it plans the work and runs the fleet, with AI in the decision seats and a deterministic safety layer beneath. The Iron Table proves every run on simulated ground first. We consult with the same tools.
Why
Half the workforce retires within the decade.
More than half of the heavy-industry workforce retires within the decade. Fewer people will supervise more machines, and those machines will work near people.
Large-fleet autonomous haulage serves mines with fifty trucks or more, on a single vendor's closed system. Mid-tier sites cannot buy that. They are a countable set on the federal register, and no one is building for them.
Iron Context
Three systems above the machine.
Iron Context holds what a fleet has to know: the sites, the work and the machines. Hitch is the autonomous system that plans the work and runs it. The Iron Table is the simulation every run is proven on.
The whole architecture is drawn at ironcontext.si: pick a system there to see what it does.
Iron DetectorIron Context · sites
Every mine, quarry, earthwork, landfill and cargo dock is on a public register. We join the registers to aerial imagery, draw each site, and count the machines working on it.
Iron CurriculumIron Context · plays and test tracks
What a competent crew does, in what order and under which rules. We read operator training courses, operating procedures, codes of practice and standards, and write them down as plays, each cited to its source. A play is run on a test track, a site reduced to the one thing the play has to get right, before it is trusted on a site.
Iron YardIron Context · machines
The machine roster: dimensions, limits and 3D models read from the makers' published specification sheets. Each model is rigged at its working joints (boom, stick, bucket, blade, body, articulation, tracks), so it moves the way the machine moves.
BlockModelHitch · the supervisor
The site as blocks, and the supervisor that works from them: the plan, the day's targets, mission dispatch, fleet state and the operator's screen. It runs at the site or in the cloud, and AI can work in it beside the operator.
Iron TacticsHitch · on each machine
The computer on each machine. It takes the work order, picks the play, plans the path and drives it, and AI can run in its planning and perception. The gain from autonomy is in hours recovered, not in cycle time.
Iron ReinsHitch · the safety controller
The safety-rated controller on each machine. A command from a person or from an AI is treated as unsafe until Iron Reins has checked it against the boundaries and the stops. It is deterministic, no AI runs inside it, and it has the final say on motion.
Iron TableSimulation
The site in three dimensions, live: a real-time strategy style interface for running Hitch, and a record and a film of every run. Under it, Iron Pit models the ground, the machines that work it, and the sensors on those machines.
Figures counted from our repositories on 11 November 2026. Ask for any of them and we will show the source.
Hitch · how we do it
The full system, less the machine.
Hitch is an ISO 17757 compliant architecture for autonomous work beside manned machines, based on the standard and on thirty years of architecture work in heavy mobile autonomy. It connects to your machine or your system, and provides as much as the whole system less the machine, or as little as the one interface your product needs.
It has four parts. BlockModel is the supervisor: mission release, the operator's surface and the plan. Iron Tactics is the computer on each machine: it picks the play, plans the path and drives it. Iron Reins is the safety controller on each machine, and holds stop authority. Site devices are the control room, the stop stations and the units manned machines carry. AI has a seat in BlockModel and in Iron Tactics; Iron Reins is deterministic and checks every command before a machine acts on it. It is written from the top down and every level is tested.
Concept of operations
The mission, the site use cases, the operating modes, and the operational design domain: where the system may work, in what conditions, and beside whom.
Requirements
Market requirements at the top, product requirements for each of four systems beneath them, technical requirements beneath those. Each traces up to its source and down to its test.
Hazards, and the safety case
Six hazards anchored to the industry's collision scenarios, analyzed by two methods, with five safety goals and the functional safety requirements that follow from them.
Safety functions
Perception, corridor broadcast, spatial enforcement, remote stop, stop arbitration, command authority, and operating-condition monitoring. They decide what the machine will and will not execute.
Function blocks and interfaces
Four systems: Iron Tactics on the machine, Iron Reins the safety controller, BlockModel the supervisor, and the communication network. The interface documents between them are where another product connects.
Tests
From the single function block up to the site scenario, each tied to the requirement it checks. The planners and trackers carry 2,800 more. The specification runs as code.
Where you fit
Hitch is the rest of the system: safety functions, planning, supervision and the operator's surface, above your drive-by-wire.
Your autonomy runs the machine. Take the parts you do not have: the supervisor system, the safety functions, the planners, or the test tracks.
We connect at the interface your product defines, and build as much of that interface as the product needs.
Developed to align with ISO 17757, ISO 13849-1, ISO 23725 and IEC 61784-3. No third-party assessment is claimed.
Consulting
We bring the tools to your site.
We take on work for operators and for the teams that build autonomy, and we do it with the tools above. You get the answer and the records behind it.
You keep the machine: control, perception, path following and the retrofit kit stay with your team. The site and the autonomy team both sign the safety case.
What we take on
- Site and market screeningTarget sites, fleet counts and operating conditions for a region or a commodity, drawn from public records. Iron Detector.
- Operations scenario analysisYour operation modeled as it runs, a change proposed, and the two compared before money is spent. Iron Tactics, BlockModel and Iron Table.
- Autonomy validationA track built from your customer's site, recorded runs, a scenario coverage matrix, and a trace from each scenario to a safe state. Iron Curriculum's test tracks, the Iron Table and Hitch.
- Safety engineeringThe hazard analysis, the requirements and the safety case, developed to align with ISO 17757 and the standards around it.
- Deployment planningSite readiness, specification, operating boundary, field testing, commissioning. Each stage ends with a signed gate.
Who we are
Thirty years in heavy mobile autonomy.
Across mining, construction and heavy civil, and port and rail logistics. Drills, explosives loading, haulage underground and on the surface, earthmoving, and cargo handling. On the vendor side and as the owner's independent reviewer. Architecture at Pronto.ai, SafeAI and ASI/Epiroc, for mines, quarries and port terminals. The owner's independent check on Caterpillar and Komatsu deployments. A doctorate in functional safety for heavy mobile autonomy.
Partners
Track record
- 8 of 10Between them, the partners have delivered services and products to eight of the ten largest aggregates producers in the United States.
- 30 yearsSome of those producers have been customers for more than thirty years.
- Beyond the pitAutonomy for construction and heavy civil earthmoving, and for port and rail yards.
- TodayOur tools are being delivered under contract to public and private aggregates producers and autonomy companies.