Graph Studio licensing
Graph Studio uses legacy CSI licensing provided through initialization JSON (initJSON / initJson). The base64-encoded license string is supplied in the licenseEncoded key within the activation JSON payload.
Kubernetes deployments must also set a stable serverId in the activation JSON. Treat this value as installation-scoped licensing material: retain it securely and use the same value for every restart, upgrade, or redeployment of that Graph Studio installation. Do not generate a new ID during a redeployment.
Operator configuration
In the Graph Studio operator (anzo.cambridgesemantics.com/v2 Anzo), supply licenseEncoded inside spec.initJSON:
spec:
role: AnzoServer
jsonActivation: true
initJSON: |
{
"sysadminUser": "k8s://anzo-graph-studio/admin_user",
"password": "k8s://anzo-graph-studio/admin_password",
"hostname": "graph-studio",
"serverId": "${SERVER_ID}",
"licenseEncoded": "${CSI_LICENSE}"
}
Standalone Helm configuration
In standalone Graph Studio Helm values, supply licenseEncoded under anzo.initJson:
anzo:
jsonActivation: true
initJson:
sysadminUser: "k8s://anzo-${RELEASE_NAME}-credentials/admin_user"
password: "k8s://anzo-${RELEASE_NAME}-credentials/admin_password"
hostname: graph-studio
serverId: "${SERVER_ID}"
licenseEncoded: "${CSI_LICENSE}"
isOnPremise: true
The licenseEncoded string and serverId are sensitive licensing material. Neither the operator CRD nor Helm values accept an indirect Secret reference for these fields in initJSON. Never commit plaintext license strings, server IDs, or rendered manifests to version control. Restrict RBAC access to Anzo custom resources and Helm release Secrets.
Always render sensitive license values ephemerally at deployment time from an authorized secret manager. For automated CI/CD injection mechanics and safe non-interactive rendering pipelines, see Agentic reference.
Verify licensing status through the product administration console after initial startup and admin login.