Skip to content

docs(subgraphs): add the GraphOps Platform as a Subgraphs provider - #1133

Open
chriswessels wants to merge 1 commit into
graphprotocol:mainfrom
graphops:docs/add-graphops-subgraphs-provider
Open

chriswessels wants to merge 1 commit into
graphprotocol:mainfrom
graphops:docs/add-graphops-subgraphs-provider

Conversation

@chriswessels

Copy link
Copy Markdown
Contributor

Summary

Adds the GraphOps Platform as a provider under Subgraphs > Providers. The page follows the gateway provider template and covers how the service works, pricing, sign-up, querying, and what Indexers need to know.

Changes

  • website/src/pages/en/subgraphs/providers/graphops.mdx: the new provider page.
  • website/src/pages/en/subgraphs/providers/_meta.js: adds graphops after subgraph-studio. The sidebar label is "GraphOps", taken from the page's sidebarTitle.
  • website/route-lockfile.txt: adds /en/subgraphs/providers/graphops/.

Page contents

  • Overview table: endpoints (by Subgraph ID or Deployment ID), payment, support, and where Indexers find transparency data.
  • How it works: GraphOps selects an Indexer on The Graph Network that serves the deployment, forwards the query, and pays the Indexer in GRT with TAP receipts from its own escrow. Customers pay GraphOps in credits by card or another payment method. They need no GRT or wallet.
  • Publishing: every deployment queried or deployed through GraphOps is available on The Graph Network. GraphOps allocates to every Managed Subgraph as an Indexer, so that capacity serves queries from any gateway. To publish a Subgraph ID, the page points to Subgraph Studio.
  • Sign-up, query examples, supported networks, additional services and support.
  • For Indexers: where to find the version requirements, blocklist and QoS data, plus the TAP sender addresses and aggregator endpoint with an indexer-service / tap-agent config snippet.
  • Indexer Portal: a guide to indexer-portal.graphops.xyz, where Indexers can see their selection, QoS results and constraints and contact GraphOps support.

Notes for reviewers

  • Links to graphops.xyz properties carry UTM tags so we can attribute traffic from this page. Indexer Portal and status links are untagged.
  • The page uses only standard MDX and existing components. Notes use the > [!NOTE] callout syntax.
  • No translations are included. The page is English-only, like other provider pages at launch.

Checks

  • Prettier and ESLint pass on the changed files
  • The MDX compiles with the site's @mdx-js/mdx and remark-gfm versions

Lists the GraphOps Platform under Subgraphs > Providers in the Foundation's gateway page template: how requests reach Indexers, pricing, sign-up, query examples, the transparency data and TAP senders Indexers need, and the Indexer Portal.

@brandonleekramer brandonleekramer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On first pass, only requesting this language change. The rest of the team will review early next week, but it looked pretty good. Thanks @chriswessels!


The GraphOps Platform serves GraphQL queries for Subgraphs on The Graph Network to applications that pay with a GraphOps API key and credits, with no GRT or wallet required. It is for teams that want one account and one bill for Subgraphs, RPC, and Substreams, and for teams that want guaranteed indexing and query capacity with [Managed Subgraphs](https://docs.graphops.xyz/subgraphs/managed-subgraphs?utm_source=thegraph-docs&utm_medium=referral&utm_campaign=provider-listing-2026-11&utm_content=intro-managed-subgraphs).

This page describes a gateway that an independent team operates. GraphOps sets its own pricing, terms, and support. For the canonical gateway, see [Subgraph Studio](/subgraphs/providers/subgraph-studio/introduction/). For all gateways, see [Subgraph Providers](/subgraphs/providers/overview/).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to avoid using "canonical gateway". I'd suggest removing that line completely and referencing the overview page or calling it "The Graph Foundation's gateway" or "the Foundation's gateway".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants