Physical AI · Additive manufacturing autonomy

The floor runs itself. You decide how far.

Powdrix is an agent operating system for production 3D-printing floors. An as-built part twin picks the recipe before the build, edge agents steady the melt pool layer by layer and control recoat, powder and thermal distortion, CT and vision grade every part against qualification criteria, robots handle plates, powder and post-processing, and a floor brain predicts build failure and schedules the fleet, all bounded by a policy engine and the qualified parameter envelope you control.

SUCCEEDED run_7c2e4b scenario complete10 steps · 1 approval gatePBF-2 · 3,140 layers

run_7c2e4b · agent graph · PBF-2 · scenario 10 nodes · 1 approval gate
01 · orchestrator ingest.job ✓ SUCCEEDED 02 · parttwin twin.simulate ✓ SUCCEEDED 03 · prep_parameter prep.release ✓ SUCCEEDED 04 · recoat_powder recoat.check ✓ SUCCEEDED 05 · melt_layer melt.stabilise ✓ SUCCEEDED 06 · thermal_distortion thermal.compensate ✓ SUCCEEDED 07 · orchestrator approve.human ◆ APPROVAL 08 · robot_handling handle.depowder ✓ SUCCEEDED 09 · defect_inspect inspect.ct ✓ SUCCEEDED 10 · quality_conf release.qualify ✓ SUCCEEDED

Illustrative scenario: PBF-2 · Ti-6Al-4V bracket family, 24-part build, 23 of 24 parts released, one held

Design partners wanted · 3 to 5 floors · machines and cells we are looking for

Metal powder-bed fusion Electron-beam PBF Directed energy deposition Polymer SLS and MJF CT inspection cells Heat treat and HIP

Pre-launch. No customers, pilots or logos are claimed. The first cohort gets a paid pilot on one machine against a baseline agreed in writing.

Run timeline · scenario

One scenario run, step by step

Every Powdrix run is an ordered, inspectable sequence. This is run_7c2e4b on PBF-2 · Ti-6Al-4V bracket family, 24-part build. Scenario completes in 10 steps with one approval gate. Twin recipe #14 selected, one lack-of-fusion precursor at layer 1,872 cleared by a bounded power trim, CT triage in 11 minutes, 23 of 24 parts released with full genealogy and one held for review.

run_7c2e4b PBF-2 · Ti-6Al-4V bracket family, 24-part build illustrative scenario SUCCEEDED
  1. 01 ingest.job SUCCEEDED 0.7 s

    Floor Orchestrator · Pulled the job from AM MES: 24 Ti-6Al-4V brackets, 60 µm layers, 3,140 layers, density target 99.7%, geometry tolerance ±0.10 mm, AS9100 evidence packet required. Locked the OEM-approved parameter envelope for PBF-2.

  2. 02 twin.simulate SUCCEEDED 6 m 12 s

    Part Twin · Simulated 40 candidate orientation, support and parameter recipes for thermal field, residual stress and distortion, ranked on predicted density, geometry deviation, takt and energy.

  3. 03 prep.release SUCCEEDED 48 s

    Prep-and-Parameter · Recipe #14 released: 32° orientation, lattice supports on two faces, laser power and speed inside the qualified envelope. Predicted distortion 0.06 mm, predicted density 99.8%.

  4. 04 recoat.check SUCCEEDED continuous

    Recoat-and-Powder · Recoater image checked every layer. Powder lot L-2291 on its third reuse, humidity in window. One short-feed at layer 412 corrected with a dosing increase before the next layer fused.

  5. 05 melt.stabilise SUCCEEDED continuous

    Melt-and-Layer · Melt-pool, photodiode and thermal streams fused at 120 fps. Lack-of-fusion risk rose to 0.61 on part 17 at layer 1,872 and was cleared by a 3% power trim inside the envelope within four layers.

  6. 06 thermal.compensate SUCCEEDED 2 m 04 s

    Thermal-and-Distortion · Interlayer temperature on the tall brackets ran 14 °C above the twin's prediction from layer 2,300. A 1.5 s interlayer dwell held the thermal field inside the predicted band through the top section.

  7. 07 approve.human APPROVAL 4 m 30 s

    Floor Orchestrator · Melt-and-Layer proposed a hatch-spacing change on part 17 beyond the qualified envelope. Held for the AM process engineer, who declined it and chose to flag part 17 for CT priority instead. Decision logged.

  8. 08 handle.depowder SUCCEEDED 38 m

    Robot-and-Handling · Plate unloaded by the handling cell on build complete, depowdered, and parts transferred to stress relief. Powder returned to the sieve with lot L-2291 reuse count incremented in genealogy.

  9. 09 inspect.ct SUCCEEDED 11 m

    Defect-and-Inspect · 24 CT volumes segmented for pores, cracks and lack of fusion in 11 minutes. 23 parts graded accept against the acceptance criteria. Part 17 shows a 180 µm indication at layer 1,870 and is routed to the inspector for disposition.

  10. 10 release.qualify SUCCEEDED 1 m 20 s

    Quality-and-Conformance · 23 parts released with the full genealogy: recipe, layer tags, melt-pool events, thermal trace, approvals, post-processing cycles and CT result. Part 17 held with a non-conformance opened. Evidence packet assembled for sign-off.

