# Eventual

Official pricing: https://www.eventual.ai/  
Category: paas · Isolation: not published

## Pricing regimes (raw)

- **Daft open-source self-hosted engine** (resource) [alt]
- **Eventual robotics data platform** (resource) [sales, beta, alt]

## Features

Yes: ≥24 h sessions, self-hosting, BYOC, open source, GPU, arm64, Python

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, Windows, macOS, Node.js, HTTP method/path egress rules, wake on request, live resize, live fork (no pause), memory fork, 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/eventual.json → feature_evidence

## Caveats

- Public open-source multimodal engine and cloud/BYOC offering; arbitrary Python UDFs may fit batch compute, but no captured per-vCPU tariff. Not a general interactive sandbox. Customer infrastructure and platform price must be distinguished.
- 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 2022; directory status **Active**. Research scope: public-product-researched. Source: https://www.ycombinator.com/companies/eventual

Daft distributed data compute

## Regime table

| Regime | When it applies | How billed | Numbers | Source |
|---|---|---|---|---|
| Native product; see regime notes | Incomplete or non-resource economics: rates remain null, never interpreted as free. | resource; CPU alloc, memory alloc | Unknown or native-unit billing; see facts below | https://www.daft.ai/ |
| Current applicable tariff unverified | Plan limits apply | Monthly fee; credits only as stated | fee=None; included usage=$None; concurrent=None; max session h=None | https://www.daft.ai/ |
| Retained disk / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.daft.ai/ |
| Snapshots / GiB-month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.daft.ai/ |
| Egress / GiB | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.daft.ai/ |
| IPv4 / month | Lifecycle/scope must be checked | Native add-on | unverified, not $0 | https://www.daft.ai/ |

## Verified billing facts and gotchas

1. Public open-source multimodal engine and cloud/BYOC offering; arbitrary Python UDFs may fit batch compute, but no captured per-vCPU tariff. Not a general interactive sandbox. Customer infrastructure and platform price must be distinguished.

## 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/eventual
- https://www.daft.ai/
- https://www.daft.ai/llms.txt

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.