> ## Documentation Index
> Fetch the complete documentation index at: https://repost.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Track Webhook Event Usage, Quota, and Overage in Repost

> Track your workspace event consumption, quota limits, per-bucket traffic breakdown, and billing period overage from the Repost dashboard usage page.

The Usage page shows how much of your workspace plan is consumed in the current billing period. You can see your total event count against your quota, any overage if you are on a paid plan, and a per-bucket breakdown that shows which buckets are driving the most traffic. Use this page to make informed decisions about upgrading, archiving inactive buckets, or tuning forwarder behavior.

## Billing period

Usage is calculated inside the workspace billing period, not by calendar month — unless your billing anchor happens to land on the first day of the month.

<CardGroup cols={3}>
  <Card title="Period start" icon="calendar">
    The first day included in the current usage period, derived from your workspace billing anchor.
  </Card>

  <Card title="Period end" icon="calendar-check">
    The first day after the current period. Events on that day belong to the next billing period.
  </Card>

  <Card title="Days remaining" icon="clock">
    The number of days left before the current period closes and usage resets.
  </Card>
</CardGroup>

<Note>
  The billing anchor is the subscription day, capped at day 28 for month-to-month consistency. If your workspace was created or billed on day 29, 30, or 31, Repost uses day 28 as the anchor.
</Note>

## Event quota

The event meter is the most important usage signal on this page. What happens when you reach the quota depends on your plan.

<Tabs>
  <Tab title="Free plan">
    The Free plan includes **50,000 events per month** with a hard cap. Once you reach 50,000 events in the billing period, Repost stops recording new events until the period resets. No overage is charged — new traffic is simply not accepted.

    <Warning>
      If you are on the Free plan and approaching the event cap during a critical period, upgrade before you hit the limit. Events dropped at the cap cannot be recovered retroactively.
    </Warning>
  </Tab>

  <Tab title="Starter plan">
    Starter includes **200,000 events per month**. After your included volume is exhausted, Repost continues to accept and record events. The extra events are counted as overage and billed at the end of the billing period at the per-1,000-event rate.
  </Tab>

  <Tab title="Pro plan">
    Pro includes **2,000,000 events per month** with a lower overage rate than Starter. Like Starter, Pro does not stop recording after the included quota is used — overage is billed at the end of the period.
  </Tab>

  <Tab title="Enterprise">
    Enterprise workspaces have a custom event volume negotiated by agreement. The Usage page may show **Unlimited** for event limits on Enterprise plans.
  </Tab>
</Tabs>

## Per-bucket usage breakdown

The Usage page includes a breakdown that shows event consumption per bucket for the current period. Use this breakdown to identify which buckets are driving the most traffic and which are idle.

<AccordionGroup>
  <Accordion title="High-volume buckets" icon="trending-up">
    Buckets with unexpectedly high event counts can indicate a misconfigured sender, a retry loop, or a forwarder that is reprocessing events. Investigate the bucket's event history if you see volume you did not expect.
  </Accordion>

  <Accordion title="Inactive buckets" icon="archive">
    Buckets with zero or very low event counts over multiple periods are good candidates for archiving. Archiving an inactive bucket removes it from the active bucket count without permanently deleting the bucket or its history.
  </Accordion>

  <Accordion title="Bucket limits" icon="folder-plus">
    Bucket limits are enforced at creation time. If your workspace is at the plan's bucket limit, delete or archive an unused bucket before creating a new one, or upgrade your plan for a higher allowance.
  </Accordion>
</AccordionGroup>

## How to reduce usage

If you are consistently approaching or exceeding your event quota, there are several ways to bring consumption down before upgrading your plan.

<Steps>
  <Step title="Archive inactive buckets">
    Buckets you are no longer actively using may still be receiving traffic from old integrations. Archive them to stop accepting new events and free up your bucket count.
  </Step>

  <Step title="Tune forwarder rate limits">
    If a forwarder is retrying aggressively, each retry attempt counts as an event. Review your forwarder retry configuration and reduce the retry limit or backoff window for lower-priority destinations.
  </Step>

  <Step title="Remove unused forwarders">
    Forwarders that are no longer connected to a live destination generate failed delivery events that still count toward your quota. Remove or disable forwarders that are no longer in use.
  </Step>

  <Step title="Upgrade if the pattern persists">
    If you consistently exceed your included quota across multiple billing periods, upgrading to the next plan tier will give you more headroom, a lower overage rate, and longer event retention.
  </Step>
</Steps>

<Tip>
  Check the per-bucket breakdown at the midpoint of each billing period rather than waiting until the end. Early visibility gives you time to act before hitting a hard cap or accumulating unexpected overage.
</Tip>

## Understand the bucket meter

In addition to events, the Usage page shows your current bucket count against your plan's bucket allowance.

| Plan       | Included events             | Bucket limit |
| ---------- | --------------------------- | ------------ |
| Free       | 50,000 / month (hard cap)   | 3 buckets    |
| Starter    | 200,000 / month + overage   | 25 buckets   |
| Pro        | 2,000,000 / month + overage | 100 buckets  |
| Enterprise | Custom                      | Unlimited    |

<Note>
  Payload size (bytes) is not a quota meter. Repost meters event volume and bucket count only. You will not be charged or throttled based on the size of individual webhook payloads.
</Note>

## Related pages

<CardGroup cols={2}>
  <Card title="Plans & Billing" icon="credit-card" href="/docs/workspace/billing">
    Compare plan limits, upgrade your subscription, and manage billing details from the Plans page.
  </Card>

  <Card title="Team" icon="users" href="/docs/workspace/team">
    Manage seat licenses and understand how seat counts interact with plan changes.
  </Card>
</CardGroup>