Tool calls · scenario

The agent shows its work

Every tool invocation, argument and result is written to an append-only, human-readable log, and every reasoning step is expandable. Nothing about a build is hidden from the floor or from the certification engineer.

tool-call stream · run_7c2e4b · timestamps span a 31-hour build
  1. 05:10:04mes.read_job({ printer: "PBF-2", job: "J-4471" })
  2. 05:10:05ok 24 parts · Ti-6Al-4V · 3,140 layers · envelope locked
  3. 05:10:05twin.simulate({ candidates: 40, targets: ["density", "geometry", "takt"] })
  4. 05:16:17ok best recipe #14 · distortion 0.06 mm · density 99.8% · takt 31.2 h
  5. 05:16:18policy.evaluate({ recipe: 14, autonomy: "L3" })
  6. 05:16:18ok recipe inside envelope · 6 bounded writes permitted
  7. 05:16:19printer.release_recipe({ id: 14, orientation: 32, supports: "lattice" })
  8. 05:17:07ok build started · layer 1 of 3,140
  9. 06:02:40recoat: short feed at layer 412 · dosing +4% applied
  10. 13:48:11precursor: lack-of-fusion risk 0.61 · part 17 · layer 1,872
  11. 13:48:12printer.trim_power({ part: 17, delta: "-3%", layers: 4 })
  12. 13:49:03ok risk 0.61 → 0.08 · pool stable
  13. 13:49:04approval.request({ action: "hatch_change", part: 17 })
  14. 13:53:34ok declined by AM process engineer · part 17 flagged CT priority
  15. 18:21:50printer.set_dwell({ interlayer: "+1.5 s", from_layer: 2300 })
  16. 18:23:54ok thermal field inside predicted band
  17. 12:20:30isaac.plan_grasp({ task: "unload_plate", cell: "RC-1" })
  18. 12:58:30ok depowdered · 24 parts to stress relief · lot L-2291 reuse 4
  19. 14:05:02ct.segment({ volumes: 24, criteria: "BRK-TI-A" })
  20. 14:16:02ok 23 accept · 1 indication 180 µm · part 17 → inspector
  21. 14:16:03packet.sign({ job: "J-4471", parts: 23, hold: [17] })
  22. 14:17:23ok scenario complete · 23 released · 1 NCR opened

Reasoning trace

Plan, thought, action, observation, exactly as the orchestrator would record it.

GoalRun job J-4471, 24 Ti-6Al-4V brackets on PBF-2, to 99.7% densi…

Run job J-4471, 24 Ti-6Al-4V brackets on PBF-2, to 99.7% density and ±0.10 mm, with an AS9100 evidence packet on every released part.

PlanSimulate the recipe on the twin first. Release only inside the…

Simulate the recipe on the twin first. Release only inside the qualified envelope. Watch recoat and melt pool every layer, compensate thermally against the twin, and route anything outside the envelope to the process engineer. Triage every part by CT before release.

ThoughtThree candidate recipes beat #14 on takt but predicted distort…

Three candidate recipes beat #14 on takt but predicted distortion above 0.08 mm on the tall brackets. Takt is not worth a geometry failure on a qualified part family. Recipe #14 wins on the stated targets.

Actiontwin.simulate(candidates=40) returns recipe #14: 32° orientati…

twin.simulate(candidates=40) returns recipe #14: 32° orientation, lattice supports, power and speed inside the envelope, predicted distortion 0.06 mm.

ObservationLack-of-fusion risk 0.61 on part 17 at layer 1,872. A 3% power…

