MajorDom

This page isn't a MajorDom pitch, that's what majordom.io is for. It's the story of what building MajorDom actually took, and why it's the reason we can offer the services on this site at all.

Why we built it

MajorDom started in 2022 out of a simple frustration: every smart home option worth using shipped your voice and habits to someone else's cloud. Control did not work without internet even when at home. Vendor-locks. No DIY suppost whatsoever. Or complex over-engineered open source. We wanted a hub that worked offline, didn't limit you, was DIY-friendly yet was simple to setup and use. So we built it ourselves.

What it took, department by department

Hardware Lab. The hub and device line went through multiple PCB revisions. Enclosures were designed and iterated in-house, printed on our own 3D farm through several rounds before settling on the current design.

Software Studio. A full-stack platform end to end: the mobile app, the backend, and the device firmware, plus STARK underneath for offline voice. None of it outsourced, all of it maintained by the same team that ships client work.

Business Automation. Running a hardware product means manufacturing, assembly, logistics, distribution, and support as much as it means code. We built our own internal tooling to handle it rather than duct-taping together off-the-shelf services.

The crowdfunding campaign and the expo demos were both stress tests for the whole stack at once: hardware that has to work reliably in a stranger's hands, software that has to onboard someone with zero context, in minutes, live. When we offer contract development, consulting, or hardware prototyping as services, this is where that experience comes from.

Learn more

• Product details, pricing, and setup: majordom.io
• Crowdfunding campaign: Kickstarter
• Announcements and origin story: blog
• Device integration and API docs (relevant if you're building an integration): docs.majordom.io