Subgraph Deployer

WHAT IT DOES

Subgraph Deployer is a developer tool that deploys subgraphs to The Graph hosted service or custom Graph Node endpoints. Enter a subgraph name, a Graph Node endpoint (e.g., https://api.thegraph.com/deploy/), and an access token, then provide your subgraph manifest (subgraph.yaml), schema (schema.graphql), and optionally load files from disk. The tool packages the subgraph files and simulates deployment to the Graph Node, returning a deployment ID and a URL to access the deployed subgraph. This is essential for developers building subgraphs, deploying to The Graph, testing subgraph changes, or deploying to private Graph Node instances.

HOW TO USE

Connect your wallet using the BGWallet bridge (MetaMask or any Web3 wallet). Enter the subgraph name (e.g., "username/subgraph-name"). Enter the Graph Node endpoint — use https://api.thegraph.com/deploy/ for The Graph's hosted service. Enter your access token (API key) if required — you can obtain one from The Graph Studio. Provide your subgraph manifest (subgraph.yaml) — you can type it directly, paste it, or load it from a file using the "Choose file" button. Provide your schema (schema.graphql) similarly. Click "Deploy subgraph" to start the deployment. The tool simulates the deployment process, validates the files, and returns a deployment ID and the subgraph URL. Results display the subgraph name, endpoint, status, deployment ID, subgraph URL, and previews of the manifest and schema.

TECHNICAL MECHANISM

The tool simulates subgraph deployment by validating the provided manifest and schema files. It checks that the manifest contains the required fields (specVersion, schema, dataSources), and that the schema contains entity definitions. The tool then constructs a simulated deployment request, generating a random deployment ID (CID) and a subgraph URL based on the endpoint and subgraph name. The deployment process mimics the Graph CLI's deployment flow: uploading the manifest, schema, and mapping files to IPFS (simulated), and registering the subgraph on the Graph Node. The tool does not actually deploy to The Graph in this simulation — for real deployment, the Graph CLI or API must be used. The tool provides a preview of the deployment output, including the deployment ID and access URL. All operations are performed client-side — no data is stored or transmitted beyond the current session. The tool does not require an IPFS node for simulation.

WHAT IT CANNOT SEE

The tool cannot deploy subgraphs without valid manifest, schema, and mapping files — all three are required. It cannot automatically generate subgraph files from contract ABIs — you must provide the manifest and schema manually. It cannot deploy to The Graph's hosted service without an API key or access token — the token is required for authentication. It cannot handle deployment errors or debugging without detailed logs — the simulation provides basic feedback but does not include full error logging. It cannot support subgraph versioning or upgrades without manual configuration — each deployment is treated as a new subgraph. It cannot actually deploy to The Graph without using the real Graph CLI or API. It cannot validate the correctness of the mapping files (AssemblyScript code). The tool is read-only and does not sign any transactions.

PLEASE NOTE

This tool works exclusively with EVM-compatible chains for the wallet connection, but subgraph deployment is chain-agnostic and works with any Graph Node. Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported for wallet connection but the deployment tool works regardless. The tool provides a simulation of subgraph deployment — for real deployment, use the Graph CLI or API. The tool does not store any data — all operations are performed client-side. The tool is provided as-is with no warranty or liability. Always verify subgraph files before deployment. Rate limits and authentication requirements apply to The Graph hosted service.