Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Announcing the Supabase ETL! Supabase ETL is a change-data-capture pipeline that replicates your Postgres tables to analytical destinations in near real time! Available as private alpha starting today!

Tyler Shukert

18,254 subscribers

24,973 views • 9 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Introducing Supabase Pipelines. Your app runs on Postgres, but your analytics usually live somewhere else, like BigQuery. Pipelines keeps that data in sync for you in near real time, with no pipeline to build or maintain.

Introducing Supabase Pipelines. Your app runs on Postgres, but your analytics usually live somewhere else, like BigQuery. Pipelines keeps that data in sync for you in near real time, with no pipeline to build or maintain.

Supabase

63,308 views • 1 month ago

Watch Gemini 3 Flash transform manual ETL into a near real-time workflow. This demo shows how the model’s speed and reasoning capabilities instantly resolve mismatched sources, clean messy data, and fully automate the pipeline.

Watch Gemini 3 Flash transform manual ETL into a near real-time workflow. This demo shows how the model’s speed and reasoning capabilities instantly resolve mismatched sources, clean messy data, and fully automate the pipeline.

Google AI Developers

65,671 views • 8 months ago

In the next 2-3 years, the skills you need to build an ETL process will fundamentally differ from anything we've done in the last decade. The EXTRACT and LOAD steps of an ETL pipeline have been solved forever. They are boring, and I suspect they will continue to be boring. But the TRANSFORM step is where the money is at (and where innovation will continue happening!) An ETL pipeline that can use Large Language Models effectively to transform data is a whole new ballgame. I recorded a video to talk about this. And more importantly, I talk about how you can build ETL pipelines to transform UNSTRUCTURED data (the kind of data that's really hard to handle).

In the next 2-3 years, the skills you need to build an ETL process will fundamentally differ from anything we've done in the last decade. The EXTRACT and LOAD steps of an ETL pipeline have been solved forever. They are boring, and I suspect they will continue to be boring. But the TRANSFORM step is where the money is at (and where innovation will continue happening!) An ETL pipeline that can use Large Language Models effectively to transform data is a whole new ballgame. I recorded a video to talk about this. And more importantly, I talk about how you can build ETL pipelines to transform UNSTRUCTURED data (the kind of data that's really hard to handle).

Santiago

56,412 views • 1 year ago

As part of our effort to move the platform toward declarative code, new tables in the public schema will no longer be automatically exposed to the Data API in new Supabase projects starting May 30th. Instead, tables will need to be explicitly granted each permission to each role, either through the dashboard or via SQL. Explicit Postgres grants are reviewable, diffable, and greppable. They also give you per-role control: anon and authenticated need different privileges in most schemas, and an explicit grant makes that difference visible in your migrations. This was always possible; now it's the default.

As part of our effort to move the platform toward declarative code, new tables in the public schema will no longer be automatically exposed to the Data API in new Supabase projects starting May 30th. Instead, tables will need to be explicitly granted each permission to each role, either through the dashboard or via SQL. Explicit Postgres grants are reviewable, diffable, and greppable. They also give you per-role control: anon and authenticated need different privileges in most schemas, and an explicit grant makes that difference visible in your migrations. This was always possible; now it's the default.

Supabase

40,247 views • 3 months ago

We are announcing the Supabase UI Library, a set of shadcn-based components you can easily add to your app to implement common features! You can easily add sign-in/sign-up, image drop-zone, real-time chat, and many other components to your app using the shadcn CLI!

We are announcing the Supabase UI Library, a set of shadcn-based components you can easily add to your app to implement common features! You can easily add sign-in/sign-up, image drop-zone, real-time chat, and many other components to your app using the shadcn CLI!

Supabase

125,241 views • 1 year ago

Databricks Co-founder and Chief Architect Reynold Xin announces LTAP (Lake Transactional/Analytical Processing) at #DataAISummit 2026. LTAP is a new data processing architecture that unifies OLAP and OLTP on a single copy of data in the lake, eliminating ETL, replicas, and pipelines by design.

Databricks Co-founder and Chief Architect Reynold Xin announces LTAP (Lake Transactional/Analytical Processing) at #DataAISummit 2026. LTAP is a new data processing architecture that unifies OLAP and OLTP on a single copy of data in the lake, eliminating ETL, replicas, and pipelines by design.

