Pricing plans

Plans describe what your organization can do in Tinybird, the compute resources at your disposal, and how usage is billed. All plan features, limits, and resources are applied at the organization level and shared across all workspaces within your organization.

To see current prices, see Pricing.

Available plans

PlanInfrastructureWhat you getWhen to upgrade
FreeShared
  • All Tinybird features, with limitations.
  • Use Tinybird without time limits.
  • You can upgrade at any time.
  • You need more resources.
  • You're ready for production.
  • You want Tinybird support.
DeveloperShared infrastructure without a commitment
  • More resources and fewer limits.
  • Select compute needs of up to 8 vCPUs.
  • vCPU overages for usage exceeding your plan size.
  • You need more than 8 vCPUs on shared infrastructure.
  • You need credit-based billing with a commitment.
  • You need a dedicated cluster.
SaaSShared infrastructure with a commitment
  • Shared infrastructure, 4+ vCPUs.
  • Credit-based billing with a 12-month commitment.
  • QPS and active minutes overages.
  • You need a dedicated cluster.
  • You need private networking.
EnterpriseDedicated
  • Your own ClickHouse® cluster.
  • No resource sharing.
  • No predefined limits; scale with replica SKUs.
  • You need to adjust cluster size or add private networking.

You can upgrade from Free and Developer plans at any time. SaaS and Enterprise plans require contacting sales.

Features included in all plans

  • Unlimited seats
  • Unlimited source connections
  • Unlimited tables, pipes, and endpoints
  • Multi-cloud, multi-region support
  • RBAC and Workspace administrator controls. See Organizations.
  • SOC2 Type II and HIPAA compliance. See Compliance.

Deployment options

Plans run on one of two infrastructure types:

  • Shared infrastructure for Free, Developer, and SaaS plans: You share resources with other customers. Each plan page documents billing and plan-specific limits.
  • Dedicated infrastructure for Enterprise plans: Your own isolated ClickHouse® cluster. There are no predefined resource limits. Billing depends on replica SKUs and usage. See Enterprise.

On-demand CPUs

On-demand CPUs cover temporary compute capacity for jobs that need dedicated compute instances. On-demand compute is available on both shared and dedicated infrastructure.

This currently applies to:

  • Deployment populate jobs.
  • Copy Pipe jobs run with --on-demand-compute.

Deployment populates use on-demand compute automatically for large data migrations when one of these thresholds is met:

  • Data size exceeds 50 GB.
  • Row count exceeds 100 million rows.

Copy Pipe jobs use on-demand compute only when you explicitly run them with --on-demand-compute.

On-demand compute uses 64-core instances by default. You can request smaller instances for less resource-intensive workloads. Contact Tinybird support for configuration options.

Billing is based on the actual compute time used, measured in credits per core per minute. Pricing varies by region:

RegionPrice (Credits per core per minute)
aws-us-east-10.0029
aws-us-west-20.0029
aws-eu-west-10.0032
aws-eu-central-10.0035
aws-ap-east-10.004
aws-ap-southeast-20.0036
gcp-us-east40.0027
gcp-europe-west30.0031
gcp-europe-west20.0031
gcp-northamerica-northeast20.0027

Example calculations:

  • A 2-hour deployment populate in AWS us-east-1: 0.0029 credits × 120 minutes × 64 cores = 22.3 credits.
  • A 30-minute Copy Pipe job in AWS us-east-1: 0.0029 credits × 30 minutes × 64 cores = 5.57 credits.

The credits are automatically deducted from your monthly invoice.

Next steps

  • Free plan: What's included and how to upgrade.
  • Developer plan: Plan sizes, billing, and resize options.
  • SaaS plan: Shared infrastructure with 4+ vCPUs and a commitment.
  • Enterprise plan: Dedicated cluster, replica SKUs, and premium support.
  • Limits: Platform and operational limits.
Updated
Looking for Classic docs?