Tinybird is a managed ClickHouse® service for AI-native software teams. Get ClickHouse performance without ClickHouse complexity.

Joined April 2019
Paginating large ClickHouse tables with LIMIT and OFFSET is a latency trap. To fetch page 500 at OFFSET 50000, ClickHouse must scan and discard 50,000 rows. As offsets grow, queries slow down and consume unnecessary memory.
1
8
542
select * from x where trend = 'dots'
2
8
446
Unpredictable event payloads usually force a bad tradeoff: rigid upfront migrations, or raw string columns that waste CPU parsing JSON on every single query. Tinybird's native JSON data type is now on by default across all workspaces.
2
8
693
Scheduled Copy Pipes can now run on temporary dedicated compute. Add `ON_DEMAND_COMPUTE true` to keep recurring batch work separate from primary workspace compute. How it works and when provisioning is worth it: tinybird.co/blog/on-demand-c…
1
1
8
579
Building microservices just to expose ClickHouse queries to your app creates unnecessary plumbing. In Tinybird, write parameterized SQL with template variables like {{ Int32(hours, 24) }}. Tinybird publishes an authenticated, production REST API instantly.
2
11
898
Scanning raw events for every dashboard view wastes compute and adds latency. Tinybird Materialized Views aggregate streaming data on insert. Define a Pipe with countState() or uniqState(), and rows roll up into AggregatingMergeTree tables continuously.
2
6
464
We’re at Rows & Columns Summit today 👋 Visit our booth to talk real-time data with us and get an early look at @rawtreedb, what we’re building next. Scan the QR code and leave your details to enter our iPad raffle. 📍 Contemporary Jewish Museum
2
5
359
Streaming data into ClickHouse often starts with standing up Kafka, connectors, and consumer fleets. With Tinybird's Events API, you POST JSON directly over HTTP at 1K+ events/sec. Data lands in MergeTree tables and is queryable in seconds.
1
11
698
With Jev with realize that when people get something that's faster (even with some limitations) they find new ways and new use cases. I saw this with data, when people started to use ClickHouse instead of Spark (or even Snowflake) they naturally used it for new use cases and solve problems they didn't even consider before. A good lesson to learn, speed is more than a feature.
9
1,440
just migrated from @tinybird classic to forward - was smooth af, nice work birdies 🐦
4
1,247
Slate’s data layer used to define what was possible. Now, it gives the team the freedom to build around what users want. Here’s how @SlateWT rebuilt its real-time prices and P&L data layer.
1
1
6
665
Overview shows usage, infrastructure metrics, recent errors, and resource health. Logs lets you search and filter activity across every Workspace. Filters and time ranges stay in the URL, so you can share the exact investigation with your team.
1
1
300
The new Tinybird Overview page and organization-wide Logs explorer are generally available. One place to understand what's happening across every Workspace in your Organization.
1
10
792
The recurring mistakes: • Reading more data than needed • Ignoring sorting keys • Repeating work at query time • Poor data types • Joining too much data • Misusing materialized views • Over-partitioning The fix: make ClickHouse do less work.
1
5
355