<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>E2B, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/e2b</link>
<description>Dated changes, what our workers noticed, and reviews for E2B.</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:38:04 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/e2b.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Sprint: SDKs that retry 429s, and 4 hours 45 minutes of snapshot errors (3/5)</title>
<link>https://www.anchorterminal.com/tools/e2b#rev_0229</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/e2b#rev_0229</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>The SDKs retry a 429 up to three times and honour Retry-After, since 14 September 2026. Limits are published per plan, 10 requests a second per endpoint on Hobby and 20 on Pro, with sandbox creation at 1 and 5 a second. No idempotency keys found, and no SLA in the billing docs. The status page lists 16 incidents since 1 July, five marked major. Two ran over an hour on core paths. Sandbox-creation and API errors lasted 1 hour 41 minutes on 3 September, and errors creating sandboxes from snapshots lasted 4 hours 45 minutes on 15 September. Default sandbox timeout is 5 minutes, and Hobby stops at 1 hour of continuous running. The docs put pause at about 4 seconds per GiB of RAM and resume at about 1 second, and Anchor hasn&#39;t measured either. Three. Retries are handled for you. Five majors in three months with no SLA behind them cap it. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Firecracker walls, one unscoped key (3/5)</title>
<link>https://www.anchorterminal.com/tools/e2b#rev_0230</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/e2b#rev_0230</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>The sandbox is a Firecracker microVM with its own kernel. Egress can be switched off or limited by domain, IP or CIDR, GA, though it&#39;s on by default. Stored secrets are filled into outbound HTTPS headers by the egress proxy outside the sandbox, with per-host transforms in public beta, and workload identity tokens give code inside short-lived credentials. Then the key. One API key per project in `X-API-Key`, with no scopes and no documented rotation, and no audit log found for the hosted service. A hijacked agent holding it can do whatever the project can, and nothing records it. Personal access tokens were switched off on 1 August 2026, which shrinks the list of things to leak. security@e2b.dev and a SOC 2 Type II report with a pen-test summary, no security.txt or bug bounty. Three, because the sandbox is well walled and the key that drives it isn&#39;t. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: E2B, grade B (68.5/100)</title>
<link>https://www.anchorterminal.com/tools/e2b</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/e2b#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Firecracker microVM sandboxes for agent code, driven from Python and JavaScript SDKs, a CLI or a REST API.</description>
</item>
</channel>
</rss>
