specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Ory providerId: ory 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: true tags: - FinOps - FOCUS - Identity - CIAM - OAuth2 description: FOCUS-aligned FinOps definition for Ory Network. Combines an annual subscription fee per project plan with usage-based metering on aDAU, M2M tokens, and permission checks net of a fixed monthly credit. sources: - https://www.ory.com/pricing - https://www.ory.com/docs/guides/rate-limits - 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: Ory Corp. serviceCategory: Identity billingModel: pricingCategory: Subscription + Pay-As-You-Go billingFrequency: Annual subscription with monthly usage settlement billingCurrency: USD chargeCategories: - Purchase - Usage - Credit - Tax focusColumns: ServiceName: Ory Network ServiceCategory: Identity ProviderName: Ory PublisherName: Ory Corp. InvoiceIssuerName: Ory Corp. BillingCurrency: USD ChargeCategory: Usage meters: - name: adau description: Active Daily Active Users measured per project per month, net of monthly credit unit: aDAU aggregation: sum dimensions: - project - environment - plan - name: m2m_tokens description: Machine-to-machine OAuth2 tokens issued per project per month unit: token aggregation: sum dimensions: - project - environment - plan - name: permission_checks description: Ory Keto permission check evaluations per project per month unit: check aggregation: sum dimensions: - project - environment - plan - name: project_subscription description: Annual subscription fee per project at the chosen plan level unit: project-year aggregation: count dimensions: - project - plan - name: monthly_credit description: Included monthly usage credit applied against meters before billable usage accrues unit: USD aggregation: sum dimensions: - project - plan principles: - name: Visibility description: Use the Ory Console usage dashboards to monitor aDAU, M2M token issuance, and permission check counts per project; reconcile against the monthly invoice and credit consumption. - name: Allocation description: Allocate by Ory project (one project per app/tenant is a common pattern) and by environment (production vs staging). Tag identity flows by client_id to attribute M2M token spend to consuming services. - name: Optimization description: Reduce aDAU by aligning session lifetime to user behavior, prefer long-lived sessions over re-authentication where appropriate, batch permission checks via Keto check requests, and right-size plan tier so the included monthly credit covers steady-state usage. - name: Accountability description: Each Ory project should have a named owner who reviews monthly usage versus the included credit and decides when to escalate from Production to Growth or Enterprise. maintainers: - FN: Kin Lane email: kin@apievangelist.com