Skip to main content
SQD Cloud deployment and monitoring interface
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.
Cloud currently supports Squid SDK indexers. Pipes SDK deployments are not supported.

​
What Cloud manages

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:
Use a tag URL from applications:
The tag can move to a validated replacement slot without changing the client URL. See 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 and Pricing.

​
Production lifecycle

1

Run locally

Test the same commit, lockfile, manifest commands, migrations, and required environment variables locally.
2

Deploy to a new slot

Cloud builds the image, runs init, then starts processor and API services.
3

Verify progress and output

Check processor height and lag, inspect logs, query representative records, and confirm the API shape expected by clients.
4

Attach or move the production tag

Applications continue to use the stable tag URL.
5

Observe and clean up

Keep the previous slot during a rollback window. Remove it after the new deployment is stable.
Parallel slots, named processors, and API replicas are independent billable resources. Review Scaling and Billing and Usage before long replays.

​
Start here

Deployment guide

Deploy a locally tested Squid SDK project.

Deployment manifest

Configure services, addons, environment, and resources.

Slots and tags

Use stable URLs, zero-downtime cutovers, and rollback.

Monitoring

Distinguish service health from indexing progress and freshness.

​
Operational guides

Schema changes and backfills

Choose between an in-place migration, database backfill, and fresh-slot replay.

Background jobs

Run scheduled aggregates without blocking processor transactions.

Troubleshooting

Diagnose build, runtime, database, API, and data-source failures.

Pricing

Estimate compute, storage, replicas, processors, and slot overlap.

Related topics

Hosting your indexerHomePricing OverviewFAQBuild with SQD