Explore with Kubling Studio
Kubling Studio is the embedded workspace for exploring, querying and operating a running Kubling instance. It is not a mutable data-source configuration wizard: providers and production VDB definitions remain version-controlled deployment artifacts.
Embedded Studio is served from /console when ENABLE_WEB_CONSOLE is
enabled. Protect it with the same network, TLS and identity controls used for
the instance HTTP APIs.
First exploration
Open Studio
In the Quickstart, open
http://localhost:8282/console and enter
quickstart as both username and password. The values only satisfy the local
login form; the sample VDB has no authentication delegate and does not persist
them.
Select the Virtual Database
Choose ProviderQuickstartVDB. Studio loads its live catalog from Kubling and
shows the physical provider schema imported through the Provider gRPC
contract.
Inspect the catalog
Expand provider and inspect the PROJECT, TASK, AUDIT_EVENT and
TYPE_SAMPLE tables. Schema DDL inspection shows keys, types, mutability and
annotations reported by the provider.
Use SQL Workspace
SQL Workspace provides catalog-aware completion, query history, dynamic result grids and mutation feedback. Follow the Quickstart’s deterministic query and mutation to exercise both read and write paths against the In-memory provider.
Semantics preview v26.5+
When the selected VDB has an active semantic package, the Semantics workspace lets you inspect the compiled result rather than reconstruct it from source files. It includes:
- package and activation overview
- entities, properties and identities
- relationships and executable bindings
- an interactive relationship graph
- diagnostics and the normalized JSON document
The workspace is read-only. Provider fragments, authored modules and VDB composition remain version-controlled deployment artifacts.
catalogOnly means that the VDB is active without a compiled semantic package.
An invalid state exposes diagnostics rather than presenting a partial graph as
usable. See Semantics for bootstrap, composition and failure
policy.
Investigations preview v26.5+
Studio contains an Investigations workspace for the investigation capability,
but it remains disabled. Kubling does not yet expose a read-only runtime-readiness
endpoint that Studio can use to distinguish an available task runtime from a
configured but unreachable one.
The authenticated Task API is the executable interface. It runs synchronously and returns a terminal snapshot. Closing the browser or aborting the HTTP request is not a public task-cancellation operation.
Investigation history in Studio is browser-local presentation state, not a durable task store. The UI can be enabled after the readiness contract is available without changing the public Task API.
Other Studio surfaces
| Surface | What it shows |
|---|---|
| Catalog | VDBs, schemas, tables, columns and provider-reported DDL. |
| Semantics | Compiled entities, relationships, bindings, graph and diagnostics. |
| Investigations | Preview workspace, currently disabled pending a safe runtime-readiness signal. |
| Activity | Live engine, worker-pool, request and session information. |
| Schedules | Configured scheduled JavaScript tasks and their source. |
| Functions | Built-in and module-provided SQL and template functions. |
| Endpoints | Query and action templates plus JavaScript endpoint routes. |
| Modules | Installed JavaScript module-backed data sources and metadata. |
These views describe the selected Kubling instance. They do not replace version-controlled provider configuration, application configuration or VDB descriptors.
Next steps
- Choose a provider for a real source.
- Register a provider in a VDB.
- Compose a semantic model for a federated VDB.
- Configure investigation tasks.
- Review HTTP security before exposing Studio outside a trusted local environment.