Lack-of-fusion risk 0.61 on part 17 at layer 1,872. A 3% power trim, inside the envelope, clears it in four layers. The proposed hatch change would leave the envelope, so it goes to a human and is declined.

ActionFlag part 17 for CT priority. Hold interlayer dwell at +1.5 s …

Flag part 17 for CT priority. Hold interlayer dwell at +1.5 s from layer 2,300 to keep the thermal field inside the twin's band.

ObservationCT confirms a 180 µm indication on part 17 at layer 1,870, two…

CT confirms a 180 µm indication on part 17 at layer 1,870, two layers below the precursor. The other 23 parts grade accept. The precursor, the action and the CT result are now one linked record.

OutcomeScenario complete. 23 parts released with full genealogy, part…

Scenario complete. 23 parts released with full genealogy, part 17 held with a non-conformance, CT triage in 11 minutes, no unapproved parameter left the envelope.

How it works

A job becomes a recipe becomes a run

Nothing about a Powdrix build is implicit. The job is declared, the recipe is simulated on the twin, each step is typed and bounded by the qualified envelope, and the outcome is written to the build genealogy.

Active path

The orchestrator plans, the agents act

A run starts as a job, becomes a simulated recipe, and executes as a graph of typed steps across the printer, the ovens, the robot cell and the CT. The active path is always visible, always logged, always reversible.

RUNNING APPROVAL SUCCEEDED
<250 ms p95 alert latency for in-situ monitoring · design target
<1 to 2 s bounded assist recommendations · design target
30 to 240 fps melt-pool, layer and recoater streams per printer · design target
<15 min CT triage per production build · design target
Human in the loop

Autonomy is a dial, not a switch

L1 advisory, L2 supervised writes, L3 bounded autonomy inside the OEM-approved envelope, L4 unattended within an envelope once validated. Each floor sets the level per agent, per machine, per part family, and anything that affects qualification waits for a named approver. The four figures above are design targets, not measured results.

Agent roster

Ten agents, a twin and an orchestrator

Each agent owns a stage of the additive floor, a bounded tool set and a metric the floor already measures. They negotiate for shared machines and cells through the orchestrator, never directly. Five of them ship as named products.

agent.prep_parameter

Prep-and-Parameter

Build preparation, orientation, supports, nesting, process parameters

Proposes orientation, support, nesting and process-parameter recipes (laser power, speed, hatch, layer) for a build, scores them against density, geometry and takt targets with the part twin, and releases the winning recipe to the printer only inside the OEM-approved parameter envelope and after sign-off.

slicer.read_buildtwin.rank_recipesprinter.release_recipe

agent.melt_layer · shipped as Meltrix

Melt-and-Layer

In-situ melt-pool, layer and energy control

Fuses coaxial and off-axis melt-pool video, layer and recoater images, photodiode and thermal streams at high frame rate, classifies and predicts porosity, lack of fusion, keyholing, spatter and recoat faults seconds ahead, and closes into bounded, operator-graduated laser and energy control to hold the pool stable.

holoscan.fuseprinter.trim_powergenealogy.tag_layer

agent.recoat_powder

Recoat-and-Powder

Recoating, powder-bed uniformity, powder quality and reuse

Watches recoater images and bed uniformity every layer, detects streaks, short feeds and spreadability faults before the next layer is fused, tracks powder lot, reuse count and quality, and recommends or applies bounded recoat and dosing corrections.

recoater.read_imageprinter.adjust_dosepowder.lot_record

agent.thermal_distortion

Thermal-and-Distortion

Thermal fields, residual stress, distortion

Tracks the thermal history of the build from in-situ thermal streams against the twin's prediction, estimates residual stress and distortion as the part grows, and recommends thermal compensation, scan-strategy or dwell changes before geometry leaves tolerance.

thermal.read_fieldtwin.compare_thermalprinter.set_dwell

agent.defect_inspect · shipped as Poroscan

Defect-and-Inspect

CT, vision and metrology inspection, grading, qualification evidence

Triages CT volumes for pores, cracks and lack of fusion with GPU 2D and 3D segmentation, fuses surface vision and metrology deviation, grades each part against the alloy and part acceptance criteria with a human sign-off checkpoint, and links every defect back to the in-situ signal and the recipe that produced it.

ct.segmentmetrology.comparepacket.assemble

agent.postprocess_heat

Postprocess-and-Heat

