# Vibrant Labs

Official pricing: https://vibrantlabs.com/  
Category: agent-sandbox · Isolation: not published

## Pricing regimes (raw)

- **Native service** (resource) [alt]

## Features

Yes: ≥24 h sessions

No: snapshots, memory snapshots, fork/clone, pause/resume, persistent disk, volumes, idle auto-stop, start from your own snapshot, your own Docker/OCI image, Docker inside, nested virtualization, browser, desktop GUI, computer-use API, browser + desktop control, anti-bot stealth, CAPTCHA solving, preinstalled agents, SSH, public IPv4, HTTPS preview URLs, egress allowlist, static egress IP, self-hosting, BYOC, open source, SOC 2, HIPAA, SSO, GPU, arm64, Windows, macOS, Python, Node.js, HTTP method/path egress rules, wake on request, live resize, live fork (no pause), memory fork, EU data residency, MCP server, automatic snapshots, snapshots on demand, agent harness API, hosted agent API (their own agent), inbound access rules, firewall inside (nftables), secret proxy, secret proxy for any API, extra volumes, shared volumes

Unknown: everything else. Evidence (source + quote) per feature: https://battleships.dev/data/providers/vibrant-labs.json → feature_evidence

## Caveats

- Vibrant Labs (Exploding Gradients Inc., the Ragas team) sells autoscaled RL post-training DATA (tasks, environments, verifiers) for frontier agents — tool-use and computer-use modalities — not rentable compute. No pricing (404), no docs, no API.
- Null values mean unknown, not free/unlimited. No model-token cost, tax or unverified ancillary charge included.
- Native browser/device/task/credit prices with unknown CPU/RAM are deliberately non-priceable. Check regime before interpreting any partial resource estimate.

## How this provider charges


YC: Winter 2024; directory status **Active**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/vibrant-labs

RL environment infrastructure

## Regime table

| Regime | When it applies | How billed | Numbers | Source |
|---|---|---|---|---|
| Native service | Hardware and complete resource tariff unverified. | resource; CPU alloc, memory alloc | Unknown or native-unit billing; see facts below | https://vibrantlabs.com/ |
| Custom / unverified | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | https://vibrantlabs.com/ |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://vibrantlabs.com/ |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://vibrantlabs.com/ |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://vibrantlabs.com/ |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://vibrantlabs.com/ |

## Verified billing facts and gotchas

1. Public AI-agent training environments and simulations; pricing 404. May be generated training tasks rather than general compute rental. Public product but no verified CPU/RAM tariff.

## Worked example

Requested: 4 vCPU/8 GiB, 50 simultaneous × 8 h/day × 22 days = **8,800 instance-hours**, 30% CPU; 50 GiB snapshots and 100 GiB egress. A month is 730 hours only when explicitly used in rate conversion.

**Total: unknown.** This product does not publish a verified complete 4-vCPU/8-GiB tariff and/or the service bills a different unit. Fifty concurrent instances and eight-hour sessions are not automatically supported. Neither 30% utilization nor retained snapshots can be converted into free resources. Use the native plan terms above and request the missing CPU/RAM, retention, egress and concurrency quote.

## Sources and coverage

- https://www.ycombinator.com/companies/vibrant-labs
- https://vibrantlabs.com/

Page captures and documentation indexes/bundles are in `raw/`; provider JSON lists the evidence paths. HN query results were captured separately as `<id>--hn.txt`; they are discovery leads, not current tariff authority. Downloaded docs do not imply every feature was verified; unsupported assertions remain null.