Status
There is no live status page yet. We could put a green tick and a number here, but an uptime figure nobody measures is worse than no figure, and this is exactly the page where a made-up number would be noticed.
If something looks wrong
Email [email protected]. Include the request_id from any error you got (every failure carries one) and the Product id. That is enough to find the specific request in our logs, which saves a round trip.
If you are running Helm7 yourself, the same address works. We do not have a separate queue for people who pay us.
What we run today
eu-central
Falkenstein, Germany. The default region.
eu-north
Helsinki, Finland.
Both are in the EU. There is no US region and no Asia-Pacific region. If your users are not in Europe, that is a real cost and we would rather you knew before signing up than after.
What is not built yet
- A public status page with per-component health and a history of incidents. This is the page you are reading, and it is a placeholder for that.
- Published uptime figures. We will publish them once there is enough of an operating record for the number to mean something.
- Incident notifications by email or webhook. For now, an incident means we contact affected customers directly.
Scale-plan customers get direct support, which today means a human rather than a dashboard. See pricing.
Check your own application first
Most problems that look like an outage are a failed deploy or a service that is crashing on start. Three read-only calls answer that in under a minute, from the CLI, the API or an agent over MCP. None of them changes anything.
- deployment_list shows whether the latest deployment succeeded, and when. A failed one means your application is still running the previous version.
- service_logs returns recent stdout and stderr for a service. A crash loop shows up here as the same error repeated at start-up.
- activity_list lists what changed and who or what changed it, which settles the question of whether an agent or a teammate did something recently.
If all three look healthy and the application is still unreachable, email us with the request_id. The full list of operations is in the API reference.
How we will report problems
Until there is a public page, an incident that affects your Products means we contact you directly, by email, with the request_ids we can see on our side.
Backups are a separate thing to check. Builder keeps daily backups for seven days, and the backup and restore guide shows how to prove a backup restores before you need it.