#Work from question to trusted result
JustyBase is a multi-database SQL workspace for VS Code. It combines a parser-backed editor, schema intelligence, operational tools, and a result explorer so the database context stays close to the work.
This portal is the canonical product documentation. The reference catalog is generated from the current extension manifest and the database matrix is the place to check dialect boundaries. Pages labelled Desktop only, Web only, Read-only, Partial, or Preview are deliberate product boundaries, not promises of identical behavior everywhere.
#Six workflows worth starting with
| If you need to… | Start here |
|---|---|
| Understand why the editor catches a problem before execution | Parser, LSP and SQL Editor |
| Review safety, correctness, performance, and type warnings | SQL quality and diagnostics |
| Explore a large result without losing control of the data boundary | Data Grid and Result Exploration |
| Move data between files and databases | Import and export |
| Find an object or a column across a warehouse | Schema Search |
| Use AI while keeping execution and privacy explicit | AI SQL Assistant |
#Choose your route
#New to JustyBase
Read Getting started, save a connection, open the Schema Browser, and run the small query from that page. Then use Connections to understand active database context per tab.
#Moving from another SQL client
The product guides cover the workflows that are easy to miss in a feature list: metadata refresh and Schema Refresh Details, result-set persistence, all-rows filtering, staged imports, query history, DDL, and maintenance.
#Running the Web Editor
Administrators should start with Web Editor and Deployment and security. The Web Editor shares parser contracts and result-session concepts with the desktop extension, but it is a separate server with its own authentication and session lifecycle.
#Extending JustyBase
The developer guide explains the boundaries between contracts, SQL core, runtime, desktop, API, and web. Testing and documentation describes the checks expected when a capability changes.
#Status vocabulary
Supported means the workflow is implemented and covered by the current product surface. Partial means the main path exists but the dialect or platform has a stated limitation. Preview marks a capability that may change. Read-only means the feature intentionally does not write data. Desktop only and Web only identify platform-specific surfaces. See Statuses and permissions for the full legend.
#Version and evidence
This portal was verified against product version 3.16.38 on 2026-08-19. Generated command, setting, database, AI-tool, MCP, format, and Web API tables are derived from repository sources during the Pages build. The build also publishes machine-readable build metadata with the source commit and generated counts. Narrative pages still require human review when behavior changes.