specification: FinOps Framework specificationVersion: '1.0' 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/ provider: Vendure providerId: vendure publisherName: Vendure serviceCategory: Software created: '2026-05-22' modified: '2026-05-25' tags: - Commerce - Headless - eCommerce - Open Source - FinOps - Cost Management - FOCUS description: >- FinOps framework alignment for Vendure. Because Vendure Core is open source (GPLv3) and self-hosted, the dominant cost surface is the underlying infrastructure (compute, database, cache, object storage, egress) plus, optionally, the Vendure Platform commercial license and Vendure Cloud managed hosting. This document maps those drivers onto the FOCUS schema. principles: - name: Visibility description: >- Make Vendure infrastructure costs (compute, DB, Redis, object storage, CDN/egress) and the Vendure Platform / Cloud subscription visible to engineering, product, and finance teams. - name: Allocation description: >- Tag Vendure deployments and underlying cloud resources with the consuming Channel, environment, region, team, and feature so cost can be allocated. - name: Optimization description: >- Right-size the Vendure server, database, and Redis tier; use the asset server with object storage and a CDN; tune the job queue concurrency; cache search results. - name: Accountability description: >- Assign budget owners per Channel / region / brand and run periodic reviews against the Vendure deployment footprint. domains: - name: Infrastructure description: >- Compute, database, cache, object storage, and egress underpinning the self-hosted Vendure server. Sourced from the underlying cloud provider's billing surface (AWS, GCP, Azure, Hetzner, Fly, etc.). costDrivers: - compute_hours - database_iops_and_storage - redis_throughput - object_storage_volume - egress_volume focusMapping: ChargeCategory: Usage ChargeClass: Consumption ServiceCategory: Compute ServiceSubcategory: Self-Hosted Application - name: Vendure Platform (Subscription) description: >- Annual flat-fee subscription for the commercial Vendure Platform capability layer. costDrivers: - subscription_tier focusMapping: ChargeCategory: Purchase ChargeClass: Committed ServiceCategory: Software ServiceSubcategory: Commerce Platform - name: Vendure Cloud (Managed Hosting) description: >- Managed hosting subscription / commitment for Vendure Cloud (design partner / GA Q4 2026). costDrivers: - environment_tier - region_count - data_residency focusMapping: ChargeCategory: Usage ChargeClass: Committed ServiceCategory: Managed Hosting ServiceSubcategory: Commerce Platform focusFields: required: - BillingPeriodStart - BillingPeriodEnd - ChargeCategory - ChargePeriodStart - ChargePeriodEnd - ProviderName - PublisherName - InvoiceIssuerName - ServiceName - ServiceCategory - BilledCost - EffectiveCost - ListCost - ContractedCost - PricingCategory - PricingUnit - PricingQuantity recommended: - SubAccountId - SubAccountName - ResourceId - ResourceName - ResourceType - Region - Tags allocationDimensions: - Channel - Seller - Environment - Region - Team - Brand notes: - >- Vendure Core itself has no per-request, per-order, or GMV-based fee. The framework's only cost obligation is GPLv3 compliance. - >- For self-hosted deployments, the bulk of FinOps work happens against the underlying cloud provider's FOCUS export; this document anchors Vendure-specific tags (Channel, Seller, Environment). - >- For Vendure Platform / Cloud subscribers, reconcile the contracted annual fee against the FOCUS Purchase / Committed Usage charge classes.