# Feature status

A clear inventory of the platform, its gaps and the release gates.

Status: Updated 10 September 2026 · No production compute availability

## Implementation and release status
| Capability | Current state | Required before customer use |
|---|---|---|
| Website, searchable docs, pricing | Implemented | Hosting verification |
| Account authentication and API keys | Implemented locally | Production service configuration |
| Inventory, reservation and renewal logic | Implemented locally | Verified hardware and payment/controller checks |
| Stripe top-ups and refunds | Sandbox adapter implemented | Paid sandbox settlement, webhook and live configuration |
| MCP rental management | Implemented | Accessible API and client verification |
| Boardly rental attachment | Integration in development | Tenant isolation and end-to-end tests |
| OpenClaw / Hermes access | Integration guides; shared MCP bridge | Installed-client compatibility verification |
| Screenshots, keyboard, mouse, shell | Planned controller contract | Physical desktop controller and authorization tests |
| Browser desktop / human takeover | Planned | Session broker and live transport |
| File transfers and ephemeral reset | Planned | Storage implementation and cleanup verification |
| Templates, clone, resize, multi-screen | Roadmap | Capacity-aware runtime implementation |
| Audio, events, streamed terminal | Roadmap | Authenticated streaming transport |
| Managed model routing / agent threads | Roadmap | Provider integration, metering and retention |
| Proxies | Catalog/quote foundation | Supplier access and connection tests |
| NAS/S3 storage and disaster recovery | Architecture proposal | Hardware/provider configuration and restore drills |
| Enterprise SSO, SLA and regional fleets | Roadmap | Commercial and operational readiness |

## Release gates
A computer must have verified identity, hardware, awake/healthy state, isolation and sanitization before allocation. Billing must be reconciled against confirmed provider events. Rental activation requires controller acknowledgement. Access revocation must terminate existing access, not just reject new login attempts.

## Documentation is not a capability grant
Planned features are documented to make the platform design reviewable. An endpoint in a design discussion is not a deployed API. The [OpenAPI file](/openapi.json) describes the implemented management surface; runtime features will be added only as their handlers exist.