Name: The Graph
Brand: The Graph

The Graph is differentiated by the subgraph development pattern and an operator model. Managed competitors compete on ease of procurement, conventional SaaS SLAs, and alternative pricing structures. Competitor-authored cost comparisons should be validated with representative workloads and by assessing operational trade-offs, including tokenomics and governance implications where relevant.

	The Graph	Goldsky	Bitquery
Starting Price	Free tier with a monthly allowance and per-query pricing thereafter.	Starter free tier, then usage-based pricing (examples include worker-hour and storage/entity pricing).	Free developer tier; commercial pricing is negotiated with sales for higher-volume needs.
Recommended For	Teams seeking a protocol-based indexing approach with GraphQL subgraphs and an operator marketplace.	Teams seeking a managed, centralized subgraph-like experience with conventional SaaS operations.	Teams needing broad chain coverage via packaged APIs and managed real-time streams.
Key Strength	Ecosystem standardization around a subgraph pattern and a network of independent indexers.	SaaS operational model and managed pipelines with productized onboarding.	Breadth of packaged endpoints and commercial streaming APIs.
Key Weakness	Operational complexity from open-source components and limited publicly available enterprise compliance artifacts for the protocol as a whole; per-query cost considerations at very large scale.	Centralized vendor dependency and cost drivers tied to worker-hours and storage.	Commercial terms and SLAs are typically sales-led and require contract negotiation for enterprise guarantees.

	The Graph	Goldsky	Bitquery
Starting Price	Free tier with a monthly allowance and per-query pricing thereafter.	Starter free tier, then usage-based pricing (examples include worker-hour and storage/entity pricing).	Free developer tier; commercial pricing is negotiated with sales for higher-volume needs.
Recommended For	Teams seeking a protocol-based indexing approach with GraphQL subgraphs and an operator marketplace.	Teams seeking a managed, centralized subgraph-like experience with conventional SaaS operations.	Teams needing broad chain coverage via packaged APIs and managed real-time streams.
Key Strength	Ecosystem standardization around a subgraph pattern and a network of independent indexers.	SaaS operational model and managed pipelines with productized onboarding.	Breadth of packaged endpoints and commercial streaming APIs.
Key Weakness	Operational complexity from open-source components and limited publicly available enterprise compliance artifacts for the protocol as a whole; per-query cost considerations at very large scale.	Centralized vendor dependency and cost drivers tied to worker-hours and storage.	Commercial terms and SLAs are typically sales-led and require contract negotiation for enterprise guarantees.

The Graph

01Competitive Landscape