Stress relief, heat treatment, HIP, support removal

Holds stress-relief, heat-treatment and HIP recipes against the part's as-built state and the qualification spec, sequences support removal, and records each thermal cycle into the part genealogy so post-processing stops being the blind, reactive end of the floor.

oven.read_cycleoven.set_recipegenealogy.write_cycle

agent.yield_takt · shipped as Yieldex

Yield-and-Takt

Yield, build-failure risk, energy, fleet scheduling

Ingests build health, inspection results, recipes and cell state from the whole floor, predicts build-failure and qualification risk per job, and schedules machines, ovens, HIP, inspection cells and robots for yield, takt and energy with cuOpt, re-optimising after a delay or a quality hold.

cuopt.schedulerisk.predict_failuremes.read_orders

agent.robot_handling · shipped as Forgebot

Robot-and-Handling

Build-plate, powder, part handling and depowdering

Drives Isaac and Jetson robot cells that load and unload build plates, handle and sieve reactive powder, depowder parts and move them through heat treatment, HIP and support removal, with motion planned and checked in simulation and coordinated with live printer and oven state.

isaac.plan_graspcell.transferpowder.sieve

agent.quality_conf

Quality-and-Conformance

Right-first-time, non-conformance, build genealogy, qualification traceability

Maintains the immutable build genealogy from recipe to layer to inspection to disposition, runs non-conformance workflows, and blocks shipment when genealogy or defect evidence is incomplete, so every qualified part carries a record a certification engineer can audit.

genealogy.writencr.openpacket.sign

agent.am_knowledge

AM-Knowledge

Parameter sets, specs, AM standards, procedures, operator Q&A

Answers process and qualification questions from parameter sets, build and qualification specs, AM standards and quality procedures, with every answer cited to its source and scoped to the tenant, so engineers get grounded reasoning rather than a chat window.

rag.retrievestandards.citeprocedure.lookup

twin.parttwin · shipped as Parttwin

Part Twin

As-built part simulation and recipe optimisation before the build

Simulates the build for candidate orientation, support, nesting and parameter recipes: thermal fields, a melt-pool proxy, residual stress and distortion. Auto-optimises against density, geometry, takt and energy targets, stress-tests the winner against rare defect and distortion scenarios, and hands the validated recipe to Meltrix.

twin.simulatetwin.rank_recipesscenario.generate

agent.orchestrator

Floor Orchestrator

Planning, arbitration, human approval

Plans the build job, routes events to the right agent, arbitrates between agents competing for the same machine or cell, enforces the autonomy level and the OEM parameter envelope, and sends any qualification-impacting action to a named approver.

plan.composepolicy.evaluateapproval.request
Where it pays

Four loops, four metrics

Powdrix is not a dashboard. Each agent closes a loop an additive floor already measures in scrapped builds, failed qualifications, CT hours and idle machine time. The tables show what each loop watches and what it is allowed to move.

Melt-pool instability

Catch the pore before the layer fuses

Melt-pool video, photodiode and thermal streams are fused at the printer edge into a rolling risk score for porosity, lack of fusion and keyholing. When risk crosses the threshold the agent has layers, not hours, to trim power inside the envelope instead of scrapping the build at CT.

  • Vision, photodiode and thermal fused at 30 to 240 fps
  • Prediction seconds ahead, not review after the fact
  • Every precursor, action and CT outcome labelled into the training set
agent.melt_layer SUCCEEDED
Catch the pore before the layer fuses: signals watched and parameters moved
SignalWatchesMoves
Melt-pool signatureWatched per layer, per partPower and speed trim inside the envelope
Keyhole and spatterClassified from video and photodiodeFocus and speed recommendation
Lack-of-fusion riskScored continuouslyTrim, CT priority flag, or hold request
Recoat and powder

Stop the streak from becoming a scrapped build

A recoat fault at layer 400 ruins a build that finishes a day later. Recoat-and-Powder reads the recoater image every layer, tracks lot, reuse and humidity, and corrects dosing or asks for a hold before the next layer is fused.

  • Recoater image and bed uniformity map checked every layer
  • Powder lot, sieve and reuse history carried into genealogy
  • Short feeds and streaks corrected before fusion
agent.recoat_powder SUCCEEDED
Stop the streak from becoming a scrapped build: signals watched and parameters moved
SignalWatchesMoves
Bed uniformityRecoater camera, every layerDosing and recoat speed inside limits
Powder qualityLot, reuse count, humidityReuse limit and sieve request
StreaksDetected before fusionHold request to the orchestrator
Inspection

