---
description: Understand plans, accepted-event limits, retention, overage, and plan changes.
---

# Limits and billing

WeaveScope applies usage limits while accepting trace data. Plans and billing
belong to the organization, while retention is applied to each project.

## Plans

| Plan | Price | Accepted events | Ingest data | Retention | Users | Projects | Overage |
| --- | ---: | ---: | ---: | ---: | ---: | ---: | --- |
| Free | €0 | 100,000 | 100 MB/hour | 14 days | 2 | 1 | Not available |
| Pro | €29/month or €313.20/year | 1,000,000 | 2.5 GB/hour | 30 days | Unlimited | Unlimited | €10 per 1M |
| Scale | €99/month or €1,069.20/year | 10,000,000 | 5 GB/hour | 90 days | Unlimited | Unlimited | €10 per 1M |
| Enterprise | Custom | 50M+ or custom | Custom | Custom | Custom | Custom | Negotiated |

Annual Pro and Scale prices are 10% lower than twelve monthly payments.

## What the limits measure

WeaveScope applies three separate controls:

| Control | Window | Response | Purpose |
| --- | --- | --- | --- |
| Events per request | One request | `413 Content Too Large` | Keeps each batch within processing bounds. |
| Accepted events | Billing cycle | `402 Payment Required` | Enforces included usage and funded overage. |
| Ingest data | Rolling hour | `429 Too Many Requests` | Protects ingestion from large payload bursts. |

A native, LangSmith-compatible, or OTLP request can contain at most 1,000
events or spans. A larger request is rejected before any usage is counted.

Each accepted observation event counts toward the billing-cycle limit. A trace
can contain several events. Events rejected during validation do not count.

{% hint style="warning" %}
A partially accepted batch counts and queues its accepted events. Review the
itemized response before retrying rejected entries.
{% endhint %}

## Hourly ingest data

The rolling hourly limit counts accepted data in:

- `inputs`
- `outputs`
- `metadata`
- `context_metadata`
- `events`

When the limit is reached, the response includes `hourly_ingest_reset_at`.
Retry after that time or reduce large payload fields.

## Handle a limit response

For `402 Payment Required`:

1. Open **Settings → Billing**.
2. Review accepted-event usage for the current cycle.
3. Change plans or enable and fund balance overage on Pro or Scale.
4. Reduce accidental or excessively noisy instrumentation.

For an hourly-ingest `429 Too Many Requests`:

1. Read `hourly_ingest_reset_at`.
2. Retry after the reset.
3. Reduce large payload fields or store large blobs elsewhere and trace a
   reference instead.

The ingestion edge can also return `429` for excessive request rate or
concurrency. Those responses may have a different body and should be retried
with backoff.

## Overage and balance

Pro and Scale can extend their event limit with a prepaid organization balance.
Additional usage costs:

```text
€10 per 1,000,000 accepted events
```

Enable **Allow overage from the balance** to make funded events available after
the included allowance is exhausted. Accrued overage is settled hourly. When
overage is disabled or the balance can no longer cover more usage, ingestion
stops at the available limit.

Fund the balance with:

- **Manual top-up** — charged immediately through Stripe Checkout, from €5 to
  €10,000.
- **Auto top-up** — charges the saved payment method when the balance falls
  below your configured threshold.

If an automatic charge requires authentication or there is no saved payment
method, auto top-up is disabled until a manual top-up succeeds.

Refunds and disputes can make the balance negative when the returned funds have
already paid for usage. Later top-ups repay that amount first. Funded overage
remains unavailable until the balance becomes positive.

There is no end-of-cycle overage invoice; overage is always prepaid.

## Usage alerts

WeaveScope notifies active owners and admins when accepted-event usage reaches:

- 80%
- 90%
- 100%

## Retention

Each project keeps trace data for the retention period of the active plan.
Changing plans updates the organization's projects to the new retention period
when the plan becomes effective.

Scheduled cleanup permanently removes expired observations and their payloads.
Deleting a project permanently removes that project's trace data immediately.

## Plan changes

An effective plan change starts a new usage cycle under the new plan. Usage
from the previous plan does not carry into the new limits.

**Upgrades apply immediately after payment succeeds.** WeaveScope then resets
usage to zero and applies the upgraded plan's limits and retention.

**Downgrades are scheduled for the end of the current billing period.** Until
then, the active plan, limits, retention, and usage cycle stay unchanged. When
the downgrade takes effect, usage resets to zero and the lower plan becomes
active.

Scheduling, canceling, or resuming a pending change does not reset usage.
Subscription renewals and repeated synchronization of the same active plan also
preserve the current usage cycle.

An immediate change is blocked when current project or user counts exceed the
target plan's limits. A scheduled downgrade can still take effect with excess
projects or members: existing resources remain accessible, but new projects or
member activations are blocked until the organization is within the active
limits. Plan changes never delete projects or disable members.

Cancellation takes effect at the end of the billing period and moves the
organization to Free. You can resume before the cancellation applies.

Use the Stripe billing portal to manage payment methods and invoices. The
WeaveScope Billing page shows plan status, usage, invoices, balance, and balance
transactions.