AlchemiStudioAlchemiStudio
Skip to Content
SUSE AIDeploy on Rancher / RKE2Deploy paths

Deploy on Rancher Prime / RKE2

AlchemiStudio ships as a single umbrella Helm chart, alchemistudio-platform. One install stands up the full platform — data tier (pgvector PostgreSQL, Redis, APISIX + etcd, OpenObserve), the APISIX gateway, and the app tier (web, AI, compute, worker, zenith, guardrails). Keycloak provides SSO.

There are two supported paths on SUSE.

Path A — Rancher App (guided form)

The chart exposes a questions.yaml, so it installs through the Rancher UI › Apps form. A single domain input fans out to the APISIX routes, Keycloak hostnames, and OIDC redirect URIs — no manual URL wiring.

  1. In Rancher, add the AlchemiStudio Helm repository (OCI): <PUBLIC_HELM_REPO>/alchemistudio-platform (publisher-provided; see below).
  2. Apps › Charts › AlchemiStudio Platform › Install.
  3. Fill the guided form: domain, TLS mode (BYO / ACME / self-signed), storage class (longhorn), and which components to enable.
  4. Install into a dedicated namespace (e.g. alchemi).

Path B — SUSE AI Factory Blueprint

AlchemiStudio can be referenced as an AI Factory Blueprint and reconciled by Fleet GitOps onto RKE2 — this makes it appear as a card in the SUSE AI Factory catalog and keeps it in sync from Git. See AlchemiStudio on SUSE AI Factory.

Path C — Helm CLI

For scripted installs:

helm install alchemistudio-platform \
  oci://<PUBLIC_HELM_REPO>/alchemistudio-platform --version 1.0.23 \
  --namespace alchemi --create-namespace \
  --set global.domain=ai.example.com \
  -f values-suse.yaml

values-suse.yaml selects the SUSE-native options (bundled data tier, Longhorn storage, RKE2 ingress).

Component toggles

Every tier is gated by an <component>.enabled flag, and each data service has a *.mode = bundled | external switch. So you can:

  • run everything bundled for a self-contained trial, or
  • point at external PostgreSQL / Redis / object storage in production, or
  • disable components you don’t need.

Registry & images

AlchemiStudio images are pulled from the publisher registry using an image-pull token secret (there is no cloud managed-identity on RKE2). For air-gapped clusters, mirror the images into your private registry and override the image repositories in values.

Publisher note: replace <PUBLIC_HELM_REPO> with the public OCI Helm repository URL you distribute to customers.

Next: the step-by-step installation guide.

Last updated on
RequirementsInstallation guide