Bunny Ears
Installed runtime
A permissioned runtime that lives on a real machine or VM, installs workloads, and keeps them manageable.
Bunny
A permissioned runtime ecosystem for local machines and cloud VMs.
Bunny takes the app story past packaging. Install Bunny Ears on a machine, run workloads as carrots, manage them from Bunny Dash, and connect them through the account and relay layer of Bunny Cloud.
System map
The stack is simple once the nouns lock in.
Carrots
Tiny workloads
Small, capable runtime units for editors, browsers, terminals, git, models, and whatever comes next.
Bunny Dash
Control surface
The main local and remote client for managing machines, workspaces, carrots, sessions, and fleet state.
Bunny Cloud
Account and relay layer
Identity, hosted access, remote routing, subscription features, and the connective tissue across machines.
More than a plugin system
The intent is not a prettier extension marketplace. The runtime boundary matters. Permissions matter. Machine presence matters.
Local and remote by default
A Bunny Ears instance might be on your laptop, a spare mini PC, or a cloud VM. Dash should treat all of them as first-class.
One product in multiple hosts
Bunny Dash in the browser and Bunny Dash as a carrot should be the same product with different capabilities, not separate shells that drift.
Early access
Follow the rollout from teaser into installable runtime software.
The waitlist is the current front door while Bunny Ears, Dash, and carrots keep taking shape.
Join the waitlist
Get the runtime launch notes first.