Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.endorlabs.com/llms.txt

Use this file to discover all available pages before exploring further.

Endor Labs is licensed per contributor per year, with Core and Pro tiers across the Open Source and Code product lines. Every seat includes a daily scan credit allocation that pools across your contract term, plus support for onboarding multiple repositories.

​
License tiers and SKUs

All license tiers are priced per Code Contributor per year. A Code Contributor is any developer who has made one or more commits to a private source code repository monitored by Endor Labs in the last 90 days. The current SKU lineup and per-SKU feature lists are maintained on the Endor Labs pricing page. That page is the authoritative source for Endor Labs SKUs and licenses. Each license is sold standalone and priced per Code Contributor per year. Endor Open Source and Endor Code licenses have scan credit allocations based on the license and the number of Code Contributors. If you exhaust your scan credits, you need to buy the add-on license Endor Additional Code Scans (EL-ADD-SCANS). This extends scan capacity beyond your per-seat scan credit pool. It is sold in buckets of 10,000 scans.

​
Entitlements and limits

This section describes how seats, scan credits, repository caps, and overage work across product licenses. The limits described in the following sections are fair usage limits, sized to the number of seats you purchase. The limits are generous and you will never be blocked from scanning. Teams running scan-intensive workflows can purchase additional scan credits if they need to, but most organizations won’t need to.

​
Per-seat scan credit allocation

Daily allocations accumulate into a shared pool across your contract term. You can draw from this pool flexibly so that a high-volume PR day isn’t blocked as long as the pool has remaining credits.
When a Code Contributor is licensed for more than one tier, daily allocations stack. For example:
  • OSS Core + Code Core = 2 additional scans / Code Contributor / day
  • OSS Pro + Code Pro = 3 additional scans / Code Contributor / day (1.5 + 1.5)
  • OSS Core + Code Pro = 2.5 additional scans / Code Contributor / day

​
Included and additional scans

Each Code Contributor seat supports unlimited default branch scans (typically main or master) for up to 5 repositories. Beyond that, default branch scans are counted as additional scans. A non-default branch scan is any scan you trigger against a branch other than your default branch. For example: a feature, release, or hotfix branch.

​
Credit pooling

Credits pool across the full duration of your contract:
  • Annual billing: Credits unlock yearly at each renewal anniversary.
  • Prepaid multi-year contracts: All credits across the full term are available upfront.
For example:
  • 100 OSS Core seats × 1 year = 36,500 scan credits for use during that contract year.
  • 100 OSS Pro seats × 1 year = 54,750 scan credits for use during that contract year (Pro allocates 1.5 / Code Contributor / day).
  • 100 OSS Core seats × 3 years prepaid = 109,500 scan credits available upfront across the full term.
Pools provide flexibility within the contract. High-volume PR days are supported as long as the pool has credits remaining.

​
Overage

If your scan credit pool is exhausted, you can purchase additional scans in buckets of 10,000 scans as Endor Additional Code Scans (EL-ADD-SCANS). The platform continues to function without interruption if you exceed your allocation. Overage is handled through your account team.

​
Estimate your scan credit pool

Use the calculator to estimate your scan credit pool for a given license stack, seat count, and contract length.