July 3, 2026

Tinybird Local now supports arm64

Tinybird Local now ships a native arm64 image alongside the existing amd64 one. Starting with the Tinybird CLI v4.6.6, tb local runs the container using the host's native architecture (linux/arm64 on Apple Silicon, linux/amd64 elsewhere) instead of always forcing linux/amd64. Apple Silicon and other arm64 machines no longer run under emulation, so the container starts faster and uses fewer resources.

No changes are needed in your setup. If you previously pulled the image with an older CLI and have the emulated linux/amd64 version cached, tb local detects the mismatch and re-pulls the native image automatically.

To override the auto-detected platform, set the TB_LOCAL_IMAGE_PLATFORM environment variable (for example, linux/amd64 to keep running the amd64 image emulated on an arm64 host).

ClickHouse® upgraded to 25.8

The ClickHouse® version bundled in Tinybird Local is upgraded from 25.3 to 25.8, bringing the latest fixes and improvements to your local environment.

Action needed if you use geoToH3

ClickHouse® 25.8 changes the default argument order of the geoToH3 function. If your queries call geoToH3, you must add the following setting to keep the previous (lon, lat) order:

Set geoToH3 argument order
SETTING geotoh3_argument_order = 'lon_lat'

Add the setting to the affected queries in your project, or set it at the container level, so results stay consistent after the upgrade.

Lightweight deletes in beta

The new POST /v1/datasources/{name}/delete endpoint deletes rows using ClickHouse®'s lightweight DELETE: matched rows are marked as deleted and filtered out of queries, while the physical cleanup happens later during background merges. Requests are synchronous by default and return the number of affected rows inline, or you can pass wait=false to get a job you can poll instead. An optional partition parameter scopes the delete to a single partition.

From the CLI, add the --lightweight-delete flag to tb datasource delete. The same partition scoping is available there through the --partition flag.

The existing /v0 delete endpoint is unchanged. See the Replace and delete data guide and the Data Sources API reference for details.

Monitor Organization from Overview and Logs UI pages

The Organization settings page now includes Overview and Logs pages to help you understand how your Organization is performing across Workspaces without switching context.

  • Overview helps you start from the most relevant Workspaces, check recent usage, and spot errors from a single landing page.
  • Logs brings logs from all Workspaces into one explorer, so you can filter by time range, status, source, Workspace, or text search and share the exact view with your team.

Improvements and bug fixes

  • [Forward]: tb pull generates Kafka, blob storage and DynamoDB connection files and automatically writes any necessary secrets.
  • [All]: In the UI, Enterprise billing now shows a consistent credit forecast through the end of the contract and warns when recent usage trends project a credit shortfall.
  • [All]: The Jobs API now returns jobs in a stable order, so polling views no longer show different jobs in the same row across refreshes.
  • [Forward]: The Jobs page now keeps rows stable while refreshing, reducing flicker during automatic polling.
  • [Forward]: SQL editor suggestions now keep working after typing a dot and correctly show column suggestions for dotted table names, such as system.query_log.