Today, we are releasing RisingWave Cloud V2 into Public Preview.
V2 is a ground-up rewrite of the Cloud control plane and UI. It ships three things at once: a redesigned console, a new CLI called rwc, and native AI agent support through the RisingWave Skill and MCP server. They are separate pieces, but they are built around a single idea.
The Idea
The way developers build and operate data systems is changing. Two years ago, if you wanted to set up a streaming pipeline, you would open documentation, copy SQL, debug in the console, and iterate manually. That workflow still works. But increasingly, developers are doing this work alongside AI coding agents — asking Claude Code or Cursor or Copilot to help write queries, inspect schemas, and configure connectors.
We built V2 around a bet: in the agentic era, a cloud data platform needs to be drivable from three surfaces — the browser, the terminal, and an AI coding agent. Not as an afterthought, but as a first-class design constraint.
That is what V2 delivers.
The Console
The new console is a clean, modern redesign of the management UI. SQL Console, Data Catalog, Connect, Backup, and Metrics are all there — what changed is the shape.
The design is deliberately oriented toward coding. Cleaner information architecture. Readable layouts. Surfaces that work alongside a terminal and an editor, not instead of them.
The Classic UI remains one click away. We are not forcing a migration. But the new console is where V2 is going, and the direction it reflects — building a UI optimized for developers who live in their tools — is intentional.
rwc — The RisingWave Cloud CLI
rwc is a new command-line tool for operating RisingWave Cloud without the browser.
# Authenticate
rwc auth config --api-key '<KEY>' --api-key-secret '<SECRET>'
# List clusters
rwc cluster list
# Install the RisingWave Skill into Claude Code
rwc skill install --target claude-code
The first two commands give you cluster lifecycle management from the terminal — scriptable, CI-friendly, composable with the rest of your toolchain. Cluster setup belongs in a Makefile or a GitHub Action, not a sequence of browser clicks.
The third command is different. rwc skill install drops the RisingWave Skill directly into your local AI tool configuration. It is how the CLI connects to the agent layer.
Full reference: docs.risingwave.com/cloud/install-cli
RisingWave Skill and MCP Server
These are the two open-source building blocks for AI-native development with RisingWave.
RisingWave Skill is a structured knowledge reference for AI coding agents, published at github.com/risingwavelabs/agent-skills. It ships two packages: risingwave (connections, the Source → Materialized View → Sink pipeline, CDC ingestion, time-windowed aggregations) and risingwave-best-practices (14 rules across schema design, materialized views, streaming SQL patterns, sink configuration, and performance tuning). Compatible with Claude Code, Cursor, GitHub Copilot, Windsurf, Gemini CLI, and 18+ other agents.
Install with one command:
npx skills add risingwavelabs/agent-skills
Or via the rwc CLI if you are already authenticated with RisingWave Cloud:
rwc skill install --target claude-code
Why does this matter? Streaming SQL has sharp edges that batch SQL does not. The difference between CREATE TABLE and CREATE SOURCE, the role of watermarks in windowed aggregations, the state implications of certain join patterns — these are the things that separate SQL that runs from SQL that runs correctly in production. The Skill exists to give agents that knowledge before they write a line of SQL.
RisingWave MCP Server exposes over 100 tools for query execution, schema inspection, DDL operations, job monitoring, and cluster management. Agents that connect through MCP see your actual schemas and running jobs — not hallucinated ones. The server is open source and works with VS Code Copilot and Claude Desktop today. Available at github.com/risingwavelabs/risingwave-mcp.
Public Preview
Public Preview is open to everyone. No waitlist.
This is the first version of Cloud designed for the agentic era, not adapted to it. We expect to learn a lot from how developers actually use these three surfaces together — what works, what is missing, what needs to change.
If you find a bug or have feedback: reply to this post, open an issue on GitHub, or join us on Slack.
Yingjun Wu is the co-founder and CEO of RisingWave Labs.