Databricks

27,639 views • 2 months ago

Supabase now has an official MCP Server! This means you can create, edit, and connect a Supabase project to your app from your AI IDE like Cursor or Windsurf! We will also be adding more features to the MCP server, such as Edge Functions and Storage, in the near future!

Supabase now has an official MCP Server! This means you can create, edit, and connect a Supabase project to your app from your AI IDE like Cursor or Windsurf! We will also be adding more features to the MCP server, such as Edge Functions and Storage, in the near future!

Tyler Shukert

85,127 views • 1 year ago

Let Postgres own the Iceberg catalog and delegate analytics to DuckDB. The result => transactional lakehouse updates with fast analytical queries. This isn’t a concept. It’s exactly what pg_lake delivers today. pg_lake combines a set of extensions and components that let you query and modify Iceberg tables (and other lakehouse formats) directly from Postgres. DuckDB is used to accelerate analytical queries and runs in a sidecar process called pgduck_server, which communicates with Postgres during query execution. How it works (diagram below): 1. An application sends a query to Postgres to calculate unrealized PnL (Profit and Loss) for the Disney ticker. 2. Postgres parses the query and identifies the part that computes the average price from historical lakehouse data. 3. That part is forwarded to pgduck_server for accelerated execution. 4. pgduck_server delegates execution to DuckDB, which queries the lakehouse (reusing cached data if available). 5. DuckDB computes the average price and returns it to Postgres. 6. Postgres joins the result with local portfolio data and computes the unrealized PnL. 7. The final result is returned to the application.

Let Postgres own the Iceberg catalog and delegate analytics to DuckDB. The result => transactional lakehouse updates with fast analytical queries. This isn’t a concept. It’s exactly what pg_lake delivers today. pg_lake combines a set of extensions and components that let you query and modify Iceberg tables (and other lakehouse formats) directly from Postgres. DuckDB is used to accelerate analytical queries and runs in a sidecar process called pgduck_server, which communicates with Postgres during query execution. How it works (diagram below): 1. An application sends a query to Postgres to calculate unrealized PnL (Profit and Loss) for the Disney ticker. 2. Postgres parses the query and identifies the part that computes the average price from historical lakehouse data. 3. That part is forwarded to pgduck_server for accelerated execution. 4. pgduck_server delegates execution to DuckDB, which queries the lakehouse (reusing cached data if available). 5. DuckDB computes the average price and returns it to Postgres. 6. Postgres joins the result with local portfolio data and computes the unrealized PnL. 7. The final result is returned to the application.

Denis Magda

28,503 views • 7 months ago

Your agents can't keep up with real-time data. Especially when it's scattered across dozens of sources. Most teams waste weeks building custom connectors for every database, API, and data warehouse. Then they build ETL pipelines to sync everything. By the time your agent retrieves the data, it's already outdated. Picture this: Your Postgres database updated 5 minutes ago. Your MongoDB collection changed 2 minutes ago. Your agent is still pulling from yesterday's snapshot. This is why most production RAG systems fail. There's a better approach: MindsDB is an open-source AI platform with a federated data engine that lets you query multiple data sources in real-time using SQL - without moving any data. Here's what makes it different: ↳ Your data stays in place. No ETL pipelines or data duplication ↳ Query Postgres, MongoDB, REST APIs, and more using consistent SQL ↳ JOIN across different sources in real-time with a unified interface ↳ Works with both structured and un-structured data And here's the best part: You don't even need to write SQL. Just describe what you want in plain English, and MindsDB converts it to SQL automatically. The system does all the heavy lifting. The breakthrough for AI agents is simple: When data updates at the source, your agent gets fresh results immediately. No sync delays. No stale embeddings. No custom code for each integration. You can literally write a SQL query that joins a Postgres table with a MongoDB collection and gets live results. This is what production AI applications need but rarely get. In this video, I give you a complete walkthrough of what we just discussed and how to actually do it. Make sure you watch this till the end. I've shared the link to MindsDB's GitHub repo in the next tweet!

