Platform

One runtime at the printer, one orchestrator, one genealogy.

The Powdrix platform is a floor-edge inference runtime on NVIDIA Jetson at every printer and cell, GPU inspection servers at CT, a floor orchestrator with a policy engine, specialist agents for every stage of the floor, and an as-built part twin that rehearses each build. Everything an agent does is typed, bounded by the qualified envelope and logged.

Printer edge · Jetson OrinOrchestrator · policy engineTwin · Omniverse

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

Architecture

Six layers, one loop

Perceive the build, plan the recipe, act inside the envelope, inspect every part, optimise yield and takt, log everything, retrain. The layers below are the design, not a description of a shipped system.

Layer 01 · Connectors

Slicer, printer, sensor, CT, oven, robot and MES connectors

Build-prep and slicer software, printers through OEM control APIs, coaxial and off-axis melt-pool cameras, photodiodes, layer and recoater cameras, thermal sensors, powder lots, CT, vision and metrology, ovens and HIP, robot cells and AM MES. Signals are normalised into one time-aligned record per build and layer.

slicerprinterctmes

Layer 02 · Floor-edge runtime

Perception and bounded control at the printer

DeepStream and Holoscan process melt-pool video and sensor streams on Jetson Orin. TensorRT-optimised models classify and predict porosity, lack of fusion, keyholing, spatter and recoat faults; time-series models track thermal history and machine, laser and recoater health. Triton serves them with canary rollout by machine.

Jetson OrinHoloscanTensorRTTriton

Layer 03 · Orchestrator and agents

Plan, arbitrate, approve, act

The floor orchestrator routes events to specialist agents. Agents retrieve parameter sets, specs and standards through permission-aware retrieval, evaluate the qualified envelope and the policy, ask for approval when required, and write through validated connectors only when the checks pass.

plan.composepolicy.evaluateapproval.request

Layer 04 · Part twin

Simulate before you build

The Omniverse twin simulates thermal fields, a melt-pool proxy, residual stress and distortion for candidate recipes, ranks them against density, geometry, takt and energy, and compares as-run against as-designed as the build progresses. Cosmos and Replicator generate rare defect scenarios for stress tests.

OmniversecuOptModulus (planned)

Layer 05 · Inspection and training loop

CT inference, models, registry

Triton-served 2D and 3D segmentation on L4, L40S or A100 class GPUs at the inspection cell. Weekly training over multimodal build data on DGX or HGX class capacity, a fleet model registry and gated promotion. Federated aggregation across floors is planned and waits on data agreements.

TritonNeMoDGX or HGX (planned)

Layer 06 · Review console and audit

Humans in the loop, by design

A review console for AM process and certification engineers to approve, correct and give feedback. Corrections train the models. An append-only, assurance-grade quality and qualification audit log records every agent action with model version, lineage and qualification impact from day one.

consoleaudit.writegenealogy
Core flow

Perceive, plan, print, sense, post-process, inspect, optimise, log, retrain

The core user flow, in order. Outputs are reviewed by an AM process engineer whose corrections train the models.

  1. Perceive the build, layer, melt pool and part. Fused melt-pool video, photodiode, thermal, recoater and layer images, time-aligned to build and layer.
  2. Plan prep, parameters, print, post-process and inspection. The orchestrator composes the job and the twin ranks candidate recipes against density, geometry and takt.
  3. Run with adaptive parameter and thermal control. Bounded writes inside the OEM-approved envelope, at the autonomy level the floor has set.
  4. Sense and predict porosity, lack of fusion, distortion and build-failure risk. Meltrix scores the melt pool ahead of the fused layer; Thermal-and-Distortion compares against the twin.
  5. Optimise yield, build failure, energy and takt. Yieldex prices each move and schedules machines, ovens, HIP, inspection and robots with cuOpt.
  6. Flag off-spec and qualification risk, then log. Hold, route to CT priority, or release, with the evidence written to build genealogy.
  7. Retrain. Every supervised correction, CT label and part outcome goes back into the models.
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.

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
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.

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

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

See the platform on 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.