One operator.
Real infrastructure.

Why Stratum exists.

I've run Klipper print farms for six years — a 7-printer fleet at a day job, then a 15-printer fleet of my own. Spreadsheets, cron jobs, and prayer to track what was running, what was broken, and what needed maintenance.

MEMAR came later, built for my own subsequent ventures once I went looking for real fleet management and found it exorbitantly expensive for what it actually did — cloud-only, per-machine priced, locked to a single vendor's machines. So I built the tool I wanted: self-hosted, AGPL-3.0 licensed, works with any machine that has an API endpoint. Once it was solid for my own fleet, productizing it to lower that barrier for everyone else was the obvious next step.

6 adapters are proven — Klipper/Moonraker, OctoPrint, Marlin, Duet, FluidNC, Prusa Connect. My own six years has been all on Klipper; the rest are solid, mature protocols, just not something I've personally run for years like Klipper. CNC and the other machine types (including Bambu Lab, which uses reverse-engineered APIs) are real, working code, but earlier-stage: alpha, community-tested, liability-on-you until they've had the same mileage. See what's proven vs. alpha →

Stratum is the company I run it under. No VC funding. No growth-at-all-costs. A solo operator building useful things and selling them directly to the people who need them.