Tinybird Release Notes

The JSON data type is no longer in private beta

Every workspace can create JSON columns and query them with no flag or request needed. If you were holding back dynamic or semi-structured event data because of the beta, you can start using JSON columns today.

Organization pages work without workspace access

Organization pages (Overview, Observability, Logs, Cluster) now load for members who don't belong to any workspace. You can read organization-level data with your user token alone instead of an empty screen.

Improvements and bug fixes

• [All]: Resource descriptions in the sidebar render as markdown, and the sidebar scrolls correctly instead of clipping long description lists.
• [All]: Authenticated requests resolve token scopes faster. Scope lookup no longer loads every Data Source in the workspace for each request, which reduces endpoint latency in the regions where it was most costly.
• [API]: Query requests that time out now return HTTP 408 instead of 500, so client-side timeouts no longer look like server failures.
• [Forward]: The Logs page Resources filter now matches job rows by pipe or Data Source name, including deleted resources, and ignores case.
• [Forward]:
  tb deployment promote --wait
  and
  tb deployment discard --wait
  exit with the deployment error instead of polling forever when removing the old deployment fails.
• [SDK]: The TypeScript SDK now serializes JSON parameters correctly.

From the blog

Cluster Management: keep the controls, skip the cluster ops: Observe workload signals, resize Dedicated clusters, and rebalance traffic from the Organization UI or API. Part of the Cluster Management campaign that kicked off this week.

The default execution timeout for Query API and Pipe endpoint requests is now tiered by plan: 10 seconds on the free plan, 20 seconds on paid plans with shared infrastructure, and 30 seconds on dedicated infrastructure. Workspaces with a custom timeout override keep their existing setting.

New replica column in pipe_stats_rt

The pipe_stats_rt service Data Source now includes a replica column showing which ClickHouse® replica executed each request. Use it to spot load imbalance or latency differences across replicas.

Improvements and bug fixes

• [All]: Import jobs now use a routing algorithm that picks the least-loaded ClickHouse® replica instead of always using a single fixed server, on clusters with multiple writer replicas.
• [API]: Fixed browser-based uploads to the v1 Data Source append and replace Endpoints, which previously failed CORS preflight checks.
• [API]: You can now retry failed or cancelled S3 and GCS sync jobs. Retries skip files that earlier attempts already imported instead of re-importing everything, and work on jobs with many files.
• [Classic]: Fixed the dashboard Jobs widget showing no results after filtering while on page 2 or later.
• [Forward]: Deployments no longer fail when a materialized pipe has a leftover alter deployment method directive with nothing left to change; Tinybird shows a warning instead.

Until now, changing the right side of a Materialized View join forced a rebuild of the Materialized View and every resource downstream of it. Deployments now follow only left-table dependencies, so a change to the joined table alone skips those backfills. For a table joined by several Materialized Views, changing its partition key now rebuilds only that table.

Improvements and bug fixes

• [Forward]: Sending events to /v0/events for a Data Source that does not exist yet returns HTTP 404 with an explanation instead of a 500. Data Sources in Forward Workspaces are created through deployments.
• [All]: Ingestion failures caused by duplicate columns are now treated as user errors. They are no longer retried, so the error surfaces immediately instead of after retries that cannot succeed.

From the blog

How Guideless uses Tinybird to build training people actually finish: Play rates, completion rates, and step-level drop-off for every published guide, powered by Tinybird instead of a separate analytics backend.

The v1 Data Sources API can now append or replace rows from a remote CSV, NDJSON, or Parquet file. Pass the file URL and format to the existing /append or /replace endpoint instead of downloading and uploading the file yourself.

Improvements and bug fixes

• [Forward]: Fixed a bug that made deployment backfills fail with certain partition keys.
• [Forward]: Deployment validation no longer repeats Connection and bucket checks when multiple Sink Pipes use the same Connection.
• [Forward]: Promoting a missing or deleted deployment now returns HTTP 404 instead of an internal error.

Forward now retains the existing quarantine table when a Data Source deployment changes its sorting key, partition key, or column types without changing the set of columns.

Quarantined rows remain available to users after the deployment instead of requiring support help to recover them.

Seven-day workspace trends

The Organization Workspaces table now shows seven-day sparklines for vCPU time, memory, and errors. Totals remain available if a trend query times out.