Grade every part, in minutes, with the evidence attached

Spot CT on a sample and hours of manual review cannot keep pace with serial production. Poroscan segments every volume on GPUs, grades against the acceptance criteria with a human sign-off, and links the defect back to the layer and the signal that produced it.

  • 2D and 3D CT segmentation served on Triton
  • Criteria-aware grading with a named sign-off
  • Qualification packet assembled with citations
agent.defect_inspect SUCCEEDED
Grade every part, in minutes, with the evidence attached: signals watched and parameters moved
SignalWatchesMoves
Porosity and cracksCT volume segmentationAccept, reject or inspector routing
Surface faultsVision inspectionRework or reject suggestion
GeometryMetrology deviationCompensation feedback to Parttwin
Before the build

Rehearse the build on the twin

Every recipe is simulated for thermal field, residual stress and distortion before release. Candidates that save takt but push distortion or predicted density outside target are discarded automatically, and the winner is stress-tested against rare defect scenarios.

  • 10 to 40 candidate recipes per part family
  • Ranked on density, geometry, takt and energy
  • The chosen recipe is released inside the envelope and logged
twin.parttwin SUCCEEDED
Rehearse the build on the twin: signals watched and parameters moved
SignalWatchesMoves
Orientation and supportsThermal and stress simulationValidated recipe to Prep-and-Parameter
ParametersMelt-pool proxy and density predictionEnvelope-checked recipe to Meltrix
DistortionAs-built versus as-designedCompensation and predicted-defect map to Poroscan
Multi-agent handoff

Agents negotiate, they do not collide

Two agents will want the same machine or the same parameter. The orchestrator arbitrates on the job goal and the qualification rules, not on who asked first, and the handoff is logged like any other step.

Contested move: PBF-2 laser power on part 17

  1. 01yield_takt.request(speed +4%) SUCCEEDED0.2 s

    Yield-and-Takt wants to raise scan speed on the build to recover takt lost to the recoat correction at layer 412.

  2. 02melt_layer.request(power −3%) SUCCEEDED0.2 s

    Melt-and-Layer wants to trim laser power on part 17 to clear a lack-of-fusion precursor at layer 1,872.

  3. 03orchestrator.arbitrate SUCCEEDED0.4 s

    Lack-of-fusion risk 0.61 on a qualified part outranks 1.1 hours of takt under the job goal. Melt-and-Layer wins the parameter for four layers; the speed change is deferred.

  4. 04yield_takt.handoff(rescheduled) SUCCEEDED1.1 s

    Yield-and-Takt recovers the takt by re-sequencing the oven queue with cuOpt instead. Density prediction holds at 99.8%.

Illustrative scenario.

Arbitration rules

  • Job goal first. Every request is scored against the declared density, geometry and qualification targets, not the requesting agent's local objective.
  • Qualification outranks takt. A pore in a qualified part costs more than an hour of machine time.
  • The envelope is not negotiable. No arbitration outcome can leave the OEM-approved parameter envelope; that path always goes to a human.
  • Time-boxed ownership. An agent holds a contested parameter for a bounded number of layers, then must re-justify.
  • Everything is logged. The losing request, the score and the reason all appear in the build genealogy.
  • Deadlocks escalate to a human rather than resolving by timeout.

See the agent roster

Autonomy

Four levels, set per agent and per machine

A qualified floor does not go from manual to unattended in one step. Powdrix makes the level explicit, auditable and reversible at any time, and human approval for anything that affects qualification stays mandatory until validation exists. The first release runs shadow mode, then assist mode, then graduated autonomy.

Autonomy levels and the human role at each
LevelWhat the agent doesWhat the human doesWhere it sits in a pilot
L1 · AdvisoryPredicts and recommends, with citations; nothing is writtenEnters every change manuallyShadow mode on one machine, first weeks of a pilot
L2 · SupervisedProposes a parameter, thermal or inspection move; it executes on approvalApproves each move in the review consoleAssist mode once accuracy is measured against CT
L3 · BoundedWrites inside the OEM-approved parameter envelope and per-tag limitsApproves anything that leaves the envelope or affects qualificationGraduated autonomy on low-risk loops, if the floor is satisfied
L4 · UnattendedRuns the envelope without promptingSets the envelope; reviews the shift recordPlanned; only after validation on the part family
Targets

