RisingWave Console Overview

Learn what RisingWave Console is, when to use the built-in RisingWave Dashboard instead, and what capabilities RisingWave Console provides for operating RisingWave clusters.

RisingWave includes a built-in web UI, the RisingWave Dashboard, which is served by the meta node on port 5691 by default. If you start RisingWave with an official Docker or standalone configuration that exposes port 5691, open http://localhost:5691 in your browser to access it. For more details, see Monitor a RisingWave cluster.

RisingWave Console is a separate self-hosted operations console from RisingWave Labs. It is designed for teams that need additional operational workflows for managing RisingWave environments and clusters.

To obtain RisingWave Console, contact RisingWave Labs at [e-mail].

Key features

RisingWave Console provides:

• Kubernetes environment management: Install supporting services with one-click workflows and manage RisingWave environments from a central UI.
• Cluster lifecycle operations: Create and operate managed RisingWave clusters, or connect existing clusters for day-2 operations.
• Operational tooling: Run risectl commands, create metadata snapshots, and collect diagnostic data for troubleshooting.
• SQL Console: Browse schemas, run SQL in the browser, track DDL progress, and inspect the streaming graph.
• Metrics integration: Register metrics stores and use them with managed environments and clusters.

Who is this for?

This documentation is for DevOps engineers, Site Reliability Engineers (SREs), database administrators, and RisingWave users who are responsible for operating, monitoring, and managing self-hosted or Kubernetes-based RisingWave deployments.

Getting access and support

For access to RisingWave Console or product-related questions, contact RisingWave Labs at [e-mail].