specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Langfuse providerId: langfuse created: '2026-05-08' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-08, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-08' reconciled: true tags: - AI - LLM - Observability - Open Source - Evaluations - FinOps - Cost Management - FOCUS description: FOCUS-aligned FinOps profile for Langfuse Cloud. Cloud billing combines a flat-rate monthly subscription per plan tier with usage-based overage on units (a unified metric covering traces, observations, and scores). Self-hosted has no platform fees. sources: - https://langfuse.com/pricing - https://langfuse.com/docs - https://focus.finops.org/focus-specification/v1-3/ alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: Langfuse GmbH serviceCategory: AI billingModel: pricingCategory: Subscription + Usage billingFrequency: Monthly billingCurrency: USD chargeCategories: - Usage - Purchase - Adjustment focusColumns: ServiceName: Langfuse Cloud ServiceCategory: AI ProviderName: Langfuse PublisherName: Langfuse GmbH InvoiceIssuerName: Langfuse GmbH BillingCurrency: USD ChargeCategory: Usage meters: - name: subscription_fee description: Monthly plan subscription (Core $29, Pro $199, Enterprise $2,499). unit: month aggregation: sum dimensions: - account - plan - name: units description: Billable units (traces, observations, scores). Each plan includes a baseline; overage at $8/100k with volume discounts. unit: unit aggregation: sum dimensions: - organization - project - name: teams_addon description: Optional Pro Teams add-on ($300/month) for SSO and fine-grained RBAC. unit: month aggregation: sum dimensions: - organization principles: - name: Visibility description: Use Langfuse usage dashboards and invoices to map unit consumption to organizations and projects. - name: Allocation description: Tag traces by environment and product to allocate units to consuming services. - name: Optimization description: Sample low-value traces, choose appropriate retention tier, and consider self-hosting for high-volume workloads. - name: Accountability description: Assign each project to a budget owner and review monthly unit consumption against forecast. maintainers: - FN: Kin Lane email: kin@apievangelist.com