Your agents can't keep up with real-time data. Especially when it's scattered across dozens of sources. Most teams waste weeks building custom connectors for every database, API, and data warehouse. Then they build ETL pipelines to sync everything. By the time your agent retrieves the data, it's already outdated. Picture this: Your Postgres database updated 5 minutes ago. Your MongoDB collection changed 2 minutes ago. Your agent is still pulling from yesterday's snapshot. This is why most production RAG systems fail. There's a better approach: MindsDB is an open-source AI platform with a federated data engine that lets you query multiple data sources in real-time using SQL - without moving any data. Here's what makes it different: ↳ Your data stays in place. No ETL pipelines or data duplication ↳ Query Postgres, MongoDB, REST APIs, and more using consistent SQL ↳ JOIN across different sources in real-time with a unified interface ↳ Works with both structured and un-structured data And here's the best part: You don't even need to write SQL. Just describe what you want in plain English, and MindsDB converts it to SQL automatically. The system does all the heavy lifting. The breakthrough for AI agents is simple: When data updates at the source, your agent gets fresh results immediately. No sync delays. No stale embeddings. No custom code for each integration. You can literally write a SQL query that joins a Postgres table with a MongoDB collection and gets live results. This is what production AI applications need but rarely get. In this video, I give you a complete walkthrough of what we just discussed and how to actually do it. Make sure you watch this till the end. I've shared the link to MindsDB's GitHub repo in the next tweet!

Akshay 🚀

65,672 views • 10 months ago

We're excited to introduce NEAR AI Private Chat to the HOL Registry. Starting today, you can: → Discover and chat with Near models using our Registry Broker → Utilize Near Models within the Hashnet MCP Server Private Chat ensures your data is secured in TEEs ↓

We're excited to introduce NEAR AI Private Chat to the HOL Registry. Starting today, you can: → Discover and chat with Near models using our Registry Broker → Utilize Near Models within the Hashnet MCP Server Private Chat ensures your data is secured in TEEs ↓

HOL

11,906 views • 9 months ago

Today, CranL is bringing Supabase and Convex to Saudi Arabia🇸🇦! Introducing: CranL BaaS—The cheapest, easiest, smoothest way to deploy your Backend service in any region you choose. Included in your plan, with no extra fees Full data residency Fully managed by CranL

Today, CranL is bringing Supabase and Convex to Saudi Arabia🇸🇦! Introducing: CranL BaaS—The cheapest, easiest, smoothest way to deploy your Backend service in any region you choose. Included in your plan, with no extra fees Full data residency Fully managed by CranL

CranL

257,813 views • 1 month ago

Just Use Postgres feat. Denis Magda Denis literally just published a book called “Just Use Postgres”. In this conversation, that turned out to be super fun, we talked about: • what MySQL got wrong w.r.t community • the recent explosion of Postgres development in the world (Supabase, Neon, Crunchy, ClickHouse) • when Postgres instead of Kafka • the significance of the meme “just use postgres” • Postgres for data analytics Chapters (00:00) Intro (04:26) The Just Use Postgres Movement (08:36) The Small Data Trend and Its Implications (15:49) The Shift from Distributed Systems to Simplicity (17:15) Updating your priors re: PG capabilities (20:28) MySQL's OSS community split & our experiences with such things (39:48) Postgres for Analytics (55:49) PG in the lake house (59:27) AI Marketing Slop (01:02:19) How you'd build a brand new app on Postgres (01:05:24) Speedrun through PG extensions (01:11:56) PG as a Message Queue

Stanislav Kozlovski

13,036 views • 7 months ago

As part of our walkthrough series, today we are covering labor in the physical AI era—why real robots and real jobs hinge on grounded data, human judgment, and a pipeline from capture to delivery, not simulation alone. If you’re following Harbor or the future of work in AI, this one connects the dots in a few minutes.

As part of our walkthrough series, today we are covering labor in the physical AI era—why real robots and real jobs hinge on grounded data, human judgment, and a pipeline from capture to delivery, not simulation alone. If you’re following Harbor or the future of work in AI, this one connects the dots in a few minutes.

Harbor ML

13,472 views • 4 months ago

Today we're announcing that hybrid agentic inference is coming to Perplexity Computer. Computer can split tasks between a local model running on your machine and frontier models in the cloud. This keeps private data on your device and maximizes token efficiency. Coming soon.

