specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Tomorrow.io
providerId: tomorrow
created: '2026-05-30'
modified: '2026-05-30'
reconciled: false
tags:
  - FinOps
  - FOCUS
  - Weather
  - Forecast
  - Climate
description: >-
  FOCUS-aligned FinOps for Tomorrow.io: tiered monthly subscriptions (Free /
  Hobby / Builder / Enterprise) plus per-key request quotas. Spend is driven by
  the request meter against the API key, with secondary meters for monitored
  locations and configured alerts.
sources:
  - https://www.tomorrow.io/weather-api/
  - https://docs.tomorrow.io
  - 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: The Tomorrow Companies Inc.
serviceCategory: Weather & Climate Intelligence
billingModel:
  pricingCategory: Tiered Subscription
  billingFrequency: Monthly
  billingCurrency: USD
  chargeCategories:
    - Usage
    - Purchase
    - Tax
    - Adjustment
    - Refund
focusColumns:
  ServiceName: Tomorrow.io Weather API
  ServiceCategory: Weather & Climate Intelligence
  ServiceSubcategory: Forecast and Historical Weather Data
  ProviderName: Tomorrow.io
  PublisherName: The Tomorrow Companies Inc.
  InvoiceIssuerName: The Tomorrow Companies Inc.
  BillingCurrency: USD
  ChargeCategory: Usage
meters:
  - name: api_requests
    unit: request
    aggregation: sum
    dimensions:
      - endpoint
      - tier
      - api_key
    notes: Counts every Realtime, Forecast, Timelines, Historical, Climate, Routes, Events, Map Tile, Locations, Insights, and Alerts call.
  - name: monitored_locations
    unit: location
    aggregation: max
    dimensions:
      - tier
    notes: Concurrent saved locations subject to plan ceiling.
  - name: configured_alerts
    unit: alert
    aggregation: max
    dimensions:
      - tier
    notes: Concurrent alert resources subject to plan ceiling.
  - name: forecast_horizon_days
    unit: day
    aggregation: max
    dimensions:
      - tier
    notes: Maximum forecast horizon entitlement — 5 days on Free, 14 days on Enterprise.
  - name: subscription_seats
    unit: month
    aggregation: sum
    dimensions:
      - plan
    notes: Per-tier monthly subscription line item ($0 / $50 / $300 / custom).
  - name: webhook_deliveries
    unit: delivery
    aggregation: sum
    dimensions:
      - alert_id
    notes: Activations dispatched from Alerts to customer webhooks (informational; not separately metered).
principles:
  - name: Visibility
    description: >-
      Track consumption from the Tomorrow.io developer console request-usage
      dashboard, and join request_logs from the API gateway against the
      `apikey` query parameter to attribute spend per integration. Map quota
      ceilings to alarms so a team sees throttle pressure before it impacts
      production traffic.
  - name: Allocation
    description: >-
      Issue separate API keys per product team, per service, and per
      environment (dev / staging / prod). Use a `tier` and `cost_center` tag in
      the key name to feed FOCUS `ResourceTag` columns, then aggregate by tag
      in the FinOps platform.
  - name: Optimization
    description: >-
      Cache tile responses and aggregate Timelines requests across users
      sharing a location. Right-size the plan to actual daily request volume
      rather than peak burst — Tomorrow.io plans bill on tier ceiling not on
      consumption, so a quieter month does not reduce the monthly subscription
      line.
  - name: Accountability
    description: >-
      Assign each API key an owner in the Tomorrow.io console and review
      monthly request burn at the Cost & Usage review. Throttle and quota
      events are tied to the key, so attribution to a team is unambiguous.