Introduction

What is Banata?

Banata is a cloud platform that provides two core primitives for automation:

• Browser Sessions — On-demand Chromium instances with optional anti-detection, accessible via the Chrome DevTools Protocol (CDP). Connect with Puppeteer, Playwright, or any CDP-compatible client.
• Sandboxes — Isolated code execution environments with shell access, file system operations, and optional browser pairing. Run scripts, build projects, or orchestrate multi-step workflows.

Both are accessed through a single REST API. You create a session, get back a connection URL, and start working.

How It Works

Your Application
    |
    v
Banata API (REST)
    |
    ├── POST /v1/browsers   → Browser session
    │       Returns CDP WebSocket URL
    │       Connect with Puppeteer/Playwright
    |
    └── POST /v1/sandboxes   → Code execution sandbox
            Returns terminal WebSocket URL
            Execute commands, write files, run code

1. Authenticate with an API key (Authorization: Bearer br_live_...).
2. Create a session — browser or sandbox — with a single POST request.
3. Poll for readiness — the session moves through queued → assigning → ready.
4. Connect and work — use the returned WebSocket URL to interact with your session.
5. Clean up — end the session with a DELETE request when you are done.

Browser Sessions

Browser sessions give you a real Chromium instance running on a remote machine. Depending on your plan, sessions can include:

• Anti-detection (Stealth) — Fingerprint generation, navigator/WebGL spoofing, and CDP-level overrides that pass major bot detection suites. Available on Builder plans and above.
• Session recording — MP4 capture of everything that happens in the browser. Available on Pro plans and above.
• CAPTCHA solving — Automatic reCAPTCHA, hCaptcha, and Turnstile solving.
• Egress profiles — Choose between shared datacenter IPs, dedicated datacenter IPs, rotating residential IPs, static residential IPs, or bring your own proxy.
• Profile persistence — Save and restore browser profiles (cookies, localStorage) across sessions.
• Dedicated isolation — Get an entire machine to yourself. Available on Pro plans and above.

Typical use cases: web scraping, QA and synthetic monitoring, login automation, agentic browsing workflows, and anti-bot-sensitive flows.

Sandboxes

Sandboxes give you isolated Linux environments for running code and commands. Each sandbox includes:

• Multiple runtimes — Bun (JavaScript/TypeScript), Python 3, or a minimal base Linux container.
• Shell access — Full terminal via WebSocket. Run any command the runtime supports.
• File system — Read, write, list, upload, and download files within the sandbox workspace.
• Standard compute shape — Sandboxes currently run on a standard 2 shared vCPU / 4 GB worker shape.
• Browser pairing — Optionally attach a Banata browser session to a sandbox for end-to-end automation. Available on Pro plans and above.
• AI agent integration — Built-in OpenCode support for prompt-driven code generation and task execution.
• Pause and resume — Suspend a sandbox to save costs, then resume exactly where you left off.
• Human handoff — Request human intervention for MFA, CAPTCHAs, or ambiguous UI, then resume automation.

Typical use cases: CI/CD pipelines, code generation, data processing, automated testing, and multi-step AI agent workflows.

Plans and Feature Availability

Not all features are available on every plan. Here is a summary:

See Billing & Plans for complete plan details.

Key Concepts

API Keys

Every request to Banata requires an API key in the Authorization header. Keys are scoped to an organization and carry permissions for the resources you can access.

Authorization: Bearer br_live_...

API keys are created through the Banata dashboard or the seed endpoint during development.

Sessions

A session is the fundamental unit of work. Whether you create a browser session or a sandbox session, you get an isolated environment that runs until you end it or it reaches its time limit.

Sessions move through a state machine: queued → assigning → ready → active → ending → ended. You can poll the GET endpoint to track progress.

Organizations

Resources are scoped to organizations. Usage limits, billing, and concurrent session caps are all enforced at the org level.

SDK

What's Next

• Quick Start — Launch your first browser session in under 5 minutes
• Browser Sessions — Deep dive into browser session creation and options
• Sandboxes — Learn about code execution environments
• API Reference — Full endpoint documentation