LoginSign Up
← Back to all sparks
O

OpenStatus

INFRA · APIS
Velocity5.0

Open-source synthetic monitoring and status page platform

www.openstatus.dev ↗

OpenStatus is closing protocol gaps and adding enterprise auth, positioning monitoring as a queryable layer in AI workflows.

uptime-monitoringgrpcenterprise-authdeveloper-toolsincident-management
◆Current state
OpenStatus ships incremental additions that expand its protocol coverage (HTTP, TCP, and now gRPC) and enterprise capabilities (SAML SSO, OAuth-based MCP connections). The Dashboard Response Logs give teams searchable, filterable access to every check run. The Monitor Pack add-on creates a new pricing tier for teams that need monitoring at scale without a full plan upgrade. OAuth for the MCP server is the most recent signal: teams can now connect Claude, Cursor, or any MCP client with a consent screen rather than a raw API key.
◆Where it's heading
OpenStatus is becoming enterprise-viable while maintaining its developer-focused identity. SSO, SAML, and OAuth-based MCP auth are the credentialing story; gRPC monitoring and detailed response logs are the technical breadth story. The MCP track is the most interesting signal for where OpenStatus is headed—making monitoring data queryable from within LLM-assisted workflows.
◆Prediction
WebSocket and DNS-level monitoring are likely protocol additions. On the enterprise side: alert routing, runbook integration, and deeper incident management. The MCP investment suggests OpenStatus wants to be the observability source agents query when debugging production issues in AI-assisted development workflows.

◆Recent moves

  1. 5d ago

    OAuth for the MCP server

    Replacing API key authentication with an OAuth consent screen for MCP connections reduces the operational risk of key management and makes OpenStatus more auditable in multi-user team setups. This is the expected progression from raw API key access as MCP becomes a mainstream integration pattern.

    View source ↗
  2. 7d ago

    Monitor Pack

    Monitor Pack adds 10 monitors for $15/month as a modular add-on—useful for teams that need more monitoring capacity without upgrading their core plan tier. This pricing flexibility is a common request pattern and reduces churn from teams that were otherwise limited by monitor count.

    View source ↗
  3. 9d ago

    Dashboard Response Logs

    Dashboard Response Logs make every check run searchable and filterable—this is audit-grade visibility into monitoring history, useful for post-incident analysis and for teams that need to demonstrate SLA compliance. It's a meaningful step beyond just alerting on failures toward understanding patterns across the full check history.

    View source ↗
  4. 17d ago

    gRPC Monitoring

    gRPC monitoring extends OpenStatus beyond HTTP/TCP to cover services using gRPC health checks—a protocol common in microservices architectures. Teams running gRPC-based APIs previously had to use workarounds or separate monitoring for those endpoints; this closes that gap.

    View source ↗
  5. 1mo ago

    SAML single sign-on

    SAML SSO through Okta, Entra ID, or any SAML provider removes per-seat credential management for enterprise teams and is a prerequisite for procurement approvals in regulated organizations. In context with OAuth for MCP and gRPC monitoring, it's part of OpenStatus's consistent push toward enterprise-grade credentialing and protocol coverage.

    View source ↗
  6. 1mo ago

    Command Menu for the Dashboard

    ⌘K command menu for dashboard navigation—a quality-of-life improvement for power users who navigate frequently. Reduces click depth for common actions but doesn't change what OpenStatus can monitor or how.

    View source ↗