Skip to main content

​
What does the E2B integration do?

Steadwing accesses sandbox execution data from your E2B account to diagnose AI application failures. During root cause analysis, Steadwing pulls sandbox logs, lifecycle events, resource metrics, and template configurations to identify why sandboxed code execution failed or degraded.

​
Why Use E2B with Steadwing?

Sandbox Monitoring

List running and paused sandboxes to understand what was active during an incident

Execution Logs

Pull sandbox logs to find execution errors, crashes, and unexpected output

Resource Analysis

Detect CPU, memory, and disk exhaustion that caused sandbox failures

Lifecycle Tracking

Identify unexpected sandbox terminations, timeouts, and state changes

​
How do I connect E2B to Steadwing?

​
Step 1: Get Your E2B API Key

  1. Sign up or log in at e2b.dev
  2. Navigate to the Dashboard
  3. Go to Settings → API Keys
  4. Copy your existing API key or create a new one
Store your API key securely. It provides access to your E2B account data including sandbox logs and metrics.

​
Step 2: Connect E2B in Steadwing

  1. Navigate to Steadwing Settings
  2. Find the E2B integration card
  3. Click to expand the collapsible form
  4. Paste your API key in the API Key field
  5. Toggle the switch to Enable the integration

​
What data does Steadwing pull from E2B?

​
Data Collection

Steadwing queries E2B for:
  • Sandbox List - Running, paused, and recently terminated sandboxes and their states
  • Sandbox Logs - Execution output, error messages, and crash reports from sandbox processes
  • Lifecycle Events - Sandbox creation, termination, pause/resume events, and timeout triggers
  • Resource Metrics - CPU, memory, and disk usage to detect resource exhaustion
  • Template Status - Build status and configuration of sandbox templates
  • Team Metrics - Concurrent sandbox counts and limit usage across your team

​
What permissions does the E2B integration need?

​
Required Permissions

The E2B API key requires read access to:
  • Sandboxes - Read sandbox list, status, and timeout configuration
  • Logs - Read execution output and error messages
  • Lifecycle - Read start, stop, pause, resume, and timeout events
  • Resources - Read CPU, memory, and disk usage metrics
  • Templates - Read template list, build status, and installed packages
  • Team - Read concurrent sandbox counts and usage limits
Steadwing only needs read access to your E2B account. It never creates, modifies, or terminates sandboxes.

​
FAQs

Steadwing reads sandbox states, execution logs, lifecycle events, resource metrics, and template configurations. It does NOT create, modify, or terminate any sandboxes.
No. E2B uses API key authentication — just paste your key in Steadwing Settings and the integration connects immediately. No OAuth redirect required.
No. Steadwing only has read access. It queries sandbox states, logs, and metrics but never executes code or modifies sandbox configurations.
Steadwing can still access logs and lifecycle events for recently terminated sandboxes, subject to E2B’s data retention policy.
The integration will stop working. Simply create a new API key in your E2B dashboard and update it in Steadwing Settings to reconnect.
Need additional help? Please reach out to us at hello@steadwing.com