namehash · tk-o · May 26, 2026 · May 26, 2026 · May 27, 2026 · May 27, 2026
@@ -208,6 +208,18 @@ export const integrateSidebarTopic = {
           label: "ENSDb (SQL)",
           link: "/docs/integrate/integration-options/ensdb",
         },
+        {
+          label: "ENSDb Writers (Indexers)",
+          link: "/docs/integrate/integration-options/ensdb-writers",
+        },
+        {
+          label: "ENSDb Readers (Custom APIs)",
+          link: "/docs/integrate/integration-options/ensdb-readers",
+        },
+        {
+          label: "ENSNode Plugins (data models)",
+          link: "/docs/integrate/integration-options/ensnode-plugins",
+        },
         {
           label: "enscli (CLI)",
           link: "/docs/integrate/integration-options/enscli",

@@ -91,7 +91,7 @@ export const servicesSidebarTopic = {
           items: [
             { label: "Overview", link: "/docs/services/ensindexer/contributing" },
             {
-              label: "Creating a Plugin",
+              label: "Creating an ENSNode Plugin",
               link: "/docs/services/ensindexer/contributing/creating-a-plugin",
             },
           ],

@@ -22,7 +22,7 @@ Full access to ENS data formerly required two separate data-fetching strategies
 
 ## How ENSNode solves this
 
-**The Unigraph Data Model** — [ENSIndexer](/docs/services/ensindexer)'s `unigraph` plugin builds a single, **unified** indexed data model in [ENSDb](/docs/services/ensdb) that combines all of ENSv1 — mainnet `.eth`, Basenames on Base, Lineanames on Linea, 3DNS on Optimism — together with ENSv2. One data model, every chain, both protocol versions.
+**The Unigraph Data Model** — The `unigraph` [ENSNode plugin](/docs/integrate/integration-options/ensnode-plugins), implemented in [ENSIndexer](/docs/services/ensindexer), builds a single, **unified** indexed data model in [ENSDb](/docs/services/ensdb) that combines all of ENSv1 — mainnet `.eth`, Basenames on Base, Lineanames on Linea, 3DNS on Optimism — together with ENSv2. One data model, every chain, both protocol versions.
 
 **The Omnigraph API** — The [ENS Omnigraph API](/docs/integrate/omnigraph), delivered by [ENSApi](/docs/services/ensapi), is a fully typed GraphQL API on top of that Unigraph data model. It handles the ENS protocol's many implementation details for you, so you can focus on building your app instead of wiring up the protocol's internals.
 

@@ -0,0 +1,54 @@
+---
+title: ENSDb Readers (Custom APIs)
+description: How to build custom APIs and other services on top of ENSDb, using the ENSDb Reader standard.
+---
+
+import { LinkCard } from "@astrojs/starlight/components";
+
+An [ENSDb Reader](/docs/services/ensdb/concepts/glossary#ensdb-reader) is any service that interacts with ENSDb to read ENS data. This can be anything from a custom GraphQL or REST API, to a data analytics pipeline, to a command-line interface, to a dashboard, and more.
+
+:::tip[Build your own ENSDb Reader]
+You can build your own ENSDb Reader in any language, using any framework, as long as you follow the [ENSDb Standard](/docs/services/ensdb/concepts/glossary#ensdb-standard). The ENSDb Standard defines rules and constraints for how an ENSDb Reader should read data from an ENSDb instance in a way that maintains the integrity of the data and supports interoperability with any ENSDb Writer.
+:::
+
+## Current ENSDb Readers
+
+### ENSApi
+
+ENSApi is a reference implementation of an [ENSDb Reader](/docs/services/ensdb/concepts/glossary#ensdb-reader) that includes the following APIs:
+
+- The new [ENS Omnigraph GraphQL API](/docs/integrate/integration-options/omnigraph-graphql-api) that's built on top of [ENSNode Plugins](/docs/integrate/integration-options/ensnode-plugins) such as `unigraph` and `protocol-acceleration`.
+- A backwards-compatible [ENS Subgraph GraphQL API](/docs/integrate/ens-subgraph) that's built on top of [ENSNode Plugins](/docs/integrate/integration-options/ensnode-plugins) such as `subgraph`, `basenames`, `lineanames`, and `threedns`.
+- APIs for various queries related to the metadata stored in ENSDb, such as the indexing status from the [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer) and [metadata](/docs/services/ensdb/concepts/glossary#indexing-metadata-context) about the overall [ENSNode stack of services](/docs/services) active in the ENSNode instance.
+
+<LinkCard
+  title="Learn more about ENSApi"
+  description="A reference implementation of ENSDb Reader, built by the NameHash team."
+  href="/docs/services/ensapi"
+/>
+
+### New ENSDb Readers Under Development
+
+Multiple new [ENSDb Reader](/docs/services/ensdb/concepts/glossary#ensdb-reader) services are planned by the NameHash team. Find out more about each of them below.
+
+<LinkCard
+  title="Learn more about ensdb-cli"
+  description="A command-line interface for interacting with ENSDb."
+  href="/docs/integrate/integration-options/ensdb-cli"
+/>
+
+<LinkCard
+  title="Learn more about ENSEngine"
+  description="A push-based web service allowing you to track ENS data changes as they occur."
+  href="/docs/integrate/integration-options/ensengine"
+/>
+
+<LinkCard
+  title="Learn more about ENSAnalytics (coming soon)"
+  description="A web service that provides analytics and insights on ENS data."
+  href="/docs/services"
+/>
+
+:::note[Build your own ENSDb Reader]
+Creating your own ENSDb Reader service enables you to build your own completely custom APIs and data pipeline services. See related inspiration on the [ENSDb integration options page](/docs/integrate/integration-options/ensdb). Use any programming language or framework you wish! If you'd like any help or guidance feel welcome to reach out to the NameHash team on [Telegram](https://t.me/ensnode).
+:::
@@ -0,0 +1,44 @@
+---
+title: ENSDb Writers (Indexers)
+description: How to build your own custom indexer implementation for ENSDb, using the ENSDb Writer specification.
+---
+
+import { LinkCard } from "@astrojs/starlight/components";
+
+An [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer) is the implementation of an indexing service that implements one or more standards-compliant [ENSNode plugins](/docs/integrate/integration-options/ensnode-plugins) and implements a standards-compliant [ENSDb Metadata Writer](/docs/services/ensdb/concepts/glossary#ensdb-metadata-writer) that stores [metadata](/docs/services/ensdb/concepts/glossary#indexing-metadata-context) about the [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer).
+
+:::tip[Build your own ENSDb Writer]
+You can build your own ENSDb Writer in any language, using any indexing framework, as long as you follow the [ENSDb Standard](/docs/services/ensdb/concepts/glossary#ensdb-standard). The ENSDb Standard defines rules and constraints for how an ENSDb Writer should write data into an ENSDb instance in a way that maintains the integrity of the data and supports interoperability with any ENSDb Reader.
+
+Your ENSDb Writer must include:
+
+- The _implementation_ of 1 or more standards-compliant [ENSNode plugins](/docs/integrate/integration-options/ensnode-plugins).
+- The _implementation_ of an [ENSDb Metadata Writer](/docs/services/ensdb/concepts/glossary#ensdb-metadata-writer) that stores [metadata](/docs/services/ensdb/concepts/glossary#indexing-metadata-context) about the [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer) overall, including which [ENSNode Plugins](/docs/integrate/integration-options/ensnode-plugins) it has activated, what the status of indexing is across each indexed chain, etc.
+
+:::
+
+## Current ENSDb Writers
+
+### ENSIndexer
+
+[ENSIndexer](/docs/services/ensindexer) is a reference implementation of an [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer) built by the NameHash team. It is a multi-chain ENS indexer built on top of [Ponder](https://ponder.sh/) that implements many ENSNode Plugins.
+
+<LinkCard
+  title="Learn more about ENSIndexer"
+  description="A reference implementation of ENSDb Writer, built by the NameHash team."
+  href="/docs/services/ensindexer"
+/>
+
+## New ENSDb Writers Under Development or Discussions
+
+### Envio
+
+The [Envio](https://envio.dev/) team is actively collaborating with NameHash Labs to build another standards-compliant [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer) that uses Envio as the indexing engine. Their initial ENSNode plugin under development is `subgraph`, with plans to support `unigraph` after that.
+
+### Amp (Edge & Node)
+
+[Edge & Node](https://www.edgeandnode.com) has discussions scheduled with the NameHash Labs team to investigate the use of their new [Amp](https://www.edgeandnode.com/articles/stream-live-chain-data-into-your-analytics-stack-with-amp) platform to implement an ENSDb Writer.
+
+### Build Your Own
+
+You can build your own ENSDb Writer in any language, using any indexing framework, as long as you follow the [ENSDb Standard](/docs/services/ensdb/concepts/glossary#ensdb-standard). Join us on [Telegram](https://t.me/ensnode) for any questions and support.
@@ -9,7 +9,9 @@ import EnsDbUseCases from "@components/molecules/EnsDbUseCases.astro";
 
 For special use cases that go beyond what the ENS Omnigraph exposes — you can query the live onchain state of both **ENSv1 and ENSv2** directly via `SQL`.
 
-**ENSDb** is a bi-directional integration standard for any EnsDbWriter and EnsDbReader implementations to coordinate around the live unified onchain state of ENSv1 **and ENSv2** in a carefully-crafted standardized data model within a PostgreSQL database. Because ENSDb builds on Postgres, you can use _any_ language with a Postgres driver — **TypeScript**, **Python**, **Rust**, **Go**, and more.
+The bi-directional [ENSDb integration standard](/docs/services/ensdb/concepts/glossary#ensdb-standard) enables any decoupled [ENSDb Writer](/docs/integrate/integration-options/ensdb-writers) and [ENSDb Reader](/docs/integrate/integration-options/ensdb-readers) implementations to coordinate around the live unified onchain state of **ENSv1 and ENSv2** in a carefully-crafted standardized data model within a PostgreSQL database. Because ENSDb builds on Postgres, you can use _any_ language with a Postgres driver — **TypeScript**, **Python**, **Rust**, **Go**, and more.
+
+The ENSDb standard also defines _the abstract specification_ for how ENSDb Writers store their [metadata](/docs/services/ensdb/concepts/glossary#indexing-metadata-context) in an [ENSDb instance](/docs/services/ensdb/concepts/glossary#ensdb-instance).
 
 :::tip[Coming soon: ensdb-cli & ENSDb snapshots]
 We're building [**`ensdb-cli` & ENSDb snapshots**](/docs/integrate/integration-options/ensdb-cli) so you can pull down a fresh ENSDb in minutes instead of paying for a full historical RPC backfill among many other benefits.

@@ -0,0 +1,66 @@
+---
+title: ENSNode Plugins
+description: How to customize data models for ENSNode, using the ENSNode Plugin specification.
+---
+
+import { LinkCard } from "@astrojs/starlight/components";
+
+## What is an ENSNode Plugin?
+
+An **ENSNode Plugin** is an abstract specification that defines how onchain data relevant to ENS should be indexed into [ENSDb](/docs/services/ensdb). It is **not** an implementation — it is a standard that any [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer) can implement and that any [ENSDb Reader](/docs/services/ensdb/concepts/glossary#ensdb-reader) can read.
+
+Each ENSNode Plugin defines:
+
+- **Name** — e.g. `unigraph`, `protocol-acceleration`, `subgraph`.
+- **Datasources** — which onchain contracts should be indexed, as a function of an ENS namespace.
+- **Dependency relationships** — other plugins that must (or must not) be activated concurrently.
+- **Indexed data model** — the tables, columns, and indexes that implementations of the plugin must produce in ENSDb.
+- **Standards and invariants** — rules for how onchain events from the datasources are translated into the indexed data model during indexing.
+- **Versioning** — a version number that can be stored in the ENSNode Metadata, to track which version of the plugin standard is being created by an ENSDb Writer and is available to ENSDb Readers.
+
+## Why ENSNode Plugins Matter
+
+ENSNode Plugins are a key architectural piece that enables a decoupling between [ENSDb Writers](/docs/services/ensdb/concepts/glossary#ensdb-writer) and [ENSDb Readers](/docs/services/ensdb/concepts/glossary#ensdb-reader), so that anyone can create their own implementations of these. For example, any team working on indexing infrastructure can implement an ENSDb Writer and have it produce a standards-compliant ENSDb. On the other hand, any team working on products or infrastructure in the ENS ecosystem can build their own standards-compliant ENSDb Reader and have it query ENSDb.
+
+:::note[Interoperability between ENSDb Writers and Readers]
+When new ENSNode plugins are created, it becomes possible for the [ENS Omnigraph API](/docs/integrate/omnigraph) (or other APIs built by any ENSDb Reader) to unify the ability to query across ENSNode plugins in a single query. For example, you could query both ENS state from the `unigraph` and EFP state about followers from the `efp` plugin in a single Omnigraph GraphQL query.
+:::
+
+## Existing Plugins
+
+[ENSIndexer](/docs/services/ensindexer) is a reference implementation of an [ENSDb Writer](/docs/services/ensdb/concepts/glossary#ensdb-writer) that implements multiple existing ENSNode Plugin specifications. The code for each plugin inside ENSIndexer is a reference implementation of that plugin's abstract specification. [The ENSNode Plugins implemented in ENSIndexer today](https://github.com/namehash/ensnode/tree/main/apps/ensindexer/src/plugins) are:
+
+| Plugin                  | Description                                                |
+| ----------------------- | ---------------------------------------------------------- |
+| `unigraph`              | Unified ENSv1 + ENSv2 data model with polymorphic entities |
+| `protocol-acceleration` | Accelerated lookups for ENS resolution                     |
+| `subgraph`              | Legacy ENS Subgraph-compatible data model                  |
+| `basenames`             | Basenames (`.base.eth`) subname indexing                   |
+| `lineanames`            | Lineanames (`.linea.eth`) subname indexing                 |
+| `threedns`              | 3DNS (`.box`) name indexing                                |
+| `registrars`            | Registration and renewal lifecycle tracking                |
+| `tokenscope`            | NFT tokenization of ENS names                              |
+
+## New Plugins
+
+### Under Development
+
+An `efp` plugin for the [Ethereum Follow Protocol](https://efp.app/) is [already under active development](https://github.com/Quantumlyy/efpnode/tree/main/packages/ensnode-plugin-efp) by the [EthId team](https://ethid.org/).
+
+### Build Your Own
+
+If you are interested in defining a new ENSNode plugin or implementing an existing one, reach out to the NameHash Labs team — we are happy to provide support and additional info. Join us on [Telegram](https://t.me/ensnode) for any questions.
+
+## Related
+
+<LinkCard
+  title="ENSDb Writers"
+  description="Learn how to build indexers that implement ENSNode plugins."
+  href="/docs/integrate/integration-options/ensdb-writers"
+/>
+
+<LinkCard
+  title="ENSDb Readers"
+  description="Learn how to build APIs and other services that read from ENSNode plugins."
+  href="/docs/integrate/integration-options/ensdb-readers"
+/>
@@ -45,7 +45,34 @@ For special use cases that go beyond what the ENS Omnigraph exposes, query the l
   href="/docs/integrate/integration-options/ensdb"
 />
 
-## 5. enscli
+## 5. ENSDb Writers
+
+Build your own indexer for ENSDb by implementing the [ENSNode Plugin](/docs/integrate/integration-options/ensnode-plugins) specifications you're interested to index. ENSDb Writers index onchain data and write it into an ENSDb instance according to the standards set by relevant ENSNode Plugins.
+
+<LinkCard
+  title="ENSDb Writer Documentation"
+  href="/docs/integrate/integration-options/ensdb-writers"
+/>
+
+## 6. ENSDb Readers
+
+Build custom APIs or other specialized services on top of ENSDb. ENSDb Readers read indexed ENS data from an ENSDb instance and serve it through any API surface (GraphQL, REST, gRPC, webhooks, etc.) or pipe it into specialized data processing pipelines through the PostgreSQL write-ahead-log.
+
+<LinkCard
+  title="ENSDb Reader Documentation"
+  href="/docs/integrate/integration-options/ensdb-readers"
+/>
+
+## 7. ENSNode Plugins
+
+ENSNode Plugins are abstract specifications that define indexed data models relevant to ENS. They are a key architectural piece that enables complete decoupling between ENSDb Writers and ENSDb Readers.
+
+<LinkCard
+  title="ENSNode Plugins Documentation"
+  href="/docs/integrate/integration-options/ensnode-plugins"
+/>
+
+## 8. enscli
 
 `enscli` is a CLI that wraps `enssdk` to bring the ENS Omnigraph to the terminal. Designed for developers exploring or validating integrations, operators wiring ENS lookups into shell pipelines, and AI coding agents driving `ensskills`.
 
@@ -54,7 +81,7 @@ For special use cases that go beyond what the ENS Omnigraph exposes, query the l
   href="/docs/integrate/integration-options/enscli"
 />
 
-## 6. ensskills
+## 9. ensskills
 
 `ensskills` is a collection of curated skill bundles that give AI coding agents a well-defined contract for working with ENS — powering conversational ENS lookups and streamlining integration code written with `enskit`, `enssdk`, or the raw Omnigraph API.
 
@@ -63,7 +90,7 @@ For special use cases that go beyond what the ENS Omnigraph exposes, query the l
   href="/docs/integrate/integration-options/ensskills"
 />
 
-## 7. ensdb-cli & ENSDb snapshots
+## 10. ensdb-cli & ENSDb snapshots
 
 `ensdb-cli` is the operator-facing tool for ENSDb snapshots — portable, versioned packages of an ENSDb instance. Pull one down, restore it into Postgres, and start querying ENS in minutes instead of waiting days to complete a full historical indexing backfill from scratch.
 
@@ -72,7 +99,7 @@ For special use cases that go beyond what the ENS Omnigraph exposes, query the l
   href="/docs/integrate/integration-options/ensdb-cli"
 />
 
-## 8. ENSEngine
+## 11. ENSEngine
 
 ENSEngine watches your ENSDb for changes in real time and delivers ENS-aware events — including webhooks — to any sink you configure. Stop polling and start reacting to ENS state changes.
 

@@ -82,7 +82,7 @@ query Namegraph {
 
 The **Unigraph** is the entire collection of these disjoint ENSv2 Namegraphs and multiple ENSv1 Nametables, combined together into a single unified data model using ENS Resolution semantics. Navigating the Unigraph from `"eth"` down to `"vitalik.eth"` and beyond looks identical regardless of whether the underlying entities are ENSv1 or ENSv2.
 
-The [`unigraph` plugin](/docs/services/ensindexer) in ENSIndexer is what builds this unified model. The Unigraph constructs two Namegraphs, one rooted at the ENSv1 Root Registry and another rooted at the ENSv2 Root Registry. It's also where multichain coverage lives: Basenames (`.base.eth`), Lineanames (`.linea.eth`), and 3DNS names (`.box`) are all stitched into the ENSv1 Namegraph.
+The `unigraph` [ENSNode plugin](/docs/integrate/integration-options/ensnode-plugins), implemented in [ENSIndexer](/docs/services/ensindexer), is what builds this unified model. The Unigraph constructs two Namegraphs, one rooted at the ENSv1 Root Registry and another rooted at the ENSv2 Root Registry. It also includes special support for unifying multiple ENSv1 Nametables across multiple chains into the unigraph, including: Basenames (`.base.eth`), Lineanames (`.linea.eth`), and 3DNS names (`.box`).
 
 ```mermaid
 flowchart TD