Data Streaming Summit 2026 — Registration is Open!
Register Now >Postgres-compatible SQL directly on your Kafka and Pulsar topics.
Query Kafka and Pulsar topics directly — no separate system.
Materialized views update as events arrive. No batch schedule.
psql, DBeaver, BI tools, and agent frameworks connect directly.
Query Kafka and Pulsar topics, build continuously updated materialized views, and serve real-time data to applications, BI tools, and AI agents — all with SQL.
• THE OBJECT MODEL
SQL Workspace, powered by the RisingWave SQL engine, organizes resources using concepts SQL users already know, while preserving what makes streaming valuable: continuous updates, low latency, and the ability to react as events arrive.
Connect to and read external data, including topics from associated Kafka and Pulsar clusters.
Persist current data and state for repeatable access.
Continuously transform incoming events and maintain up-to-date results as source data changes.
Send processed data to an external system or destination database.
• HOW IT WORKS
Poke at a topic in the browser editor, and when the query is right, leave it running for good — then serve the result to anything that speaks Postgres.

Connect one workspace to multiple clusters, discover streaming data as sources, and write SQL against topics and materialized views from a browser-based editor.
Inspect catalog resources without learning cluster-specific APIs
Filter, join, aggregate, and transform live event streams in SQL
A SQL statement can become a long-running process that continuously reads new events, applies business logic, and keeps a table or materialized view current — without scheduling batch jobs.
Move from exploration to production in the same language and workspace
Saved queries make transformations easier to review, reuse, and operate
Every SQL Workspace is a PostgreSQL-compatible endpoint. What the Kafka protocol did for streams, the Postgres protocol does for queries — if it speaks Postgres, it can query your streams.
Connect from psql, DBeaver, application frameworks, and BI tools
Most agent frameworks already speak Postgres
• USE CASES
Read order, payment, and fulfillment events from Kafka or Pulsar, join them into a materialized view that stays current, and write the result into a database table your customer-service applications already use.
Express detection logic once in SQL and let it run continuously against live event streams, so signals surface as events arrive rather than on the next batch window.
Maintain inventory, operational metrics, and customer profiles as materialized views — no connector infrastructure and no separate processing engine to operate.
Serve real-time context to agents over the PostgreSQL wire protocol, or retrieve it in natural language through Rio, the AI assistant built into StreamNative Cloud. Agents read the same governed data your applications do.
• SUCCESS STORIES
Organizations across industries use StreamNative as the foundation for real-time data, applications, and AI.
Not yet. SQL Workspace is currently in Private Preview, and Public Preview is coming soon. Contact the StreamNative team to request access.
SQL Workspace is powered by the RisingWave SQL engine. RisingWave provides the streaming SQL foundation for executing continuous queries and incrementally maintaining results as new events arrive, while StreamNative Cloud provides the integrated workspace experience and connectivity to Kafka and Pulsar clusters.
No. SQL Workspace presents Kafka and Pulsar topics directly as queryable sources. You can filter, join, aggregate, and transform live event streams without first copying them into a separate analytical system.
Every SQL Workspace is a PostgreSQL-compatible endpoint, so anything that speaks the PostgreSQL wire protocol can connect. Use psql, DBeaver, your BI tools, application frameworks, or most agent frameworks to query tables and continuously updated materialized views with familiar drivers.