# ENS Subgraph

:::danger[🚨 The ENS Subgraph is not ENSv2 compatible]
The ENS Subgraph **fundamentally fails as a source of ENS data as soon as ENSv2 launches.**

[Keep ENS apps working 🚨](/docs/integrate/why-ensnode/keep-ens-working)
[Key Limitations 🚨](/docs/integrate/ens-subgraph/key-limitations)
:::

:::tip[Start here instead: the ENS Omnigraph API]
The [ENS Omnigraph API](/docs/integrate/omnigraph) is the ENSv2-ready replacement: one unified, typed GraphQL API over **both ENSv1 and ENSv2**, multichain by default, with protocol-correct [ENS Protocol Acceleration](/docs/integrate/omnigraph/protocol-acceleration) resolution built in.

[ENS Omnigraph API](/docs/integrate/unigraph)
:::

## ENSNode Subgraph compatibility

ENSNode maintains a verified Subgraph-compatible API for migrating existing integrations from The Graph, but it is **not** the path forward for ENSv2.

<LinkCard
  href="/docs/integrate/ens-subgraph/backwards-compatibility#ensnodes-backwards-compatibility-with-the-ens-subgraph"
  title="ENSNode’s Backwards Compatibility with the ENS Subgraph"
  description="A verified Subgraph-compatible GraphQL endpoint for migrating existing integrations to ENSNode."
/>