Status
Service status for Extentos. There is no public status page or uptime instrumentation yet — Extentos is pre-1.0. The backend that powers the browser simulator and the managed AI gateway runs at api.extentos.com. For what shipped, see the changelog; to report an outage or incident, email hello@extentos.com with the [incident] prefix.
Honest status: there is no public status page or uptime dashboard yet. Extentos is pre-1.0, and formal uptime instrumentation (a hosted status page, historical SLAs) hasn't been stood up. This page will link a dedicated status page once one exists.
What runs where
- Backend —
api.extentos.com. This is the one piece of Extentos infrastructure with runtime dependencies: it powers the browser simulator session hub (WebSocket, voice STT/TTS proxy, event-log persistence) and the managed AI gateway behind the Phase-4 voice assistant. - What does not depend on Extentos uptime — the MCP server runs on your machine (or via
npx), on-device simulation (LocalSimTransport) never reaches a backend, and production apps on real Ray-Ban Meta hardware (RealMetaTransport) talk to the glasses over Bluetooth, not to Extentos. An Extentos backend outage does not take down a shipped app unless that app uses the managed gateway.
Reporting an incident
If something on the Extentos backend looks down (simulator sessions won't mint, the gateway returns errors), email hello@extentos.com with the [incident] prefix. Include the timestamp, what failed (session mint / gateway / event log), and any error surfaced by your agent or the simulator. There's no SLA at launch — see support for honest response expectations.
Where to look instead
- Changelog — what shipped and when (the closest thing to a "what changed" feed today).
- Support — diagnostics, bug reports, and the security disclosure path.
Related
- Changelog — release history
- Support — file issues, self-diagnose
- The managed AI gateway — the backend-dependent assistant path
Support
How to get help with Extentos — which GitHub issue tracker owns which component (android-glasses, swift-glasses, mcp-server), self-service diagnostics through the extentos-mcp CLI (whoami, status, getEventLog), what to include in a bug report so it's actionable across the four components (MCP server, native libraries, backend, simulator UI), the private email path for security and billing, and pre-1.0 response expectations. No paid support tiers exist at launch.
License
Extentos license terms. The @extentos/mcp-server npm package is MIT-licensed (declared in its package.json, surfaced on the npm package page). The Android library (com.extentos:glasses) and the iOS library (Extentos) are distributed as public packages with proprietary source. This page states the current, verifiable licensing position per component.