> ## Documentation Index
> Fetch the complete documentation index at: https://ormilabs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# The new home of Chainstack Subgraphs

Chainstack is sunsetting its Subgraphs service. Ormi has been selected to continue operating and supporting existing Chainstack subgraphs.

## Summary

* Chainstack Subgraphs end on **February 1, 2026**
* Ormi is now the official home for existing Chainstack Subgraphs

## TL;DR for Chainstack Subgraph users

<Info>
  ### Status

  **Your subgraphs are safe**

  * Chainstack Subgraphs end on **February 1, 2026**
  * **Ormi is handling the migration of existing subgraphs**

  ### What you need to do

  **Minimal action required**

  * Most users only need to **create an Ormi account and swap their endpoints**
  * Join the **dedicated Telegram group** (invitation sent via email)
  * If more action is needed, **Ormi will contact you**

  ### What you get

  **Free access & support**

  * Free access: **Feb 1 → Mar 1, 2026**
  * Pricing remains aligned with Chainstack
</Info>

## What's happening

Chainstack is discontinuing its Subgraphs offering. To ensure continuity, all existing subgraph workloads are being migrated to Ormi.

Starting **February 1, 2026**, your subgraphs will be fully synced and queryable on the Ormi infrastructure.

**Ormi will be handling the migration so for most users, no actions are required beyond swapping endpoints.**

## Why Ormi?

Chainstack selected Ormi because it operates reliably under real-world traffic and production workloads.

Ormi is built for teams that need:

* data at the tip of the chain
* consistent performance at scale
* zero throttling during traffic spikes
* end-to-end monitoring and observability tools

Today, Ormi powers production workloads across crypto and DeFi, supporting **\$50B+ TVL** and **\$100B+ in annual transaction volume**.

This makes Ormi a natural fit to continue supporting Chainstack users without disruption.

## What we've already handled

**Ormi is handling the migration of active Chainstack Subgraphs so most users do not need to migrate data or redeploy Subgraphs.**

