New plans and pricing¶

We've updated our pricing to make it more predictable, more flexible, and more aligned with the value that you get from Tinybird.

• Tinybird still offers a time-unlimited, no-credit-card-required, the Free plan.
• Pricing is now based on vCPU hours, not processed data, for more predictability.
• You can choose a Developer plan size and scale up or down as needed.
• Legacy plans are being sunset on April 29, 2025. See Migrate from legacy plans.

For more details, see the following resources:

• A guide to Tinybird's new pricing model
• New pricing page
• Billing documentation

Migrate from legacy plans¶

We've set a sunset date for legacy plans at April 29, 2025. Until then, Workspaces on legacy Build and Pro plans will continue to operate on the legacy pricing model, with per Workspace limits, until you create an Organization or upgrade to a new plan. You will be prompted to create an Organization in the Tinybird UI. For Enterprise accounts, we'll reach out to you to help you migrate.

When you migrate to a new plan, you can estimate your costs and select the right plan based on the last 30 days of activity on your Workspaces.

A big welcome to Organizations¶

Organizations provide a centralized way of managing Workspaces and members in a region. From the Organization settings section you can monitor resource usage and check your current plan's usage and billing if you're on a paid plan.

You must have an Organization to create new Workspaces or migrate existing Workspaces to a new plan. You'll be prompted to create a new Organization when you log in to app.tinybird.co for the first time after this change.

After you create an Organization, all free and paid Workspaces for which you are an admin will be assigned to the Organization, and subject to the selected plan of that Organization.

Improved monitoring and observability¶

After you've upgraded, you'll find a Usage inside your organization settings where you can monitor plan usage against limits for vCPU time, queries per second, and memory.

You can track your usage against your billing plan in the Usage tab of your Organization admin console. In addition, you can query Tinybird service data sources to calculate ad hoc metrics and produce observability endpoints for consumption in Datadog, Grafana, or other third-party observability services.

JSON Schema supported for the Kafka connector¶

You can now ingest from Kafka topics that use a schema registry for JSON messages, either int the values or keys, using the new settings KAFKA_VALUE_FORMAT and KAFKA_KEY_FORMAT.

Future updates include adding UI support for this feature and validating messages against the schema at ingestion time.

Performance improvements for Pipes¶

When you open a Pipe, we automatically run each node so you can see all the results right away. However, in complex Pipes with many nodes, this could get messy, with lots of nodes resizing simultaneously as results pop in, plus heavy queries putting extra load on our servers.

To make Pipes run smoother, we've added two improvements: we now queue queries, running a maximum of 2 at a time, and we cache your latest results. This means next time you open the same Pipe, everything loads instantly since we'll show you the cached results from your last run.

Warning when Events API request size limit is hit¶

To ensure consistent high performance and reliability for all Events API users, we've started enforcing the maximum request size limit. According to the Events API documentation, the maximum request size for the Events API is 10 MB.

If you exceed this limit, you'll get a warning message in the HTTP response body and also you will see an error in the tinybird.datasources_ops_log table with the error message WARNING: Max request size 10 MB exceeded ({content_length} bytes sent), limit not enforced.

In the following weeks, we'll start rejecting requests that exceed this limit and you'll get an HTTP 413 - Request Entity Too Large error. For requests larger than 10MB, split them into multiple smaller requests to ensure smooth data ingestion.

New column memory_usage in datasources_ops_log¶

We've added a new column, memory_usage, in the datasources_ops_log table. This column shows the memory used by the operations done to your Data Sources.

Using this new column, you can identify Materialized Views that consume more memory and optimize it.

Improvements and bug fixes¶

• New Auth0 + Tinybird JWT template: Set up an Auth0 action to get a Tinybird JWT token as part of the post-login Auth0 trigger.
• New Link Click Analytics (Dub) template: Learn how to set up Dub locally.