Boltz AI · Generative Inverse Design

Generative inverse design for physical and engineered systems.

Boltz learns an AI map from achievable outcomes to the designs that deliver them — trained on your engineering evaluators, not a historical corpus. Specify the performance you need; get back a library of diverse, feasible, physics-verified designs.

01 · THE PROBLEM

Forward design commits early and learns late.

Traditional engineering makes the problem manageable by freezing an architecture first — then explores and validates designs only within that narrowed space, one at a time.

Each candidate must be configured, tested and validated. When a design fails, the architecture reopens and the work resets — and that early commitment is a bet made with the least information the project will ever have.

Why this breaks now

Several forces are compressing more coupled decisions into less time:

Scale

More parts and interfaces

Systems integrate more components, more sensing, more software — more decisions that move together.

Design freedom

New materials, geometries, software

Additive manufacturing and new materials open design possibilities the old process never had to search.

Customization & speed

More briefs, shorter cycles

High-mix demand means every new brief is a new integrated design — on a faster clock.

02 · THE IDEA

Invert the problem: start from the outcome.

Inverse design is a learned map from the requirement space — goals, constraints, operating envelope — back to the designs that achieve them.

Forward design

  • Choose one architecture — commit before you can evaluate
  • Configure → evaluate → revise — serial iteration
  • Failure reopens the architecture — and resets the work
  • Tests designs one at a time

Inverse design

  • Start from achievable outcomes — define targets in the feature space
  • Generate directly — the learned map returns feasible designs for those targets
  • Architecture is an output, not an up-front bet
  • Test only what is learned to work

Where the training signal comes from

Engineering already knows how to evaluate a design — physics, rules, simulation, test, expert judgment. What it rarely has is a direct rule for constructing the right one. And predictive ML alone doesn't fix this: engineering data is sparse, partial and biased, and novel designs have no historical examples.

When no representative corpus exists, the evaluators themselves become the training signal.

Boltz learns the inverse map from your existing evaluators — physics, rules, specs, simulations, lab data, private tools behind APIs. No historical design corpus required.

03 · HOW IT WORKS

Generate. Evaluate. Learn. Repeat.

The generator proposes designs; evaluators score feasibility, performance and coverage of the feature space; the model retrains on that feedback — probing the design space where the map is still uncertain.

A closed loop between generation and evaluation

Training is a closed loop: the generator proposes candidates; the evaluators score feasibility, performance and coverage; the model retrains and proposes again. Each pass teaches the generator the structure of valid constructions and where the achievable envelope actually lies — and because the loop probes where the map is still uncertain, exploration is directed, not exhaustive. That is what makes a combinatorial space searchable at all.

Trained against your trusted evaluators

The evaluators are yours, not ours. Boltz trains against each customer's trusted evaluation layer — physics models, design rules, simulations, catalogs, lab data and private tools — accessed through APIs and connectors. Every design you see has already been scored by your standards, and the trained map inherits the credibility of the stack behind it.

The result of training is not one optimized design. It is a reusable, target-conditioned generative model of the achievable design space — its feasible envelope, its trade-off frontier, its corners.

At inference: query the map

1 · Target profile

Specify the envelope

Define ranges across performance, cost, resilience, buildability — a region, not a point.

2 · Query

Hit the achievable map

The trained model samples the feasible envelope and trade-off frontier inside your target region.

3 · Design library

Diverse · feasible · ranked

A set of complete architectures spanning the trade-offs — not a single answer to defend.

Map once, query many. Train per application family, then condition and reuse across briefs, customers, programs and operating envelopes — amortizing design search instead of restarting it.

The same pattern applies across design decisions

System architecture · platform, modules, component families Topology · connectivity, routing, arrangement Geometry · shape, dimensions, spatial fields Operating policy · sequence, settings, controls

What makes the engine different

Knowledge-led

No corpus needed

Starts from computable domain knowledge — not thousands of prior designs.

Any evaluator

Heterogeneous feedback

Rules, physics, simulations, documents, experts, private black boxes, test data.

Valid structure

Feasibility-aware

Learns the structure of valid constructions instead of generating the impossible.

Set-level

Population utility

Scores the whole set for coverage, Pareto reach, extrema and diversity — not just each candidate.

Reusable

Amortized search

Train once; condition and reuse across targets, constraints and programs.

04 · WORKED EXAMPLE · ROBOTICS

