Tinybird is now available in AWS ap-east-1 (Hong Kong) and AWS ap-southeast-2 (Sydney).

If you're running workloads that serve users in APAC, these regions put your data and compute closer to them. Lower query latency at the edge, faster ingestion from local sources, and data residency in Hong Kong or Australia.

Full feature parity in both regions: Kafka and S3 connectors, Events API, real-time Materialized Views, and low-latency API Endpoints.

Select either region when you sign up for Tinybird or create a new Workspace.

Faster deployments with ATTACH PARTITION¶

Deployment backfills now use ATTACH PARTITION ALL FROM instead of SELECT * ... populate when possible. This skips the full data scan and copy, attaching existing partitions directly. For large Data Sources, this can make deployments significantly faster.

Destructive column changes require --allow-destructive-operations¶

Deployments that overwrite existing columns with default values (for example, changing a column type in a way that loses data) now require the --allow-destructive-operations flag. Without it, the deployment fails with a clear error message explaining which columns would be affected. This prevents accidental data loss during schema evolution.

Deployments unblocked when copy jobs are running¶

Previously, if a Copy Pipe job was running, all deployments were blocked, even when the deployment didn't touch any Data Sources involved in the copy. Now, deployments that don't modify Data Sources used by an active copy job proceed without waiting.

optimize_aggregation_in_order from all interfaces¶

The previous changelog introduced optimize_aggregation_in_order support for inline SETTINGS in SQL queries. You can now use it everywhere:

• As a query parameter: /v0/pipes/<pipe>.json?optimize_aggregation_in_order=1
• In Pipe SQL templates: %{{activate('optimize_aggregation_in_order')}}
• In the Playground
• Via the ClickHouse® HTTP interface

This setting can speed up aggregation queries where the Sorting Key matches the GROUP BY columns.

Forward CLI updates¶

tb copy pause and tb copy resume: commands to pause and resume copy jobs from the CLI.

CLI 4.4.2: tb build and tb dev now display git branch, Tinybird branch name, and dashboard URL before building. In local mode, a separate Workspace is created per git branch.

Python SDK init no longer requires --type¶

The tinybird init command in the Python SDK no longer requires the --type parameter. The project type is now inferred automatically.

TypeScript SDK updates¶

Several improvements landed in the TypeScript SDK (v0.0.65-0.0.66):

• Custom fetch exposed on typed client. You can now pass a custom fetch implementation to the typed Tinybird client for use cases like custom auth headers or request logging.
• Local workspace URL format updated. Local workspace dashboard URLs now use the format cloud.tinybird.co/{provider}/{region}/{ws}~local~{branch} instead of cloud.tinybird.co/local/{port}.

UI improvements¶

• Unified resource actions. Data Source, Endpoint, and Copy Pipe resource pages now have consistent action buttons: "Open in Playground" and "Open in Time Series" on Data, Output, and Log tabs. A row limit selector and "Show as table/JSON/CSV" controls are also standardized.
• DataFlow performance. The lineage graph now computes dependencies centrally instead of per-node, making large graphs render faster. Tab switching in resource pages no longer re-renders the lineage.
• Overview charts. Tooltips are synced across overview charts, and each chart now includes "Open in Playground" and "Open in Time Series" buttons.
• Connector logs. Connector log views now include "Open in Playground" and "Open in Time Series" buttons.

Pipe query validation on tb check¶

Running tb check now validates Pipe queries against ClickHouse®, catching SQL errors before deployment. Postgres and Iceberg query Pipes are excluded from this validation since they use different query engines.

API: 413 for oversized query results¶

The query API now returns HTTP 413 when a query result exceeds the maximum allowed size, instead of a generic error. This makes it easier to detect and handle large result sets programmatically.

SQL length limit updated to 128KB¶

The maximum SQL query length has been increased from 64KB to 128KB across all plans. See the limits docs for details.

Bug fixes and improvements¶

• [Forward]: Fixed Pipe resource Query and Output tabs not using parameters properly.
• [Forward]: Fixed playground reuse to match by SQL and nodes, not just by name.
• [Forward]: Fixed deployment view URL persistence. The selected view in deployments is now stored in the URL, so it's preserved when refreshing.
• [Forward]: Fixed CSV import of Tuple columns through ClickHouse®.
• [Forward]: Fixed CSV quarantine for Nullable(DateTime) columns. Empty strings in nullable datetime columns were incorrectly quarantined instead of being treated as NULL.
• [Forward]: Improved CSV header and separator detection during ClickHouse® import, preventing conflicts with ClickHouse®'s auto-detection.
• [Forward]: Fixed NDJSON replace operations that were marked as done before the replace hook finished.
• [Forward]: Fixed replace_tables failures in copy jobs when Materialized View SQL references external tables not in the Workspace.
• [Forward]: Fixed deployment token scopes when a Data Source is replaced with a Pipe of the same name.
• [Forward]: Fixed cyclic dependency detection during deployment phase calculation.
• [Forward]: CLI messages now show uv run tinybird for Python SDK projects and npx tinybird for TypeScript SDK projects instead of tb.
• [Forward]: Blocked creating and promoting releases in Forward Workspaces (deletion still allowed for cleanup).
• [All]: Fixed duplicated regions in the region selector menu.
• [All]: Fixed Workspace redirect after deletion and when the last stored Workspace no longer exists.
• [All]: Fixed total storage not being displayed in the credits usage table.
• [All]: Fixed CPU time chart in the overview page.
• [All]: Fixed multipart form-data requests without a boundary parameter returning 500 instead of 400.
• [All]: Documented mode=replace requirement for pre-signed S3 URLs and FORWARD_QUERY backfill warnings.

hfi_requests: ch_written_rows, ch_written_bytes, and ch_cpu_time deprecated¶

The ch_written_rows, ch_written_bytes, and ch_cpu_time columns in the tinybird.hfi_requests Service Data Source are now deprecated and will be removed in a future release.

If you're using these columns in queries or dashboards, remove them. All other hfi_requests columns remain available and unchanged.

Finding and fixing bugs in ClickHouse®'s Alias table engine: We tested ClickHouse®'s experimental Alias table engine against real workloads, found two bugs in DDL dependency tracking and Materialized View triggering, and shipped a fix upstream.

Tinybird is now available in AWS ap-east-1 (Hong Kong): Lower latency for APAC workloads with data residency in Hong Kong.

Tinybird is now available in AWS ap-southeast-2 (Sydney): Lower latency for Australia and Oceania workloads with data residency in Sydney.