---
title: "RedlineFeed | Normalized Multi-Asset Market Data | Redline"
description: "RedlineFeed consolidates direct exchange feeds from 230+ global venues into a single normalized stream, removing the need to maintain individual venue connections. Distributed from a managed publishing hub with embedded InRush receivers at each application server, it adds only single-digit microseconds in co-located deployments."
source: https://www.pico.net/products/data-and-trading-software/redline-feed/
markdown_url: https://www.pico.net/products/data-and-trading-software/redline-feed.md
---

# RedlineFeed
Normalized, low-latency market data from 230+ venues, delivered via a fully managed hub and embedded receivers across your enterprise.

- Hosted and managed market data distribution eliminating exchange connectivity overhead
- Single API access to multi-asset class data (equities, options, futures, FX, fixed income)
- Customizable views: composite books, synthetic NBBO/EBBO, user-defined depth, conflation
- Embedded InRush Ticker Plant receivers with local book reconstruction

## What is a consolidated market data feed?

A consolidated market data feed aggregates direct exchange feeds into a single normalized stream, eliminating the need for each subscriber to maintain individual exchange connections. RedlineFeed is distributed from a managed publishing hub with embedded InRush Ticker Plant receivers at each application server, providing enterprise-wide access to multi-asset class market data via a single API.

## Choose your deployment model

### Shared service

Cost-effective multi-tenant publishing hub for firms without dedicated infrastructure requirements.

### Dedicated service

Private publishing hub for firms requiring isolated infrastructure and custom configuration.

### Managed hosting

Full turnkey service with colocation, connectivity, and 24/7 monitoring.

### Self-managed deployment

Deploy RedlineFeed with your infrastructure team using Redline monitoring tools.

## Common use cases (and what you'll achieve)

### Enterprise market data distribution

- Distribute normalized data to hundreds of endpoints across trading, risk, and surveillance
- Eliminate per-app exchange connectivity requirements

### Rapid market entry and venue onboarding

- Add new trading venues without managing feed protocols or connectivity
- Redline handles exchange integration at the publishing hub

### Simplified API integration

- Write to one API (InRush) to access all published venues
- Optional Bloomberg bridge for teams that wish to Bloomberg

### Custom market views

- Generate composite books, synthetic NBBO/EBBO, and user-configurable depth feeds
- Conflated quotes reduce processing burden for slow consumers

### Lower exchange connectivity costs

- Centralize direct feeds at the publishing hub and distribute via multicast
- Reduce or eliminate per-server exchange fees

## RedlineFeed FAQs

### What is the difference between RedlineFeed and direct exchange feeds?

RedlineFeed consolidates direct exchange feeds into a single normalized distribution, eliminating the need for each subscriber to maintain individual exchange connections, manage feed protocol changes, or handle connectivity infrastructure. You write to one API (InRush) instead of managing 230+ venue-specific protocols.

### How does RedlineFeed compare to direct feeds in terms of latency?

RedlineFeed adds single-digit microseconds compared to direct feeds, measured from exchange tick to trading application in co-located deployments. The latency trade-off is minimal compared to the operational benefits of centralized connectivity and normalized distribution.

### What does "embedded InRush receiver" mean?

Each subscribing application server runs a local instance of InRush Ticker Plant that receives the RedlineFeed multicast stream and reconstructs full-depth order books in memory. Applications access data via the low-latency InRush API as if connecting directly to exchanges.

### Can I customize the market data views RedlineFeed publishes?

Yes, especially with dedicated service. Options include synthetic NBBO/EBBO calculation, composite books across venues, user-configurable depth levels, conflated quotes, and symbol striping to specific multicast channels.

### What deployment models does RedlineFeed support?

RedlineFeed offers shared service (multi-tenant hub), dedicated service (private hub), fully managed hosting (turnkey with Redline), or self-managed deployment (you operate infrastructure with Redline monitoring tools).

### How does RedlineFeed handle exchange connectivity and protocol changes?

Redline manages all exchange connectivity, feed protocol updates, and venue changes at the publishing hub level. Subscribers are insulated from these operational burdens: updates are deployed centrally without requiring changes to your application servers.

### What asset classes and venues does RedlineFeed support?

RedlineFeed supports 230+ global venues across equities (U.S., Europe, Asia-Pacific), equity options, futures, foreign exchange (FX), and fixed income markets. Contact Redline for specific venue availability.

### Can RedlineFeed integrate with legacy applications?

Yes. In addition to the native InRush API, RedlineFeed provides Bloomberg and Reuters API bridges for legacy applications that cannot be rewritten.

### What is a market data feed handler?

A feed handler decodes one venue's market data protocol and turns it into a usable stream, handling sequencing, gap recovery and book state for that venue specifically. RedlineFeed runs feed handlers for 230+ venues and consolidates them into a single normalised output, so the per-venue work does not land on your team. The surrounding system is described in [what is a ticker plant](https://www.pico.net/kb/what-is-a-ticker-plant/).

## Start with the right service model

Talk to a Redline specialist about your exchange coverage requirements, infrastructure preferences (shared, dedicated, or self-managed), and enterprise distribution needs.