Quick Start Guide

Choose the services your team depends on, activate monitoring, and check that an alert reaches you. Vendor status adds context to your investigation; keep your own application and network checks alongside it.

Create your account and activate monitoring

1. Create an account using an available sign-in method. If you use email, follow the verification link in your inbox.
2. Select your services in onboarding. If you started from a vendor's alert form, check that the saved service is selected.
3. Review the available incident history. No recorded incident in the preview does not prove the vendor has never had an outage.
4. On Confirm & activate, review your selected plan, its trial terms, and its price after the trial.
5. Before activating, use Send test alert and check the inbox shown beside it. The message is labeled as a test. If sending fails, use Try sending again; check spam if a sent message is missing.
6. Activate the trial if eligible. Returning customers use their existing plan or choose a paid subscription. Completing activation takes you to the welcome page.

See current plans and trial terms. You can manage your subscription and cancellation from billing settings.

Verify delivery after setup

To send another test after activation, open Integrations, find the destination, and use its test action. Check the actual inbox or channel: a successful request alone does not establish that everyone can see the message. An email test does not also verify Slack or Teams.

A test proves the delivery path. A real incident notification or useful historical record provides different evidence of the product's value.

Choose relevant components and notifications

1. Open a service from Monitors to reach its Overview. Under Monitored components, choose Add or remove (or Pick components for an empty selection).
2. Choose Only the components I choose, select the components or regions your team uses from the options that provider exposes, then click Save.
3. Open Notifications and configure each monitor's destinations and status filters.
4. Verify each destination with a test. Recovery notifications follow the configured alert rules.

Vendor checks follow reported status changes. Update timing depends on the provider, polling, and delivery; a green vendor page does not rule out an account-specific issue.

For engineering teams

Start with a dependency involved in a recurring workflow, such as GitHub Actions for deployments. Add the service, select the relevant component, and configure the engineering channel responsible for responding.

• Engineering workflow
• Set up Slack alerts
• Set up PagerDuty
• Third-party outage runbook

For internal IT teams

Start with the business tools staff ask about. Route alerts to IT and create a board containing the monitors staff need to see. Share its link in your intranet or incident update.

• IT workflow
• Set up Microsoft Teams alerts
• Shared status boards

Unprotected boards are viewable by anyone with the link and do not grant workspace access. Include only services and labels you intend to share. Board features and limits depend on the plan. Adding an internal service means your team maintains its status manually.

If setup stops

• No verification email: check spam, then use the resend control when available. If a link expired, request a fresh link rather than repeatedly opening it.
• No trial available: trials are limited to eligible first-time customers. Check your existing subscription or choose a paid plan.
• Activation failed: read the message and retry using the activation control. A saved service selection alone does not mean alerts are active.
• Channel needs approval: ask your workspace administrator for the required installation permission, or use an available destination your team controls.
• Test arrives but no incident alerts: check that monitoring and the destination are active, the plan includes the channel, and notification rules include the relevant components and severity. There may have been no matching status change.

Choose a plan by workflow

Compare alert channels, sharing and reporting first, then confirm monitor and member capacity. Current limits and prices are listed below.

• Basic: $5/mo - 5 monitors
• Starter: $20/mo - 15 monitors
• Pro: $60/mo - 40 monitors
• Team: $150/mo - 90 monitors