specification: API Commons Plans specificationVersion: '0.1' schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/Plans provider: Chronosphere providerId: chronosphere created: '2026-05-04' modified: '2026-08-29' generated: '2026-08-29' method: searched source: >- https://chronosphere.io/ (footer and navigation, no pricing link), https://chronosphere.io/pricing and https://chronosphere.io/pricing/ (both HTTP 404), https://chronosphere.io/demo-request/ (HTTP 200), https://docs.chronosphere.io/administer/limits-licensing/licensing, /administer/limits-licensing/concepts/capacity-licensing and /administer/limits-licensing/concepts/consumption-licensing, all fetched 2026-08-29. tags: - AIOps - Observability description: >- Chronosphere publishes no plans, no tiers and no prices. There is no pricing page on chronosphere.io — /pricing and /pricing/ both return 404 and no navigation or footer link exists — and the only commercial call to action is "Request a Demo". Commercial terms are negotiated per contract. What IS public is the shape of the meter, documented for existing customers, and that is recorded below because it tells a buyer what they will be charged against even though it does not tell them the rate. plan_count: 0 plans: [] public_pricing: false self_serve_signup: false free_tier: false trial_published: false sales_motion: entry_point: https://chronosphere.io/demo-request/ http_status: 200 form: Request a Demo note: >- No self-service sign-up, no published free tier, no credit-card path. Access to the API requires an existing Observability Platform tenant, which is why the API base URL is a per-customer subdomain. tools_published: - name: Business Value Calculator note: Marketing-side ROI calculator; produces no price. - name: Migration Timeline Estimator - name: Migration calculator url: https://chronosphere.io/migration-calculator/ licensing_model: documented: true docs: https://docs.chronosphere.io/administer/limits-licensing/licensing models: - name: Capacity licensing docs: https://docs.chronosphere.io/administer/limits-licensing/concepts/capacity-licensing basis: >- Contracted capacity per license dimension. Quotas split the total system-persisted writes per second into per-pool allocations, and quotas determine which data drops first when capacity is exceeded. dimensions: - name: Standard Metrics License measures: - aggregations - persisted writes - persisted cardinality applies_to: - cumulative counter - delta counter - gauge - legacy Prometheus histograms and OTel explicit-bucket histograms (persisted as counters) - name: Histogram Metrics License measures: - aggregations - persisted writes - persisted cardinality applies_to: - cumulative exponential histogram - delta exponential histogram - Prometheus native histograms - name: Consumption licensing docs: https://docs.chronosphere.io/administer/limits-licensing/concepts/consumption-licensing basis: Metered consumption against contracted license dimensions. telemetry_dimensions: - metrics - logs - traces - events in_product_visibility: >- A License Overview page inside each tenant (Admin > License Overview) shows current consumption against contract limits, with Snapshot and Trends tabs, and flags dimensions at or near capacity. Exceeding a license dimension risks data being dropped. api_surface: note: >- Cost control is itself an API. ConsumptionBudget, ConsumptionConfig, ResourcePools, LogAllocationConfig and the DropRule/RollupRule/MappingRule family are all Config V1 resources, and the State V1 API exposes metric usage by metric name and by label name. A customer can automate against their own consumption even though they cannot see a price. operations: - ListConsumptionBudgets - ReadConsumptionBudget - CreateConsumptionBudget - UpdateConsumptionBudget - DeleteConsumptionBudget - ReadConsumptionConfig - UpdateConsumptionConfig - ListMetricUsagesByMetricName - ListMetricUsagesByLabelName provenance_note: >- This file replaces a 2026-05-04 bulk-sweep scaffold that invented three tiers (Free / Professional / Enterprise) with placeholder quotas and TBD prices. None of that was published by Chronosphere and none of it was true. plan_count 0 is the measured answer. maintainers: - FN: Kin Lane email: kin@apievangelist.com