Today we're announcing that hybrid agentic inference is coming to Perplexity Computer. Computer can split tasks between a local model running on your machine and frontier models in the cloud. This keeps private data on your device and maximizes token efficiency. Coming soon.

Perplexity

353,867 views • 3 months ago

Your Postgres is 100x slower than traditional OLAP engines. A deceptively simple OSS extension fixes this. Here's an interview where we dive into the deep engineering around how this is achieved. Joining me (and leading the conversation) is Marco Slot: an engineer with an EXTENSIVE and impressive career history around PostgreSQL: 👉 Created pg_cron in 2017 (3.7k stars) - a tool to run cron-jobs in Postgres 👉 Built pg_incremental - fast, reliable, incremental batch processing inside PostgreSQL itself 👉 co-created pg_lake (after working on Crunchy Data's Warehouse, and getting acquired into Snowflake) 👉 Helped get pg_documentdb (MongoDB-on-Postgres) off the ground Marco Slot is a world-class expert in Postgres extensions. He seriously impressed me with his knowledge over the course of a private LinkedIn conversation, and now that I type out his resume - I understand where it came from. He should be on everyone's radar. So I brought him on the pod. In our full 2-hour deep-dive, we went over: • 🔥 how pg_lake makes analytics 100x faster (literally) • 🔥 perf internals like vectorized execution & CPU branching • 🤔 practical differences between OLTP and OLAP database development (and the age-old mission in uniting both) • 🤔 how (and why) pg_lake intercepts query plans and delegates parts of the query tree to DuckDB • 💡 why Postgres is architecturally terrible at analytical queries (and how vectorized execution fixes this) • 💡 Marco's hard-won experience through a decade+ career in Postgres • 🏆 Iceberg's role as the TCP/IP for tables • 🏆 what the real moat of PostgreSQL is Developments like pg_lake are a real reason why "Just Use Postgres" is much more than a meme, and it'll continue to dominate discourse. I promise you will learn a lot from this episode. Timestamps: (0:02) What is pg_lake? (2:23) Postgres' 100x slower problem and columnar storage experiments they had to make Postgres fast for analytics (6:00) practical examples and internals (16:20) perf internals - vectorized execution & CPU optimization (23:00) pg_lake architecture (why DuckDB isn't embedded) and the connection-per-process issue (29:16) how pg_lake intercepts the query plan tree and delegates parts to DuckDB (41:09) Iceberg catalogs (48:24) postgres to iceberg ingestion patterns (and pg_incremental) (53:40) Marco's (long) career: early AWS, Citus, Microsoft, Crunchy Data & Snowflake (1:04:20) Marco's observations around the merging between OLTP and OLAP (and the subtle dev differences there) (1:15:30) reverse ETL (1:33:08) Iceberg as the TCP/IP for tables (1:35:00) Marco's thoughts on the "Just Use Postgres" fever

Your Postgres is 100x slower than traditional OLAP engines. A deceptively simple OSS extension fixes this. Here's an interview where we dive into the deep engineering around how this is achieved. Joining me (and leading the conversation) is Marco Slot: an engineer with an EXTENSIVE and impressive career history around PostgreSQL: 👉 Created pg_cron in 2017 (3.7k stars) - a tool to run cron-jobs in Postgres 👉 Built pg_incremental - fast, reliable, incremental batch processing inside PostgreSQL itself 👉 co-created pg_lake (after working on Crunchy Data's Warehouse, and getting acquired into Snowflake) 👉 Helped get pg_documentdb (MongoDB-on-Postgres) off the ground Marco Slot is a world-class expert in Postgres extensions. He seriously impressed me with his knowledge over the course of a private LinkedIn conversation, and now that I type out his resume - I understand where it came from. He should be on everyone's radar. So I brought him on the pod. In our full 2-hour deep-dive, we went over: • 🔥 how pg_lake makes analytics 100x faster (literally) • 🔥 perf internals like vectorized execution & CPU branching • 🤔 practical differences between OLTP and OLAP database development (and the age-old mission in uniting both) • 🤔 how (and why) pg_lake intercepts query plans and delegates parts of the query tree to DuckDB • 💡 why Postgres is architecturally terrible at analytical queries (and how vectorized execution fixes this) • 💡 Marco's hard-won experience through a decade+ career in Postgres • 🏆 Iceberg's role as the TCP/IP for tables • 🏆 what the real moat of PostgreSQL is Developments like pg_lake are a real reason why "Just Use Postgres" is much more than a meme, and it'll continue to dominate discourse. I promise you will learn a lot from this episode. Timestamps: (0:02) What is pg_lake? (2:23) Postgres' 100x slower problem and columnar storage experiments they had to make Postgres fast for analytics (6:00) practical examples and internals (16:20) perf internals - vectorized execution & CPU optimization (23:00) pg_lake architecture (why DuckDB isn't embedded) and the connection-per-process issue (29:16) how pg_lake intercepts the query plan tree and delegates parts to DuckDB (41:09) Iceberg catalogs (48:24) postgres to iceberg ingestion patterns (and pg_incremental) (53:40) Marco's (long) career: early AWS, Citus, Microsoft, Crunchy Data & Snowflake (1:04:20) Marco's observations around the merging between OLTP and OLAP (and the subtle dev differences there) (1:15:30) reverse ETL (1:33:08) Iceberg as the TCP/IP for tables (1:35:00) Marco's thoughts on the "Just Use Postgres" fever

