Webhook monitoring for E2B, built from scratch.

E2B runs the cloud sandboxes where AI agents execute code, over a billion so far. We joined its team on the dashboard every customer uses, then handed the work to the dashboard team E2B built.

First release
2 days
from kickoff to production
Shipped
9 features
from team settings to webhook monitoring

E2B’s engineers are strongest deep in the stack: the sandbox runtime, the infrastructure, the services underneath. The dashboard sits on top of all of it. It’s where every customer manages their team, API keys, usage limits and billing.

By early 2026, E2B had more than 20 people across San Francisco and Prague, but nobody dedicated to the dashboard, and its backlog kept growing. E2B needed it moving without waiting to hire, and Vasek Mlejnsky, its CEO, asked us to take it on.

We already knew E2B as customers. Since 2023, Maige, our GitHub agent, had run in its sandboxes: each time someone commented on an issue, Maige cloned the repository into a sandbox and carried out the request there.

A small first release

We started with a walkthrough of the codebase, and our first pull request was in production two days later. A small first release runs the whole loop, from ticket to deploy, and turns up missing access or context while the stakes are low.

From there we worked like E2B engineers, in its tools and on its new design system. We planned with the team every Monday, posted a short written update every day, and got on a call whenever we were blocked. Its designer reviewed our work like anyone else’s. The team, API key and usage limit pages came first.

“They became an organic extension of our engineering team, contributing to our codebase within days.”
Vasek MlejnskyCEO, E2B

Every webhook, visible

E2B customers use webhooks to hear about their sandboxes as things happen. We built monitoring for them end to end, from storing every delivery to the charts a customer checks when something looks off.

Webhook monitoring in the E2B dashboard: a week of deliveries, a 1.4% failure rate, and response times for one endpoint

Any delivery opens to its full request and response, so a customer can see exactly why one failed.

Webhook deliveries in the E2B dashboard: each sandbox event with its status, attempts and duration, and one delivery open to the payload E2B sent

We also shipped each sandbox’s event history, so a customer can follow one sandbox from the moment it’s created to the moment it’s killed.

One sandbox’s events in the E2B dashboard: created, updated, paused and resumed twice, then killed

The rest of the list was smaller but touched every customer: recovery flows for billing problems like a missing payment method, and timezone settings, so every timestamp reads in the customer’s own time.

The handoff

By summer, E2B had built its own dashboard team. That’s the ending we work toward: systems the client’s own team can run. We packaged the remaining work for the new team and made sure any engineer could run the full dashboard on their own machine.

Keep reading

Agents an enterprise can deploy, debug, and trust.

Work with us

Want outcomes like this in your product? Let's talk.

Rubric Labs is a small team of founder-level engineers with a research lab. We join your team, learn your problem, and build it with you all the way to production.

Book a call1 slot open in Q4 2026