Fair use

Every plan includes the AI-powered analysis DevUpdate.io performs for you: release summaries, diff analysis, digests, and the one-time extraction when you're the first to track an AI-parsed source. There is no per-use metering, no credit balance, and no usage-based billing. The only limit is fair use.

How it works #

Each tier carries an internal fair-use allowance sized generously above typical usage, so most accounts will never notice it exists. Shared work (a release summary computed once and reused by everyone watching that source) doesn't count against anyone. What does count is work done specifically for you: digests, and the first-sync extraction of AI-parsed sources nobody else tracks.

What happens at the limit #

If an account exceeds its allowance within a billing period, further discretionary AI processing is deferred, never billed:

• Onboarding additional AI-parsed sources queues until the next period (the UI tells you in place, before anything is charged, because nothing is ever charged).
• Release tracking, existing summaries, available upgrades, security issues, and the MCP server keep working throughout: they read computed data and cost nothing.

The account ceiling on tracked sources #

Separately from your plan's source cap (none on Professional and Team), every account on every plan has an anti-abuse ceiling on how many sources it can actively track at once. It sits far above what a real portfolio needs; it exists so a compromised account or a runaway script can't fan out across an unbounded number of repositories. It applies the same way wherever a source is added: by hand, from a lockfile (including the dependencies a sync tracks automatically), or from your GitHub stars. If you reach it, the message says it is the account limit rather than suggesting an upgrade, because no plan raises it; email us and we'll raise it after a quick look.

Both limits count active sources only. Pausing a source frees its slot straight away, and resuming one needs a free slot, the same as adding a new one. Unchecking packages or swapping one for another is always allowed, even over a limit, so an account that ends up past it (say, after a team plan lapses) can always get back under. When a plan ends, sources past the Hobbyist cap are paused, not deleted.

Sustained high volume #

If you keep hitting the gate with a legitimate use case (large org, many custom sources), email info@devupdate.io. That's a conversation about the right plan shape, not a meter.