# Go-live requirements

Use this page as the go-live requirements checklist for Syntho. Items labelled with a ⏰ icon usually take most time, start them as early as possible. Appoint a single accountable implementation lead to oversee and coordinate all implementation activities end-to-end, including onboarding, architecture, infrastructure, security, DevOps, database access, compliance, approval processes, and use-case prioritization.

{% hint style="info" %}
The Implementation Statement of Work Status Tracker contains the full list and latest status.
{% endhint %}

***

### A - Scoping & success

* [ ] Top 3–5 prioritized use cases identified (including database(s)/schema(s)). Usually more time consuming for non TDM use-cases ⏰
* [ ] Priority use case(s) selected
* [ ] Use-case execution order defined
* [ ] 1–3 super users assigned
* [ ] Super users are available 2–3 days per week during onboarding
* [ ] Super users are comfortable with database concepts (tables, permissions, referential integrity)
* [ ] If you use AI-powered generation a super user can prepare an [entity table](/configure-a-data-generation-job/configure-column-settings/ai-powered-generation.md#entity-tables) if needed

***

### B - Architecture & data flow

* [ ] Onboarding procedure approvals completed (as applicable) ⏰
  * [ ] InfoSec review
  * [ ] Vendor risk / procurement intake
  * [ ] Privacy officer / board approval
  * [ ] AI review (if applicable)
* [ ] Architecture defined, documented and approved ⏰
  * [ ] Network zone placement decided
  * [ ] Intended data flow documented (production → source → Syntho → destination)
  * [ ] Security requirements agreed
  * [ ] Architecture diagram available
* [ ] Data governance plan defined (if needed)
  * [ ] Data access model and approvals documented
  * [ ] Audit/compliance requirements documented
  * [ ] Data retention policy documented

***

### C - Deployment, databases & users

#### C-1 - Deployment

* [ ] Deployment method selected: [Docker Compose](/deploy-syntho/deploy-syntho-using-docker.md) or [Kubernetes (Helm)](/deploy-syntho/deploy-syntho-using-kubernetes.md)
* [ ] Deployment prerequisites met
  * Docker Compose: [Prerequisites](/deploy-syntho/deploy-syntho-using-docker/prerequisites.md)
  * Kubernetes (Helm): [Prerequisites](/deploy-syntho/deploy-syntho-using-kubernetes/prerequisites.md)
* [ ] Hardware sizing confirmed: [Deployment overview](/deploy-syntho/introduction.md)
* [ ] Registry access works (client can authenticate and pull images)
* [ ] If required, outbound access to `syntho.azurecr.io` is whitelisted (or images are mirrored to a local registry)
* [ ] License key received and available for deployment
* [ ] Deployment instructions received (and shared with the deployment team) ([Docker Compose](/deploy-syntho/deploy-syntho-using-docker.md), [Kubernetes (Helm)](/deploy-syntho/deploy-syntho-using-kubernetes.md))
* [ ] Infrastructure provisioned (compute, storage, networking, DNS as needed) ⏰
* [ ] Infrastructure readiness confirmed (required compute/storage available, DNS prepared if used)
* [ ] Syntho deployed and reachable by intended users
* [ ] UI reachable over HTTP(S). DNS/TLS and ingress/proxy posture defined (if applicable) ⏰
* [ ] If using DNS/TLS, hostname resolves and HTTPS works without browser warnings
* [ ] Deployment validated (UI loads, admin login works, Ray dashboard visible, logs clean) (see [Logs and monitoring](/deploy-syntho/logs-and-monitoring.md) and troubleshooting: [Docker Compose](/deploy-syntho/deploy-syntho-using-docker/troubleshooting.md), [Kubernetes](/deploy-syntho/deploy-syntho-using-kubernetes/troubleshooting.md))
* [ ] Backups confirmed functional (policy defined + restore tested):
  * Docker Compose: [Back up PostgreSQL](/deploy-syntho/deploy-syntho-using-docker/back-up-postgresql.md)
  * Kubernetes: [Back up PostgreSQL](/deploy-syntho/deploy-syntho-using-kubernetes/back-up-postgresql.md)

#### C-2 - Databases

* [ ] Data owner(s) identified for the priority use-case dataset/database
* [ ] Source and destination access request process started (firewall/proxy rules, permissions) ⏰
* [ ] Source database prepared for read-only access (database needs to be static during data generation, use a consistent snapshot) ⏰
* [ ] Destination database prepared for writing synthetic data (schema aligned) ⏰
* [ ] Source DB connectivity + read-only permissions validated ([Step 1. Validate source db](/configure-a-data-generation-job/generation-and-validation/validate-and-synchronize-workspace.md), [Connect to a database](/setup-workspaces/create-a-workspace/connect-to-a-database.md))
* [ ] Destination DB connectivity + write/truncate permissions validated ([Step 2. Validate destination db](/configure-a-data-generation-job/generation-and-validation/validate-and-synchronize-workspace-1.md), [Connect to a database](/setup-workspaces/create-a-workspace/connect-to-a-database.md))
* [ ] First end-to-end data generation job completed successfully

#### C-3 - Users

* [ ] Admin user exists: [Manage admin users](/deploy-syntho/manage-users-and-access/manage-admin-users.md)
* [ ] Non-admin users provisioned (Owner/Editor/Reader): [Manage non-admin users](/deploy-syntho/manage-users-and-access/manage-non-admin-users.md)
* [ ] If using SSO, configured and tested: [Single Sign-On (SSO) in Azure](/deploy-syntho/manage-users-and-access/single-sign-on-sso-in-azure.md) ⏰
* [ ] Database users created for Super Users (source read-only, destination write, alter & truncate) ⏰
* [ ] Super User credentials shared securely (platform + database)
* [ ] Super Users can log in and complete the full flow without errors
  * [ ] Connect source and destination ([Connect to a database](/setup-workspaces/create-a-workspace/connect-to-a-database.md))
  * [ ] Create a workspace ([Create a workspace](/setup-workspaces/create-a-workspace.md))
  * [ ] Validate source and destination ([Step 1. Validate source db](/configure-a-data-generation-job/generation-and-validation/validate-and-synchronize-workspace.md), [Step 2. Validate destination db](/configure-a-data-generation-job/generation-and-validation/validate-and-synchronize-workspace-1.md))
  * [ ] Run a generation job end-to-end ([Step 3. Generate](/configure-a-data-generation-job/generation-and-validation/view-and-adjust-generation-settings.md))


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.syntho.ai/overview/get-started/prerequisites.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.