Improvements and bug fixes

• [Forward]: ALTER-based deployments can now drop a column across a landing Data Source and Materialized View flow. The Materialized View query is updated before the referenced column is removed.
• [Forward]: DynamoDB-backed Data Sources now show the correct type and detail link in the UI.
• [All]: Invalid UTF-8 ingestion now returns a clear HTTP 400 error instead of an internal failure.
• [Forward]: Classic to Forward migrations no longer fail when a legacy Data Source lacks cached engine metadata.
• [All]: Copy job timeout and memory errors now point to on-demand compute when it is applicable.
• [Classic]: The region list in the workspace menu no longer reorders while workspace information loads.
• [All]: Delete, Copy, and Sink job concurrency errors now clarify that working and queued jobs both count toward the limit.

From the blog

Better organization-wide visibility, for every Tinybird user: A tour of the new Organization Overview and Logs pages available to organization members.

Slate scopes product ideas around users, not infrastructure: How Slate replaced a Redis bottleneck with Tinybird to deliver real-time prices and profit and loss data.

From OLTP to OLAP: 7 ClickHouse® Optimization Mistakes: Seven common OLAP modeling and query mistakes, with practical fixes.

Tinybird CLI 4.6.14 for Forward and 6.5.6 for Classic now use the v1 import flow by default when appending or replacing a Data Source from a local CSV, NDJSON, or Parquet file. The --experimental=use_v1 option is no longer required.

Forward CLI 4.6.14 returns the queued job ID by default. Pass --wait to wait for completion. Classic CLI 6.5.6 waits for completion by default. Pass --no-wait to return the queued job ID immediately. tb datasource append --events also uses the v1 import flow. Imports from remote URLs keep their existing behavior.

The Tinybird UI and Tinybird Local now use the same v1 flow for local file append and replace operations.

This requires the latest Tinybird Local version because local v1 imports depend on the newer append and replace endpoints.

Conditional TTLs

Data Source deployments now support conditional TTL rules, including multiple rules and DELETE WHERE conditions. TTL validation uses ClickHouse® syntax directly, so ENGINE_TTL accepts the same expressions as ClickHouse®. You can now do things like:

ENGINE_TTL "ts + INTERVAL 6 MONTH WHERE client_id != 'long-ttl-client', ts + INTERVAL 1 YEAR WHERE client_id = 'long-ttl-client'"

Live data-movement progress for deployments

Forward deployment pages now include a Data movements tab when a deployment requires a backfill. It shows each affected Data Source, its current status, elapsed or estimated time, and progress. Deployment and job status update automatically while work is running.

Unified job type for deployment backfills

Deployment backfills now log with job_type = 'deployment_backfill' regardless of how they move the data.

Until now, backfills that ran as a populate were logged as job_type = 'populate', with no metadata linking them to the deployment that triggered them.

Now all backfills log the same way in tinybird.jobs_log and tinybird.datasources_ops_log, including deployment_id and deployment_job_id in job_metadata, so you can tie every backfill back to its deployment.

Rows written before this change keep their original job type. To find old and new deployment backfills in the same query, filter on both:

SELECT * FROM tinybird.jobs_log WHERE job_type IN ('populate', 'deployment_backfill')

Updated Tinybird agent skills

The Tinybird agent skills now guide coding agents to parse JSON once when extracting several fields in a Materialized View, instead of parsing the same payload once per field.

The skills also recommend aligning partition granularity with Data Source TTL windows and using ttl_only_drop_parts=1 when appropriate, allowing ClickHouse® to drop complete expired parts instead of rewriting partially expired ones.

Organization info available to all users

Organization visibility is no longer limited to admins. Every member of an Organization can now see the Overview, Logs, Observability, Workspaces, Members, and Managed regions pages, so the whole team gets the same picture without asking an admin for access.

Admin-only actions stay protected: managing the cluster, viewing Billing, and adding, removing, or changing member roles in Workspaces they don't administer.

Improvements and bug fixes

