Installed on real machines
A laptop, desktop, home server, or rented VM should all look like valid targets once Bunny Ears is present.
Bunny Ears
The installed runtime that makes machines part of the Bunny fleet.
Bunny Ears lives on the machine itself. It logs in, installs workloads, enforces permissions, tracks health, and keeps the runtime present whether the machine is local hardware or a cloud VM.
Permission-first runtime
Carrots request capabilities. Bunny Ears decides how they are granted and enforced on that machine.
Built for recovery
The runtime layer has to stay manageable even when a higher-level shell fails, which is why Ears matters as its own product surface.
Why it exists
Without the installed runtime, there is no trustworthy local presence.
Browser UIs and hosted dashboards are useful, but they do not replace the need for software installed on the actual machine that can install workloads, manage updates, expose local capabilities, and survive network topology changes.
Bunny Ears is the layer that makes the rest of the ecosystem believable.
Runtime launch
Get notified when Bunny Ears opens up beyond the teaser.
Waitlist
Follow the runtime rollout.