Market data feeds: what each tick really costs

Operations dashboard showing market data feed metrics and trading infrastructure costs
Photo by Aedrian Salazar on Pexels

At the end of a bad week, an operations lead looks at a dashboard full of red: feed-handler CPU peaked during the open, a venue connection dropped, and the monthly data bill is higher than forecast. The word "tick" appears in all three reports, but it does not mean the same thing in each.

For a broker or prop firm, the cost of a tick is not simply the exchange fee divided by the number of prices received. It includes the right to access and use the data, the network and compute needed to process it, and the operational work required to keep it available. A useful estimate starts by defining the event being counted.

A tick is an event, not a standard unit

A feed can carry trades, quote changes, order-book updates, status messages and administrative events. A vendor may call each message a tick. An internal analytics system might count only trades or changes to the best bid and offer. Those totals can differ by an order of magnitude without either system being wrong.

Consider a liquid instrument. One market update may change the best bid, while another changes the ask.

A depth feed can also send several updates to levels away from the touch. Some protocols transmit incremental changes; others send snapshots, often after a recovery or at defined intervals. A feed handler may receive one network packet containing multiple messages, then publish each message separately to internal consumers.

These distinctions matter for both capacity and cost. If a vendor charges by connection, instrument, user or message volume, the relevant billing unit may differ from the event count used to size a system. Before comparing prices, write down what each counter measures:

  • Exchange event: an update as defined by the venue's protocol, including its treatment of trades, quotes and book changes.
  • Vendor message: the data product delivered over a connection, which may be normalised, filtered or bundled.
  • Internal event: the record published to a strategy, risk service, chart or client-facing system.
  • Billable unit: the unit in the contract, such as a user, device, connection, instrument, redistribution count or non-display use.

Keep these measures separate in dashboards. A single "ticks per second" graph can hide whether a load spike came from more venue updates, more downstream fan-out or a change in how the application counts messages. For background on the systems and providers involved, the Trading Technology infrastructure coverage provides useful market context.

What the feed invoice buys

The bill usually combines several layers. The exchange sets permissions and fees for its data. A vendor or consolidator may charge for access, normalisation, connectivity or support. The firm then pays for infrastructure, network paths and the people who monitor and maintain the service.

Exchange fees depend on venue, product, depth and user classification. Non-professional status is generally subject to the exchange's definition and reporting rules, not a label a broker can assign freely. Professional users, firms redistributing data and systems using data for non-display purposes can face different terms. A broker also needs to account for client entitlements, reporting and evidence that access was granted correctly.

The figures below are typical market ranges for planning, in US dollars per user per month. They are indicative rather than quotes. Venue schedules, bundles, professional status and local taxes can move the actual charge substantially.

Data productTypical market rangeCharging basisCommon cost driver
US equities, top of book, non-professional$1-$5Per user, per exchangeExchange and display entitlement
US equities, depth, non-professional$10-$25Per user, per exchangeNumber of book levels and venue
US equities, top of book, professional$25-$100Per user, per exchangeProfessional classification and venue
US equities, depth, professional$100-$300+Per user, per exchangeDepth product and exchange schedule
US futures, top of book, non-professional$3-$15Per user, per exchangeContract group and display use
US futures, professional depth$30-$150+Per user, per exchangeVenue, depth and professional status

Those per-user numbers do not describe the cost of a production feed plant. A market-data vendor may quote a separate service fee, and direct connectivity can add cross-connects, circuits and support.

A small deployment may spend hundreds or a few thousand dollars monthly on some components; a multi-venue, redundant institutional setup can run into tens of thousands or more. Treat those as typical planning ranges, not a tariff. Ask suppliers to separate exchange pass-through fees from their own charges.

Licensing can be the largest risk in an otherwise tidy technical budget. A feed received for internal trading is not automatically licensed for display to clients, redistribution to affiliates or use in a derived product. "Non-display" can cover systems such as automated trading and analytics, depending on the exchange terms. Include legal, compliance and vendor teams when defining the permitted use, rather than relying on an engineer's interpretation of a data field.

Measure the workload before setting a price

A practical cost per tick needs a defined perimeter. One useful internal measure is the fully loaded monthly cost of a feed path divided by the number of valid events delivered to a specified consumer. State whether the denominator counts raw exchange messages, normalised events or events after filtering. Otherwise, two teams can report different costs for the same feed.

