Architecture Overview

Gnok separates the browser workspace, query execution, and table metadata. This overview helps you understand connections and diagnose failures; Gnok manages the underlying service components.

Studio

Studio is the browser interface for SQL worksheets, notebooks, saved queries, and other workspace tools. It submits queries using a selected connection. A browser page can load while a query dependency is unavailable, so distinguish sign-in failures from execution errors.

Query execution

The query service parses SQL, resolves metadata and permissions, plans execution, and returns results. Distributed execution and vectorized processing are service implementation details; customers choose supported workload settings rather than managing worker processes.

Catalog and storage

The catalog tracks objects, schemas, access policies, and Iceberg metadata. Query execution reads and commits table data through the configured storage and catalog paths. Model restoration and metadata commands also depend on catalog availability.

AI integrations

Native models execute within the service's supported runtimes. Remote models and provider-backed functions call configured endpoints. Availability, network access, your organization's AI Governance policy (budget, rollout, egress and retention approvals), and input/output contracts determine whether a particular integration can run. Do not assume all AI operations keep data inside Gnok.

Troubleshooting across components

Start with the failing operation, its query or error reference, the connection, and the time it occurred. Your administrator or Gnok support (support@gnok.io) can use these details to investigate service dependencies. See troubleshooting.