specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Envoy Proxy providerId: envoy-proxy created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: false tags: - FinOps - FOCUS - Open Source - Gateways - Proxies - Service Mesh description: 'FinOps view of Envoy Proxy: the upstream project is free open-source software, so direct software cost is zero. The relevant FinOps surface is the operating cost of running Envoy (compute, egress, observability) plus any third-party commercial distribution.' sources: - https://www.envoyproxy.io/ - https://www.cncf.io/projects/envoy/ notes: No vendor invoice is generated by the Envoy project. This file frames the indirect FinOps surface (infrastructure to run Envoy) for completeness; replace with vendor-specific data if Envoy is consumed via a commercial distribution. 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: Cloud Native Computing Foundation serviceCategory: Networking / API Gateway billingModel: pricingCategory: Open Source (no direct cost) billingFrequency: N/A billingCurrency: USD chargeCategories: - Usage focusColumns: ServiceName: Envoy Proxy ServiceCategory: Networking / API Gateway ProviderName: Envoy Proxy PublisherName: Cloud Native Computing Foundation InvoiceIssuerName: N/A (open source) BillingCurrency: USD meters: - name: compute_hours unit: instance-hour aggregation: sum dimensions: - cluster - region - instance_type - name: egress_bytes unit: GB aggregation: sum dimensions: - cluster - region - name: telemetry_volume unit: GB aggregation: sum dimensions: - cluster - sink principles: - name: Visibility description: Envoy emits Prometheus stats, OpenTelemetry traces, and access logs; route them to your observability stack to attribute infrastructure cost to traffic flows. - name: Allocation description: Tag downstream services and clusters in Envoy's stats/labels so cost of compute and egress can be attributed to the consuming team or product. - name: Optimization description: Tune connection pooling, HTTP/2, compression, and caching at the Envoy layer to reduce upstream egress and CPU; right-size Envoy sidecars and gateways. - name: Accountability description: Platform team owns Envoy fleet cost; charge back compute/egress to consuming teams using cluster and route tags. maintainers: - FN: Kin Lane email: kin@apievangelist.com