Everything you need to run Brily.
This is the preview. Stable API and versioned docs ship with our public beta in Q3 2026. What is here reflects the current private-beta build. If a page seems out of date, email docs@brily.app.
Quickstart
Ship your first monitor and status page in under two minutes. Code samples in curl and TypeScript.
API reference
REST API with full endpoint coverage for monitors, incidents, releases, and NPS responses. Auth, rate limits, pagination, error codes.
Slack integration
Route alerts to channels by severity, attach runbooks inline, promote alerts to public incidents with one click.
Telegram integration
Bot-based alerts to private chats, group chats, or channels. On-call friendly, especially where Slack is not the norm.
WhatsApp integration
P1 outage alerts via the WhatsApp Business Cloud API. Pre-approved template messages and opt-in compliance handled for you.
Webhooks
Signed generic webhooks for PagerDuty, Opsgenie, your own services, or custom routing logic.
Monitors-as-code
Keep your monitors in git. Declarative YAML, diff on pull requests, deploy via CLI or CI.
What is covered today
Docs for everything shipped in private beta are live: monitor configuration, status pages, NPS widget, release markers, alert-channel routing, and the monitors-as-code CLI. The API reference is marked v0 preview. Endpoint behaviour is stable, but we reserve the right to rename paths before v1 freeze at public beta.
What is still missing
- Self-hosted probe regions. Planned for H1 2027, Enterprise only.
- Synthetic scripted checks. Planned for H1 2027.
- Generated SDKs. TypeScript, Python, and Go SDKs land with public beta, generated from the OpenAPI spec.
See the full public roadmap for dates and commitment levels.
Need help now?
Email support@brily.app for product questions, or docs@brily.app for corrections and doc gaps. Design partners have a private Slack channel. Details are in your invite email.