<Info>
  Subgraphs are migrated on a rolling basis. **To complete the migration, all users must [**create an Ormi account**](https://app.migration.ormilabs.com/) so we
  can attach existing subgraphs to your environment.**
</Info>

## If your subgraph needs attention

While Ormi handles the migration process end to end, there are rare cases where additional steps may be required due to factors outside of Ormi’s control. These can include:

* IPFS deployment issues that require deploying the subgraph from source
* Indexing failures caused by mapping or schema issues in the subgraph code

If this happens, the Ormi team will work directly with you to resolve it.

To ensure we can act swiftly, we strongly recommend that all users:

* [Create an Ormi account](https://app.ormilabs.com/) as soon as possible
* Join the dedicated Telegram group when you receive the email invitation

This allows us to coordinate efficiently and keep your subgraphs running smoothly.

If a subgraph requires action and we are unable to reach the owner through available channels, data access on **February 1** cannot be guaranteed.

## What you need to do

In most cases, you will only need to swap out your subgraph endpoint.

<Steps>
  <Step title="Create an Ormi account">
    [Sign up for an Ormi account](https://app.ormilabs.com/) to get started.
  </Step>

  <Step title="Generate an API key">
    Follow our guide to [generate your API key](subgraphs/quickstart/generate-an-api-key).
  </Step>

  <Step title="Replace your Chainstack endpoint">
    Update your application to use your new Ormi endpoint instead of the Chainstack endpoint.

    **To find your Ormi endpoint**

    <Frame>
      <img src="https://mintcdn.com/ormilabs/XEL8aVMOSaZH2cuR/images/0xgraph/endpoint-access2.png?fit=max&auto=format&n=XEL8aVMOSaZH2cuR&q=85&s=826071b1abb801feaec154427be43fc9" alt="endpoint-access-api" width="2195" height="1168" data-path="images/0xgraph/endpoint-access2.png" />

      <figcaption>REST API</figcaption>
    </Frame>

    **Endpoint differences:**

    | **Chainstack**                                                               | **Ormi**                                                                                    |
    | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
    | `https://<network>.graph-<region>.p2pify.com/<project_id>/<deployment_slug>` | `https://api.subgraph.ormilabs.com/api/public/query_deployment?subgraph_id=<deployment_id>` |

    **Note**: Your exact endpoint may differ depending on your subgraph and environment. Always use the Ormi dashboard to copy the correct endpoint.
  </Step>

  <Step title="If your subgraph needs attention">
    {" "}

    <Info>Optional - only if notified. If this applies to you, we'll contact you directly with specific instructions.</Info>

    Some subgraphs may require manual intervention due to:

    * IPFS migration issues
    * Mapping or schema errors
  </Step>
</Steps>

## To deploy a Subgraph on the Migration Environment

<Warning>**Important**: This environment is different from Ormi’s general subgraph environment.</Warning>

To deploy a subgraph in the migration environment, follow the steps below:

### Step 1: Use the migration environment

Make sure you are using the migration-specific app (not the standard Ormi app):

```
https://app.migration.ormilabs.com/
```

### Step 2: Deploy your Subgraph

Use the following command to deploy:

```
graph deploy <your_subgraph>
--node https://api.subgraph.migration.ormilabs.com/deploy
--ipfs https://api.subgraph.migration.ormilabs.com/ipfs
--deploy-key <api_key>
```

### Notes

* Replace `<your_subgraph>` with the subgraph name configured for the migration environment.
* Replace `<api_key>` with the deploy key generated from the migration app, not from the general Ormi environment.
* Using keys or endpoints from the standard environment will cause the deployment to fail.

## Monitoring and platform visibility

Once live, you can use the Ormi dashboard to:

* view indexing speed,
* check query performance
* monitor availability

Check out our [monitoring docs](subgraphs/manage-and-monitor/monitor-subgraph) to learn more about Ormi's monitoring capabilities.

You can also check platform health here:

➡ [Ormi Status Page](https://ormi-labs.instatus.com)

## Learn more about Ormi

If you want to explore everything Ormi offers beyond subgraph migration — including features and environments— visit our documentation:

➡ **[Ormi Subgraph Features](/docs/subgraphs/features)**

## Free access for Chainstack Subgraph users

All Chainstack subgraph users receive **one month of free access** to Ormi to validate performance and explore the platform.

Free access runs through **March 1, 2026 at 00:00 UTC**.

**No action is required to activate this**.

## Pricing

To keep the transition predictable, Ormi is adopting Chainstack’s existing billing structure for migrated users.

This means:

* familiar pricing
* no changes to usage calculation
* no billing surprises during the transition

You will have time to review performance and usage during the free period. If you have billing questions, our team is available to help.

## Billing and project ownership

Billing on Ormi is managed **at the project level**.

* Only the **project owner** can manage billing and payment methods
* We recommend that the person responsible for payments **creates the project**
* Additional users can then be invited to the project with appropriate access

For a detailed walkthrough on configuring payments and selecting a plan, see our [Billing Setup Guide](subgraphs/tutorials/billing-setup-chainstack).

## Environments

Most teams start in a shared environment.

For higher-throughput or production-critical workloads, Ormi also offers:

* Dedicated environments for reserved capacity
* Custom environments for large or complex deployments

Pricing details will be shared separately. If you want help choosing the right setup, our team can review your usage with you.

## Support and escalation

Our engineers are actively monitoring all migrated subgraphs. We have created a dedicated support channel for Chainstack users. You will receive an email invitation to join the Telegram group via email.

You can also reach us through the [Contact Us](https://www.ormilabs.com/contact-us) page.

To report an issue, please **submit a ticket in the app platform**.

<Frame>
  <img src="https://mintcdn.com/ormilabs/Tp_jQ45n5B1KcxhR/images/0xgraph/support-ticket.png?fit=max&auto=format&n=Tp_jQ45n5B1KcxhR&q=85&s=5feed6be3bc9c66df12f568d7a0bcb1d" alt="0xGraph support ticket" width="1911" height="907" data-path="images/0xgraph/support-ticket.png" />

  <figcaption>support-ticket</figcaption>
</Frame>

## FAQ

<Accordion title="Do I need to reindex my subgraphs?">No. All subgraphs already synced on Ormi.</Accordion>

<Accordion title="Will my GraphQL schema or queries change?">No. Ormi is fully Graph-compatible. Existing queries continue to work.</Accordion>

<Accordion title="Is Ormi production-ready?">
  Yes. Ormi runs production subgraphs for high-throughput protocols and ecosystems and is designed to operate reliably under sustained load.
</Accordion>

<Accordion title="How is Ormi different from The Graph, Goldsky, and other indexers?">
  Legacy indexers were designed for slower chains and lighter workloads, making them struggle under real-time, high-volume demand.

  Ormi is built differently:

  * A next-generation indexing engine purpose-built for fast chains and high-throughput applications.
  * Optimized for real-time data at scale, even during mass adoption and traffic spikes.
  * Runs on a vertically integrated stack across bare-metal and cloud infrastructure, ensuring no single point of failure.
  * Scales elastically to handle any chain or application workload without throttling.

  To learn more about our technology, visit our [technology page](https://www.ormilabs.com/why-ormi).
</Accordion>

<Accordion title="What happens if I notice an issue?">
  Join the Telegram support group, submit a ticket in the app, or [contact us](https://www.ormilabs.com/contact-us) directly. Our team will investigate and
  assist.
</Accordion>

<Accordion title="Can I move to a Dedicated or Custom Environment?">
  Yes. Dedicated or Custom Environments are available for teams with higher throughput or stricter reliability requirements.

  [Contact us](https://www.ormilabs.com/contact-us) for more details.
</Accordion>

## Next steps

After creating an Ormi account and joining the Telegram support group, please wait for further instructions confirming that your subgraph is fully synced.

1. Wait for confirmation that your subgraph is live on Ormi
2. Swap your endpoint using the quickstart guide
3. Verify indexing and queries in the dashboard
4. Reach out if you want help validating your setup