Frequently Asked Questions

Sandbox Platform provides isolated cloud compute environments for AI agents and automation. We offer:

• Sandboxes: Secure Linux environments for code execution
• Browser Containers: Remote Firefox/Chrome instances for web automation
• Desktop Containers: Full Linux desktops accessible via web browser
• Ephemeral Instances: Short-lived containers for batch processing

1. Create an account from the login page

2. Generate an API key from your dashboard

3. Make your first API call:

curl -X POST https://api.ab0t.com/sandboxes -H "X-API-Key: your_key"

Check our Developer Guide for detailed tutorials.

Sandboxes run Ubuntu Linux and support virtually any language or tool:

• Python (with pip)
• Node.js (with npm)
• Go, Rust, Java, Ruby, PHP
• Docker (in supported tiers)
• Any Linux CLI tools

Browser containers include Firefox, Chrome, and Chromium with full Playwright/Puppeteer support.

We bill based on compute usage (per-minute billing, 1-minute minimum):

• Sandboxes (ab0t.micro): $0.02/hr
• Browser containers: $0.1/hr
• Desktop containers: $0.2/hr

See our pricing page for all instance types and volume discounts.

Yes! New accounts receive $10 in free credits to try the platform. That's roughly 500 hours on ab0t.micro or 100 hours of browser time.

We also offer extended trials for startups and educational institutions. Contact sales@ab0t.com.

Yes. You can set monthly spending limits in your dashboard under Billing settings. When you reach 80% of your limit, we'll send an alert. At 100%, new containers will be blocked but running containers continue.

Each sandbox runs in a dedicated container with:

• Separate process, network, and filesystem namespaces
• Resource limits (CPU, memory, I/O)
• Restricted syscall access via seccomp
• No access to host system or other containers

See our Security page for technical details.

No. Your sandbox contents are private. We don't access, analyze, or use your code or data except:

• When you explicitly request support assistance
• To investigate security incidents or abuse reports
• When required by valid legal process

All data is encrypted at rest (AES-256) and in transit (TLS 1.3).

Typical cold start times (from warm pool, which is the default for Pro/Enterprise):

• Browser containers: <1 second (warm pool) · 10–30s cold
• Sandboxes: <1 second (warm pool) · 30–90s cold
• Desktop containers: <1 second (warm pool) · 45–90s cold

Free tier uses cold starts. Pro and Enterprise get priority warm-pool access.

Default limits per container:

• CPU: 1 vCPU (burstable)
• Memory: 2 GB
• Storage: 10 GB
• Network: 1 Gbps

Higher limits available on Pro and Enterprise plans.

Docker-in-Docker is available on Pro and Enterprise plans. It requires elevated permissions that we enable on request. Contact support to enable this feature.

Resources have configurable idle timeouts (default 30 minutes, set via auto_stop_minutes). When idle time is exceeded:

• Sandboxes: stopped gracefully; filesystem is preserved and the sandbox can be restarted
• Ephemeral containers (browsers, desktops): terminated; filesystem is discarded
• Billed time ends at stop — you only pay for active minutes