For example, suppose a desk allocates $28,000 a month to exchange and vendor charges, network, compute and support for a set of feeds. If those feeds deliver 2.8 billion normalised events in the month, the allocated cost is $0.00001 per event, or $10 per million events. This is an illustrative calculation, not a benchmark. Change the feed scope, allocation method or event definition and the answer changes.

Use a repeatable sequence to make the calculation operational:

  1. Inventory the products. Record each venue, instrument group, data depth, protocol, vendor and intended use. Note whether the connection is direct or vendor-delivered.
  2. Map permissions to users and systems. Separate display, non-display and redistribution rights. Record the exchange's definition of each user class and the evidence needed for audits.
  3. Measure peak and normal traffic. Capture messages per second, packet rate, bytes per second and burst duration. Include open, close, auction and scheduled announcement periods, not only daily averages.
  4. Measure the processing path. Track decode time, normalisation time, queue depth, dropped or rejected messages, recovery traffic and fan-out to downstream consumers.
  5. Build a complete monthly cost. Include exchange and vendor charges, network ports and circuits, cloud or colocation allocation, storage, monitoring and on-call support. Show one-off implementation costs separately.
  6. Divide with a stated denominator. Calculate cost per million events for a defined feed path, then compare it with latency and availability. Keep a separate figure for client entitlements or other licensed units.

Capacity planning should use the burst profile, not a monthly event total. A venue can send several times its ordinary message rate during volatile periods. A common sizing approach is to test at two to five times observed peak load, then confirm recovery behaviour when a connection resynchronises. The right headroom depends on venue behaviour and the firm's service target.

Also distinguish bandwidth from message rate. Small incremental updates can create high packets-per-second pressure even when aggregate bandwidth is modest. Conversely, snapshots and depth updates can produce large bursts of bytes. Measure both at the network interface and after decoding; one figure cannot substitute for the other.

Choose the feed stack for the job

Direct exchange feeds can offer lower and more predictable latency, but the firm takes on more protocol work, venue-specific connections and recovery logic. A vendor feed can simplify connectivity, normalisation and support across venues.

It can also add another hop and a dependency on the vendor's product design and contract. Neither option is universally cheaper once engineering, resilience and licensing are included.

A common production design has a primary path and an independent recovery path, with sequence checks and a controlled failover policy. The team needs to know whether both paths are permitted to run concurrently, how duplicate events are handled and whether a recovery snapshot can temporarily overwhelm downstream queues. Redundancy is useful only when the recovery path has been tested under load.

Before expanding a feed estate, check for avoidable work:

  • Remove instruments and venues with no active consumer, after checking contractual minimums and downstream dependencies.
  • Use top-of-book data where strategies and client products do not need depth, subject to the relevant licensing terms.
  • Filter or aggregate downstream only when the application can tolerate the resulting loss of detail and the source licence permits the use.
  • Set alerts for entitlement changes, rising message rates, queue growth, sequence gaps and unexpected vendor or exchange charges.
  • Review data access when users, desks, offices or products change. A connection that is technically stable can still be out of policy.

Track a small group of service measures alongside cost: peak messages per second, end-to-end latency percentiles, packet loss, recovery time, queue depth and the share of events rejected or delayed. A low cost per event is not a saving if it comes from a feed that misses bursts or cannot recover cleanly. For more operational coverage, Trading Technology's platform and infrastructure reporting follows the systems firms use to deliver trading services.

This approach does not apply unchanged to a firm buying a fixed, all-in data package with no control over venues, entitlements or infrastructure. In that case, the useful task is contract and service-level review, not a per-tick optimisation exercise.

Frequently Asked Questions

How do you calculate the cost per market data tick?

Define what counts as a tick, then divide the monthly cost allocated to that feed path by the number of matching events delivered. Include exchange and vendor charges, network, compute and support, and report the result per million events for easier comparison.

What is the difference between top-of-book and depth market data?

Top-of-book data shows the best available bid and offer, while depth data includes additional price levels and their displayed sizes. Depth feeds typically produce more updates and can carry higher exchange fees, processing load and bandwidth requirements.

Do brokers need a licence for non-display market data use?

Often, yes, but the requirements depend on the exchange, product and use. Automated trading, analytics and other systems may fall under non-display terms, so firms should check the current exchange rules and contract with their data provider.