Stazus docs
Stazus docs

Introduction

Stazus documentationGet startedConcepts

Planned features

Feature availabilityStatus pages

Monitoring

MonitorsChecks and resultsLatency alertingMaintenance windows

Incident response

IncidentsNotificationsTeams and access

Developer API

Developer APIAuthenticationProjectsEndpointsAnalyticsIncidentsErrors and limitsMigrate from v1

Account and help

Account and security

Help

Support

Updates

Changelog
Changelog launchedDocumentation UpdatesDeveloper API v2Scope-aware maintenance windows

Feature availability

See which Stazus areas are ready to use and which areas are still planned.

The main navigation shows features that are available for operational use. This page also lists planned areas that are available only through documentation or direct preview links.

Available now

AreaWhat you can do
DashboardReview open incidents and open common team areas.
ProjectsCreate projects and manage their monitored endpoints.
EndpointsConfigure HTTP checks, run manual checks, and inspect results.
IncidentsCreate, update, merge, resolve, and review incidents.
My UpdatesFilter in-app updates and mark them as read.
Contact methodsAdd, verify, enable, and remove personal email destinations.
Team settingsManage team details, members, roles, invitations, and subscriptions.
Account settingsManage profile data, email verification, password, and authenticator setup.
AnalyticsReview team monitoring performance across projects.
APICreate scoped tokens and integrate through the Developer API.
MCPConnect an AI client with a user-bound token.
MaintenanceSchedule team, project, and endpoint windows that suppress automatic incidents.

Planned areas

The following areas are not in the main navigation. Some direct preview routes show Coming soon. Do not depend on these areas for operational work.

  • Status pages
  • Integrations
  • Map
  • Reports
  • Forecast

Maintenance availability

The team-level Maintenance page is available. Editors can schedule one-time or recurring windows for the whole team, one project, or one endpoint.

During maintenance, Stazus keeps check evidence. It marks covered checks as suppressed. It excludes covered checks from automatic incidents, latency learning, and uptime statistics.

See maintenance windows for the procedure.

Public updates

Incident checkpoints are available now. The incident page labels them as public updates. Status page and integration delivery are planned, so do not treat a checkpoint as published customer communication yet.

Last updated on

Concepts

Learn the records and states that Stazus uses for monitoring and incident response.

Status pages

Learn the current status page availability and how to prepare incident updates.

On this page

Available nowPlanned areasMaintenance availabilityPublic updates