Kaveon Studio
The governed workspace for asking questions, writing SQL, defining semantic datasets, building charts, and publishing dashboards.
Studio is the user-facing surface of Kaveon. It authenticates the user, sends trusted requests through the platform proxy, and presents results from the KaveonDB transactional plane, the distributed Engine, or a deterministic DLM context artifact. Hosting is portable: Studio can run on Vercel or as a container in the same AKS or VM deployment as the API and Engine.
Choose the surface
| Surface | Use it for | Guide |
|---|---|---|
| Chat | Ask a governed natural-language question and inspect whether the answer came from context or a live query. | Data Language Model |
| SQL Lab | Write SQL, inspect results, cancel work, save statements, and review query details. | SQL Lab |
| Catalog | Browse catalogs, schemas, columns, file locations, statistics, and table details. | Storage & Catalogs |
| Datasets | Declare dimensions, measures, time columns, and freshness semantics once. | Semantic Datasets |
| Charts | Turn a dataset query into a reusable visualization with filters and formatting. | Chart Builder |
| Dashboards | Compose charts into a shareable, filterable analytical canvas. | Dashboards |
| Settings | Manage identity, catalog access, storage connections, governance, and runtime status. | Auth & RBAC |
One governed request path
The browser session never supplies trusted identity headers. Studio resolves the authenticated session server-side, calls the API through /api/kaveon/*, and the proxy stamps the verified principal before the API routes work to KaveonDB, the DLM, or the Engine. The same contract works when Studio is hosted by Vercel or by the AKS portal chart.
Deploy Studio
For a five-minute local run, use Quickstart. For Vercel, AKS, or a Linux VM, follow Install & deploy, then verify the request path inDeployment topology and Operations.