service level agreement
the uptime briven commits to per tier, how monthly credits are calculated when we miss it, and what counts as "downtime" for purposes of this agreement. effective date 2026-05-21 (Phase 4 public-beta launch). free-tier projects are best-effort with no contractual commitment.
commitments
| tier | monthly uptime target | credit if missed |
|---|---|---|
| free | best-effort | none |
| pro | 99.5% | see schedule below |
| team | 99.9% | see schedule below |
what counts as the platform being up
three signals, measured externally from outside the briven infrastructure:
api.briven.tech/readyreturns HTTP 200 within 5 seconds. probes every 60s.realtime.briven.tech/readyreturns HTTP 200 within 5 seconds. probes every 60s.- a function invocation to a healthy deployment in your project returns within 10 seconds for at least one randomly selected hosted project per region. probes every 5 minutes.
a probe failure counts as downtime when at least three consecutive probes fail (so a single packet drop doesn't trigger the SLA). downtime accumulates per calendar month UTC. the monthly uptime % is calculated as 1 - (downtime_minutes / total_minutes_in_month).
credit schedule
if your tier's monthly uptime falls below the commitment, your next monthly invoice is credited per the table below. credits are automatic — you don't need to file a ticket unless we miss applying the credit, but you can confirm via briven doctor --month or the dashboard billing page.
| measured uptime | pro credit | team credit |
|---|---|---|
| target met | — | — |
| < tier target but ≥ 99.0% | 10% of the month's subscription | 10% of the month's subscription |
| < 99.0% but ≥ 95.0% | 25% | 25% |
| < 95.0% | 50% | 50% |
credit applies to the affected month's subscription fee. overage and metered usage aren't credited. credits never roll over into cash refunds; they offset future invoices.
what's excluded
downtime caused by any of the following does not count against the SLA:
- scheduled maintenance announced ≥ 48h in advance on the status page
- incidents caused by the customer's own code (e.g. a function that 500s under load) or by the customer's own configuration changes
- incidents caused by upstream provider failures (Hostinger, Cloudflare, Polar, Mittera) where briven's mitigation is to wait for the upstream
- force majeure: natural disasters, war, government action, internet-scale BGP events
- any period during which the customer is in breach of the Terms of Service or has overdue invoices
- downtime affecting only free-tier projects — they're best-effort by design
how downtime is measured
briven publishes its own external probes at docs.briven.tech/status and briven.tech/status. additionally, a third-party probe (Uptime Kuma on a separate provider) records minute- level availability for each public surface. monthly uptime is calculated from the third-party probe data — never from internal logs alone.
on disagreement, the third-party probe's record is authoritative for the calculation; customers may inspect the same data at the public status page's history view.
filing a claim
credits are automatic and applied to the next invoice. if you believe a credit was missed, email billing@flndrn.com within 30 days of the affected month with your project id and the time window in question. claims older than 30 days are ineligible.
changes to this SLA
briven may update the SLA with 30 days' notice posted to the public changelog. the version of this page in effect on the first day of your billing month governs that month's credits.
flndrn Limited, Limassol, Cyprus · this document is the SLA referenced in the briven Terms of Service.