> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # Check a demo for service collisions > Reads one running demo of a stack profile on the organisation's staging cluster and answers whether two services set up from a service package built on the profile could run side by side on one cluster. Every service gets a namespace of its own while each chart keeps its release name, so a cluster-scoped object the demo's releases own (ClusterRole, ClusterRoleBinding, CustomResourceDefinition, admission webhook configurations, PriorityClass, StorageClass, IngressClass, Namespace) whose name does not carry the demo's namespace (which its stack is named after) collides with a second service's copy of it. Services and Secrets whose names do carry it are listed as instance-specific, since a package connection naming them would not match another service. Only names, Secret types and Helm's release annotation are kept; the Secret data the listing carries is dropped, never kept or returned, and nothing is installed or written. `verdict` is `no_collision` only when every kind was read and nothing collides, `collisions` when something does, and `unknown` when the demo, or a kind, could not be read; `reason` says why. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json get /api/v1/org/stack-profiles/{profile_id}/demos/{workspace_id}/collisions openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - name: Onboarding description: >- Generate a first website from a prompt and deploy it to a new organisation's cluster. - name: Access Gate description: >- Private service sign-in and membership checks for trusted Ankra proxy relays. - name: Canvas Datasets description: >- Read the fixed, named datasets canvas dashboards bind their charts, tables and stats to. - name: Canvases description: >- Keep dashboards and pages in the organisation's canvas library, with revision history, undo and pins. - name: Canvas Pages description: >- Publish a chat canvas artifact at a public pages address and take it down again. - name: Cloud Delegation description: >- Platform browser consent and organisation-bound connections for Ankra Cloud. - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Pipelines description: >- Pipeline definitions, the approval of the authority they declare, and the caches pipelines keep between runs. - name: Workspaces description: >- Personal workspaces on the organisation's CI pool where a repository's heavy commands run, and the repository profiles they are built from. - name: Deploy Targets description: >- Environments, the hosts registered to receive deployments, and the releases deployed to them. - name: Deploy Provenance description: >- Whether an application's deploys verify signed provenance from the organisation's own pipeline, the keys that provenance is signed with, and a dry-run that verifies images without deploying. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: AI Memory description: >- What the assistant has learned about you: your cross-session memories and learned profile. - name: MCP Servers description: >- Register the MCP servers the organisation's AI agents can call, choose their tools and grant them to roles. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - name: Usage description: >- What your organisation used of Ankra - vCPU-hours, playgrounds, managed services, hosted logs and metrics, and AI - per meter and period, with how completely it was measured and whether a published rate applies. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account description: >- Your own account: the contact email Ankra mails when it differs from your sign-in address. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Avura description: >- The linked Avura organization, the domains it shares with Ankra Platform, and their DNS records. - name: Variables description: Organisation- and cluster-scoped variables. - name: Secret Slots description: >- Store secrets in Vault and reference them by ${SECRET_SLOT:} sentinel instead of by value. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /api/v1/org/stack-profiles/{profile_id}/demos/{workspace_id}/collisions: get: tags: - Stack Profiles summary: Check a demo for service collisions description: >- Reads one running demo of a stack profile on the organisation's staging cluster and answers whether two services set up from a service package built on the profile could run side by side on one cluster. Every service gets a namespace of its own while each chart keeps its release name, so a cluster-scoped object the demo's releases own (ClusterRole, ClusterRoleBinding, CustomResourceDefinition, admission webhook configurations, PriorityClass, StorageClass, IngressClass, Namespace) whose name does not carry the demo's namespace (which its stack is named after) collides with a second service's copy of it. Services and Secrets whose names do carry it are listed as instance-specific, since a package connection naming them would not match another service. Only names, Secret types and Helm's release annotation are kept; the Secret data the listing carries is dropped, never kept or returned, and nothing is installed or written. `verdict` is `no_collision` only when every kind was read and nothing collides, `collisions` when something does, and `unknown` when the demo, or a kind, could not be read; `reason` says why. operationId: check_stack_profile_demo_collisions_api_v1 parameters: - name: profile_id in: path required: true schema: type: string format: uuid - in: path name: workspace_id required: true schema: type: string format: uuid responses: '200': content: application/json: schema: $ref: '#/components/schemas/StackProfileDemoCollisionCheck' description: The collision verdict, or why it is unknown '401': description: Unauthorized '404': description: Profile or demo not found '500': description: Internal server error security: - BearerAuth: [] components: schemas: StackProfileDemoCollisionCheck: type: object additionalProperties: false required: - demo_status - verdict - reason - collisions - instance_specific_names - checked_kinds - unreadable_kinds - note description: >- Whether two services set up from a package built on this profile could run side by side, read off its running demo. Read `verdict` before `collisions`. properties: demo_status: type: string verdict: type: string enum: - no_collision - collisions - unknown reason: type: string description: >- Why the verdict is unknown, or that more collisions may exist; empty otherwise. collisions: type: array items: $ref: '#/components/schemas/ServiceInstanceFinding' instance_specific_names: type: array items: $ref: '#/components/schemas/ServiceInstanceFinding' checked_kinds: type: array items: type: string unreadable_kinds: type: array items: type: string note: type: string ServiceInstanceFinding: type: object additionalProperties: false required: - kind - name - reason description: >- An object that would not survive a second service set up from the same package, and why. properties: kind: type: string name: type: string reason: type: string securitySchemes: BearerAuth: bearerFormat: PAT scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.