• [All]: Data Source creation no longer selects Tuple or Map columns as inferred sorting keys. Schemas containing only composite columns now fall back to ORDER BY tuple() instead of failing to create the table.
• [All]: Strict NDJSON ingestion now handles compatible named objects for Map(String, T) columns, including numeric and nullable value types.
• [All]: Organization observability charts now use the same color for each replica in cluster load and memory charts as in the replicas table.
• [All]: You can now use do_not_merge_across_partitions_select_final as a query setting. When querying with FINAL, this setting merges parts only within each partition, which can speed up queries on well-partitioned Data Sources.
• [Forward]: Tinybird CLI 4.6.14 fixes tb migrate-to-forward so it finds and offers to delete all Classic branches before migration, including branches not created by the user running the command.

JSON ingestion preserves integer values

/v0/events ingestion into JSON and Array(JSON) columns now preserves integers when later values exceed the type inferred from the first value. Previously, a sequence such as 50 followed by 1944 could store the second value as -104.

Rows already affected are not repaired automatically and must be re-ingested.

Three months of real-time Pipe statistics

The tinybird.pipe_stats_rt and organization.pipe_stats_rt service Data Sources now retain three months of real-time Pipe request statistics instead of one month. This provides a longer window for investigating historical requests without falling back to daily statistics.

Experimental v1 ingestion in the CLI

Tinybird CLI 6.5.4 for Classic and 4.6.13 for Forward add experimental v1 ingestion for local files:

• tb datasource append --experimental=use_v1
• tb datasource replace --experimental=use_v1

The commands support CSV, NDJSON, and Parquet files, including gzip-compressed files. They return the queued import job immediately. Pass --wait to wait for completion. Remote URLs are not supported with this experimental option.

Breaking changes

• Pipe template parameter validation: Tinybird now rejects Pipe template type functions that declare a parameter without a valid, non-empty string name. Existing Endpoints continue serving traffic, but affected templates must be corrected before their next push, build, or deployment. The validation is included in Tinybird CLI 6.5.4 for Classic and 4.6.13 for Forward.

Classic: Up to 3 mutations in a single alter

The /v0/datasources/(.+)/alter endpoint now allows up to 3 mutating operations (such as DROP COLUMN or MODIFY COLUMN) in a single request, combined in one ALTER statement that runs as a single mutation. Previously, only one mutating operation was allowed per request, even alongside a metadata-only change.

Metadata-only operations, such as ADD COLUMN, don't count towards this limit and can still be combined freely with mutating operations. Requests that generate more than 3 mutating operations are rejected with an error message.

Improvements and bug fixes

• [All]: Added an email notification for users whose Workspaces are scheduled to be upgraded to ClickHouse® 25.3, ahead of the upcoming deprecation of 24.12.
• [Forward]: Failed deployment jobs no longer remain stuck as working when a concurrent Workspace update prevents the deployment status from being saved.
• [Forward]: Tinybird CLI 4.6.13 includes vendored Data Source files when running tb build, preventing false drift errors in branches that reference shared Data Sources.
• [Forward]: Authenticated users without a Workspace now see a "No workspace found" page instead of entering a redirect loop.
• [Forward]: The copyable prompt under Overview > Integrate now includes every Data Source and Endpoint in the Workspace instead of truncating each list after 10 resources.

Tinybird Classic is being sunset for Free and Developer plan Workspaces. If you have a Classic Workspace on one of these plans, migrate it to Tinybird Forward by September 15, 2026. After that date, remaining eligible Classic Workspaces will be scheduled for automatic migration. Enterprise plan Workspaces are not affected.

Forward is the main Tinybird product experience. Schema changes, local development, branching, CI/CD, SDKs, and AI-assisted workflows are all better in Forward. The migration guide walks through the process step by step, including the tb migrate-to-forward command.

Classic branches (part of the Versions functionality) are not migrated to Forward and will be removed during migration. Review how you use Classic branches before proceeding.

As a thank you for migrating early, we're offering a coupon for two months at 50% off your current plan, or one month free if you upgrade from Free to a paid plan. This offer is valid until August 15, 2026. Contact [email protected] after completing your migration to claim it.

Classic Workspace creation in the UI is now restricted to organizations on an Enterprise plan.

DynamoDB sampling for cloud branches and local

DynamoDB Data Source imports now support sampling in cloud branches and Tinybird Local. Main branches always get a full export on creation. Cloud branches and local can sample by row count or data size limits, or request a full export. This avoids slow exports on branches and reduces unnecessary egress costs.

