The Bunny Lab is an independent innovation lab: a small, multilingual crew of engineers who would rather build the tool than rent it. The name comes from the first Matrix film: following the white bunny is the first step to seeing the system for what it is. That's our job. We question what the market tells you is true, look under the layers where truth is hidden, and ship what we find. Everything here started as something we needed on a Tuesday.
We exist to help people bring their ideas to life. For the thing you have not built yet, for the people you want to build it with, and for the tools that should be helping you do both. Everything the lab ships answers to one question: did it get someone closer to the thing they were trying to create?
Everything around you started as something someone decided to create. That decision is the only scarce thing in this industry. We exist to protect the distance between having the idea and watching it run.
Almost nothing good is built alone. Work moves between people, and it should move directly, without asking anyone for permission on the way. Collaboration belongs inside the tool, not in a plan you subscribe to.
Tools decide how much of a day actually reaches the work. The right ones disappear into it and give the machine back to the person using it. If the tool is the reason an idea stalls, it is the wrong tool.
We take the complexity out of creating things and hand you the tools instead, so you can ship products faster and with a smaller team.
Creating something should not start with assembling a stack. We take the complexity out of the work and hand you the tools instead: one place to create, nothing to wire together first, nothing to keep alive on the side.
Complexity is what forces the headcount and the timeline. Take it out and the same product reaches production sooner, with a smaller team on it, because the day goes into the thing being created instead of the machinery around it.
Two products, one bench. Both exist because we needed them during a real week of work, and both are native, local first and built in Rust: fewer layers between you and the machine, not more.
One native binary, GPU rendered, polyglot by design. The editor, API client, spreadsheets, browser and agents are modes of a single program, not five applications arguing about which project is open.
Peer to peer, straight between machines. The work moves directly between the people creating it, with no server sitting in the middle of it.
Every tool of the working day in one place, sharing one project, one theme, one keymap. Python, JavaScript, Go, SQL, Bash and more, with new languages loadable at runtime.
Agents that live inside the workbench. They run the work, then open your app in the built-in browser to check what actually rendered.
Declarative Rust in a SwiftUI spirit. Views are plain values, and a state change re-runs only the views that read it. It is what Trinity is made of, and it is yours to build on too.
No webview and no garbage collector between your code and the screen. The framework crates depend on nothing but the Rust standard library, and forbid unsafe code.
Compose your own widgets exactly the way we compose ours, all the way down. Nothing in the framework is a special case you cannot rebuild yourself.
One scene, every screen: desktop as a native window, web as DOM or canvas pixels, mobile from the same source. The platform backend is the only part that changes.
// both are early: bunny_ui's API will move, and Trinity's alpha opens in waves. we ship in the open and log what breaks.
this notebook is not a screenshot: it is a Rust app compiled to WebAssembly, running in your browser on bunny_ui, the same UI engine we build Trinity with.
Nobody briefs against the bunny. That's the point: while the market watches the big platforms ship another dashboard, the small fast thing eats the problem. Being underestimated is the best position a small team can hold.
bunny_ui is open source and available now. Trinity is closed alpha, free, and opens in waves: ask for a seat and we send one.
One place for the whole working day. Editor, API client, spreadsheets, browser and agents on the same project, sharing one window and one keymap.
Use the tools to close the distance. Fewer moving parts, fewer handoffs, and less of the day spent waiting on the machine in front of you.
Shipping one thing should leave you readier for the next, not tired of the stack. Create, ship, and go again, with more of your day than you started with.
Some teams do not want the tools, they want the crew. We take on a small number of startup builds a year: we sit inside the problem with your engineers, ship in the open, and leave you owning every line. Same rules as the products, no lock-in and no dependency on us, and you end up more independent than you started.
No. It is one native binary, GPU rendered, with no webview and no JavaScript runtime underneath it. It is written in Rust, which is why it is fast, not who it is for.
Trinity is free during the closed alpha, which opens in waves: ask for a seat and we send one. bunny_ui is open source, so it costs nothing and you can read every line of it.
No. Trinity ships grammars and language server support for Python, JavaScript, Go, SQL, HTML, Bash and more, and registers new languages at runtime. Rust is how it is built, not who it is for.
In the first Matrix film, Neo is told to follow the white bunny, and discovers the world he took for granted is a construct. That's our name, and our method: we show you what your tools actually cost you, and we hand you the way out.
Every two weeks: the AI tips we actually use, what changed in the tools we build with, and the security findings worth your coffee. No spam, no growth hacks. Unsubscribe with one click, no hard feelings.