Open Source Healing Devices
We build AriHelder in the open—so you can verify performance, understand the design, and keep your device running for years.
Test Reports, Published
Optical, thermal, electrical—measured and shared.
Engineering Docs, Included
PRS, revision history, and design decisions.
Repair & Parts, Supported
Spare parts lists, guides, and printable components.
Evidence beats marketing
We publish the same internal materials we use to build and validate our products—so the numbers are checkable, and the story is honest.
What we publish (and where to find it)
Test reports
Methods, setups, results, and limitations
PRS / Requirements
Product requirements, assumptions, revision tracker
Hardware design files
Schematics, PCB, BOM, manufacturing outputs
Firmware source code
Builds, releases, changelog, safety logic
Spare parts + repair guides
Parts lists, steps, tools, diagrams
Design walkthroughs (video)
Board design → bring-up → iteration
3D printable parts
Non-safety-critical STLs/3MFs + print notes
Coming Soon!
Designed to be repaired, not replaced
We keep products modular and serviceable. You can order parts, follow guides, and keep your device running long-term.
- Spare parts list with part numbers
- Step-by-step repair procedures
- Printable parts where safe
- Local support option (factory / service)
Take a look behind the scenes of our latest product launch.
Open by Design – Share the Progress
AriHelder is open by design. You can use, modify, build on, and even sell products based on our work. The one rule is simple: if you distribute a modified version or product derived from it, you must make your improvements and source available under the same open license. That way, progress stays shared and grows for everyone.
- Hardware design files: CERN-OHL-S v2 (strongly reciprocal)
- Firmware/software: GPLv3 (or AGPLv3 if networked/service-based)
- Documentation: CC BY-SA 4.0
Each GitHub repository includes the full LICENSE file plus a plain-English summary.
Open—but safe
What we don't publish
We keep secrets, API keys, customer data, and NDA-protected content private to protect security and privacy.
Safety-critical boundaries
Some limits are in place for user safety and device integrity. We document these boundaries and explain why they shouldn't be bypassed.
Modifications
While you're free to modify our designs, certain changes may void warranty coverage or increase safety risks. We'll clearly mark what's safe to modify.
Security reporting
If you discover a security issue, please report it responsibly through our designated channels so we can address it before public disclosure.
Build with us
If you're an engineer, maker, clinic, or power user—we welcome feedback and improvements.
Verify everything. Own your device.
Open source is how we earn trust—and how we improve faster.