AlchemiStudioAlchemiStudio
Skip to Content
SUSE AISUSE AI FactoryArchitecture

AlchemiStudio on SUSE AI Factory

SUSE AI Factory turns a Rancher Prime / RKE2 cluster into a managed environment for AI workloads (a Rancher UI extension plus the aif-operator). AlchemiStudio runs as a first-class AI application on top of it.

What runs where

Rancher Prime ──manages──▶ RKE2 cluster │ ├─ SUSE AI Factory (aif-operator 2.0.0) │ └─ Blueprints / AIWorkloads (Fleet GitOps) │ └─ AlchemiStudio Platform (one Helm chart) ├─ App tier: web, ai, compute-api, worker, zenith, guardrails ├─ Auth: Keycloak (SSO, realm + clients) ├─ Gateway: APISIX (+ etcd) ├─ Data tier: pgvector PostgreSQL, Redis, OpenObserve ├─ Storage: Longhorn (RWO + RWX), object store (SeaweedFS/OpenDAL) └─ Secrets: OpenBao + External Secrets Operator (optional)

Component summary

LayerComponentRole
Applicationsalchemi-webUI backend / console
alchemi-aiAgent / LLM orchestration
alchemi-compute-apiCode / compute sandbox control plane
alchemi-workerAsync jobs
alchemi-zenithPlatform/admin services
alchemi-guardrailsPII, jailbreak, toxicity, content-filter, secret-detection, topical
IdentityKeycloakSSO / OIDC for all apps
GatewayAPISIX (+ etcd)Ingress, routing, request policy
DataPostgreSQL (pgvector)Relational + vector store
RedisCache / queues
OpenObserveLogs, metrics, traces
StorageLonghornBlock (RWO) and shared (RWX) volumes
SeaweedFS / OpenDALObject storage for files/artifacts
SecretsOpenBao + ESOStore and sync provider secrets (optional)

SUSE-native swaps

When moving from a cloud to SUSE AI, AlchemiStudio swaps managed services for SUSE-native equivalents:

Cloud managed serviceSUSE-native replacement
Managed Key VaultOpenBao (+ External Secrets Operator)
Managed PostgreSQL / RedisIn-cluster pgvector PostgreSQL / Redis (or your external ones)
Cloud container registryHarbor / your private registry / SUSE Application Collection
Cloud blob storageSeaweedFS (S3-compatible via OpenDAL)
Cloud managed disksLonghorn

The Blueprint model

AlchemiStudio can be delivered as a SUSE AI Factory Blueprint and reconciled by Fleet from a Git repository, so it appears as a catalog card and stays in sync with Git. This is the GitOps delivery path; the Rancher App path is the guided-form alternative.


Next: Model serving · Observability, security & storage.

Last updated on