Start from a working controller
Scanner and laser control, state machines, logging, users and an operator interface already work. Your roadmap starts at your process.
For machine builders
Ship your machine sooner. Keep your IP.
POWDERBED gives you a working control stack with full source code. Integrate it into your machine and focus on developing your process.
The shift
Machine tool builders have relied on standard controllers for decades.
In CNC, very few machine builders develop their own numerical control. They buy an off-the-shelf platform, then put their engineering into the mechanics, the process and the service. Their machines got better and cheaper, and the controller became something operators trust.
Powder bed fusion has not made that shift yet. Many machine builders still maintain their own control software, often as a closed system that only a few people understand. POWDERBED is the open platform for that shift: a standard controller with full source code you can adapt.
Private by licence
BSD-3 means your process plugins, scan strategies and interfaces stay private. No copyleft, no royalties on the framework.
Readable, extensible source
Open interfaces put process data in reach of your data science team. The codebase is readable and extensible. A coding assistant can help with the boilerplate.
What your team no longer builds
Plumbing, solved once.
These are needed in every powder bed machine, and they rarely set one machine apart from another.
Scanner list handlingLaser timingField correction loadingMachine state machineBuild file handling3MF toolpathsUsers & rolesLogging & journalAlertsDatabase migrationREST APIOperator interface frameworkPLC communicationExisting device drivers
What remains: your process
Design-in path
From evaluation to series production.
A typical path, adapted to your machine and schedule. Each step ends with a decision, so you only commit when you have seen it work.
Evaluate
Core 1 on your bench. Run your scanner and laser, read the code, and test your first plugin in simulation.
Integrate
Integrate your PLC, sensors and drivers. We can help adapt the operator interface and develop custom build styles and advanced toolpaths.
Design in
Agree on hardware configuration, private-label front panel, volume pricing, documentation and test procedures for your machine series.
Produce & maintain
Series supply of controllers, with Care for tested updates, long-term support and remote diagnostics.
Core 1 is the starting point for evaluation. Request a quote for an evaluation unit. Multi-laser configurations follow on the same software, so a process developed on one laser carries over.
Configurations and prices →Questions from machine builders
Something else? Write to us directly.
Do we have to publish our changes?
No. AMCF is licensed under BSD-3, which allows proprietary derivatives. Your plugins and changes stay private unless you choose to share them.
What if Aagaard AM is no longer around?
You receive the AMCF source under BSD-3, including the POWDERBED configuration and drivers. Your plugins can stay private. The RTC6 remains a standard SCANLAB product: its firmware and SDK stay SCANLAB's. Your machine is not dependent on Aagaard AM to keep running.
Can we put our own brand on the operator interface?
Yes. The operator interface is configurable, and branding is part of a design-in.
Who is responsible for machine safety and CE marking?
The machine builder remains responsible for the safety concept and conformity of the complete machine, including laser safety. We provide documentation for the controller to support your assessment.
Can we start with one machine before committing to a series?
Yes. That is what step 1 is for. Start with Core 1 and decide on a design-in when you have seen it working with your hardware.
Next step
Bring your machine roadmap. We'll bring the controller.
Talk through your machine, schedule and integration needs.