Welcome to Incido
Incido helps your team communicate service disruptions clearly and quickly. From the Dashboard you can report incidents, publish maintenance updates, and keep customers informed through your public status page.
Quick start
If you are new to Incido, start with Onboarding and first organization, then move to Components and taxonomies to define the services customers depend on. After that, use Status pages, Incidents, and Maintenances as your core day-to-day workflow. When you connect monitoring or the API, read Best practices for recommended integration and layout patterns.
What you can do
| Area | What it covers |
|---|---|
| Incidents | Declare outages, post updates, and resolve issues while subscribers are notified automatically. |
| Maintenances | Schedule upcoming work so customers know what to expect before it happens. |
| Status pages | Customize public (or private) pages with your branding, domain, and component layout. |
| Monitors | Track uptime with HTTP and heartbeat checks that trigger incidents when something goes wrong. |
| Subscribers | Manage who receives email or webhook notifications about your services. |
| Settings | Configure components, themes, email sender addresses, webhooks, and organization defaults. |
What changes on the public frontend
Most dashboard actions eventually change what customers see on the public status page. Incident and maintenance updates appear on public timelines, component and status page configuration changes affect the structure and labels customers read, and theme updates change the visual presentation. Subscriber delivery settings do not change page visuals directly, but they decide whether customers receive updates by email or webhook.
Operational effects
Publishing updates can trigger subscriber notifications, depending on the notification options you choose and each subscriber's preferences. Public status page updates usually appear within a few seconds after publishing. If your team works across several related surfaces, moving between Status pages, Subscribers, and Themes and editors keeps communication and presentation aligned.
Navigating these docs
The sidebar mirrors the main product areas: getting started guidance, best practices, operational workflows, and configuration topics. For practical operations, start with Status pages, Incidents, and Maintenances. For automation and deduplication patterns, see Best practices. For communication channels and appearance, continue with Subscribers, Email sender addresses, and Themes and editors.
Troubleshooting
You are not sure where to start in the docs. Begin with Onboarding and first organization, then move to Status pages. Those two pages establish the base workflow and link to the most common next steps.
Customers are not seeing expected updates. Check the relevant workflow page first: Incidents, Maintenances, or Status pages. Each page explains publication conditions and common causes when updates do not appear.