Trust before autonomy
Class compliance, defense security, grounding, audit, human-in-the-loop and graduated control. The level is a dial the yard turns, and a class-critical seam is the last thing it re-orders.
Hullira exists to give every shipyard a system that runs cutting, welding, fairing, coating, outfitting and erection itself, to class spec, on schedule, with less rework and dock time, and to capture the craft of a retiring welder and shipwright workforce before it disappears. The vision is to become the autonomous operations layer for the world's shipbuilding and ship repair.
So yards can meet record order books despite a shrinking skilled workforce.
VisionBecome the system of action for the world's shipbuilding and ship repair: every plate cut, every block welded, faired, coated and erected, and every hull class-assured on Hullira.
The fact on the yard floor that started it.
Ships carry about 90% of world trade and underpin every navy's deterrence, and yards are being asked to build more of them than they have in decades. Yet building a ship is still one of the most craft-bound and schedule-critical heavy industries on earth. A single hull block can weigh hundreds of tons, welds run to hundreds of kilometres per vessel, coatings cover millions of square metres, and the dock a block sits in rents for six figures a day.
Most yards run this on paper travelers, manual measurement, periodic surveyor inspection and the craft of a retiring welder, fitter and shipwright workforce. CAD/CAM plans. A welding robot runs one program. A scan tool measures. An NDT house inspects after the fact. An MES monitors. Nobody closes the loop.
The principles we work by.
Class compliance, defense security, grounding, audit, human-in-the-loop and graduated control. The level is a dial the yard turns, and a class-critical seam is the last thing it re-orders.
Every supervised correction trains the system. The closed-loop chain from weld to scan to coating to erection to class outcome is the asset.
One process, one metric, one baseline agreed in writing. Then the yard. Then the group.
Every answer from the reasoning layer carries its source. Every action carries its evidence and its envelope.
Drawings, WPS, naval data, models and memory never cross a customer boundary. Defense and ITAR-aware; on-prem for those who need it.
Figures are design targets until they are measured. Scenarios are labelled scenarios. Class rules are cited, not claimed.
For anyone checking eligibility or category.
Every Hullira run is an ordered, inspectable sequence. This is run_4b7e19 on Block B-214 · double-bottom block · panel line PL-2 · dock D1. Scenario completes in 10 steps with one approval gate. Predicted distortion at the erection joint fell from 4.2 mm to 1.8 mm after a back-step sequence, one porosity precursor on seam S-31 was cleared inside the WPS envelope, the ballast-tank coat ran inside a 3.4 °C dew-point margin, and the block landed at 1.6 mm with its conformance record written.
Yard Orchestrator · Pulled the work package for B-214 from the yard MES: 46 plates, 212 seams under WPS-117, erection tolerance 2 mm at the D1 joint, PSPC-grade ballast-tank coating, erection slot on D1 in the dock plan. Locked the qualified WPS envelope and the class scope.
Ship Twin · Simulated 18 candidate weld sequences on the as-built twin with the weld-thermal surrogate, ranked on predicted distortion at the erection joint, crane reach on D1 and shift takt. Standing sequence predicts 4.2 mm; candidate #6 predicts 1.8 mm.
Cut-and-Profile · Released the nest for 46 plates on CL-1 with the fit-up gaps candidate #6 assumes. As-cut geometry logged per plate and handed to the panel line; material yield 91.4% against the nest plan.
Panel-and-Weld · Loaded the back-step sequence for the non-critical seams on PL-2 and set heat input and travel speed inside WPS-117. Weld-pool and seam cameras streaming on 12 channels.
Yard Orchestrator · Candidate #6 also re-orders two class-critical butt seams, S-31 and S-32. Sequence changes on class-critical seams stay with a human, so the step was held for the shift welding engineer and approved at 06:12:44.
Quality-and-Anomaly · Twelve weld cameras and the UT station fused at the yard edge. One porosity precursor on S-31 at 06:41 flagged and cleared by a 4% wire-feed trim inside the WPS-117 envelope; the joint was routed to UT and passed.
Fair-and-Form · Post-weld scan registered against the twin: 2.1 mm at the erection joint. Two line-heating passes planned on the inner bottom and executed by the fairing crew; re-scan read 1.8 mm, inside the 2 mm tolerance.
Blast-and-Coat · Ballast-tank blast and first coat scheduled to a window with steel temperature 3.4 °C above dew point. Dry-film thickness read 312 µm against a 280 µm minimum on the stripe coats; PSPC evidence assembled per area.
Schedule-and-Yard · Re-solved the D1 dock and crane plan with B-214 ready 6 hours early and a neighbouring block late: erection slot pulled forward one shift, crane G2 reassigned, no berth conflict. Planner approved the revised plan.
Erect-and-Align · Both blocks scanned on D1 and registered against the twin; fit predicted at 1.6 mm. Shimming guidance issued to the erection crew, block landed and welded out, final scan 1.6 mm. Conformance record written: welds, scans, coating readings, approvals and class evidence for B-214.
Figures are the company's own estimates.
Hullira is led by its founder and CEO, Edward Griffin, and its CTO, Kyle Emerson. The profiles below describe what each of them owns and the ground they cover.
Founder & CEO
Edward runs the company and owns the design-partner relationships, the pilot structure and the commercial model. He decides which shipyard and which production stage go first, what weld-quality, rework, accuracy-control or schedule number a pilot is judged on, and who at the yard signs off on the baseline.
Focus: shipbuilding and ship-repair operations, yard economics, partnerships and go-to-market.
CTO
Kyle owns the yard-edge runtime, the welding, cutting, fit-up and coating models, the weld and dimensional inspection, the as-built ship digital twin, and the audit architecture behind every Hullira agent. He is accountable for the bounded, logged write-back into welding and cutting robots and yard controls, and for every agent starting in shadow mode.
Focus: edge computer vision, robotics and welding control, simulation and digital twins, safety-critical industrial software.
The founding roles we expect to open are on the careers page: edge perception, controls and OT integration, simulation, and a welding or accuracy-control engineer.
A dry dock rents for six figures a day. One warped hull block can cost weeks of it. Most yards still find out at the lift.
A yard does not go from paper travelers to unattended welding in one step, and a class-critical seam should not be the first thing an agent re-orders.
Yards commit a block, a crew and a dock slot before they know the block will fit. The twin changes the order.
A weld pool is decided in milliseconds and a dock waits by the hour. Perception has to be local, deterministic and fast, so Hullira runs GPU inference at the yard edge and keeps training, simulation and optimisation in the cloud or on-prem.
6 to 24 cameras per process area plus UT, X-ray, thermal, laser-scan, photogrammetry, robot and coating-instrument streams fused at the yard edge. Sub-50 ms weld alerts and sub-150 ms coating or scan prompts are the design targets. Jetson Thor is planned for higher camera density.
Weld-defect, distortion-risk, coating-risk, point-cloud and schedule-risk models behind one orchestrator at the yard edge, versioned with rollback, routed by latency, tenant, sensitivity and cost.
Weld-defect vision, UT and X-ray classification, NeMo class-rule reasoning and weld-thermal FEA surrogates fine-tuned per tenant: 100 to 500 GPU-hours per yard during onboarding, then monthly retraining from engineer corrections and class outcomes. Dedicated training capacity is planned.
Block erection, weld sequence, robot reach, crane paths and yard layout simulated before the shift, as-built against as-designed. GPU weld-thermal and structural FEA is the workload; physics-informed surrogates rank plans at shift cadence.
Rare weld defects, coating failures, distortion modes, occluded seams and erection misalignment cases generated and validated against real NDT and scan distributions before promotion. 50k to 250k variants per vessel class is the target. Planned.
Dock, crane and berth schedules, work-package sequencing, yard logistics and erection order, re-solved as progress changes.
Robotic weld, blast, coat and inspection cells and crawler or drone hull inspection, with paths validated in simulation before they run next to a hull.
Telemetry ETL across weld parameters, scans, NDT results, coating readings, non-conformance and schedule history, for retraining, drift detection and rework, dock-time and schedule benchmarks.
WPS and PQR, class-rule, PSPC, cyber and human-approval policies enforced before any action writes back to robots, MES, QA or work packages; retrieval with citations and tenant isolation.
Hullira writes to production equipment. Every capability is scoped, every write is policy-checked against the qualified WPS, class and PSPC constraints, and every action is written to an append-only audit log the yard owns.
| Item | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | QUEUED Planned, first 6 months, with a defense and ITAR-aware review |
| SOC 2 Type II | Cloud control plane | QUEUED Planned, 6 to 12 months |
| SSO and RBAC | Console and approvals | QUEUED Planned, 6 to 12 months |
| Class-society and defense assurance packages | Disposition and genealogy evidence | QUEUED Planned, 6 to 12 months; not a class approval or certification claim |
| Cited reasoning | WPS and PQR, ABS, DNV, LR, ClassNK, IMO PSPC, naval specs | RUNNING In the design, every answer cites its source |
| Per-tenant and IP isolation | Drawings, WPS, naval data, models, memory | RUNNING In the design from day one |
| On-prem and yard-edge deployment | Naval and regulated yards | RUNNING Design option |
The questions production directors, welding engineers and class-compliance leads ask in the first meeting.
Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, inside the qualified WPS, coating, dimensional and schedule constraints, and only at the autonomy level your yard has set. Design partners start in shadow mode, where Hullira writes nothing. Class-critical seam changes, lift plans and block release stay with named people.
Control returns to the robot controller, PLC or planner's last known-good state. Hullira is a supervisory layer on top of the controllers and interlocks you already run, never a replacement for them, so an outage degrades the process to its current way of running, not to a stop.
Advisory recommendations start from the physics-based twin, the WPS and the block drawings in the first weeks. Defect, distortion and coating prediction improve as block history and labelled NDT and surveyor outcomes accumulate. Onboarding is sized at 100 to 500 GPU-hours per yard and 50,000 to 250,000 synthetic variants per vessel class, both design targets.
Only if you choose cloud training. Drawings, WPS and PQR, naval data, process models and quality records are isolated per tenant and never used to train another customer's models. Security is defense and ITAR-aware, a fully on-prem deployment at the yard edge is available for naval and regulated yards, and federated learning across yards is planned and waits on data-rights agreements.
You are, the same as with any procedure change, which is why every write is policy-checked, bounded, logged and reversible, and why anything above your risk threshold waits for a named approver. The audit log records the request, the evidence, the WPS or class citation applied and the human decision.
A paid pilot on one process, scoped to a single wedge with a success metric written into the order form: weld rework, fairing hours, coating non-conformance, dock days or class-approval cycle time. Shadow mode comes first and the baseline is measured from your own records. We do not publish a pilot length because we have not run one.
↑↓ navigate↵ openesc close