Plan your GitLab seats and Duo credits before renewal
Enter your subscription details, or drop in exports from GitLab, to see seat true-up exposure, a renewal projection, and a credits burn-down — all worked out in this browser tab.
FileReader inside this browser tab and never leaves your machine — there is no
server behind this page, no analytics call, and no network request this page is allowed to make
(see the strict Content-Security-Policy in the page source: connect-src 'none').
1. Subscription basics
2. License data (optional — self-managed / Dedicated)
Paste or drop the JSON from GET /api/v4/license (GitLab Self-Managed and Dedicated only;
needs administrator access — GitLab.com has no License API). Fills seat counts and term dates automatically.
license.json here, click to browse, or paste below.
3. Billable users (optional)
Drop the JSON array from GET /api/v4/users?using_license_seat=true. Counts stay
aggregated by default — names are never shown unless you opt in below, and that view stays local.
billable-users.json here or click to browse.
4. Credits usage (optional)
A billing account manager can export credit usage from the Customers Portal (GitLab Credits dashboard → Export usage data): a ZIP holding a daily-summary CSV and a per-event CSV, up to 31 days per export. Use the per-event file — it carries the user ID and credits used for each billable event, which lets included credits be applied per user. GitLab does not publish that file's column headers, so map the columns yourself after upload (docs.gitlab.com/subscriptions/gitlab_credits_dashboard, checked 2026-09-26). If you skip this, use "estimate from activity" in the settings below instead.
.csv here or click to browse.
5. Credit settings checked against GitLab's published docs 2026-09-26
Draw-down order: each user's included credits → Monthly Commitment Pool → on-demand. Included credits belong to each user individually — they are not pooled or shared between users — reset on the first of each month and do not roll over. Service accounts and bots receive no included credits. This prototype does not model a Monthly Commitment Pool balance: everything above a user's included credits is costed as on-demand. Source: docs.gitlab.com/subscriptions/gitlab_credits, checked 2026-09-26.
Results
Seat true-up exposure
Formula
Formula
Formula
Annual true-up bills the full annual fee for every user added during the year; QSR bills the quarter's maximum seats over subscription, prorated for the quarters remaining in the term (GitLab's own example: a $100/yr seat added in Q1 costs $25 × 3 quarters). QSR applies only to 12-month terms bought by credit card or invoice — reseller, purchase-order, multi-year and public-sector subscriptions are reconciled annually. Source: docs.gitlab.com/subscriptions/quarterly_reconciliation, checked 2026-09-26. Your contract governs — confirm with your account team.
Renewal projection
Formula
Formula
Credits burn
Formula
Formula
Formula
Formula
Formula
Reclaim opportunity
Formula
Reclaiming a seat doesn't reduce a bill already paid — it reduces exposure at the next true-up or renewal, or frees a seat for a new hire instead of buying one.
Plain-language summary
Want a second opinion before you sign? ReleaseTEAM helps teams read a GitLab renewal before it's final.
Talk to ReleaseTEAM about your GitLab renewal