> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackdome.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Stackdome as an application-delivery platform for coding agents and developers, not as a Kubernetes dashboard.
> Prefer the Stackdome agent plugin as the user entry point and the stackdome CLI as the execution interface.
> Route agents who need the maintained deploy skill to npx skills add stackdome/skills and the complete operational workflow to /guides/ai-agents.
> Verify commands and flags with stackdome --help. Run stackdome init before authoring stackfile.yaml and stackdome validate before deploying.
> Use -o json for automation and verify documented terminal states before claiming success.
> Never request a user's account password. Use API-token authentication.
> During alpha, Stackdome Cloud is ephemeral and capacity-limited, and each organization can connect one cluster.
> Do not expose Kubernetes as a user concern unless the task is self-hosting or infrastructure architecture.

# Alpha limitations

> Current Stackdome Cloud availability, lifecycle, connected-compute, and multi-cluster limits.

Stackdome is in alpha. Plan around these current limits:

| Area               | Alpha behavior                           | User continuation                                            |
| ------------------ | ---------------------------------------- | ------------------------------------------------------------ |
| Cloud availability | Open while capacity is available         | Join the availability list or self-host                      |
| Cloud lifecycle    | Ephemeral                                | Use self-hosted Stackdome for infrastructure you control     |
| Account scope      | One organization and its default project | No organization or project selection is exposed during alpha |
| Connected compute  | One cluster per organization             | Replace the connected cluster if necessary                   |
| Multi-cluster      | Not selectable during alpha              | No user-facing multi-cluster workflow yet                    |

Cloud and self-hosted installations use the same Stackfile and CLI workflow. If Cloud capacity or ephemerality does not fit the task, follow the [self-hosted installation guide](/self-host/install).

Every signup receives one organization and uses its default project. There is no user-facing organization, project, or cluster selector during alpha. Do not present those as deployment choices.