Indexing Co vs Goldsky

How Indexing Co's custom pipeline platform compares to Goldsky's managed subgraph hosting and Mirror streaming service.

Goldsky started as managed subgraph hosting, taking the operational pain out of running subgraphs yourself. They've since added Mirror, a data streaming product that pipes indexed data into your database. It's a step forward from raw subgraphs, but the underlying architecture carries the same limitations.

Architecture

Goldsky: Managed Subgraphs + Mirror Streaming

Goldsky's core is hosted subgraph infrastructure with sub-second indexing latency. You deploy subgraphs to Goldsky instead of running them yourself. Mirror extends this by streaming subgraph output (or raw blockchain data) into PostgreSQL or other targets, with SQL transforms and external HTTP handlers for custom logic.

This means fast deploys, sub-second latency, and less operational overhead than self-hosted subgraphs. Mirror adds flexibility beyond raw subgraphs, but the subgraph side still carries the contract-centric model and AssemblyScript requirement.

Indexing Co: Custom Pipelines, Full Control

Indexing Co doesn't use subgraphs at all. You define pipelines that source events from any chain, transform them with TypeScript, and deliver directly to your infrastructure. The transformation layer is fully custom: you write the logic, not a subgraph mapping.

Feature Comparison

	Indexing Co	Goldsky
Architecture	Custom pipelines	Managed subgraphs + Mirror
Transform language	TypeScript	AssemblyScript (subgraphs), SQL + HTTP handlers (Mirror)
Data destination	PostgreSQL, BigQuery, webhooks, GraphQL	PostgreSQL, webhooks (via Mirror)
Multi-chain	Single pipeline definition	Separate subgraph per chain
Block-to-database delivery	sub-500ms (dedicated infra)	Sub-second via Mirror; seconds via hosted GraphQL
Chains	100+	150+
VM support	EVM, Solana, Cosmos, Move	EVM + Solana, Starknet, Sui, others
Custom transforms	Full TypeScript control	Subgraph mappings or Mirror SQL/HTTP handlers
Schema changes	Hot-swap, no re-index	Re-index required
Pricing model	Pipeline-based	Subgraph + streaming based

Key Differences

Transform Control Goldsky's subgraphs use AssemblyScript for transformation. Mirror adds SQL transforms and external HTTP handlers, giving you more flexibility at the streaming layer. But the two systems are separate: subgraph logic and Mirror logic don't share a unified pipeline model. With Indexing Co, transformation is a single TypeScript layer in every pipeline. One language, one model, no intermediate step.

Multi-Chain Approach Goldsky requires separate subgraphs for each chain. Mirror can stream from multiple subgraphs, but the indexing is still per-chain. Indexing Co defines multi-chain pipelines natively: one pipeline, multiple chains, unified output schema.

Beyond Contract Events Goldsky has expanded beyond EVM with support for Solana, Starknet, Sui, and others. Mirror can stream raw blockchain data beyond contract events. But the primary workflow is still subgraph-driven, and cross-chain analytics require stitching together separate subgraphs. Indexing Co indexes contracts, wallets, blocks, and transactions from the same pipeline with a unified multi-chain definition.

When to Use What

Use Goldsky if

You have existing subgraphs and want managed hosting with sub-second latency, or Mirror's SQL transforms and streaming model fit your workflow.

Use Indexing Co if

You want a unified pipeline model with TypeScript transforms, single-definition multi-chain pipelines, or need to combine contract events with wallet/block/transaction data in one pipeline.

Get Started

Get a Demo | Open the Console