Tinybird

PASS consensus from 3 PASS.

One quickstart defines page_views, ingests three events, queries top_pages, and deploys with tb deploy. One linear path gives the install command, the complete page_views.datasource and top_pages.pipe file bodies, tb build, a working Events API curl with three sample rows, the query call, the expected JSON response, and tb deploy, with no step left to inference. The quickstart walks through install, project init, datasource creation, endpoint creation, build, data ingest via Events API, curl query, and deploy with unambiguous step-by-step commands and file examples.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The values are 250 per IP per region and 20, 100, and 200 per workspace, but pricing says all limits are organization-wide. Every value is exact and on one page (250 concurrent connections per IP per region; Copy Pipes 20 Free, 100 Developer, 200 Enterprise), but the scope contradicts itself: the page opens by stating all limits are organization-level and shared across workspaces, while the Copy Pipe table states the same quotas are per Workspace. The concurrent connection limit and Free (20), Developer (100), and Enterprise (200) Copy Pipe quotas are tabulated clearly per plan with active-job, execution-time, and frequency columns.

PASS consensus from 3 PASS.

The common-patterns page names both codes and pairs each with causes and a Solutions list. Both codes get a named section with a cause list and a solution list on a single page, and the API Endpoints page closes the loop by documenting the X-DB-Exception-Code response header that surfaces the numeric code in the first place. Both error codes 241 and 252 have dedicated entries on the common-error-patterns page and full dedicated sub-pages with causes, example errors, fixes, and Tinybird-specific debugging notes.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The full static-token path is documented, but its PIPES:READ table says TOKEN APPEND while the quickstart says TOKEN READ. All four stages are documented end to end, but the static-token scope reference table maps PIPES:READ:pipe_name to "TOKEN <token_name> APPEND in .pipe files", contradicting the working example directly below it on the same page and the CLI quickstart, both of which use READ. The docs cover both static tokens (resource-scoped via TOKEN directive in datafiles, workspace-level via CLI) and JWTs (payload creation, signing, scopes, expiration, rate limits). Storage and transmission are documented for CLI, SDK, CI/CD, and raw API contexts.

PASS consensus from 3 PASS.

The SDK quickstart covers initialization, definitions, build, ingest, query, and deploy while preserving the CLI resource names. The SDK quickstart mirrors the CLI quickstart step for step on the identical page_views and top_pages example, so defineDatasource, defineEndpoint, npx tinybird build, ingest, and query map one to one onto the datafile concepts. The TypeScript SDK quickstart mirrors the CLI workflow exactly: same datasource/endpoint names (page_views, top_pages), same build/ingest/query pattern, same branch-based iteration with materialized views. The typed client provides a direct conceptual mapping from CLI datafiles to SDK resources.