piapia123
en

GitHub Copilot Credit Estimator

Web

Everything runs locally in your browser — nothing is uploaded

Output

Pick a plan and enter this month’s premium requests and your seat count; the tool works out the included allowance, what is left, the overage and an estimated overage cost, then projects usage at the current pace (used ÷ days elapsed × days in month) to show whether this month is heading over the limit. ⚠️ Every number is an estimate: prices and included allowances change often, and these use the public rates as of 2026-10. The unit is premium requests (some docs call them credits; this tool treats 1 credit as about 1 premium request). Treat it as a rough guide, not an invoice.

Features

  • Five plans: Free, Pro, Pro+, Business and Enterprise
  • Allowance scales with seats for teams
  • Remaining allowance and overage at a glance
  • Overage cost estimated and written as “about”
  • Linear projection of whether the month ends over the limit
  • Billing period choice; yearly counts about 12 months
  • States the unit clearly: premium requests / credits
  • ⚠️ Includes a note that every figure is an estimate

How to use

  1. Choose a plan and set the number of seats
  2. Enter the premium requests used this month
  3. Tick “show the overage cost estimate” if you want it
  4. Read the projection: is this pace heading over the limit

FAQ

Why do these numbers not match my bill?
Because they are estimates. Prices and included allowances change constantly, and contracts differ between teams. The tool uses the public rates as of 2026-10 and rounds values to “about”. Use the official invoice for the truth and this for a rough guide.
Is the unit credits or premium requests?
GitHub has used both names at different times: premium requests earlier, credits more recently. This tool treats 1 credit as about 1 premium request and says which word it used in the result, so it lines up with the column on your bill.
How accurate is the projection?
It assumes usage is evenly spread across the month: used ÷ days elapsed × days in month. A burst early on, then idle, or the reverse, will throw it off. So it is a hint at the current pace, not a forecast — good enough to spot a month heading over the limit.

Related tools