Limits & plan tiers

trackagoat enforces per-organization limits based on your plan tier. This page explains what each limit does, how they're enforced, and what happens when you hit one.

Plan tiers

Limit keys

How limits are enforced

Count limits (creators, projects, members, etc.) are enforced atomically — two concurrent requests cannot both succeed past the cap. You'll see a modal in the UI explaining which limit was hit.

Daily limits (API requests, manual scrapes) reset at UTC midnight. If you hit your daily API limit, requests return HTTP 429.

Scrape frequency floors (min_*_hours) set a minimum interval between scheduled scrapes — your configured frequency is clamped to no lower than the tier minimum. These floors do not apply to manual "Scrape Now" triggers, which are governed instead by max_manual_scrape_triggers_per_day. See How scraping works for a full breakdown of manual vs. automatic scraping.

Stats retention — a daily background job prunes history older than your retention window. Ultra tier has unlimited retention.

When you hit a limit

In the dashboard: A modal appears with the limit key, your current count, and the cap. If your org is retroactively over a limit (e.g., after a tier downgrade), a banner appears at the top of every page until the org is back within limits.

In the API: Count limits return HTTP 402:

{
  "data": null,
  "error": "Limit reached: max_creators_per_org",
  "meta": {
    "code": "limit_reached",
    "limitKey": "max_creators_per_org",
    "current": 5,
    "max": 5
  }
}

Daily rate limits return HTTP 429:

{
  "data": null,
  "error": "Rate limit exceeded",
  "meta": {
    "code": "rate_limit_exceeded",
    "retryAfter": 3421
  }
}

retryAfter is seconds until UTC midnight when the counter resets.

Per-user limits

One limit applies per user rather than per org:

The default is 6. If you need to belong to more orgs, contact support.

Requesting a raise

Limits are adjusted by the trackagoat team. There is no self-serve upgrade path yet.

To request a raise: