Prerequisites
Requirements before deploying the Scrydon platform
Use this page to see what must be ready at each point in deployment. The table below separates install blockers from bundled defaults and post-install configuration.
| Timing | What it means |
|---|---|
| Before Helm | Required before helm install can succeed. |
| Before setup | Required to activate the installed platform in /setup. |
| Included | The chart ships a working default. Only prepare an external service if you want to replace it. |
| Before use | Not needed for the chart install, but needed before the related product capability is useful in production. |
1. Kubernetes Cluster
You bring the cluster and the capacity. Scrydon cannot install anything until these are in place.
| Area | Timing | Why it matters |
|---|---|---|
| Kubernetes | Before Helm | The chart needs Kubernetes 1.28+, Helm 3.14+, and permissions to create workload, service, ingress, config, and secret resources. |
| Resources | Before Helm | The default stack needs enough CPU, memory, disk, and rollout headroom for pods to schedule and start reliably. |
2. Network Entry
You bring the route users will take into the cluster. Scrydon can render Ingress objects, but it cannot own your DNS zone or certificate authority.
| Area | Timing | Why it matters |
|---|---|---|
| DNS | Before Helm | The public or private hostname must point at the ingress before browser traffic and ACME validation can work. |
| TLS | Before Helm | Choose cert-manager, internal ACME, BYO certificates, or upstream TLS termination before exposing the platform. |
3. Scrydon Access
These are supplied by Scrydon, but they block different moments.
| Area | Timing | Why it matters |
|---|---|---|
| Registry | Before Helm | Helm and Kubernetes need the customer-scoped ACR credential to pull the private chart and images. |
| License | Before setup | The installed platform needs the { jwt, publicKey } bundle before /setup can activate the deployment. |
4. Defaults You Can Accept
These are not prerequisites unless you choose to replace the bundled defaults.
| Area | Timing | What to decide |
|---|---|---|
| Dapr | Included | Use the bundled Dapr control plane, or pre-install an operator-managed Dapr control plane. |
| PostgreSQL | Included | Use bundled PostgreSQL 18 + pgvector, or pre-provision managed Postgres databases. |
5. Configure Before Real Use
These do not block the Helm install. They matter when you want users to actually use the product.
| Area | Timing | Why it matters |
|---|---|---|
| AI Provider | Before use | AI-backed features have no model to call until an org admin connects a hosted or self-hosted provider. |
| Mail Provider | Before use | Production sign-up verification, invitations, and password resets need transactional email. Evaluation installs can skip it. |
Recommended order
- Prepare Kubernetes Cluster and Network Entry.
- Get the Scrydon Registry credential.
- Decide whether to accept the bundled Dapr and PostgreSQL defaults.
- Run the location-specific install guide.
- Use the License bundle in
/setup, then configure AI and mail before onboarding users.
Next step: Pick where you're deploying — On-Premise, Azure, or Air-Gapped — or go straight to the Helm reference.