Design targets, stated as targets

These are the figures in our compute plan. None is a measured result. Every pilot measures against the floor's own baseline, reproduced from the floor's build records and CT outcomes, not from our telemetry.

Weekly model updates over multimodal build data, gated shadow to assist to bounded · design target
1k to 10k synthetic scenarios per qualified part family · design target
L4 to A100 class GPUs for Triton-served 2D and 3D CT segmentation · design target
1 per printer Jetson Orin edge node for in-situ perception · design target
Segments

Where additive floors start

Aerospace, medical and dental implants, energy and defence, tooling and industrial, and service bureaus, on metal powder-bed fusion, directed energy deposition and polymer SLS, MJF and FDM. Most floors pick one machine and one wedge, prove the number, then expand.

AerospaceBrackets, nozzles, structural parts

Aerospace

Qualified part families where one failed build or failed qualification is expensive. Meltrix and Poroscan on one metal PBF printer first, with the AS9100 evidence packet attached.

Medical and dental implantsTi and CoCr implants

Medical and dental implants

Porosity and surface faults are patient safety. CT grading against acceptance criteria with a named sign-off, genealogy for every implant.

Energy and defencePressure-bearing and reshored parts

Energy and defence

Serial production under qualification and reshoring pressure. Build-failure prediction and fleet scheduling with Yieldex as the floor scales.

Tooling and industrialConformal-cooled tooling, series parts

Tooling and industrial

Cost per part decides the business. Parttwin to cut coupon campaigns and ramp scrap, Forgebot to reclaim idle machine time.

Service bureausMulti-machine, multi-material fleets

Service bureaus

Many customers, many part families, one floor. Yieldex scheduling across machines, ovens and inspection, with per-customer genealogy.

Accelerated computing

Physical AI, at the melt pool

A build is thousands of layers and a day of machine time. Perception has to be local, deterministic and fast, CT has to be triaged in minutes, and the twin has to run before the build. Powdrix runs GPU inference at the printer edge and keeps training, simulation and optimisation in the cloud or on-prem.

Jetson Orin · DeepStream · Holoscan · TensorRT

Edge perception

One Jetson node per printer for 30 to 240 fps melt-pool, layer and recoater streams with photodiode and thermal fusion. Sub-250 ms alerting and 1 to 2 s bounded recommendations are the design targets. Jetson Thor is planned for multi-laser machines.

Triton · TensorRT · L4, L40S, A100

CT and vision inference

2D and 3D segmentation models for porosity, cracks, lack of fusion, surface defects and metrology comparison, served per inspection cell. Sub-15-minute CT triage per build is the design target.

DGX or HGX · NeMo

Training

Defect, melt-pool-instability, build-failure and AM reasoning models trained weekly over multimodal build data, with gated promotion from shadow to assist to bounded. Dedicated capacity is planned.

Omniverse · OVX

Part twin

Thermal, melt-pool-proxy, residual-stress and distortion simulation for recipe ranking, plus robot-cell and queue simulation. Modulus surrogates are planned so sweeps run at production cadence.

Cosmos · Omniverse Replicator

Synthetic data

Rare pore, lack-of-fusion, spatter, recoat-streak and distortion scenarios generated and validated against real CT and in-situ data before promotion. 1,000 to 10,000 per qualified part family is the initial target.

cuOpt · RAPIDS

Optimisation and analytics

Build nesting, fleet scheduling across machines, ovens, HIP, inspection and robots, energy windows, and GPU analytics over genealogy tables.

Isaac · Isaac Sim · NIM

Robot handling and serving

Plate, powder and part handling policies trained in simulation and run on Jetson in the cell. NIM packages perception, prediction and reasoning services behind the floor orchestrator.

Developers

Define an agent, bound it, run it

The Powdrix SDK is typed Python. Tools are declared with schemas, a qualified parameter envelope and limits, and the policy engine enforces them at call time, not in a review meeting. This is a design preview; the API will change before release.

What you get

  • Typed tool definitions with a qualified parameter envelope and per-layer rate limits
  • Deterministic replay of any historical build against a new model
  • Local twin harness so a recipe is simulated before it is released
  • Autonomy policy as code, versioned and reviewed like any other change

Read the docs Developer guide

pbf2_melt_agent.py
# Design preview. Bound the melt-pool agent to printer PBF-2.
from powdrix import Agent, Tool, Envelope, Autonomy

