March 14, 2025

Tinybird Forward is out of beta!

Tinybird Forward is now generally available and includes a lot of exciting features:

  • The new Forward CLI with LLM-powered prompts to help you get started.
  • Forward queries to ease the evolution of your data source schemas.
  • File-based data projects you can version and collaborate on.
  • Built-in mock data and test generators.

Read the announcement post for more details.

If you're already a Tinybird user, know that:

  • The Tinybird you already know and love is now called Tinybird Classic, and it's not going anywhere.
  • When you create a new workspace, you'll be given the choice between Classic and Forward.
  • New signups will be created in Tinybird Forward by default.

Have a look at the Tinybird Forward docs to learn more. The Classic docs are still where they were.

We're eager to hear your feedback!

Tinybird Local compatibility mode

The Tinybird Local container can run now in two modes: Tinybird Classic or Tinybird Forward.

If you want to keep running Tinybird Local as Tinybird Classic set COMPATIBILITY_MODE="1" when running your container.

Improvements and bug fixes

  • All: We added validation for supported data types for the Bloom filter and N-gram Bloom filter indexes. Now, you get an error if you try to create an index with an unsupported data type.
  • Classic: Workspaces now have a limit on the number of playgrounds they can have. We enforce a maximum of 200 in the UI, so you can't create more than that. Before, you could end up with unreachable playgrounds due to the lack of limitation. If you need more playgrounds, delete old unused ones.
  • Classic: We set the PostgreSQL statement timeout to 5 minutes for the BI Connector. It was already limited to 10 seconds when querying Tinybird data. Some inefficient queries could be left running in the PostgreSQL side infinitely.
View previous update