Skip to main content

Quickstart

You need a web browser and an email address. Gnok runs as a hosted service: there is nothing to install, and Gnok manages the infrastructure, updates, and maintenance.

Create your organization​

  1. Open studio.gnok.io/login and choose New to gnok? Create an organization.
  2. Enter your Organization name, Email, Full name, Username, and a Password (at least 10 characters, with an uppercase letter, a lowercase letter, and a digit). Your organization name becomes its sign-in name: lowercase, with other characters replaced by _. For example, Acme Corp becomes acme_corp.
  3. Accept the Terms of Service and Privacy Policy, and submit.
  4. Open the verification email (the link is valid for 24 hours). In the browser you signed up in, the link verifies your email immediately. In another browser or on another device, choose Verify email and continue.
  5. Sign in at studio.gnok.io/login with your organization's sign-in name, your email, and your password.
  6. As the organization's administrator, set up a second factor the first time you sign in: a passkey, or an authenticator app. If you choose an authenticator app, save the recovery codes Gnok shows you.

Studio opens when you finish signing in. Bookmark https://studio.gnok.io/login?org=<organization> (for example ?org=acme_corp) to have your organization filled in next time.

If the email doesn't arrive, check your spam folder and choose Resend verification email on the confirmation page. Account access covers passkeys, recovery codes, forgotten passwords, and other sign-in problems.

Joining a team that already uses Gnok? Don't create a new organization. Ask your organization's administrator to add you, then sign in with your organization's sign-in name and your email.

Connect and query​

  1. Open the SQL editor in Studio.
  2. Select the Gnok connection provisioned for your organization, or another connection your administrator has provided. If the selector is empty, see connections.
  3. Open a new editor tab and run:
SELECT 1 AS connected;

The result should contain one row with connected = 1. This checks that your current session can execute SQL without needing a sample table.

Now run a small calculation:

SELECT 120 + 80 AS total_amount, 2 AS order_count;

Expect total_amount = 200 and order_count = 2. A working connection does not imply access to every catalog or table: the service checks your permissions for each operation.

Try a guided example​

In the SQL editor's sidebar, open the Saved tab and expand Shared with me. The AI & ML tutorials are listed there by name, such as Tutorial: Churn Prediction End-to-End; type tutorial in the search box to filter the list. AI tutorials need an organization administrator to enable AI Governance first. For a procedural example, download the Order Processing worksheet and paste it into a new editor tab; it shows a practical SQL workflow with expected outputs and rollback behavior.

Read the prerequisites and reset statements before choosing Run All. Tutorials create or replace named objects, so use a schema intended for experiments. AI features stay off until an organization administrator turns them on in Studio (Operations → AI Governance), and background workloads need additional permissions. Tutorial setup explains these requirements.

Inspect each statement's result. Use Save As… to keep your own copy of a shared tutorial. See shared tutorials and saved queries.

Use your own data​

Browse the Catalogs panel for objects visible to your account. Use fully qualified names such as catalog.schema.table. If you need to load a file, follow data exploration and uploads.

Next steps​

Last updated on