What it doesCoverageIntegrationsChangelogSecurityPricing
Sign inCheck my app
Terms/The agreement

Plain terms,
honest scope.

These are the rules of the road for using BeforeRed. They are written for the product as it is today: a solo-built monitoring service in authenticated alpha, with 14 runtime-wired provider connections and 8 bounded live-reconciled provider surfaces. 9 permission-restricted connection paths are offered to users. Where the product or the law changes, we update this page and bump the date below.

Service
Permission-restricted monitoring
Provider status
9 connectable · 14 runtime
Scheduled sync
Hourly
Last updated
2026-08-12
Summary

Read this
in two minutes

If you only have time for one screen, read this section. Everything below is a longer version of the same ideas, written for builders who want the full picture before they connect a provider.

Summary

What BeforeRed does

Reads usage and limit data from providers you connect, then shows you risk states and estimates. We do not write to your infrastructure.

Summary

What BeforeRed does not guarantee

Detection, freshness, forecasts, and confidence levels are best effort. Provider APIs can be delayed, changed, or unavailable. You stay responsible for your own systems.

Summary

Your data and credentials

Tokens are encrypted at rest. We never see your source, your database rows, or your end users. You can disconnect and delete at any time.

Summary

Acceptable use

Use BeforeRed only on accounts and projects you own or are authorized to monitor.

Summary

Pricing

Free for your first app. Pro pricing is published on the Pricing page. Billing is not yet live as of the last updated date.

Summary

Alpha service level

The service is provided as is during alpha. Targets are goals, not contractual SLAs.

Service

What BeforeRed
is, in plain terms

BeforeRed is a usage and limit monitor for the infrastructure behind your app. You connect a provider, we read the public documented APIs that provider already publishes, and we surface what is safe, what is approaching a limit, and what is already over.

What the service does

  • Reads usage, quota, and limit data through the official APIs a provider already publishes.
  • Stores short-lived snapshots of those readings so it can compute risk states and trend lines.
  • Generates estimates, forecasts, and plain-English warnings, each with an explicit confidence level.
  • Can send optional email warnings when the warning channel is separately configured.

What the service does not do

  • Does not write to your infrastructure, your databases, your DNS, or your provider settings.
  • Does not read your application source code, your logs, your environment, or your user records.
  • Does not reverse engineer provider dashboards or undocumented endpoints.
  • Does not combine unrelated quotas into a single universal app-health percentage.
Accuracy

Estimates, not
guarantees

BeforeRed provides estimates and early warnings. It does not promise to detect every limit event, and it does not promise that its forecasts will always be right. This section is the most important one on this page.

Forecasts are ranges with confidence

When the product forecasts runway, it shows a range and a confidence level, not a single number. The range comes from a model that depends on history length, variance, and reset behavior. A forecast can be wrong. If your business depends on hitting a deadline, do not rely on it.

Unknown is a real state

If a metric cannot be read, has not been read recently enough, or lacks the source data needed for a forecast, the product will say so. It will not pretend the answer is safe. A green badge only ever means a recent successful read on a metric whose source is current.

Provider APIs are not under our control

BeforeRed depends on third-party APIs. Those APIs can be delayed, rate-limited, paginated differently, deprecated, or temporarily unavailable. When that happens, readings can be stale. The product will tell you when data is stale rather than fake a green status.

You stay responsible for your infrastructure

BeforeRed is an aid, not a control plane. You are responsible for your own provider plans, your own spend, your own backups, your own incident response, and your own customer communications. Use BeforeRed as a signal, not as a substitute for operating your stack.

Scope

We never
change your infrastructure

BeforeRed only reads. It does not call provider write endpoints on your behalf, and it does not assume the right to make changes of any kind to your projects, accounts, or data.

Restricted access by design

New connections are offered only where the provider supports a credential restricted against infrastructure changes. We identify the required provider scope and ask you to confirm it before connecting. BeforeRed cannot independently prove the scope of every opaque token, so you must not paste a broader personal, admin, deploy, or account-wide credential.

No billing changes

We never initiate upgrades, downgrades, or any change to your provider plan. We never enter payment information on your behalf. If a provider is about to bill you for overage, we tell you. We do not act on your behalf to prevent it.

No configuration changes

We never toggle features, rotate provider-managed keys, change DNS, alter rate limits, or modify any setting inside your provider account. Suggestions that look like recommendations are just suggestions, written in plain text and clearly labeled as such.

No data writes back to you

We do not push data into your databases or your queues. The product writes its own connection, snapshot, and alert history, scoped to your account. Self-serve export and deletion controls are not shipped in the current alpha.

Acceptable use

Use it on what
you are allowed to monitor

BeforeRed is a monitoring tool. It is meant for people who own or are explicitly authorized to operate the infrastructure they connect. It is not a tool for collecting data on services you do not control.

You may use BeforeRed to

  • Monitor your own provider accounts, projects, and resources.
  • Monitor accounts and projects you administer with the owner's knowledge and consent.
  • Monitor a client account only when you have a written or contractual right to do so.
  • Use the service only for accounts and projects you are authorized to monitor.

