99.9% monthly uptime on paid plans.

The commitment

For workspaces on the Starter, Pro, Team and Enterprise plans, Buildfyio commits to a Monthly Uptime Percentage of at least 99.9% for each of the covered services, measured per calendar month:

• Platform API — api.buildfyio.com, the surface the dashboard, CLI, Git integrations and your own automation call.
• Dashboard — buildfyio.com and everything under /dashboard.
• Edge delivery of production deployments — HTTPS serving of your production deployment on its platform domain and on verified custom domains, including TLS.

Builds, preview deployments, add-on databases and the Hobby plan are provided on a best-effort basis and are not covered by credits; their health is published on the status page all the same.

How uptime is measured

We measure from outside the production host: a separate machine in another Hetzner location probes each covered service once a minute through public DNS and TLS, exactly as a visitor would. A probe succeeds when it receives an HTTP 2xx or 3xx within 10 seconds; a failed probe is retried once after 5 seconds before it counts.

• A minute counts as downtime when it is part of a run of at least three consecutive failed probes for a covered service. Shorter blips count as uptime.
• Monthly Uptime Percentage = 100% − (downtime minutes ÷ minutes in the month), computed per covered service.
• The same probes drive the 30-day figures on the status page below, so what you see there is what the credit is computed from. We keep the per-minute history for 13 months and will share it on request.

Exclusions

Downtime caused by any of the following does not count against the commitment:

• Scheduled maintenance announced on the status page at least 24 hours in advance, limited to 4 hours per calendar month.
• Your application or configuration — crashing or slow code, exhausted plan limits, an unverified or misconfigured custom domain, DNS you control, or a deployment you paused, deleted or rolled back.
• Third parties outside our control — your DNS provider or registrar, a CDN or proxy in front of us, GitHub, payment providers, or an internet-wide routing failure.
• Suspension for non-payment, abuse or a legal order, and force majeure events.

Service credits

If the Monthly Uptime Percentage of a covered service falls below 99.9% in a calendar month, your workspace is entitled to a credit against the next invoice:

• The platform fee is the fixed subscription charge for the month in question; usage charges and add-ons are not credited. Credits are capped at 50% of that fee and are never paid in cash.
• Request the credit within 30 days of the end of the affected month by emailing support@buildfyio.com with the workspace and the month. We confirm against the probe history and apply the credit to the next invoice.
• Credits are the sole and exclusive remedy for a missed uptime commitment. Enterprise agreements may define different targets, remedies and support response times; where they do, the agreement prevails.

Changes

We may update this agreement by publishing a new version on this page with a new effective date. Changes that reduce the commitment take effect 30 days after publication and never apply retroactively.