jarm builds the humanoid base layer
— hardware, core stack, and developer tooling —
so developers can create tasks, workflows, and real-world applications faster.
share your interest— hardware, core stack, and developer tooling —
so developers can create tasks, workflows, and real-world applications faster.
and get updates ->
philosophy
Most humanoid companies optimize for one of two extremes. A single narrow use case, or one large model meant to do everything. Both approaches create friction for developers and make scaling harder.
jarm takes a different path. We build below the use-case layer: the humanoid base, core stack, and developer tooling that make task creation easier. Our focus is not to compete at the application layer, but to enable developers, labs, startups, and frontier teams to build on top of a practical humanoid platform.
The real question is no longer whether humanoids can do useful work. The question is whether they will be usable, adaptable, and scalable enough to matter in real workflows.
multifaceted demand of humanoids
fragments from real conversations about endusage areas that exist today
Vehicles come back from construction sites needing daily pressure-washing, then inventorying, and both could be handled by a humanoid robot.
Jan
construction professional
Seasonal work at the vineyard depends on extra hands, but finding people for these tasks is becoming increasingly difficult.
Julia
local vineyard owner
From preparing the base to checking grow states and harvesting, there are many steps in mushroom growing where robotic help could make a difference.
Patrick
co-founder, BetterMyco
At home, a humanoid could help my father with his daily routine in everyday rooms and up the stairs, so he can stay in his own home a few years longer.
Marc and Anna
support their aging parents
On site, a humanoid could move through changing work environments and help with prep, inventorying, and demanding tasks like core drilling.
Leo
electrician
Changing shopping habits and reduced staffing make regular opening hours harder to maintain, but a humanoid could help keep the shop open.
Lisa
local store owner
If a humanoid pre-assembled the parts I prep by hand every morning, I could take on bigger orders without hiring.
Thomas
workshop owner
developer UX
jarm is built for task creation, not task ownership. We help teams move from data and simulation to reusable tasks, then extend those tasks with components and runtime modules for deployment.
A typical workflow looks like this: Data and simulation → task creation → components and extensions → humanoid deployment
Tasks are modular building blocks inside larger workflows. Examples include picking, grabbing, using tools, and interacting with an environment. This makes it easier to combine capabilities, adapt them to different contexts, and deploy them at runtime.
partners & programs
the platforms and startups we build with
why jarm
Founder-led and product-focused. jarm is being built by a small team, led by Jacob Munke with a strong focus on usability, adaptability, and humanoid enablement.
Self-funded through prototype 1. That gives the company execution discipline and lets us move with focus before raising externally.
Built in Europe, close to robotics and AI talent. With proximity to THWS and JMU, jarm has access to engineering talent, academic collaboration, and a strong base in Germany and central Europe.