Service Responsibilities

Gnok operates the infrastructure and services that support your workspace. Your team controls the workspace's users, data, and workloads through Studio and authorized client endpoints.

Area	Customer responsibility	Gnok service responsibility
Account access	Add authorized members, assign roles, keep second factors and recovery codes safe	Operate sign-in, signup, and workspace services
Data	Choose datasets, privileges, retention actions, and sharing audiences	Operate the service's query and catalog infrastructure
Workloads	Review SQL, select available compute, monitor usage	Operate and maintain supported execution services
External integrations	Authorize data egress, provide approved resources and access	Configure and operate supported service-side integrations
Incidents	Supply an error reference, timestamp, and reproducible description	Investigate service-side failures

Availability and account limits

The SQL reference describes supported interfaces, not an entitlement to every feature or endpoint. Use the features and limits enabled for your account. Your plan's limits are listed in Limited Availability; every new workspace starts with a trial, online payment isn't available yet, there is no service-level agreement during the preview, Gnok runs in one region (AWS us-east-1), and retention is described in the Privacy Policy. Implementation defaults are not plan promises.

Requesting assistance

Email support@gnok.com. Include your workspace's sign-in name, the operation, time and time zone, and a query ID or error reference. Share only the minimal sanitized SQL and metadata needed to reproduce the problem. Never include passwords, tokens, or private keys.

See Studio administration for customer controls and troubleshooting for recovery steps.