On your Kubernetes,
in eight steps.

Get your demo key

Register your company on Licman, open the Ventic product, choose On Premise and request the demo. The key is shown once: save it in a private file.

install -d -m 700 private private/staging
umask 077
$EDITOR private/staging/license.key   # paste the key

Start from the template

Use the template repository as a new repository (or fork it) and clone it. Contoso Ltd is fictional: you will replace identity, domains and artwork.

git clone git@github.com:<YOUR-ORG>/acme-provider.git
cd acme-provider
python3 -m venv .venv && . .venv/bin/activate
python -m pip install -r requirements-installer.txt
make help

Fetch the signed release

Save the release public key, obtained through an independent trusted channel, at private/release.pub. Set version and origin in config/distribution.yaml, then fetch and verify: nothing is compiled.

make release-fetch
make release-check
VENTIC_INSTALLER="$(python scripts/binary-release.py path)"

You never build Docker images: the cluster pulls them from the registry pinned in the signed manifest.

Prepare the cluster

Kubernetes 1.36 or 1.37, Linux amd64 nodes, a NetworkPolicy-enforcing CNI and a persistent StorageClass. Install any missing controllers (KEDA, cert-manager, ingress, CloudNativePG, External Secrets, Reloader) and deploy OpenBao for secrets.

kubectl --kubeconfig private/staging/kubeconfig --context acme-demo \
  get namespace kube-system -o jsonpath='{.metadata.uid}'

python "$VENTIC_INSTALLER/scripts/controllers.py" \
  --context acme-demo --kubeconfig private/staging/kubeconfig \
  --cluster-uid <INSPECTED-UID> \
  --openbao-values config/openbao.yaml --openbao-namespace acme-credentials

Configure domain and brand

Start from config/production.yaml and save config/demo.yaml. Point six public hosts (marketing, portal, api, docs, chat with wildcard, push) at the ingress. Your logo goes in artwork/portal/.

installation: acme-demo
domain: demo.example.org
profile: bundled
localBuild: false
provider:
  name: Acme Demo
  support_email: support@example.org
  terms_url: https://legal.example.org/acme/terms
  privacy_url: https://legal.example.org/acme/privacy
postgres:
  instances: 1        # demo only, no high availability
settings:
  SMTP_HOST: smtp.example.org
  S3_BUCKET: acme-demo-data

Plan, then install

The plan is offline and lists what is still missing. When complete, Helm installs the four namespaces and verify checks the rollout.

make deploy-plan ENVIRONMENT=staging
make deploy-release ENVIRONMENT=staging
make deploy-verify ENVIRONMENT=staging

Connect a model and try it

Connect an approved endpoint or a Rust agent on your hardware, publish the model, fund the workspace and send the first request from the portal.

The demo includes neither hardware nor inference credit.

Move to a paid licence

Buy the licence on Licman: same data, same services, same encryption keys. No reinstall needed.