Public alpha status
What actually works today, and what does not. This page is deliberately blunt: an unexercised capability is never reported as working.
Working
| Capability | Status |
|---|---|
| Firecracker microVM sandboxes | Working, exercised end to end |
| Docker runtime | Working, trusted deployments only |
| Exec, stdin, environment, cwd | Working, bounded by time and output size |
| File read/write/list/delete | Working, confined to the workspace |
| Coding guest image | Working — Git, CA certificates, Python, curl, tar |
| HTTPS Git clone, edit, diff | Working, verified inside a real microVM |
| Workspace snapshots | Working, portable between owners |
| PostgreSQL state, leases, quotas | Working |
| S3-compatible object storage | Working |
| Worker recovery and fencing | Working — reassignment at a higher generation, stale workers rejected |
Limited
| Capability | Limitation |
|---|---|
| Signup | Invite-only. No open registration during alpha. |
| Capacity | Limited by the hosted provider's free allowance. When it is exhausted, creation stops with TEMPORARY_CAPACITY_UNAVAILABLE rather than overage. |
| SLA | None. This is alpha software without a support commitment. |
| Regions | A single execution region during alpha. |
| API stability | Endpoints may change before 1.0. |
| Snapshots | Workspace archives are portable. VM memory snapshots are not. |
Not yet implemented
Stated plainly so nobody plans around them:
- Per-tenant snapshot and persistent-storage byte quotas. Per-request size ceilings exist; aggregate accounting does not yet.
- A control-plane sandbox lifetime reaper. Lifetime is enforced by the runtime; a worker restart resets the in-process timer.
- Multi-host validation with separate control and worker machines. Same-host multi-worker recovery is proven; genuinely distributed operation is not yet.
- An audit log viewer in the dashboard. Events are recorded, the UI is not built.
- Self-service billing. Usage is metered and displayed; payment collection is behind a manual activation step.
Hosting model
Cloud execution is provided by a hosted sandbox provider with Firecracker-based isolation. AIec's own native Firecracker implementation is complete and is what self-hosted deployments run — but the hosted capacity is not AIec operating its own hardware. We report these separately rather than merging them into one claim.
| Claim | Status |
|---|---|
| AIec native Firecracker runtime | Complete and verified |
| Hosted Cloud execution capacity | Provided by a third-party Firecracker provider |
| AIec-operated multi-host worker fleet | Not deployed |
Security posture
The full picture, including what is not yet enforced, is in SECURITY.md. Report a vulnerability to security@gobrowse.dev, not to a public issue.