The status page alternative from Europe
When something breaks, your customers hear it from you.
Statuswerk shows incidents and maintenance on your status page and notifies everyone affected. That saves support questions and builds trust. Hosted in Germany, with European providers only.
- No trackers, no third-party requests
- Subscriber import when you switch
- API, webhooks and MCP
How an incident runs
You report once. The rest runs itself.
An example: at 03:12 at night your API stops answering. Scroll on and watch what your customers see.
You report an incident by hand via API via MCP
The monitoring alerts you or switches the component
-
03:11
Everything is running
Checks from 2 European regions watch your services. Your customers see: operational.
-
03:12
One region reports a timeout
Nothing happens yet. A single vantage point can be wrong, and a false alarm costs trust.
-
03:12
A second region confirms
Only now does the outage count. Statuswerk alerts you, or switches the component itself.
-
03:13
Everyone affected knows
You open the incident: by hand, via API or via MCP. Whoever subscribed to the API gets an email or SMS, your team reads it in Slack, Microsoft Teams, Discord or Google Chat. Nobody has to ask support.
-
03:41
Resolved
You close the incident, the all-clear goes to every subscriber. The day stays visible in the 90-day history, service by service.
What you need Statuswerk for
Six moments when it pays off.
01
Something breaks
You report the incident once. The status page shows it, and everyone who subscribed to the affected service gets the message.
02
Maintenance is coming up
You announce it. Subscribers get the announcement, a reminder and the all-clear without another click from you.
03
A provider of yours has a problem
Your host or payment provider has an outage. You pass it on in a minute, and your customers know what is going on.
04
Not every customer uses everything
You split your services by product or region. From the Pro plan, customers subscribe only to what concerns them.
05
Your own systems are unreachable
Your status page runs apart from your product: not on your servers, not behind your deployment. When your service is down, your customers still reach the news.
06
A large customer asks how you communicate
Security questionnaires ask how you inform customers about incidents. You send a link: 90 days of history, service by service, and a subscription for their team.
What others lack
What comes with Statuswerk as a matter of course.
Subscriptions per component
Whoever uses 3 of your 10 services hears about those 3 only. Your customers read your messages again, because each one concerns them. From the Pro plan.
Groups by product or region
Bring services together in groups: by product, location or customer. Your customers see at once whether their part is affected. From the Basic plan.
Private incidents, shared by link
Something affects one customer only? Open it as a private incident or maintenance and send that customer the link. It stays off your status page, its history and the feeds.
On every plan.
Templates for incidents and maintenance
Frequent messages as templates: filled in within seconds when it matters, without searching for words.
From the Basic plan.
AI assistants via MCP
Claude, Cursor and others read and maintain your status page.
Reading from the Starter plan. Writing from the Basic plan.
Sent through your own mail server
Notifications go out through your own SMTP server, with your sender address.
From the Business plan.
Four-eyes approval
A second person approves before a message goes out. Every change is in the audit log.
From the Business plan.
Why Statuswerk
European here means actually in Europe.
Built for the highest European data protection standards from the start.
An alternative to Atlassian Statuspage, Instatus and Better Stack. Compare with Atlassian Statuspage
- Hosted in Germany
- All providers in the EU
- No transfer to the USA
- Built for the GDPR
- No trackers
What you get with many providers
- Data with a US corporation, even when it says “EU region”
- Your subscribers sit with some third party
- Fonts and trackers loaded from third parties
- Every incident reaches everyone, whoever it affects
- Whoever types, publishes: no second person looks first
What you get with Statuswerk
- Application and data at Hetzner in Germany, every provider in the EU
- Subscribers stay in the EU: email and SMS through EU providers
- No trackers, no third-party requests, no data transfer to the USA
- Subscriptions per component: customers hear only about what they use
- Four-eyes approval before anything goes out (Business)
What you get
Everything a status page needs to do.
Keep people informed
- Email + SMS subscribers
- Subscribers get notified per incident or component. SMS via Seven.io — a GDPR-compliant German provider. Switching? Import your existing list.
- Slack, Microsoft Teams, Discord and Google Chat
- Incidents and maintenance land in your team's chat, and check alerts too.
- Maintenance windows
- Schedule maintenance ahead of time with automatic reminders. Checks of the affected components stay quiet in the meantime.
Keep watch
- Component groups + uptime bars
- Components are the services your customers use: website, API, login. Group them by product or region, with 90-day uptime bars per component and for the whole platform.
- HTTP Monitoring
- Checks from 2 European regions at Hetzner and UpCloud. An outage only counts once a second region confirms it — then we alert you or switch the component.
- System Metrics
- Show your own figures as charts, such as response times or queue lengths, pushed via API.
Connect your tools
- Public API, webhooks + MCP
- Open incidents straight from Grafana, Prometheus, or CI. Every UI action has an API equivalent, and AI assistants like Claude connect via MCP.
- RSS, iCal, badge & widget
- RSS/Atom feeds, iCal subscription for maintenance windows, and a badge or widget for your own site.
- Custom domains + auto-SSL
- Bring your own domain. We verify it via DNS and take care of the Let's Encrypt certificate.
Stay in control
- Four-eyes approval & audit log
- A second person approves before anything goes out, and every change is recorded.
- Private Pages
- Internal status pages behind a password or limited to your networks.
- White label + multi-language
- Your brand only: no Statuswerk logo, your own design — in German or English.
Pricing
Start for free, scale as you grow.
Basic
- 1 status page
- Unlimited Components
- 500 Subscribers
- Custom Domain
Pro
- 3 status pages
- Unlimited Components
- 2,000 Subscribers
- SMS Notifications
- Custom Domain
Business
- 10 status pages
- Unlimited Components
- 5,000 Subscribers
- SMS Notifications
- Custom Domain
Enterprise
- More than 5,000 subscribers
- More than 10 status pages
- Limits agreed with you
Want to try it first? Starter is free: 1 status page, 25 components, 150 subscribers.
Start FreeEvery status page included — no per-page surcharge
Other providers bill each status page as its own subscription, and private pages on a separate price list on top. With us the pages in your plan are covered — including the private ones.
Feature Comparison
| Feature | Starter | Basic | Pro | Business | Enterprise |
|---|---|---|---|---|---|
| Limits | |||||
| Status Pages | 1 | 1 | 3 | 10 | By agreement |
| Components | 25 | Unlimited | Unlimited | Unlimited | By agreement |
| Subscribers | 150 | 500 | 2,000 | 5,000 | By agreement |
| Team Members | 2 | 5 | 10 | Unlimited | By agreement |
| System Metrics | 2 | 5 | 15 | 50 | By agreement |
| HTTP checks from 2 regions | 3 | 10 | 20 | 100 | By agreement |
| Shortest check interval | 3 minutes | 2 minutes | 1 minute | 30 seconds | By agreement |
| Notifications | |||||
| Email Notifications | |||||
| RSS Feed | |||||
| Reply-To address of your choice | |||||
| Webhooks | |||||
| Chat Integrations (Slack, Teams, Discord, Google Chat) | Unlimited | Unlimited | Unlimited | By agreement | |
| SMS Notifications * | 250 / month | 1.000 / month | By agreement | ||
| Component Subscriptions | |||||
| Status page | |||||
| Scheduled Maintenance | |||||
| Uptime History | |||||
| Private incidents & maintenance (link only) | |||||
| Custom Domain | |||||
| Component Groups | |||||
| Search Engine Visibility Control | |||||
| Visitor analytics (Plausible, Umami, Matomo) | |||||
| Custom HTML & CSS | |||||
| White Label (no Statuswerk branding) | |||||
| Integrations & workflow | |||||
| API Access | Read-only | Full Access | Full Access | Full Access | |
| MCP server for AI assistants | Read-only | Full Access | Full Access | Full Access | |
| Incident Templates | |||||
| Control | |||||
| Audit Log | 30 days | ||||
| Four-eyes approval | |||||
| Private Pages (password or IP allowlist) | |||||
| Send from your own mail server | |||||
* SMS per workspace and month, for subscribers, confirmation codes and check alerts together. 160 characters are one SMS (70 with emoji or other special characters outside the SMS character set; umlauts are fine); a longer message counts as several. When the allowance is used up, SMS pause until the next month — email, webhooks and chat carry on. Extra SMS packs can be bought in the dashboard: 250 SMS 29,00 €, 1.000 SMS 99,00 € plus VAT, usable at once, they do not expire.
Who is behind Statuswerk
Built by people who run operations themselves.
„I worked with the big status page services for years. Statuswerk is what I wished for along the way: hosted in Europe, subscribers in the EU, and the features that count when it matters.“
Statuswerk is built and run by Andreas Lehr and the team at We Manage. Andreas has been running online applications for more than 25 years; We Manage looks after SaaS companies, agencies and scale-ups around the clock. We know what you need from a status page at three in the morning.
FAQ
Frequently asked questions.
Statuswerk is a status page service that helps you communicate service disruptions and maintenance to your customers. It is built for the GDPR and hosted exclusively in the European Union.
For your customers: they see at once whether a problem is on their side or yours, and they hear about maintenance before it starts. And for you: one place to point to when a customer asks how you communicate incidents.
Statuswerk is first of all your channel to your customers: incidents, maintenance and notifications. Monitoring comes on top: a check alerts you and can switch a component by itself. You report incidents by hand, via API or MCP, or straight from the monitoring you already have.
A service your customers use: your website, the API, the login, payments. You group components by product or region. Each one shows its own status and uptime, and customers can subscribe to just the ones they use.
Your status page is the channel for the moment your own service is down. On the same servers, the same network or behind the same deployment, it goes down with it. That is why large providers run their status page apart from their own platform. With Statuswerk it runs independently of your product, and you neither maintain nor secure it.
From the status of each component over time. That status comes from Statuswerk's own monitoring, from your own monitoring tools via API, or from incidents you manage by hand, via API or via MCP. Announced maintenance does not count as downtime.
Every status page speaks German or English: the page, its feeds and every notification. You choose per page in its settings, independently of your dashboard language.
Statuswerk is built for the GDPR: all data is stored and processed exclusively in the EU. We do not use any US-based cloud providers, and we offer a Data Processing Agreement (DPA) for all customers.
All our service providers for email delivery, SMS notifications, and infrastructure are European-based companies with EU data processing guarantees.
Yes, you can use your own domain (e.g., status.yourcompany.com) for your status page. You add two DNS records: a TXT record that proves the domain is yours, and a CNAME that points it to us. We take care of the certificate.
A domain of its own such as yourcompany-status.com works too. It keeps your status page reachable even when your main domain has trouble. Your statuswerk.eu address stays reachable alongside it, as a fallback.
Subscribers can receive notifications by email, SMS, webhook or RSS feed, and your team in Slack, Microsoft Teams, Discord or Google Chat. Subscribers can also choose only the components they care about.
Yes, Statuswerk provides a full REST API that allows you to create incidents, update component status, and manage your status page programmatically. This is perfect for integrating with your CI/CD pipeline or monitoring tools. And with our MCP server, AI assistants such as Claude or Cursor can run your status page too.
Yes, we offer a free tier that includes basic features. You can upgrade to a paid plan anytime to unlock more features like custom domains, more team members, and priority support.
Ready when the next incident comes.
Start communicating service status professionally. Set up your status page in minutes.