Upcoming changes to Developer plans¶

The pricing model for plans on shared infrastructure is changing. The docs now include a detailed preview of what's coming:

• QPS overages and Active minutes are being removed. Two new SKUs replace them: vCPU overages and On-demand CPUs.
• QPS is no longer tied to billing. All plans share the same platform QPS limit (up to 600 QPS), kept as an infrastructure reliability safeguard only.
• vCPU-based billing. Each plan includes a baseline vCPU allocation. Usage above that allocation counts as vCPU overage. A burst capacity (typically 2x to 3x) absorbs spikes before rate limiting kicks in with a 429.
• No more 24-hour resize restriction. Developer plans can be resized or canceled at any time, with a minimum fee for same-day resizes.

Read the full details in the Developer plan docs.

Migrate from Classic to Forward with the new migrate-to-forward CLI command¶

From 4.5.6 upwards, Forward CLI supports the migrate-to-forward command which allows users to migrate Classic workspaces, without connectors, to Forward. This command makes migration self-serve and removes branches and releases, migrates your workspace, and produces a live deployment to fully complete a workspace's transition to Forward. The migration guide for these Classic workspaces without connectors can be found here. In addition, we have updated the overall migration docs to pave the way for migrations with connectors that will be coming soon.

Pipe stats retention extended to 30 days¶

The tinybird.pipe_stats_rt Service Data Source now retains data for 30 days, up from the previous 7-day window. You get a longer history for debugging, monitoring, and analyzing API usage patterns without needing to set up your own retention pipeline.

TypeScript SDK: Null Engine Data Sources and optional output fields¶

The TypeScript SDK now supports Null Engine Data Sources. These are Data Sources that don't store data, useful for schema definitions, testing, or as intermediaries in pipelines where you need the schema but not the storage.

Endpoint output schemas also support optional fields with .optional(). This is useful for templated Endpoints where a column may or may not be present depending on request parameters:

output: {
  event_name: t.string(),
  event_count: t.uint64(),
  // Only returned when include_debug=1
  debug_info: t.string().optional(),
}

When debug_info is marked .optional(), schema validation accepts responses both with and without the column, and the inferred TypeScript type makes debug_info an optional property.

Faster deployments¶

Forward deployments now avoid processing pipelines that haven't changed. Previously, modifying one pipeline could trigger unnecessary work on unrelated ones. Now only what you actually changed gets processed, so deploys are faster and use fewer database resources.

More accurate memory charts in observability¶

The memory usage charts in Workspace and Organization observability now include data from both Data Source operations and Pipe stats, giving a more complete picture of memory consumption. Previously, only Data Source ops log was counted.

Bug fixes and improvements¶

• [All]: S3 sink errors from IAM "is not authorized" denials are now correctly surfaced as user-facing errors with a clear message, instead of being reported as internal failures.
• [Forward]: Fixed drift detection in Shared Data Sources stemming from UNIX / Windows differences in line breaks.
• [All]: Fixed NDJSON ingestion via URL, including a regression where Nullable(String) columns could fail conversion to LowCardinality(Nullable(String)) during Copy jobs.

From the blog¶

From 48 seconds to 130 milliseconds: vector search in Tinybird: A customer needed semantic search over 20 million embeddings. Three changes (HNSW indexes, pre-filtering, query structure) turned a 48-second timeout into sub-200ms responses.

Project Kijiji: building a GNN-based routing intelligence platform: A guest post about how a Graph Neural Network platform uses Tinybird to map African internet routing inefficiencies and predict where new IXP peering agreements would have the highest regional impact.