specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
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: Symphony
providerId: symphony
publisherName: Symphony Communication Services, LLC
serviceCategory: Secure Collaboration / Messaging
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:
  - Secure Messaging
  - Financial Services
  - Collaboration
  - FinOps
  - FOCUS
description: Symphony is a contact-sales enterprise collaboration platform; APIs are included with the tenancy. There is no published per-call pricing or FOCUS-aligned cost export, so FinOps shape is approximated against the negotiated tenancy / seat invoice.
sources:
  - https://symphony.com
  - https://docs.developers.symphony.com
notes: No public per-call pricing or FOCUS-aligned billing export. Cost data must be reconciled from the negotiated Symphony tenancy invoice (typically per-pod plus per-seat).
billingModel:
  pricingCategory: Subscription (Enterprise)
  billingFrequency: Annual
  billingCurrency: USD
  chargeCategories:
    - Purchase
    - Usage
focusColumns:
  ServiceName: Symphony
  ServiceCategory: Secure Collaboration / Messaging
  ProviderName: Symphony
  PublisherName: Symphony Communication Services, LLC
  InvoiceIssuerName: Symphony Communication Services, LLC
  BillingCurrency: USD
meters:
  - name: pod_tenancy
    description: Symphony pod tenancy - the foundational commercial unit covering Pod and Agent API access.
    unit: month
    aggregation: sum
  - name: licensed_seats
    description: Licensed user seats on the pod; the primary per-user commercial unit.
    unit: seat
    aggregation: max
  - name: community_connect_relationships
    description: Cross-tenant Community Connect relationships, typically negotiated separately.
    unit: relationship
    aggregation: count
principles:
  - name: Visibility
    description: Pod administrators see seat consumption and bot/app inventory through the Symphony admin console; cost reconciliation happens against the negotiated invoice rather than a usage API.
  - name: Allocation
    description: Allocate by business unit to seat counts and named bots; Community Connect cost can be allocated to the cross-firm relationship that owns it.
  - name: Optimization
    description: Optimize by reclaiming inactive seats, consolidating bots that hold redundant entitlements, and bundling Community Connect relationships at contract renewal.
  - name: Accountability
    description: Pod owner (typically central IT or compliance) and the Symphony account team jointly own commercial reviews; line-of-business sponsors own seat allocations.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com