specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Soketi providerId: soketi 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: - Realtime - Open Source - FinOps - FOCUS description: >- FinOps view of Soketi. Open source - there is no Soketi SaaS bill. Cost is purely the cloud compute (VMs / containers), memory, network bandwidth, and (for horizontal scaling) Redis used to host the deployment. sources: - https://github.com/soketi/soketi - 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: Soketi (community) serviceCategory: Realtime Infrastructure billingModel: pricingCategory: Open Source / Self-Host billingFrequency: N/A billingCurrency: USD chargeCategories: - Usage focusColumns: ServiceName: Soketi (self-hosted) ServiceCategory: Realtime Infrastructure ProviderName: Cloud provider (operator's choice) PublisherName: Soketi (community) InvoiceIssuerName: Cloud provider BillingCurrency: USD ChargeCategory: Usage meters: - name: compute description: VM / container compute hours hosting Soketi. unit: vcpu_hour aggregation: sum dimensions: - account - region - name: memory description: VM / container memory. unit: gb_hour aggregation: sum dimensions: - account - name: network_egress description: WebSocket and REST egress bandwidth. unit: gb aggregation: sum dimensions: - account - region - name: redis description: Redis instance / cluster cost for horizontal scaling. unit: month aggregation: sum dimensions: - account principles: - name: Visibility description: Tag Soketi infrastructure with a workload label; pull cloud-provider invoices into FinOps store. - name: Allocation description: Allocate compute and bandwidth to consuming product line. - name: Optimization description: Use spot instances where acceptable; right-size Redis for connection count. - name: Accountability description: Assign an SRE owner; review monthly compared to a Pusher / Ably TCO. maintainers: - FN: Kin Lane email: kin@apievangelist.com