How to deploy a no-code subgraph in 5 minutes

All you need is the smart contract address

If you plan to update or redeploy your subgraph in the future, create and use a tag before you start querying the endpoint.

Tags let you hot-swap new deployments under the same URL later without changing your front-end code.

Getting started

1. In the Ormi dashboard, click 0xGraph
2. Expand the Migrate from contract address section

Note: If you already deployed a subgraph, click on Deploy Subgraph for the window to pop up.

For this example, we’ll use VaultBridge’s Bridged USDC:

• Contract address: 0x203A662b0BD271A6ed5a60EdFbd04bFce608FD36
• Network: Katana
• Name: katana-vbusdc
• Version: v.1

Note: If the ABI cannot be auto-fetched, you may need to upload it manually.

For vbUSD, you will need to fetch the implementation contracts’ ABI, so head over to Katanascan and search for the vbUSD contract.

Fetching a contract’s ABI

Click on the Contract tab

Click Read or Write as Proxy Tab

Implementation contract address: 0x5e875267f65537768435C3C6C81cd313a570B422

Click on the implementation contract and press the contract tab

Scroll down to the bottom, and copy the Contract ABI.

Paste the Contract ABI into this section and press submit

Once submitted, the system will process your request. When it finishes loading, you’ll be taken to the next screen.

When your subgraph finishes syncing, you can start querying immediately by clicking the graphql link.

Next steps

How to query a subgraph

Learn how to run GraphQL queries to fetch smart contract data from deployed subgraphs.

How to monitor your subgraph

Learn how to monitor your subgraph syncing progress and logs after deployment.