PLAN NOTES

One subscription, two projects: when that works

Plans meter requests, not projects, so two codebases can share one key. What sharing actually shares, and when two plans are cleaner.

Two projects, one subscription. A dashboard for one idea and a model for another, both reading the same odds. The question buyers ask is whether that needs two plans. The short answer is no, because plans meter requests, not projects. The longer answer is about where the shared budget stops being comfortable.

One key, one meter

The plan you buy sets a per-second allowance and a transport set, as the plan guide lays out the dimensions, checked 2026-11-04. The API does not see your projects; it sees the requests that arrive under your key. Two codebases polling on the same plan are simply one combined load on one meter, and they fit as long as the sum fits.

That makes one subscription the default answer for two projects, with the same arithmetic as always: add both loops' requests per second at their peaks, and compare against the plan's rate.

What sharing actually shares

The rate budget is the visible shared resource. Two quieter ones matter more in practice. Failure is shared: a bug in one project that starts hammering spends the other's headroom, and a 429 storm lands on both. And accounting is shared: the account panel shows one usage picture, so the question "which project burned the day" has no built-in answer unless you log it yourself.

If either project is a client's rather than yours, sharing also mixes your books with theirs. One key, one bill, and no clean way to split the invoice by project later.

When to split into two plans

Split when the loops have different shapes. A drop-driven bot and a polling model want different transports, and two separate plans let each carry exactly what it needs, as the pricing page lists per-plan inclusions, checked 2026-11-04. Split when one project may die on its own schedule, so its cancellation is a clean event. And split when the two projects have different owners of the bill: separate subscriptions are separate budgets with separate renewal dates.

The combined-load sum is the test either way. If the two peaks together sit comfortably inside one plan, sharing is the cheaper and simpler shape.

If you share, share deliberately

Log per project from day one: a tag on each request's records, so the usage review can split the meter. Give each project its own pacing budget inside the shared allowance, so a burst in one cannot starve the other. And write down which project owns the incident when the 429s come, because shared failure needs an owner, not a shrug.

One subscription is usually right for two projects. It works when you treat the shared meter as a budget you allocate, not a commons you hope for.