power = Tool(
    name="printer.trim_power",
    tags=["PBF2.LASER_POWER", "PBF2.SCAN_SPEED"],
    envelope=Envelope(qualified="BRK-TI-A", max_step="3%", per="4 layers"),
)

melt = Agent(
    id="agent.melt_layer",
    goal="density >= 99.7%, lack_of_fusion_risk < 0.2",
    tools=[power, Tool("holoscan.fuse", read_only=True)],
    # bounded writes inside the envelope; humans gate anything outside it
    autonomy=Autonomy.L3,
    # check the move against the twin before it is written
    verify="twin",
)

run = melt.start(printer="PBF-2", job="J-4471")
for step in run.stream():
    print(step.layer, step.name, step.status)
CLI

Start a build from anywhere

The same run engine, the same policy checks, the same audit trail, from the terminal, the review console or the SDK. Design preview.

powdrix · cli · scenario
$ powdrix run "build J-4471 on PBF-2" --autonomy L3

→ plan composed          10 steps · 1 approval gate
→ twin.simulate          40 candidates · best #14 · distortion 0.06 mm
→ policy.evaluate        recipe inside envelope · 6 bounded writes permitted
→ executing              prep.release ....... ok   48s
→ executing              recoat.check ....... ok   layer 412 dosing +4%
→ executing              melt.stabilise ..... ok   layer 1872 power −3%
! approval required      hatch_change part 17 · outside envelope
→ declined               AM process engineer · part 17 → CT priority
→ executing              inspect.ct ......... ok   24 volumes · 11m
→ scenario complete      23 released · 1 NCR · genealogy complete

$ powdrix builds show run_7c2e4b --format genealogy
Pricing

Priced per machine, per floor, per group

Land on one printer with a measured baseline. Expand by machine, module, floor and autonomy level. Outcome components are available on build failure, yield, qualification and energy. Annual prepay carries a 15 to 20% discount.

Billing period
Machine $6,000 per AM machine / month · billed monthly

In-situ, parameter-control or inspection AI for one printer. For manufacturers validating ROI on the wedge.

  • One printer or inspection cell, one agent module
  • Printer-edge Jetson node included
  • Machine, camera and CT reads, bounded writes inside the envelope
  • Run log, audit trail, build genealogy
  • Business-hours support
Start a pilot
Enterprise Custom land $500k to $7M ACV

Multi-site AM manufacturers and bureaus standardising on Powdrix, with custom alloy, polymer and qualification models.

  • Multi-site floor-edge fleet
  • Custom alloy, polymer and qualification models
  • On-prem GPU inference option
  • Group autonomy policy and approval chains
  • SLAs, SSO and RBAC, dedicated engineer
  • Validated model change control and evidence packs
Contact us
Who it is for

Built for the people who run the floor

We have no customer quotes to show yet and will not invent any. These are the three roles on an additive floor we build for, and the problems they bring to the first meeting.

AM or Operations Director

Owns build throughput, quality, build-failure and yield, qualification and cost per part.

What this person is dealing with today

  • Fixed parameters and manual build prep that cap density, geometry and yield
  • Scrapped multi-hour or multi-day builds and high energy eroding cost per part
  • A severe, scarce AM process-engineer shortage that caps fleet scale-up

AM Process Engineer

Owns build prep, parameters, in-situ interpretation, thermal and distortion, and post-processing recipes.

What this person is dealing with today

  • Melt-pool instability, porosity, lack of fusion and spatter driving scrapped builds
  • Recoat streaks and powder-quality faults ruining long builds
  • Terabytes of in-situ data that nobody has time to read

Quality or Certification Engineer

Owns part quality to AS9100, ISO 13485 and ASTM and ISO AM standards, defect conformance and build genealogy.

What this person is dealing with today

  • Failed qualifications and evidence assembled by hand
  • Hidden pores and lack of fusion that pass spot CT and fail in the field
  • Build prep, in-situ, post-processing and inspection siloed and reactive across the fleet
Integrations

It speaks printer, not cloud

Powdrix reads and writes through the systems already on the floor. No rip and replace, no parallel historian, no new slicer to learn. Vendor names are examples of systems found on additive floors; connector availability is confirmed per site.

Build prep and slicers

Build-preparation and slicer software (Materialise, Autodesk Netfabb, Oqton, Siemens NX AM and nTop class tools)

Geometry, orientation, supports and parameter sets in; validated recipes out

