name: Retool API FinOps
specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Retool
providerId: retool
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
  - Internal Tools
  - Low Code
description: FOCUS-aligned FinOps for Retool. Spend is per-builder subscription plus per-end-user (internal
  and external) charges and plan-bound workflow-run quotas. The Management and SCIM APIs are administrative
  and not separately metered.
sources:
  - https://retool.com/pricing
  - https://docs.retool.com/org-users/concepts/retool-api
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: Retool, Inc.
serviceCategory: Internal Tools
billingModel:
  pricingCategory: Tiered Subscription
  billingFrequency: Monthly
  billingCurrency: USD
  chargeCategories:
    - Purchase
    - Usage
    - Tax
focusColumns:
  ServiceName: Retool
  ServiceCategory: Internal Tools
  ProviderName: Retool
  PublisherName: Retool, Inc.
  InvoiceIssuerName: Retool, Inc.
  BillingCurrency: USD
meters:
  - name: builder_seats
    unit: seat
    aggregation: sum
    dimensions:
      - tier
  - name: internal_end_users
    unit: user
    aggregation: sum
    dimensions:
      - tier
  - name: external_users
    unit: user
    aggregation: sum
    dimensions:
      - portal
  - name: workflow_runs
    unit: run
    aggregation: sum
    dimensions:
      - workflow
  - name: retool_database
    unit: GB
    aggregation: max
principles:
  - name: Visibility
    description: Visibility comes from the Retool admin billing page and the Management API's user/group
      endpoints; export builder, internal-user, and external-user counts to your finance pipeline.
  - name: Allocation
    description: Allocate builder seats to the engineering or ops team that owns the apps, internal end-users
      to the consuming line of business, and external users to the customer-facing product the portal
      serves.
  - name: Optimization
    description: Optimization levers are seat hygiene (reclaim inactive builders), promoting builders
      to internal end-users when they stop editing, sizing the Business external-user tier to the active
      portal population, and consolidating workflows to stay under the plan's run quota.
  - name: Accountability
    description: Owner is the Retool admin / platform team that controls user provisioning (often via
      the SCIM 2.0 API and SSO) and assigns workspaces to consuming teams.
notes: Per-builder + per-end-user subscription with workflow-run and database quotas; the Management
  and SCIM APIs are administrative, not separately metered. Generic per-request meters and unit economics
  removed.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com