Team overage explained: If your combined codebase grows beyond 80K LOC, you don't need to call sales. Overage charges $2 per every 1,000 lines over the limit — measured generously (see below). A natural upgrade to Enterprise becomes the better deal at around 150K LOC.
Measurement
How we count lines of code
We use cloc — the open-source industry standard. It counts only meaningful source lines, excluding comments, blank lines, and generated files. You can run it yourself and get the exact same number.
LOC is the total across all connected repos. If you connect three repos at 15K, 22K, and 10K LOC, your total is 47K — comfortably within the Builder plan's 30K limit... wait, that's 47K. You'd be on Team. See how transparent this is?
The total is measured once at the start of each billing period — not on every commit, not on every sync. We don't watch your repo moment-to-moment.
If you deprecate a large feature and your LOC drops significantly, you can trigger a manual re-measurement from your billing page. If it drops your tier, the lower rate applies to the current period.
LOC is shown with a ~ prefix throughout our UI because it's a thoughtful approximation, not an invoice-line forensic count.
cloc ./my-repo --exclude-dir=node_modules,dist
───────────────────────────────────
LanguageFilesBlankCommentCode
───────────────────────────────────
TypeScript 142 1,842 43028,491
YAML 34 210 88 1,922
SQL 18 145 61 1,408
Markdown 22 280 0 1,047
───────────────────────────────────
SUM 216 2,477 57932,868
# Git2Docs uses the CODE column only
# Comments and blanks don't count
✓ Measured LOC: ~32,868
✓ Billed as: 30K(bucket)
✓ Plan tier: Builder
The bucket system — we always round down
Your billing is based on 10,000-line buckets, always rounded down to the nearest bucket. A codebase of 79,999 lines is billed as 70K — the same as a 70,001 line codebase. We never round up.
Actual LOC measured
Billed as (bucket)
Plan tier
Monthly charge
8,400
~8K
Builder
$69
29,999
~20K
Builder
$69
30,001
~30K
Builder
$69 at limit
65,000
~60K
Team
$99
82,000
~80K
Team
$99
88,500
~80K
Team
$99 grace buffer applies
97,200
~90K
Team + Overage
$99 + $20 overage
154,000
~150K
Enterprise
Custom
Our promise
Billing that leans your way
LOC changes dynamically. Features get deprecated. We designed the billing system with that reality in mind. Our goal is to sell you documentation quality, not count lines.
↓
Always rounds down
Buckets snap to the nearest 10K below your actual count. A codebase of 89,999 lines is billed as 80K — never 90K.
📅
Measured once per period
We snapshot your LOC at the start of each billing period. We don't watch your commits or re-measure on every sync.
↘
Drops count too
If you deprecate a large feature and your LOC falls, trigger a manual re-measure. If it changes your tier, you benefit immediately — no waiting for the next period.
🛡️
10% grace buffer
Before any overage charge kicks in, we silently absorb a 10% buffer above your plan limit. We don't advertise it, we just apply it.
🔍
Fully auditable
Your billing page shows every measurement event with timestamps. You can run cloc yourself and get the same number.
🚫
No high-water billing
We never bill on the peak LOC you hit during a period. If your LOC drops after a refactor, the lower count is what matters.
Real example
What a Team plan bill actually looks like
Here's a real billing snapshot from an engineering team with four repos in April 2026. Walk through the math exactly as our system does.
April 2026 · Team Plan
Billing period: April 1 – April 30, 2026 · Measured: April 1, 2026
Connected repos (4 of 10)
api-gateway
~28,400 actual20K bucketrounds down
frontend-app
~19,100 actual10K bucketrounds down
data-pipeline
~24,300 actual20K bucketrounds down
infra-config
~10,200 actual10K bucketrounds down
Billing summary
Actual total LOC~82,000
Billed as (bucket)80K
Plan limit80K (Team)
Overage LOCnone
Base plan$99.00
Overage charge$0.00
Total this period$99.00
Status✓ Within plan
How we arrived at $99.00
1Measured repos with cloc: 28,400 + 19,100 + 24,300 + 10,200 = 82,000 actual LOC
2Apply bucket: floor(82,000 ÷ 10,000) × 10,000 = 80K — we rounded down
3Compare to Team plan limit: 80K bucketed ≤ 80K limit → no overage
4Charge: $99 base + $0 overage = $99.00
What if things changed?
Team removes deprecated module → LOC drops to 71,000
Bucket: 70K Overage: none Charge: $99.00 (still within plan)
Git2Docs is the only documentation platform that prices on what it actually costs to generate your docs — not on how many people sit in your company.
Product
Pricing model
What you're paying for
Entry price
Mid tier
Git2Docs ✦
Repos + LOC
Codebase size (what it costs us)
$69/mo
$99/mo
GitBook
Sites + editors (seats)
Number of people with edit access
Free (1 site)
$249/mo+
ReadMe
Projects + seats
API reference projects
$99/mo
$399/mo
Document360
Seats + projects
Number of editors
$149/mo
$299/mo
Archbee
Seats
Number of editors
$50/mo
$200/mo
Mintlify
Editors (seats)
Number of people writing docs
Free (1 editor)
$150/mo
Docusaurus
Open source / self-hosted
Your own engineering time
Free
Free
✦ Git2Docs is the only AI-native doc platform in this list. Competitors require humans to write and maintain all documentation content. Our AI generates a high-quality first pass; your team refines and owns it.
FAQ
Common questions
How do I know my LOC before I connect a repo?▸
When you select a repo during onboarding, we use GitHub's language statistics API to give you an estimated LOC figure before you commit. It's labeled as an estimate and shown alongside which plan tier it would fall into. The precise count is measured on your first sync using cloc.
What if my LOC changes a lot between syncs?▸
We measure once at the start of each billing period. Changes during the period — up or down — don't affect your current bill. If a large feature deprecation reduces your LOC significantly, you can request a manual re-measurement from your billing page. If it drops your tier, the new rate applies immediately.
How does the 10K bucket system work exactly?▸
We take your actual LOC, divide by 10,000, floor that number (round down), then multiply back. So 82,000 → floor(82,000 / 10,000) × 10,000 = 80,000. We always use the bucket for billing decisions — never the raw number. This means you're never penalized for being a few hundred lines over a round number.
What counts as a "line of code"?▸
We use cloc (Count Lines of Code), an open-source tool you can run yourself. It counts only executable source lines — blank lines and comment-only lines are excluded. Test files, generated output (like compiled bundles), and node_modules / dist / .git directories are also excluded. Run cloc --exclude-dir=node_modules,dist . in your repo to see exactly what we'd measure.
Can I be surprised by a large overage charge?▸
We design against surprises. Overage only applies to Team plan customers, and only after a 10% grace buffer above the 80K limit. Your billing dashboard shows your current LOC, your plan limit, and a projected overage charge before the period closes. If you're trending toward a significant overage, we'll send you an email heads-up so you can decide whether to trim repos or talk to us about Enterprise.
Is there a free tier or trial?▸
All plans include a 30-day free trial — no credit card required. This gives you enough time to connect your repos, run your first sync, and see the generated documentation portal before committing. There is no permanent free tier; developer tools that generate AI content have real infrastructure costs that a free tier would obscure.
How many times can I regenerate documentation?▸
Regeneration is designed around per-release syncs — we recommend triggering a sync when you cut a new version tag, not on every commit. Each plan includes up to 10 syncs per repo per month. Heavy regeneration beyond this is uncommon in practice and would be addressed on a case-by-case basis with affected customers — we won't silently charge you for it.
Start documenting in minutes
Connect your first repo free for 30 days. No credit card required.
