Web
LIVE
Public site and private Control Centre.
Explore the Lab's interfaces, control plane, orchestration, inference, knowledge and physical AI plans, with evidence and maturity shown for each component.
How people and tools reach the Lab.
LIVE
Public site and private Control Centre.
EXPERIMENTAL
Optional chat route. Reachability is not claimed.
EXPERIMENTAL
Mobile companion, being redesigned.
UNKNOWN
No evidence for a supported command-line interface.
State, policy and access. The API and PostgreSQL are the authority.
LIVE
Sign-in and server-side sessions.
UNKNOWN
No separate policy engine is documented.
EXPERIMENTAL
Preferences exist. The job API does not enforce them.
UNKNOWN
Job and schedule state is stored. A general memory service is not documented.
LIVE
PostgreSQL-backed queue.
LIVE
Health, usage and a public status feed.
LIVE
Request protection and audit trail.
How work gets done. OpenClaw is one component here, not the whole system.
LIVE
One execution dependency of the Lab.
LIVE
Pull jobs from the queue.
EXPERIMENTAL
Defined workflows, still being tested.
LIVE
Schedules stored with job state.
UNKNOWN
Long multi-agent chains are a research question.
Where models run.
LIVE
Light inference on the MacBook.
LIVE
Configured hosted provider.
LIVE
Configured hosted provider.
UNKNOWN
Not documented here.
Memory, capture and the tools agents may reach.
LIVE
Owner-described vault.
LIVE
Versioned sync, owner-described.
LIVE
Meeting capture, owner-described.
UNKNOWN
No documented agent web tool.
UNKNOWN
No documented external API tool catalogue.
UNKNOWN
No documented MCP integration.
Research only. Nothing is installed or built.
UNKNOWN
No hardware installed.
UNKNOWN
No hardware installed.
UNKNOWN
No prototype.
UNKNOWN
No commitment or timeline.
OpenClaw is one orchestration component, not the whole Lab. API/PostgreSQL alone owns scheduling and job state. Interfaces and inference providers do not establish automatic routing or private knowledge access.
Architecture, infrastructure, local AI, knowledge, observability and security are documented underneath SYSTEM. Live status is loaded from a reviewed public feed; a configured component is not proof of current health.