Tinybird Classic sunset for Free and Developer plans

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 support@tinybird.co 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.