near · matiasbenary · Apr 27, 2026 · Apr 27, 2026 · Apr 30, 2026
diff --git a/data-infrastructure/big-query.mdx b/data-infrastructure/big-query.mdx
@@ -34,6 +34,10 @@ The [NEAR Public Lakehouse repository](https://github.com/near/near-public-lakeh
 
 </Info>
 
+<Warning>
+**NEAR Lake (the AWS S3 source) was deprecated on March 24, 2026** and no longer indexes new blocks. The NEAR Public Lakehouse / BigQuery dataset itself remains available; check the [NEAR Public Lakehouse repository](https://github.com/near/near-public-lakehouse) for the latest ingestion source.
+</Warning>
+
 ### Example Queries
 
 - _How many unique signers and accounts have interacted with my smart contract per day?_

diff --git a/data-infrastructure/data-services.mdx b/data-infrastructure/data-services.mdx
@@ -5,9 +5,15 @@ description: "Indexers are constantly listening for transactions and storing the
 
 Data Services are constantly listening to the blockchain, processing the transactions and storing them in a database that can be easily queried. You can use them to access blockchain data efficiently:
 
+<Danger>
+**NEAR Lake deprecated as of March 24, 2026.** The NEAR Lake (AWS S3 buckets) has stopped indexing new blocks. For new projects, use [Neardata](https://neardata.xyz) (direct replacement for NEAR Lake), [Data APIs](./data-api), [Goldsky](https://goldsky.com), or the [Nearcore Indexer](./near-indexer).
+</Danger>
+
+- [Neardata](https://neardata.xyz): a direct, drop-in replacement for NEAR Lake providing a stream of blocks for your custom indexer.
+
 - [BigQuery](./big-query): Blockchain data indexing in NEAR Public Lakehouse is for anyone wanting to understand blockchain data.
 
-- [NEAR Lake Framework](./near-lake-framework): a companion library to NEAR Lake. It allows you to build your own indexer that watches a stream of blocks **from a NEAR Lake data source** and allows you to **create your own logic to process that data**. Keep in mind this is **the one you want to use for future projects**, instead of the Indexer Framework. Read [why it is better](/data-infrastructure/near-lake-framework#comparison-with-near-indexer-framework).
+- [NEAR Lake Framework](./near-lake-framework) (**deprecated**): a companion library to NEAR Lake. It allows you to build your own indexer that watches a stream of blocks **from a NEAR Lake data source** and allows you to **create your own logic to process that data**. Read [why it is better](/data-infrastructure/near-lake-framework#comparison-with-near-indexer-framework).
 
 - [Indexer.xyz Multichain Indexer](https://indexer.xyz/): Indexer.xyz is an application layer that you can build your NFT or DeFi applications entirely on top of. In addition to raw transaction indexing, Indexer.xyz provides you with a standardized GraphQL API layer to easily tap into transactions across contracts and chains.
 

diff --git a/data-infrastructure/indexers.mdx b/data-infrastructure/indexers.mdx
@@ -95,9 +95,13 @@ Another example that highlights the need for a "wide query" is when you use a se
 
 ## Indexers in the NEAR ecosystem
 
-If you are ready to host your own indexer, we recommend using the [Near Lake Framework](./lake-framework/near-lake) as it is simple, reliable, and available in multiple languages (JavaScript, Rust, Python). 
+<Warning>
+**NEAR Lake deprecated as of March 24, 2026.** The NEAR Lake (AWS S3 buckets) has stopped indexing new blocks. For new projects, prefer [Neardata](https://neardata.xyz) (direct replacement), [Data APIs](./data-api), [Goldsky](https://goldsky.com), or the [Nearcore Indexer](./near-indexer).
+</Warning>
 
-If speed is critical for your indexing needs, consider using [Near Indexer](./near-indexer). However, please note that maintaining it can be more complex and costly, as it essentially operates as an independent node in the network. 
+If you are ready to host your own indexer, we recommend using [Neardata](https://neardata.xyz) — it is the direct replacement for NEAR Lake and provides a similar streaming API.
+
+If speed is critical for your indexing needs, consider using [Near Indexer](./near-indexer). However, please note that maintaining it can be more complex and costly, as it essentially operates as an independent node in the network.
 
 If you prefer not to host your own solution, you can utilize [third-party services](./data-services).
 
@@ -110,6 +114,6 @@ We hope this article gives you an understanding of the Indexer concept. Also, we
 ---
 
 ## What's next?
-We encourage you to learn more about the [Lake Indexer project](./lake-framework/near-lake). Please, proceed to [Tutorials](/data-infrastructure/tutorials/near-lake-state-changes-indexer) section to learn how to build an indexer on practice.
+You can learn more about the [Lake Indexer project](./lake-framework/near-lake) (note: deprecated since March 24, 2026). For new projects, see [Neardata](https://neardata.xyz) and the [Tutorials](/data-infrastructure/tutorials/near-lake-state-changes-indexer) section to learn how to build an indexer in practice.
 
 Alternatively, there are a few other third-party indexers that are tightly integrated with the NEAR ecosystem. You can review all of your data sourcing options (including The Graph, Pikespeak, SubQuery, and GoldSky) under [indexing tools](./data-services).
diff --git a/data-infrastructure/lake-framework/near-lake.mdx b/data-infrastructure/lake-framework/near-lake.mdx
@@ -4,6 +4,10 @@ title: NEAR Lake Indexer
 description: "Learn how NEAR Lake indexes the network"
 ---
 
+import NearLakeDeprecation from '/snippets/near-lake-deprecation.mdx';
+
+<NearLakeDeprecation />
+
 NEAR Lake is an indexer built on top of [NEAR Indexer Framework](https://github.com/near/nearcore/tree/master/chain/indexer) to watch the network and store all the event logs such as [FT Events](https://github.com/near/NEPs/tree/master/neps/nep-0300.md) and [NFT Events](https://github.com/near/NEPs/tree/master/neps/nep-0256.md) as JSON files on AWS S3.
 
 <Info>

diff --git a/data-infrastructure/near-indexer.mdx b/data-infrastructure/near-indexer.mdx
@@ -11,7 +11,7 @@ With the NEAR Indexer, developers can perform both high-level data aggregation a
 
 <Tip>
 
-For those searching to not build their own indexer, the [NEAR Lake Framework](./near-lake-framework) provides a simpler way to access blockchain data in real-time
+For those searching to not build their own indexer, [Neardata](https://neardata.xyz) provides a hosted stream of blocks as a direct replacement for the deprecated NEAR Lake.
 
 </Tip>
 
@@ -31,6 +31,10 @@ Learn how to run it following the [tutorial](./tutorials/near-indexer).
 
 ## Comparison with [NEAR Lake Framework](./near-lake-framework)
 
+<Warning>
+**NEAR Lake deprecated as of March 24, 2026.** The comparison below is kept for historical context. For new projects, see [Neardata](https://neardata.xyz) as a drop-in replacement for NEAR Lake.
+</Warning>
+
 Comparing to NEAR Lake Framework in terms of latency the NEAR Indexer is significantly faster as it reads data directly from the blockchain the same way as RPC nodes do.
 
 Feature | Indexer Framework | Lake Framework

diff --git a/data-infrastructure/near-lake-framework.mdx b/data-infrastructure/near-lake-framework.mdx
@@ -3,6 +3,10 @@ title: What is Lake Framework?
 description: "A library to build your own indexer using the existing Data Lake"
 ---
 
+import NearLakeDeprecation from '/snippets/near-lake-deprecation.mdx';
+
+<NearLakeDeprecation />
+
 NEAR Lake Framework is an ecosystem of library companions that read data from the [`NEAR Data Lake`](#data-lake). They allow you to build your own indexer by simply subscribing to the stream of blocks that is being constantly pushed to the [NEAR Lake](#data-lake)
 
 <iframe
@@ -31,7 +35,11 @@ https://github.com/near/near-lake-framework/
 
 ## Data Lake
 
-The NEAR Lake is a set of AWS S3 buckets which are constantly receiving new blocks from a [running indexer](https://github.com/aurora-is-near/near-lake-indexer) maintained by [Aurora](https://aurora.dev)
+<Warning>
+The NEAR Lake S3 buckets stopped receiving new blocks on **March 24, 2026**. The data described below is historical only.
+</Warning>
+
+The NEAR Lake is a set of AWS S3 buckets which were receiving new blocks from a [running indexer](https://github.com/aurora-is-near/near-lake-indexer) previously maintained by [Aurora](https://aurora.dev)
 
 Events such as [FT Events](https://github.com/near/NEPs/tree/master/neps/nep-0300.md) and [NFT Events](https://github.com/near/NEPs/tree/master/neps/nep-0256.md) are constantly being written as JSON files in two AWS S3 buckets:
 

diff --git a/data-infrastructure/tutorials/near-lake-framework.mdx b/data-infrastructure/tutorials/near-lake-framework.mdx
@@ -4,6 +4,9 @@ description: "This tutorial will guide you through building a simple indexer usi
 ---
 
 import {Github} from '/snippets/github.jsx';
+import NearLakeDeprecationTutorial from '/snippets/near-lake-deprecation-tutorial.mdx';
+
+<NearLakeDeprecationTutorial />
 
 In this tutorial, we will build a simple indexer using the NEAR Lake Framework. The indexer will listen for FunctionCalls on a specific contract and log the details of each call.
 

diff --git a/data-infrastructure/tutorials/near-lake-state-changes-indexer.mdx b/data-infrastructure/tutorials/near-lake-state-changes-indexer.mdx
@@ -3,6 +3,10 @@ title: "Tutorial: State Changes"
 description: "This tutorial will guide you through building a simple indexer using the NEAR Lake Framework. The indexer will listen for StateChange events and print relevant data about account changes."
 ---
 
+import NearLakeDeprecationTutorial from '/snippets/near-lake-deprecation-tutorial.mdx';
+
+<NearLakeDeprecationTutorial />
+
 This tutorial will guide you through building a simple indexer using the NEAR Lake Framework. The indexer will listen for `StateChange` events and print relevant data about account changes.
 
 <Note>

diff --git a/data-infrastructure/tutorials/nft-indexer.mdx b/data-infrastructure/tutorials/nft-indexer.mdx
@@ -3,6 +3,10 @@ sidebarTitle: NFT Indexer
 description: "Learn to build a simple NFT indexer with NEAR Lake Framework."
 ---
 
+import NearLakeDeprecationTutorial from '/snippets/near-lake-deprecation-tutorial.mdx';
+
+<NearLakeDeprecationTutorial />
+
 This tutorial will guide you through building a simple NFT indexer using the JavaScript version of the [NEAR Lake Framework JS](/data-infrastructure/near-lake-framework). The indexer will listen for `nft_mint` events and print relevant data about newly minted NFTs.
 
 The indexer is watching for `nft_mint` [Events](https://github.com/near/NEPs/tree/master/neps/nep-0297.md) and prints some relevant data:

diff --git a/data-infrastructure/tutorials/python-nft-indexer.mdx b/data-infrastructure/tutorials/python-nft-indexer.mdx
@@ -3,6 +3,10 @@ sidebarTitle: NFT indexer for Python
 description: "Learn to build a Python NFT indexer with NEAR Lake Framework"
 ---
 
+import NearLakeDeprecationTutorial from '/snippets/near-lake-deprecation-tutorial.mdx';
+
+<NearLakeDeprecationTutorial />
+
 This tutorial shows how to build a fully functional NFT indexer built using the [NEAR Lake Framework for Python](/data-infrastructure/near-lake-framework), which monitors `nft_mint` [events](https://github.com/near/NEPs/tree/master/neps/nep-0297.md) and outputs relevant details such as the `receipt_id` of the `Receipt` where the mint occurred, the marketplace, the NFT owner's account name, and links to the NFTs on the marketplaces.
 
 The final source code is available on the GitHub [`frolvanya/near-lake-nft-indexer`](https://github.com/frolvanya/near-lake-nft-indexer)

diff --git a/data-infrastructure/tutorials/running-near-lake/credentials.mdx b/data-infrastructure/tutorials/running-near-lake/credentials.mdx
@@ -3,6 +3,10 @@ title: Credentials
 description: "Learn how to provide AWS credentials to access NEAR Lake data"
 ---
 
+import NearLakeDeprecationTutorial from '/snippets/near-lake-deprecation-tutorial.mdx';
+
+<NearLakeDeprecationTutorial />
+
 To access the data provided by [NEAR Lake](../../near-lake-framework) you need to provide valid AWS credentials in order to be charged by the AWS for the S3 usage.
 
 <Info>

diff --git a/data-infrastructure/tutorials/running-near-lake/lake-start-options.mdx b/data-infrastructure/tutorials/running-near-lake/lake-start-options.mdx
@@ -3,6 +3,10 @@ title: Start options
 description: "Learn how to create an indexer using the NEAR Lake Framework."
 ---
 
+import NearLakeDeprecationTutorial from '/snippets/near-lake-deprecation-tutorial.mdx';
+
+<NearLakeDeprecationTutorial />
+
 This tutorial will guide you through creating a simple indexer using the NEAR Lake Framework that can start from a specified block height, the latest final block, or the last indexed block.
 
 ### Start Options

diff --git a/data-infrastructure/tutorials/running-near-lake/run-near-lake.mdx b/data-infrastructure/tutorials/running-near-lake/run-near-lake.mdx
@@ -3,6 +3,10 @@ title: Running Lake Indexer
 description: "Learn how to set up and run a NEAR Lake Indexer, including prerequisites, network configuration, and commands for syncing from the latest or a specific block."
 ---
 
+import NearLakeDeprecationTutorial from '/snippets/near-lake-deprecation-tutorial.mdx';
+
+<NearLakeDeprecationTutorial />
+
 At NEAR we already have a working solution to index blockchain data and store it in AWS S3 buckets called **NEAR Lake**. In this guide you will learn how to set up and run an instance of the NEAR Lake Indexer.
 
 The Lake Indexer setup consists of the following components:

diff --git a/data-infrastructure/what-is.mdx b/data-infrastructure/what-is.mdx
@@ -31,6 +31,11 @@ A large dataset with on-chain data publicly available on Google Cloud Platform.
 <hr subclass="subsection" />
 
 ## [NEAR Lake](./near-lake-framework)
+
+<Warning>
+**Deprecated as of March 24, 2026.** NEAR Lake (AWS S3 buckets) has stopped indexing new blocks. For new projects, use [Neardata](https://neardata.xyz) (direct replacement), [Data APIs](./data-api), [Goldsky](https://goldsky.com), or the [Nearcore Indexer](./near-indexer).
+</Warning>
+
 A solution that watches over the NEAR network and stores all the events for your easy access.
 
 - Cost-efficient solution: Cost-efficient solution for building self-hosted indexers in Rust, JavaScript, Python, Go and other languages

diff --git a/index.mdx b/index.mdx
@@ -229,7 +229,7 @@ async function main() {
     FTs, NFTs, DAOs, DEXes, liquid staking, and more — ready to use.
   </Card>
   <Card title="Data Infrastructure" icon="database" href="/data-infrastructure/what-is" cta="Explore" arrow>
-    Index and query on-chain data with NEAR Lake, BigQuery, and indexers.
+    Index and query on-chain data with Neardata, BigQuery, and indexers.
   </Card>
 </CardGroup>
 
diff --git a/snippets/near-lake-deprecation-tutorial.mdx b/snippets/near-lake-deprecation-tutorial.mdx
@@ -0,0 +1,3 @@
+<Danger>
+**NEAR Lake deprecated as of March 24, 2026.** This page uses the NEAR Lake Framework, which reads from AWS S3 buckets that have stopped indexing new blocks. For new projects, use [Neardata](https://neardata.xyz) (direct replacement), [Data APIs](/data-infrastructure/data-api), [Goldsky](https://goldsky.com), or the [Nearcore Indexer](/data-infrastructure/near-indexer).
+</Danger>
diff --git a/snippets/near-lake-deprecation.mdx b/snippets/near-lake-deprecation.mdx
@@ -0,0 +1,13 @@
+<Danger>
+**Deprecated: NEAR Lake is no longer maintained**
+
+As of **March 24, 2026**, NEAR Lake (AWS S3 buckets) has stopped indexing new blocks and is no longer maintained by Aurora. Existing data remains accessible for historical use, but no new blocks will be written.
+
+Recommended alternatives:
+
+- **[Neardata](https://neardata.xyz)** — direct drop-in replacement for NEAR Lake
+- **[Data APIs](/data-infrastructure/data-api)** — community APIs from [NearBlocks](https://nearblocks.io), [Pikespeak](https://pikespeak.ai), and [FastNear](https://fastnear.com)
+- **[Goldsky](https://goldsky.com)** — managed indexer service
+- **[Nearcore Indexer](/data-infrastructure/near-indexer)** — run your own indexer node
+
+</Danger>