subgraph runtime // hosted deploys // graph-compatible indexing made by turinglabs_
UG

Self-hosted indexing infrastructure

UGraph

A portable Graph-compatible runtime for teams that want to deploy subgraphs, index chain data, and expose versioned GraphQL endpoints without handing the control plane to a hosted vendor.

01 Graph-compatible developer workflow

Keep subgraph project structure familiar while moving indexing and hosting into infrastructure you control.

02 Hosted deploys without vendor lock-in

The CLI uploads bundles to your instance and exposes Graph Node-style URLs for apps and index consumers.

03 Operator-grade visibility

Health, GraphiQL, metrics, deployment metadata, and entity-change history live next to the query surface.

Architecture

Shared feed, isolated subgraphs.

UGraph reads each chain once, stores canonical blocks and logs in a shared feed, then lets every subgraph consume only the events it subscribed to.

chain readers one reader per chain id

Poll RPC, handle reorgs, and write raw blocks/logs once.

Postgres raw feed canonical blocks + logs
growfi@4.0.4 public latest

Promoted GraphQL endpoint for apps.

growfi@next private staging

Sync and compare before promotion.

other-subgraph@1 same feed, own store

Independent entity state and query visibility.

CLI

Remote deploys from your terminal.

Hosted instances accept authenticated bundle uploads and expose Graph Node-style paths for each promoted version.

ugraph auth login \
  --endpoint https://ugraph.example.com \
  --api-key $UGRAPH_API_KEY

ugraph deploy \
  --provider remote \
  --deployment growfi \
  --version 4.0.4 \
  --visibility public \
  --chain-id 11155111 \
  --manifest subgraph.yaml \
  --rpc-url $SEPOLIA_RPC_URL

Why it exists

Portable indexing with real operator controls.

compatibility

Graph-shaped inputs

UGraph targets the standard subgraph developer workflow while keeping runtime behavior testable through fixture matrices.

control

Private or public instances

Deployment ownership, API-key scopes, and query visibility are configured per instance, not hardcoded into a single SaaS model.

operations

Observable runtime

The operational surface shows checkpoints, entity deltas, GraphiQL, health, and Prometheus metrics from the same node.

versions

Promote when ready

New versions sync into their own storage deployment before the latest alias moves, keeping old endpoints queryable.