Pluggable engine architecture
SQLWorkspace is designed around a pluggable engine architecture. During Private Preview, every workspace uses RisingWave. You cannot currently select or replace the engine. RisingWave provides PostgreSQL-compatible SQL and continuously maintained materialized views. StreamNative manages its deployment, its metadata store, its object storage, and its connections to your SQLCatalog resources. During Private Preview, SQLWorkspace engine infrastructure is supported only on AWS. Other cloud providers are not currently supported.What a workspace contains
A SQLWorkspace contains:- One managed SQLWorkspace engine.
- Zero or more SQLCatalog databases.
- Managed source objects created for eligible topics within those databases.
- SQL Studio and native PostgreSQL query paths.
Placement
When you create a workspace, select an eligible AWS hosted location or ready AWS BYOC Cloud Environment. The Cloud Console displays only placements available to your organization during Private Preview.Lifecycle
A workspace must reach Ready before you can open SQL Studio, connect through the native endpoint, or use its catalogs. You can add SQLCatalogs during creation or after the workspace is ready. Before deleting a workspace, remove its SQLCatalog resources. Deleting a workspace removes the managed SQL runtime and makes its query endpoints unavailable, but engine metadata and object-storage data are retained by default. It does not delete any connected Pulsar or Kafka cluster. See Data Retention.Access
Cloud roles control who can manage the SQLWorkspace resource. Engine permissions control what a user can do inside the workspace. During Private Preview, Organization Admin users (org-admin, or legacy admin) are synchronized as engine superusers.
For details, see Access control overview.