# We ship the data backend with your team

Point us at the programs your product depends on. We stand up the indexers, the backfill, and the APIs. You own the product.

Indexing a protocol is custom, not self-serve. We work with your team to scope the data, ship the backend, and keep it running.

- Contact: https://www.struct.to/contact

## Live firehose and full backfill

- Markets, trades, positions, and candles. One schema for the protocols we index with you.
- Millisecond latency: real-time feeds in ~10ms, 99.99% uptime, automatic failover.

## What we deliver once the backend is live

Normalized, query-ready data in one schema. Your team never runs an indexer.

- Normalized, not raw: deduped, reconciled, and consistently typed. A Solana trade and an Ethereum trade share the same shape.
- Complete history: backfilled from genesis for the datasets in scope. Every trade, transfer, and price, from the first block to now.

Data types we deliver:

- Markets & Events: every market and event, with live resolution status.
- Trades: every fill and transfer, normalized across venues.
- Wallets & Positions: holdings, cost basis, and realized PnL for any address.
- Candlesticks & Prices: OHLCV candles and price series from 1 second to 1 day.

## APIs we stand up for your product

We ship REST, websockets, webhooks, and SDKs against the data we index with you. Power internal apps or open programmatic access for anyone to build on.

- REST, websockets, and webhooks
- TypeScript SDK and MCP server
- Private or public API access

## Reliability we run for you

We run Struct beside your existing pipeline so you can cut over the moment it breaks. Backed by a 99.99% uptime SLA and ~10ms median latency, measured continuously in production.

- 99.99% uptime SLA
- Automatic failover
- Redundancy we operate, no rework

## Index any protocol you name

Point Struct at the programs and contracts your app depends on. We stand up the live firehose and full historical backfill, normalized into one schema.

- Live firehose ingestion
- Full historical backfill
- Delivered in one consistent schema

## Delivered into the stack you already run

Realtime Kafka sync and managed backfill into the Postgres, ClickHouse, or Redis you already run.

- Postgres
- ClickHouse
- Kafka
- Redis

## Your second data team

We build custom integrations like an extension of your team, then keep the backend running as you add protocols and venues.

### We build it with you

New protocols and venues without asking your team to rebuild the data layer, so the product keeps shipping as coverage grows.

- 1B+ requests/day in production
- No rate limits on enterprise
- Dedicated infrastructure and engineers

How we work:

- 24/7 support on calls, Telegram, and Slack, whenever you need us.
- Your second data team: we build custom integrations like an extension of your team.
- Volume pricing: discounts and custom rate limits as you grow.
- White-glove migration: we move you off your own pipeline with zero downtime.

## Frequently asked questions

### Getting started

- What do you build with a team? The data backend their product runs on. We index the programs and contracts you depend on, backfill history, and stand up REST, websockets, webhooks, or warehouse delivery. You own the product.
- Do we still need to run our own indexer? No. We run the indexers, the backfill, and the pipeline. Your team keeps the product. We work as an extension of your data team until the backend is live.
- How do we get started? Indexing a protocol is custom, not self-serve. Contact us and we'll scope your data, the delivery surface, and the timeline, then build it with you.

### Data & coverage

- What can you index? Any chain. The programs and contracts your product depends on — Solana, Ethereum, Ink, Arc, or a network we have not listed. Polymarket is available self-serve. Everything else we scope and ship with your team.
- How complete is the history? We backfill from genesis for the datasets in scope, so you get the entire history alongside the live firehose.
- How fresh is the data? Real time. Data is queryable the moment it lands onchain, with roughly 10ms median latency from onchain event to your app. No polling loops, no cache windows.

### Failover & reliability

- How does failover indexing work? We run Struct beside your existing pipeline so you can cut over the moment it breaks. It is a redundancy layer we operate for you, with no rework required to switch.
- What is the uptime SLA? A 99.99% uptime SLA with automatic failover, measured continuously in production. Live metrics and status are public.

### Pipelines & engagement

- Can you deliver into our own warehouse? Yes. We deliver backfilled history and realtime Kafka sync into the Postgres or ClickHouse you already run. We run the indexers, the pipeline, and the schema, you keep the queries.
- How is this priced? Custom, scoped to the protocols, history, and delivery you need. Volume discounts, dedicated infrastructure, and custom rate limits are part of the engagement. Contact us and we'll put a number on it.

## Learn more

- [Contact](https://www.struct.to/contact)
- [Prediction markets](https://www.struct.to/solutions/prediction-markets)
- [Pricing](https://www.struct.to/pricing)