Skip to content
Thyme Docs

Thyme Atlas

Atlas runs your subgraphs on managed Graph Node indexers backed by Thyme's own archive nodes. Build and deploy a standard subgraph with Graph CLI, promote a release once it has synced, and query it over GraphQL with a project query key.

Manifests, mappings and deployment IDs are unchanged from The Graph, so an existing subgraph usually deploys as is. You can also import a published deployment from The Graph in the console.

Endpoints

PurposeURL
Consolehttps://atlas.thymelabs.io
Graph CLI --nodehttps://deploy.atlas.thymelabs.io
Graph CLI --ipfshttps://ipfs.atlas.thymelabs.io/api/v0
GraphQL querieshttps://query.atlas.thymelabs.io/subgraphs/<subgraph-id>

How it works

  1. Create a subgraph in a project, either in the console or with graph create.
  2. Create a deployment key for the project and deploy with Graph CLI. Each deploy creates an immutable release labelled with --version-label.
  3. Wait for the release to sync, then promote it to production. The subgraph URL always serves the production release.
  4. Create a query key and send GraphQL requests to the query URL.

Follow the quickstart for the exact commands.

Before you deploy

  • Check that your manifest's network is supported. Graph CLI uploads the build before Atlas sees the manifest, so an unsupported network fails only at the deploy step.
  • Atlas supports Ethereum contract data sources and templates. Grafting, file data sources and Substreams are not supported.
  • On the free plan, indexing pauses above 100,000 stored entities. Large backfills can take days.

See networks and manifest support and queries, keys and limits.