Printers

Laser and electron-beam PBF, DED and polymer SLS, MJF and FDM machines through OEM control APIs

Machine state and in-situ streams in; bounded parameter writes inside the envelope

In-situ monitoring

Coaxial and off-axis melt-pool cameras, photodiodes, layer and recoater cameras, thermal sensors (EOS EOSTATE, Nikon SLM, Sigma Additive and Velo3D Assure class systems)

Frames and streams fused at the printer edge

CT, vision and metrology

CT scanners, surface vision and metrology (Zeiss, Nikon CT, Waygate and Volume Graphics class systems)

Volumes, images and scans in; grading, routing and packets out

Post-processing

Stress-relief and heat-treatment ovens, HIP units, depowdering and support removal (Solukon, AM Solutions and PostProcess class equipment)

Cycle data in; recipe parameters inside the qualified window out

Powder management

Sieving, lot tracking and reuse records

Lot, reuse count and quality into genealogy

Robot cells

Jetson and Isaac driven handling cells, grippers, transfer rigs

Build-complete and oven signals in; handling tasks out

AM MES and ERP

AM MES and build management (Oqton, Authentise, 3YOURMIND, AMFG and Materialise CO-AM class systems)

Jobs and orders in; genealogy, holds and dispositions back

See all integrations

Guardrails

An agent that can trim laser power needs a leash

Powdrix writes to production printers that make qualified parts. Every capability is scoped to the qualified envelope, every write is policy-checked, and every action is written to an append-only audit log the floor owns.

  • Bounded action space. Each agent writes only to an explicit allow-list of printer, oven and cell parameters, inside the OEM-approved envelope and per-tag rate and magnitude limits.
  • Policy engine before every write. Autonomy level, part family, qualification status, machine state and operator presence are evaluated before a parameter moves.
  • Human approval for qualification-impacting actions. Anything that leaves the qualified envelope, changes a validated recipe or affects a part's disposition waits for a named approver. This stays mandatory until validation exists.
  • Immutable audit log. Append-only and exportable. Every action records model version, data lineage, source signals, predicted impact, allowed range, approval status and qualification impact.
  • Hard fallback. Loss of the edge node, the network or a model returns control to the printer's own controller and the standing recipe.
  • Tenant and IP isolation. Parameter sets, part geometry, defect libraries and process memory never cross a customer boundary. On-prem deployment is available for sensitive producers.

Compliance posture

Compliance and certification status
ItemScopeStatus
SOC 2 Type ICloud control plane QUEUED Planned, first 6 months
SOC 2 Type IICloud control plane QUEUED Planned, 6 to 12 months
SSO and RBACConsole and approvals QUEUED Planned, 6 to 12 months
AS9100 and ISO 13485 assurance packagesEvidence packets and model change control QUEUED Planned, 6 to 12 months; not a certification claim
Standards-cited reasoningAS9100, ISO 13485, ASTM F42, ISO 52900 RUNNING In the design, every answer cites its source
Per-tenant isolation and on-prem optionRecipes, geometry, models, memory RUNNING In the design from day one

Read the security overview

Enterprise

Standardise autonomy across the group

One policy model, one audit trail, one benchmark across every machine on every floor, with the alloy, polymer and qualification models kept private to each site.

Talk to us Enterprise details

  • SSO and role-based access down to the parameter level, planned for the 6 to 12 month release
  • Group-wide autonomy policy with per-site override and approval chains
  • Cross-floor benchmarking on build failure, yield, porosity and parameters, planned as data-network tiers
  • On-prem GPU inference and floor-edge deployment, with air-gapped operation for sensitive producers
  • Validated model change control and AS9100 and ISO 13485 evidence packs, planned
  • Dedicated deployment engineer and quarterly model review per floor
FAQ

Straight answers

The questions operations directors, process engineers and certification engineers ask in the first meeting.

Only inside the OEM-approved parameter envelope, only on an explicit allow-list with per-tag limits, and only at the autonomy level your floor has set. Level 1 is advisory: Powdrix predicts and recommends and a human enters everything. Design partners start there, in shadow mode. Anything that leaves the envelope or affects qualification always waits for a named approver.

Get started

Bring autonomy to your floor

Start with one printer or one inspection cell and one measurable baseline. A paid pilot on melt-pool and build-failure prediction, CT porosity triage or pre-build recipe optimisation shows the number before you commit further.