Connect an Application
Gnok Studio is the way to work with Gnok today: sign in and use SQL worksheets, notebooks, dashboards, and shared tutorials with nothing to install.
Connecting from outside Studio (JDBC, the Python SDK, Flight SQL, the PostgreSQL wire protocol, the HTTP API, or an external Iceberg engine) isn't self-service for new organizations yet. Email support@gnok.io to request client connectivity. Gnok support provides the endpoints, client packages, and credentials for your organization.
| Interface | Purpose | Guide |
|---|---|---|
| Studio | Browser workspace with a provisioned connection | Studio connections |
| Arrow Flight SQL | Columnar query results for applications and analytics | Flight SQL |
| PostgreSQL wire / JDBC | Compatible SQL and BI clients | PostgreSQL, JDBC |
| HTTPS query API | JSON requests from applications | HTTP API |
| Python | External scripts or the pre-installed notebook helper | Python SDK |
| Iceberg REST catalog | Authorized external engines accessing table metadata | Catalog integrations |
The Studio address, query API, Flight SQL endpoint, PostgreSQL endpoint, and Iceberg catalog URL serve different purposes. Don't substitute one for another or infer one from a browser address.
Example values
Hosts under example.com, <host> placeholders, and the variables that snippets read secrets from stand for the connection details Gnok support gives you. They are not Gnok service addresses. Port numbers in protocol examples illustrate a client configuration; use the port provided for your organization.
Use HTTPS or TLS and keep certificate verification on. Keep tokens and passwords out of saved SQL, shared links, screenshots, and source control; the examples read them from a variable in your own environment or secret manager.
Client packages
Use approved client packages and versions. Gnok support provides the Gnok-specific SDKs, JDBC drivers, and connectors, with installation instructions, when your client connectivity is set up. Inside a Studio notebook, the gnok Python helper is already installed.
Test access
Run SELECT 1 AS connected;, then a bounded query against an authorized table. A successful handshake checks connectivity, not access to every object. Check authentication and troubleshooting if either step fails.