> ## 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.

# Stackdome Cloud during alpha

> Availability, ephemerality, and fallback options for Stackdome Cloud during alpha.

Stackdome Cloud lets you use the Stackdome application-delivery workflow without first setting up infrastructure. Access is open while capacity is available.

## Alpha commitments

* Environments are ephemeral.
* Capacity is limited during alpha.
* Access remains available while capacity allows.

Plan for the environment to be temporary. Stackdome does not currently document an expiry duration, quota, SLA, region list, or persistence guarantee for the alpha.

## If capacity is unavailable

If Stackdome Cloud cannot allocate an environment, you can:

* Join the Cloud availability list.
* [Connect a self-hosted Stackdome installation](/self-host/install).

Moving to a self-hosted destination does not change your Stackfile or deployment workflow. Authenticate the CLI against the new Stackdome host, then repeat the same validate, deploy, and status commands.

<CardGroup cols={2}>
  <Card title="Quickstart with an agent" icon="sparkles" href="/quickstart">
    Ask your coding agent to deploy and return a verified public URL.
  </Card>

  <Card title="Quickstart with the CLI" icon="terminal" href="/get-started/cli">
    Run the deployment workflow directly against your chosen host.
  </Card>
</CardGroup>