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

# SQD Cloud indexer hosting

> Deploy and operate Squid SDK indexers on managed SQD Cloud infrastructure.

<Frame>
  <img src="https://mintcdn.com/sqd-2119b3c3/Kx7YspEVpTTxfIRc/images/home/cloud.png?fit=max&auto=format&n=Kx7YspEVpTTxfIRc&q=85&s=5114ab7dd93424fb47f7fe41e1e913c2" alt="SQD Cloud deployment and monitoring interface" width="1440" height="600" data-path="images/home/cloud.png" />
</Frame>

SQD Cloud builds, runs, and monitors Squid SDK indexers. A deployment can include processors, an API service, managed Postgres, RPC endpoints, and optional addons configured through `squid.yaml`.

<Warning>
  Cloud currently supports Squid SDK indexers. Pipes SDK deployments are not
  supported.
</Warning>

## What Cloud manages

| Component  | Cloud responsibility                               | Your responsibility                                              |
| ---------- | -------------------------------------------------- | ---------------------------------------------------------------- |
| Build      | Build one deployment image from the repository     | Keep the project and lockfile reproducible                       |
| Processor  | Run and restart processor services                 | Data filters, transformations, retries, and correctness          |
| API        | Route and load-balance configured API replicas     | Schema, query limits, caching, and client compatibility          |
| Postgres   | Provision connection details, compute, and storage | Schema, migrations, indexes, retention, and reconstructable data |
| Monitoring | Collect logs and expose processor metrics          | Alerts, progress checks, and application-level metrics           |
| Scaling    | Apply configured profiles and API replicas         | Select and pay for appropriate resources                         |

Cloud service health does not guarantee that an indexer is advancing or that its upstream data source is complete. Monitor processor height, lag, logs, and application queries.

## Deployment model

A Cloud deployment is identified by:

* an organization;
* a squid name;
* a generated or chosen slot;
* zero or more movable tags.

Use slot URLs to inspect one deployment:

```text theme={"system"}
https://<org>.squids.live/<name>@<slot>/api/graphql
```

Use a tag URL from applications:

```text theme={"system"}
https://<org>.squids.live/<name>:production/api/graphql
```

The tag can move to a validated replacement slot without changing the client URL. See [Slots and tags](/en/cloud/resources/slots-and-tags).

## Development and production

### Playground

Every account receives a playground organization for learning and development. Playground deployments are collocated, have limited resources, and are not suitable for production.

### Professional organization

A Professional organization enables paid deployments, dedicated resources, scaling, team access, and production usage. See [Organizations](/en/cloud/resources/organizations) and [Pricing](/en/cloud/pricing/overview).

## Production lifecycle

<Steps>
  <Step title="Run locally">
    Test the same commit, lockfile, manifest commands, migrations, and required environment variables locally.
  </Step>

  <Step title="Deploy to a new slot">
    ```bash theme={"system"}
    sqd deploy .
    ```

    Cloud builds the image, runs `init`, then starts processor and API services.
  </Step>

  <Step title="Verify progress and output">
    Check processor height and lag, inspect logs, query representative records, and confirm the API shape expected by clients.
  </Step>

  <Step title="Attach or move the production tag">
    ```bash theme={"system"}
    sqd tags add production -n <name> -s <slot>
    ```

    Applications continue to use the stable tag URL.
  </Step>

  <Step title="Observe and clean up">
    Keep the previous slot during a rollback window. Remove it after the new deployment is stable.
  </Step>
</Steps>

<Info>
  Parallel slots, named processors, and API replicas are independent billable
  resources. Review [Scaling](/en/cloud/reference/scale) and [Billing and
  Usage](https://app.subsquid.io/billing/usage) before long replays.
</Info>

## Start here

<CardGroup cols={2}>
  <Card title="Deployment guide" icon="rocket" href="/en/cloud/deployment-guide">
    Deploy a locally tested Squid SDK project.
  </Card>

  <Card title="Deployment manifest" icon="file-code" href="/en/cloud/reference/manifest">
    Configure services, addons, environment, and resources.
  </Card>

  <Card title="Slots and tags" icon="tags" href="/en/cloud/resources/slots-and-tags">
    Use stable URLs, zero-downtime cutovers, and rollback.
  </Card>

  <Card title="Monitoring" icon="chart-column" href="/en/cloud/resources/monitoring">
    Distinguish service health from indexing progress and freshness.
  </Card>
</CardGroup>

## Operational guides

<CardGroup cols={2}>
  <Card title="Schema changes and backfills" icon="database" href="/en/cloud/resources/schema-changes-and-backfills">
    Choose between an in-place migration, database backfill, and fresh-slot replay.
  </Card>

  <Card title="Background jobs" icon="clock" href="/en/cloud/resources/background-jobs">
    Run scheduled aggregates without blocking processor transactions.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/en/cloud/troubleshooting">
    Diagnose build, runtime, database, API, and data-source failures.
  </Card>

  <Card title="Pricing" icon="dollar-sign" href="/en/cloud/pricing/overview">
    Estimate compute, storage, replicas, processors, and slot overlap.
  </Card>
</CardGroup>


## Related topics

- [Hosting your indexer](/en/sdk/self-hosting.md)
- [Blockchain Data APIs for 200+ Networks](/en/home.md)
- [Pricing Overview](/en/cloud/pricing/overview.md)
- [Network, Portal and SDK FAQ](/en/other/faq.md)
- [Build with SQD](/en/sdk/overview.md)