# Stagd > Stagd gives every pull request a live preview: the whole app running with its services and seeded data, on the team's own compute (Namespace, Kubernetes or a Docker host), with the link on the pull request. Mail and text messages the app sends are caught, never delivered. People use the dashboard; scripts, CI jobs and coding agents use the stagd CLI, the API (stagd.api.v1, over Connect) or the MCP server (stagd mcp), all as the signed-in person. An app is described for previews by its compose file and an optional stagd.yaml. Coding agents: start with the Coding agents guide; every API method is in the API reference. ## Get started - [Introduction](https://stagd.dev/docs/index.md): Stagd gives every pull request a live, seeded preview environment, running on your own compute, with feedback in the PR and Slack. - [Quickstart](https://stagd.dev/docs/quickstart.md): Sign in from the command line, create an org, and connect GitHub and your compute. ## Guides - [Connect GitHub](https://stagd.dev/docs/guides/connect-github.md): Install the Stagd GitHub App on your GitHub organization and choose which repositories get previews. - [Connect compute](https://stagd.dev/docs/guides/connect-compute.md): Give Stagd access to the compute account your previews run on, and choose the default. - [Connect integrations](https://stagd.dev/docs/guides/connect-integrations.md): Connect the services previews use besides compute: a Neon branch per preview, and the storage your seeds are kept in (Azure Blob Storage, S3, Google Cloud Storage). - [Seed data without personal data](https://stagd.dev/docs/guides/seed-data.md): Give previews realistic data: dump your database, take the personal data out on your own machines, put the dump in your storage and name it as a seed, or use Neon's and Xata's own anonymized copies. Why Stagd never gets the real thing. - [Sign in as Stagd](https://stagd.dev/docs/guides/sign-in-as-stagd.md): Set up Azure, AWS or Google Cloud to trust Stagd for your workspace, so an integration needs no stored key. - [Describe your app](https://stagd.dev/docs/guides/describe-your-app.md): Stagd reads stagd.yaml and your compose file to know which parts make up your app and which ones get a URL. - [Coding agents](https://stagd.dev/docs/guides/coding-agents.md): Give Claude Code, Cursor, Codex and other agents a running copy of each change, and tools to check it with. - [Traces in previews](https://stagd.dev/docs/guides/traces.md): Get your app's traces into a preview's Traces tab: what Stagd sets, and the least it takes in Node.js, Python, Go and Java. ## Concepts - [How Stagd works](https://stagd.dev/docs/concepts/how-it-works.md): Stagd is a control plane. Your code, images, data and previews stay in your accounts. - [Compute providers](https://stagd.dev/docs/concepts/compute.md): Where previews run: a Namespace workspace, a Kubernetes cluster or a Docker host of yours, behind the same interface. - [Signing in as Stagd](https://stagd.dev/docs/concepts/sign-in-as-stagd.md): How Stagd reaches your cloud without a stored key: it's an OpenID Connect issuer, and your cloud trusts it for your workspace. ## Reference - [stagd.yaml](https://stagd.dev/docs/reference/stagd-yaml.md): Every setting in stagd.yaml, what it takes and what it defaults to. - [CLI](https://stagd.dev/docs/reference/cli.md): Every stagd command. The CLI talks to the same API as the dashboard, as the signed-in person. - [API](https://stagd.dev/docs/reference/api.md): The stagd.api.v1 API behind the dashboard, the CLI and the MCP server, over Connect. Every service and method, with their fields. - [MCP tools](https://stagd.dev/docs/reference/mcp.md): Every tool Stagd's MCP server gives coding agents, with what each takes and what it answers. ## Optional - [All the docs in one file](https://stagd.dev/llms-full.txt): every page above, in this order - [stagd.yaml's JSON Schema](https://stagd.dev/schema/stagd.schema.json): for checking a stagd.yaml before it's pushed - [The API contract](https://buf.build/stagdhq/stagd): stagd.api.v1 in Protocol Buffers, for generating a client