You may not use BeforeRed to

  • Monitor accounts you do not own or are not authorized to operate.
  • Probe, fingerprint, or test third-party infrastructure without permission.
  • Attempt to reverse engineer our rate limits, our auth flow, or our credential storage.
  • Resell BeforeRed or repackage its data as a competing monitoring service.
  • Use BeforeRed to send notifications that are misleading, harassing, or unlawful.
Account

Eligibility,
security, ending

A BeforeRed account is one email address, one set of workspaces, and one set of connected providers. We try to keep the rules small and the path to leaving short.

Eligibility

You can use BeforeRed if you are at least 18 and able to enter a contract in your jurisdiction. If you are using BeforeRed on behalf of a company, you confirm that you have authority to bind that company to these terms.

Account security

You are responsible for the email address, the password, the OAuth sessions, and the provider tokens associated with your account. Use a unique password. Do not share credentials. We will never ask for your password in email, chat, or social media.

Termination

Self-serve account termination is not shipped in the current alpha. We can suspend or terminate access if you violate these terms, abuse the service, or create risk for other users. Where possible, we will warn you first and explain the reason.

Billing

Plans, prices,
and where billing stands

The free plan is live today. The Pro plan is published for transparency but the checkout flow is not yet active. The Pricing page is the source of truth for current numbers.

Free plan

One monitored app with nine permission-restricted provider connection paths, 14 adapters maintained in the runtime, hourly scheduled syncs, the closest-limit view, eligible forecasts, and risk-state events. No card is required. The Pricing page is the current source of truth.

Paid depth, when billing opens

A future paid plan may add more apps, longer history, portfolio views, summaries, notification channels, and support. Scope and price are still being tested. There is no active paid offer today.

Cancel any time

When Pro billing opens, you will be able to cancel from your account settings. Cancellation stops the next charge. We do not pro-rate refunds for partial periods beyond what the payment processor and applicable law require.

Plain note

As of the last updated date above, the Pro checkout flow is not live. We will not charge any card until the Pricing page lists an an active checkout with clear terms and a real purchase action.

The authenticated alpha is the only current plan. Future paid packaging will be announced on the Pricing page before billing opens.

Alpha status

Provided as is,
with honest targets

BeforeRed is in authenticated alpha. We are still building it. Some things will be rough, and a small number of things will break in ways that matter. This section sets expectations honestly.

Availability targets, not SLAs

BeforeRed does not offer a contractual availability or alert-delivery SLA in alpha. Scheduled sync has an hourly boundary, but provider APIs, credentials, rate limits, and incidents can delay or prevent a reading.

Changes, removals, and rough edges

During alpha we may add, change, or remove features with little notice. We try to announce breaking changes in the Changelog before they ship. Some provider integrations may temporarily fall back to an unknown state when an upstream API changes; the product will tell you when this happens.

As-is, where permitted

To the maximum extent permitted by applicable law, the service is provided as is and as available. We disclaim warranties of merchantability, fitness for a particular purpose, and non-infringement to that same extent. Where the law in your jurisdiction does not allow such a disclaimer, this section applies only to the extent permitted.

Liability

What we cover,
and what we do not

We want the rules of liability to match the reality of what we ship: an alpha monitor with permission-restricted connection paths that helps you see limits before they bite. This section is written in plain English so it is not hidden behind legal jargon.

What you can recover from us

If we charge you for a Pro plan we have not yet delivered, we refund that charge. If we fail to delete your account data within the window stated in the Privacy policy, you can ask us to confirm deletion in writing. Those are the practical remedies we commit to today.

What we do not cover

We are not liable for indirect damages, lost profits, lost business, lost data, or any other consequential or incidental loss, to the maximum extent permitted by applicable law. Our total liability for any claim related to the service is capped at the amount you have paid us for the service in the twelve months before the claim, or one hundred US dollars if you have paid us nothing.

Indemnification, kept small

You agree to indemnify us against claims arising from your misuse of the service, your violation of these terms, or your violation of any law or third-party right. The indemnity does not extend to claims caused by our own negligence or willful misconduct.

Force majeure

Neither of us is liable for delays or failures caused by events outside reasonable control, including provider outages, network failures, denial-of-service attacks, or changes in law. We will tell you when a force majeure event is affecting the service.

Changes

How we update
these terms

When the product, the law, or the provider landscape changes, these terms change with it. We keep the history short and the date visible.

What we will do

  • Bump the last updated date at the top of the Terms page.
  • Post a short note in the public Changelog for material changes.
  • Email active users for changes that affect billing, data handling, or your obligations.
  • Keep older versions reachable from the Changelog so you can compare.

What you can do

  • Stop using the alpha before a change takes effect.
  • Review the public Changelog for material product and policy changes.
  • Avoid connecting production credentials while self-serve export and deletion remain unavailable.
  • Tell us where the wording is unclear. We will rewrite it.

Governing law, in plain terms

BeforeRed does not publish a governing-law jurisdiction or registered operator identity yet. This is an alpha limitation, not a completed legal term. Do not treat the alpha as a substitute for a production vendor agreement.

Contact

A verified public legal-support mailbox is not published yet. Material terms changes are recorded in the public Changelog until a formal operator and contact route are established.