Getting Started

Welcome to Statuswerk. This guide walks you through the essentials: creating your first status page, adding components, and going live.

1. Sign up and create your workspace

After registering, you land in your dashboard. Each account gets one workspace — the container for your status pages, team members, and subscribers. Adding colleagues is covered under Team.

The dashboard speaks German or English — on your first visit, whichever your browser asks for. You can change it any time in your profile under Language. The same language applies to every email Statuswerk sends you: confirmations, orders, approval requests. Invitations to your team go out in your language. Your public status page's language is set separately.

2. Create a status page

In Dashboard → Statuspages, click New Statuspage. You need:

• Name — shown as the page title (e.g. Acme Cloud)
• Slug — the URL segment under our default subdomain (e.g. acme → acme.statuswerk.eu)
• Description — what services this page covers

Your page is immediately public at acme.statuswerk.eu.

3. Add components

Components are the services you want to communicate status about — APIs, databases, regions, dashboards. Group related components into component groups for clarity.

Production
├── API
├── Web App
└── Database

Staging
└── API

Each component has a current status: Operational, Degraded Performance, Partial Outage, Major Outage, or Under Maintenance.

4. Subscribers (optional)

If you want users to receive notifications when an incident is opened or a maintenance is scheduled, enable subscriptions on your status page. Subscribers can verify via email, SMS, or webhook.

See Subscribers for details.

5. Your first incident

When something breaks, go to Statuspages → Incidents → New. Pick severity, affected components, a title, and a first update message. Subscribers are notified immediately if subscriptions are enabled.

You can keep posting updates as the situation evolves and close the incident when resolved.

If a disruption only affects one customer, it does not have to go on the front page: see Unlisted Entries.

Next steps

Setting up

• Custom Domains — point your own domain at your status page
• Status page settings — appearance, language, timezone, SEO

The features in detail

• Components · Incidents · Maintenance
• Uptime — how the number your customers quote comes about
• Subscribers · Templates · System Metrics
• Monitoring — have your URLs checked from six regions

Distributing and embedding

• Chat & Webhooks — Slack, Teams, Discord, Google Chat
• Badges & embedding — show the status on your own website

Controlling access

• Private Status Pages · Unlisted Entries
• Audit Log — see who changed what

Automating

• API Tokens · API Reference · AI assistants (MCP)

Help

Bottom right in the dashboard is the support chat. If something doesn't work, is unclear or missing, write there.

An AI assistant answers first from this documentation; its answers are marked as automatic. It only sees your messages in the chat, not your account, and runs at STACKIT in Germany. If it cannot help, if it is about invoices, a bug or your account, or if you click "Talk to a person instead", a person from the team takes over — usually within a few hours on workdays. You see our answers in the chat and also get them by email.