What we're building,
when, and why.

The unglamorous work: data model, auth, billing, and enough monitoring to dogfood internally.

• Multi-tenant auth + org + project model
• Uptime monitor core (HTTP, TLS, heartbeat)
• Postgres schema with nested workspaces on day 1
• Stripe billing + usage metering
• Internal dogfooding: Brily running on Brily

Invite-only with 30–50 design partners. We iterate weekly on the feedback we collect in-product.

• Status pages v1 with custom domains + auto-SSL
• NPS widget + release-event API
• Slack alerting with per-channel severity routing
• Cohort before/after report for NPS
• One-click promote: alert → public incident
• Design-partner onboarding (30+ teams)

Open signup. Pricing live. Paid plans bill normally, but Free and Pro users know we are still in beta. The SLA line comes with GA.

• Self-serve signup + onboarding flow
• Public API v1 (stable)
• Published OpenAPI spec + generated SDKs (TS, Python, Go)
• Webhooks: generic + PagerDuty / Opsgenie presets
• Monitors-as-code CLI (declarative YAML/JSON)
• Partial white-label on Team

The v1 contract: 99.9% SLA on paid plans, stable API, and the Agency tier unlocked. After this, pricing and API stability are committed.

• 99.9% SLA with service credits on all paid plans
• Agency tier: nested client workspaces, full white-label
• Consolidated billing + reseller agreement
• SOC 2 Type I complete; Type II in progress
• Self-serve DPA + signed SCCs

What comes after GA: platform primitives that turn Brily into a platform, not just a product.

• API monitoring (schema validation, OpenAPI diff)
• Synthetic user-journey checks (scripted flows)
• In-app incident widget (for your app)
• Public data export via S3-compatible bucket
• Self-hosted probe regions for enterprise