One trained map answers many workcell-design questions.

The robotic workcell — not the robot alone — is the deployed product: robots, grippers, fixtures, feeders, vision, safety, layout, task allocation and controls, all coupled. Boltz's beachhead application is inverse design of complete workcells.

SAFETY PERIMETER REACH ENVELOPE CNC 01 CNC 02 CNC 03 CNC 04 ROBOT · 22 KG PART FLOW
Top-down schematic · one architecture from the trained map — 1 robot, 4 machines, two-sided gripper, single safety cell

The setup: a CNC machine-tending application family. 45 discrete variables spanning architecture, equipment, layout, tooling and flow. Evaluators run on exact geometry: reach at every pose, collision through the modeled machine-door opening, joint and singularity margins, motion timing, catalog costing.

Once trained, the same map returns the best-fit feasible architecture for each objective — without retraining:

QueryReturned cellCostCycleParts/hrFloorRun time
Cheapest cell that does the jobKUKA KR 16 · 1 robot, 1 machine$105K107 s3450 m²5.9 h
Fastest cell, any budgetKUKA KR 16 · 3 robots, 4 machines$398K27 s13584 m²1.5 h
Smallest floor areaUR10e · 1 robot, 2 machines$171K58 s6219 m²6.5 h
Longest unattended runningABB IRB 4600 · 1 robot, 1 machine$138K107 s3473 m²11.9 h
Fastest cell under $200KABB IRB 2600 · 1 robot, 4 machines$187K30 s12138 m²0.2 h
Cheapest at 100+ parts/hourABB IRB 2600 · 1 robot, 4 machines$154K33 s10938 m²3.7 h

Modeled outputs from physics evaluators on exact geometry — not vendor quotes. Each query returns the best qualifying workcell for that objective from the same trained design map.

One modeled result worth pausing on: a $165K cell beat a $502K cell on cycle time, clearance, reach margin, run time and floor area — both serving three machines. The cheaper cell used one 22 kg-payload robot with a two-sided gripper; the expensive one combined three robots, a 45 kg-payload robot and 3D vision. That is what searching the full coupled space finds, and what committing to an architecture up front does not.

Beyond a single cell

The same generate–evaluate–learn pattern extends across robotics: production lines and fleets, task allocation, lab and medical robot workflows, and mobile or mission-specific robotic systems — wherever coupled robotic design decisions meet computable evaluators.

05 · ROBOTICS LABS

From protocol to complete lab workflow.

Lab and medical robotics is breaking out — medical robot sales rose 91% in 2024, and diagnostic and laboratory-analysis robots grew 610%. Every new protocol is a new integrated design: delicate objects, human proximity and reliability reshape the complete system, not just one instrument.

LAB FOOTPRINT LIQUID HANDLER INCUBATOR ANALYZER SAMPLE STORAGE TRANSPORT HUMAN CORRIDOR
Top-down schematic · one lab configuration — stations, transport, sample flow and human corridor designed together

What Boltz does in the lab

Same engine, different evaluators: protocol steps, delicate-object handling limits, biosafety and human-proximity rules, instrument specs and uptime targets become the evaluation stack — and the trained map returns complete lab configurations that satisfy them.

Protocol → workflow

Protocol-to-workflow design

Encode an assay or sample-prep protocol as requirements; generate the complete workflow that executes it — steps, allocation to instruments and robots, sequence and scheduling.

Layout & flow

Lab layouts

Benches, instruments, robot placement and reach, sample routing and human corridors — designed together, sized to the room you actually have.

Selection

Robot & tool selection

Arms, grippers, liquid handlers and movers matched to delicate objects, human proximity and the throughput the protocol demands.

Set-level objectives

Throughput & reliability

Walk-away time, error recovery and redundancy scored across the whole population of designs — so you choose the trade-off, not defend a single guess.

06 · WHO'S BEHIND IT

Deep IP, grounded in robotics.

Boltz is built and founded by AI and robotics veterans with deep expertise in generative modeling, learning control of mechanical systems, and enterprise-scale AI. The Boltz generative engine is proprietary, patent-pending IP.

Have a design family that keeps getting redesigned one brief at a time?

Boltz trains against your trusted evaluation layer — your rules, models, simulations and private tools — and serves the inverse map as a managed service. If your team solves the same class of coupled design problem over and over, that is exactly what the engine amortizes.

contact@boltz-ai.com