# How StackAI uses E2B

As published on [e2b.dev](https://e2b.dev/customers/stackai), June 2026. Captured by usedby on 2026-10-06.

- Company: [StackAI](https://www.usedby.ai/companies/stackai.md)
- Tool: [E2B](https://www.usedby.ai/tools/e2b.md)

## What the story says

StackAI runs the code that its customers' and LLMs' agent workflows generate inside isolated E2B sandboxes. It uses them for custom Python and JavaScript code, computer use and RPA replays, and browser-based agent sessions for customers in regulated industries.

Summary written by usedby from the source page, in English. The figures are those of E2B and StackAI, not ours.

> Custom Code. Users write and execute Python or JavaScript directly inside agent workflows through the Code Node. E2B handles the sandboxing, so every execution runs in a secure, isolated environment regardless of workflow complexity.

> We built our own code sandbox VM, and it neither scaled well nor had all the features we needed. We couldn’t afford the time to take away from building revenue-generating features for 5-6 of our platform engineers to build and maintain the infrastructure
>
> Tony Rosinol, Co-Founder at StackAI

## What usedby checked

We compared the story with its live page on 2026-10-06.

- Checked: the passage quoted above is copied word for word from the page, near the name of StackAI.
- Checked: each number in our summary is printed on the page.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: StackAI uses E2B. Confirmed line. Latest check across sources: 2026-10-06.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/stackai-e2b · How we check: https://www.usedby.ai/methodology