Stanislav Kozlovski

16,857 views • 5 months ago

For you, your friends and family.😊 The KFC Big Six offer is the real deal. Available at a KFC near you only via the KIOSKS. Order today. Limited time offer.

For you, your friends and family.😊 The KFC Big Six offer is the real deal. Available at a KFC near you only via the KIOSKS. Order today. Limited time offer.

KFC Uganda

234,227 views • 1 month ago

Supabase (YC S20) is one of the fastest-growing developer platforms in the world, with more than 10 million developers using it. As AI coding agents like Claude Code, Lovable, Bolt, and Codex have taken off, they've become the backend powering millions of AI-generated apps. At Startup School Paris, Supabase co-founder and CEO Paul Copplestone (Paul Copplestone - e/postgres) sat down with YC's Nicolas Dessaigne to discuss why AI coding agents have changed the way developers build software, how open source helped Supabase compete with the cloud giants, and why the next frontier is self-driving databases. 00:56 — Paul's Origin Story 02:13 — Two Failed Startups First 04:12 — Why Postgres? Why Open Source? 07:11 — The Pivot That Actually Worked 08:03 — Targeting YC Startups from Day One 09:45 — Fully Open Source — The Risky Choice 12:04 — Winning Developer Trust 13:33 — Time to Value: 8 Minutes → 5 Seconds 15:45 — The AI Second Life Begins 17:48 — Supabase for Platforms 19:09 — Everything Going Up Into the Right 20:44 — When Agents Became the Users 22:26 — Advice for Founders Building Dev Tools Today 23:47 — Why Open Source Won the LLM Era 25:32 — $500M Round, $10B Valuation 26:01 — What Keeps a Founder Grounded 28:31 — 360 People, 60 Countries, Zero Offices

Supabase (YC S20) is one of the fastest-growing developer platforms in the world, with more than 10 million developers using it. As AI coding agents like Claude Code, Lovable, Bolt, and Codex have taken off, they've become the backend powering millions of AI-generated apps. At Startup School Paris, Supabase co-founder and CEO Paul Copplestone (Paul Copplestone - e/postgres) sat down with YC's Nicolas Dessaigne to discuss why AI coding agents have changed the way developers build software, how open source helped Supabase compete with the cloud giants, and why the next frontier is self-driving databases. 00:56 — Paul's Origin Story 02:13 — Two Failed Startups First 04:12 — Why Postgres? Why Open Source? 07:11 — The Pivot That Actually Worked 08:03 — Targeting YC Startups from Day One 09:45 — Fully Open Source — The Risky Choice 12:04 — Winning Developer Trust 13:33 — Time to Value: 8 Minutes → 5 Seconds 15:45 — The AI Second Life Begins 17:48 — Supabase for Platforms 19:09 — Everything Going Up Into the Right 20:44 — When Agents Became the Users 22:26 — Advice for Founders Building Dev Tools Today 23:47 — Why Open Source Won the LLM Era 25:32 — $500M Round, $10B Valuation 26:01 — What Keeps a Founder Grounded 28:31 — 360 People, 60 Countries, Zero Offices

Y Combinator

56,760 views • 1 month ago