Skip to main content
A stack profile demo installs a profile’s add-ons and manifests into their own isolated namespace on your organisation’s staging cluster, and stops itself when its lifetime runs out. Use it to see what a profile actually deploys before you use it on a real cluster, to check a new version against the old one, or to give a managed service package a running demo to read its connection from. This is the profile-side twin of previews. A preview runs an application’s build; a profile demo runs the stack itself, with no application in front of it. The portal has no page for stack profile demos. Use ankra stack-profiles demo or the API.

Before you start

  • The organisation has a staging cluster, and its agent is online. Every demo lands there. Someone who manages Ankra AI sets it under Ankra AI → AI workspaces, in Staging cluster, or with ankra org ai-environment set --staging-cluster <cluster>. See AI Workspaces.
  • You can read the stack profile. Your own profiles, profiles shared with your organisation, and public profiles can all be demoed. The demo runs on your staging cluster, so demoing someone else’s public profile uses none of their resources.
  • Your role holds stacks.deploy. A demo is a real deployment through the resource engine, and launching or stopping one needs that permission.
  • The Ankra CLI is installed and signed in. See Ankra CLI.

Launch and follow a demo

1

Launch the demo

Give the profile’s name or id. Without flags, the demo runs the profile’s current version with its default values, for the organisation’s default lifetime:
Pin a version with --version, set the lifetime with --ttl-hours, and bind parameters with --set name=value. For a secret parameter, use --set-env name=ENV_VAR or --set-file name=path, which keep the value out of your shell history:
Ankra creates the namespace, applies its quota, and deploys the profile into it with every member forced into that one namespace. The command prints the response as JSON, with the demo’s workspace_id, its namespace and the version it runs. The commands below take the workspace id.
2

Check that it is listed

The demo appears under demos, beside your lifetime policy and the staging cluster.
3

Watch it come up

The detail is read from the staging cluster each time you run it. Its inspection holds the steps (namespace created, guardrails applied, stack deployed), the resources the profile installed, and the namespace’s Kubernetes events. A profile demo deploys no workload of its own, so there is no image or routing step to wait on: the stack operation completing is its readiness. If a chart fails to install, the failure text is the stack’s own, not a generic demo failure.
4

Read its logs

Until the demo has a pod, this says The demo has no pod yet, so there are no logs to read.

One demo per profile

A profile has at most one live demo per organisation. Its namespace is derived from the organisation and profile ids, ankra-demo-sp-<org>-<profile> with the first eight hexadecimal characters of each, so launching again replaces the running demo rather than adding a second copy. That is also why renaming a profile never strands a demo. Launch again to pick up a new profile version or changed parameter values.

Lifetime

Without --ttl-hours, a demo lives for the organisation’s demo lifetime, 24 hours unless someone changed it (ankra org ai-environment set --demo-ttl-hours). Your role sets the longest lifetime you may ask for; a longer one is refused with Your role allows demos of at most <n> hours.

Capacity

The demo namespace carries a hard ResourceQuota at the full-stack tier, because a profile installs a whole stack rather than one workload:

Stop a demo

Stopping uninstalls the stack and deletes the namespace. Because Helm uninstall jobs have to drain before the namespace can go, a stop is asynchronous: the demo is marked as stopping and Ankra’s cleanup finishes the teardown. Every demo also stops on its own at the end of its lifetime, whether or not anyone remembers it. Run ankra stack-profiles demo list my-profile again: once the teardown has finished, the demo is no longer listed.

Where else profile demos are used

  • Previews built from a profile. An application’s preview settings can name a stack profile (Choose a profile), so every preview of that application starts its own copy of the profile beside the app: see Set what every preview starts with. When you only want to look at the stack, a profile demo is cheaper than a whole preview.
  • Publishing a managed service. When you publish a managed service package over a stack profile, Ankra can fill the package’s connection from a running demo of that profile and try it there before you publish: see Publish a managed service.

What can go wrong


API

All endpoints sit under the profile and require authentication; the mutations require a CSRF header for browser-originated requests. Bearer-token twins live under /api/v1/org/stack-profiles/... for the CLI. See Stack Profiles for authoring and versioning, and Preview a branch for the application lane.