Make a more informed choice.

Compare what projects do, what’s available, and the evidence behind each profile. Select up to three.

CompareThe Graph ↗LayerZero ↗Arc Studio ↗
PurposeThe Graph appears in Arc’s data-indexer documentation with subgraph and Substreams references. It is relevant to applications that need a reusable query model over contract events. Check whether the specific deployment is hosted, decentralized or self-operated and how indexing lag is exposed.LayerZero builds technology that makes decentralization possible, scalable, and inevitable. Listed by Arc; a specific production deployment is not established by the directory.Arc Studio turns prompts into application code with Arc and Circle integrations. Its introduction describes a generated frontend, backend and contracts, plus code export. Use it to shorten a prototype’s first iteration; inspect generated permissions, deployment settings and transaction handling before operating the result.
Best suited to
  • Queryable contract data
Read the profile and provider documentation for fit.
  • Prototyping payment applications
  • Learning how an Arc app is assembled
CategoryData & oraclesBridges & messagingCore network
AvailabilityNot establishedNot establishedNot established
EvidencePlatform documentedDirectory onlyPlatform documented
Role on ArcArc relationship documented by the linked primary reference; individual service availability is described separately.Listed by Arc; a specific production deployment is not established by the directory.AI-assisted application development product.
Access requirementsCheck provider termsCheck provider termsCheck provider terms
Watch points
  • An ecosystem listing does not prove that a suitable public subgraph already exists.
No specific watch points recorded. Check the source material.
  • Generated code still needs testing and review.
  • Studio’s mainnet terms leave mainnet deployment and operation to the developer.
Reviewed2026-09-242026-09-172026-09-24
Sources2 sources ↗1 sources ↗3 sources ↗