Dedicated infrastructure¶

The Enterprise plan with dedicated infrastructure gives you an isolated Tinybird ClickHouse® cluster: you are the only customer on that cluster. Your ingestion and query workloads run on your own dedicated replicas. This provides compute and network isolation and gives you fine-tuned control of the infrastructure required for your workloads.

Billing is credit-based. For Enterprise billing model details (commitment, invoices, and usage tracking), see Enterprise plan.

The following table summarizes all the SKUs for Dedicated infrastructure plans:

The sections below describe each SKU and how it is billed. Where applicable, rates depend on your region and contract.

Dedicated ClickHouse® cluster CPUs¶

The Dedicated ClickHouse® cluster CPUs SKU covers the cost of running your dedicated ClickHouse® cluster, which is provisioned exclusively for your organization. This cluster stores your data, runs your queries, and provides isolated compute and storage according to your topology and capacity. It includes ClickHouse® nodes, coordination services when applicable, and the underlying compute resources. Pricing for this SKU depends on the region where your cluster is deployed.

You can upgrade or downgrade your cluster at any time, immediately affecting billing for this SKU. Read more under Cluster Management.

Billing unit: CPU cores/hour.

On-demand CPUs¶

The On-demand CPUs SKU covers the cost of temporary compute capacity provisioned on demand for jobs that need dedicated compute instances. This currently applies to populate jobs that run on on-demand compute: these jobs run outside the baseline resources of your dedicated ClickHouse® cluster and use short-lived, single-host instances that exist only for the duration of the job and are deprovisioned when the job completes. Billing is based on the CPU cores used and the duration of the on-demand instance; rates may vary by region.

Billing unit: OnDemand CPU cores/hour.

Real-time ingestion¶

The Real-time ingestion SKU covers the cost of real-time data ingestion into the platform. This includes data ingested using the HFI (High-Frequency Ingestion) API, Kafka connectors, and DynamoDB connectors. Other ingestion mechanisms are not included in this SKU. Billing is based on the compute capacity required to sustain your ingestion throughput. Throughput is measured as compressed bytes sent to the platform and expressed as CPU core-hours (using P95 over time windows). Rates may vary by region and contract.

Only data that arrives at Tinybird is considered for this SKU. Once data is written, downstream operations (such as Materialized Views and Copy Pipes) are covered by the Dedicated ClickHouse® cluster CPUs SKU.

Billing unit: MB/s/CPU/hour (P95 over 15s windows).

Workers¶

The Workers SKU covers the cost of batch and asynchronous operations run by the platform on your behalf—including batch ingestion (for example, from S3, CSV, or Parquet), populate jobs, deletes, replaces, copies, and other job processor operations (excluding real-time ingestion). Billing is based on the maximum number of jobs you can run in parallel (concurrent workers) during the billing period: for each day, the platform uses the peak concurrency observed, and you are charged for that number of workers at a fixed daily rate per worker.

Billing unit: # of concurrent workers

Data Storage¶

The Data Storage SKU covers the cost of persistent data stored in ClickHouse® for your Workspaces. It accounts for the total amount of data on disk per Data Source, including both primary data and quarantine data. Storage is measured at the Data Source level and is based on peak storage usage during each billing period. Billing uses a storage-based rate per day based on the maximum storage observed.

Billing unit: TBs/day.

Backup Storage¶

The Backup Storage SKU covers the cost of stored ClickHouse® backups for organizations on dedicated infrastructure. It accounts for the total size of backups retained for your organization during the billing period, including full and incremental backups, aggregated across all your dedicated clusters. Backup usage is measured at the organization level. Billing is based on a storage rate per day based on the total backup size retained. For backup retention and related terms, see the Terms and Conditions.

Billing unit: TBs/day.

Data Transfer¶

The Data Transfer SKU covers the cost of data transferred out of the platform, primarily through Sinks that export data to external storage. It accounts for data moved across cloud providers and regions, and distinguishes between transfers within the same provider and region (intra) and transfers across different providers or regions (inter). Usage is measured at the Workspace level and aggregated daily; billing is a per-gigabyte rate that varies by transfer type and region.

Billing unit: GBs transferred.

Private Networking¶

The Private Networking SKU covers the cost of enabling and operating private network connectivity for your Workspaces—for example, private links between services, regions, or infrastructure components that are not exposed over the public internet. Billing is applied as a markup on the underlying connectivity cost.

Billing unit: GBs transferred.

Support¶

The Support SKU covers the cost of ongoing support services for your organization. Support is offered in different tiers (for example, Standard and Premier) and is defined in your contract. The applicable tier and price depend on your agreement and are not usage-based—charges do not depend on ticket volume or platform activity. Billing is typically a percentage of your total contracted credits, as agreed in your commercial terms.

Enterprise authentication¶

The Enterprise authentication SKU covers the cost of enabling Single Sign-On (SSO) with SAML for your organization. This is a flat-rate SKU: when SAML is enabled, a fixed rate is charged regardless of usage, number of users, or activity. If SAML is disabled, no charges apply. Billing is a fixed daily rate for each day the feature is active.

Private Region¶

The Private Region SKU covers the cost of enabling a private region deployment for your organization. It is a fixed SKU: when Private Region is enabled, a flat rate is charged regardless of workload, usage, or number of clusters. If the feature is disabled, no charges apply. Billing is a fixed daily rate for each day the feature is active.

Next steps¶

• Enterprise plan — Enterprise plan overview, support, and cluster management.
• Cluster management — Add replicas, choose SKUs, and set read/write weights.
• Regions and endpoints — Available regions (pricing varies by region).
• Shared infrastructure — Free, Developer, and SaaS plans and SKUs.
• Pricing — Public pricing and plan comparison.