tb_secret in Forward sink export settings

Forward Sinks now support {{ tb_secret(...) }} in EXPORT_* metadata fields like EXPORT_BUCKET_URI. Secrets are resolved at deploy time and baked into the Sink configuration. Empty secrets fail clearly instead of producing an invalid s3:// path. Changing a Workspace secret used in an export does not update existing Sinks: redeploy to pick up the new value.

v1 replace endpoint

New v1 endpoints are available for local file imports:

• POST /v1/datasources/{name}/append?format={csv|ndjson|parquet}
• POST /v1/datasources/{name}/replace?format={csv|ndjson|parquet}

These endpoints replace the equivalent v0 import request:

• POST /v0/datasources?name={name}&mode={append|replace}&format={format}

For replace operations, the v1 endpoint also accepts:

• replace_condition={SQL condition} — equivalent to --sql-condition
• skip_incompatible_partition_key=true — equivalent to --skip-incompatible-partition-key

The v0 import flow returns an import result that the client processes as a synchronous operation. The v1 endpoints stage the upload and enqueue an import job, returning immediately with the job response and import_id. Use GET /v0/jobs/{import_id} to follow the import until completion.

Improvements and bug fixes

• [All]: Log detail rows now resolve to clickable resource links for Pipes, Endpoints, Sinks, and Data Sources. Data Source operation logs show a related Pipe row when metadata is available. The logs table adds a hover state and persistent highlight for the row open in the split panel.
• [All]: ALIAS_REQUIRED and DECIMAL_OVERFLOW errors are now classified as user errors and no longer retried by the platform. Queries hitting these conditions fail faster instead of accumulating retry attempts.
• [Forward]: TypeScript SDK 0.0.82 changes the default branch_data_mode to no data. Cloud branches are now created empty by default. Set branch_data_mode: "last_partition" in your config to keep copying the last partition of production data into new branches.
• [All]: Copy Pipes that reference a deleted or missing target Workspace now return HTTP 404 instead of a generic error.
• [All]: Pipe creation with valid JSON but wrong field shapes now returns HTTP 400 early, instead of failing later when the handler treats values as mappings.
• [Forward]: Changing index_granularity now forces a new table plus backfill instead of attempting an ALTER, since this setting changes how data is stored on disk.

From the blog

The DynamoDB Connector is now in Tinybird Forward: How to mirror DynamoDB tables to Tinybird Forward with a .connection file and a single deploy, including the Classic-to-Forward migration path.

The CLI now picks the target Workspace in Tinybird Local more predictably during branch-based development. By default, commands point to the local Workspace mapped to the current Git branch. If you pass --token or set TB_TOKEN, the Token overrides Git branch detection and the command runs against the Workspace that belongs to that Token.

Sink jobs now pick the replica with the lowest load, using the same placement logic as Copy jobs and Data Source imports. Replica selection also accounts for running Sink queries, so Copy, import, and Sink placement all see the same picture of cluster load. This reduces the chance of a Sink job landing on a busy replica and slowing down.

Improvements and bug fixes

• [All]: The hostname and ProfileEvents columns are now exposed when querying system.query_log, making it easier to see which replica ran a query and more insights of the query execution.
• [All]: Import jobs created with a capitalized format, such as Parquet instead of parquet, no longer get stuck in job tracking. Previously they held a worker slot for up to 5 minutes after finishing, which throttled subsequent imports.
• [All]: Truncating a Data Source with a long history of deduplicated inserts no longer fails. When the regular TRUNCATE cannot complete, Tinybird now swaps in an empty copy of the table instead of returning an error.
• [All]: Fixed Omni integration through the ClickHouse HTTP Interface.
• [Forward]: Tinybird CLI 4.6.7 fixes an intermittent tb login failure where the browser flow returned a JSON decode error, and now raises an actionable message when authentication cannot complete.
• [Forward]: The Endpoint integration snippets in the UI now build the correct URL when working against Tinybird Local.
• [Forward]: TypeScript SDK 0.0.81 uses server-side auto-promote for deployments instead of polling and manually setting the deployment live and deleting the previous one. tb deploy now accepts --wait / --no-wait and --auto / --no-auto flags (both default to true), matching the CLI.