Endor Labs · FinOps Profile

Endor Labs Finops

FinOps view of Endor Labs spend. Endor Labs is sold as a sales-led subscription rather than transparent usage-based metering, so cost is committed annually and allocated internally by the dimensions that drive packaging - typically developers, repositories, applications, or namespaces scanned. The REST API and endorctl make it possible to attribute platform value (projects scanned, findings, policy outcomes) back to teams and cost centers via namespaces even though billing itself is contract-based.

Endor Labs Finops is the FinOps profile for Endor Labs on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 5 billable meters, billed in USD, on a annual cycle, and pricing category commitment-based.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Security, Software Supply Chain, SCA, Reachability, and AppSec.

Category: Security Pricing: Commitment-Based Billing: Annual FOCUS v1.3
SecuritySoftware Supply ChainSCAReachabilityAppSecAI SecurityFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

PurchaseUsageAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Purchase
InvoiceIssuerName
Endor Labs
PricingCategory
Commitment-Based
ProviderName
Endor Labs
PublisherName
Endor Labs
ServiceCategory
Security
ServiceName
Endor Labs Platform

Meters

developers
Unit: developers
Developers covered by the subscription, a common packaging dimension.
repositories
Unit: repositories
Repositories onboarded and scanned across the tenant.
projects_scanned
Unit: projects
Project resources scanned, attributable per namespace for allocation.
scan_results
Unit: scans
Scan executions completed, useful for internal activity allocation.
findings
Unit: findings
Findings produced, allocated to teams via namespaces for accountability.

Sources