mr.piron.Open the technical atlas
MR. PIRON / STANDARDS AND TECHNOLOGIES

The standards
under the stack.

A reference to the protocols, identifiers, classification schemes, rules and tools a systematic trading stack is engineered against, placed on one path from market data to governance. Each entry names its owner, links to the owner’s page and carries the date it was checked.

One path, ten stages.

Select a stage to filter both registries to it. Select it again to show every stage.

Signal to order / ten stages
  • Primary stage
  • Also applies here
  • Status changed
  • ITCH
  • CME MDP 3.0
  • SBE
  • FAST
  • PTP (IEEE 1588)
  • NTPv4
6 technologies
  • ISIN
  • FIGI
  • CFI
  • Tick / Lee-Ready / BVC
  • Arrow
  • Parquet
13 technologies
  • IEEE 754
  • ONNX
14 technologies
  • ISO 4217
  • GICS
  • OpenQASM 3
11 technologies
  • RTS 6 (primary stage elsewhere)
  • FINRA RN 15-09 (primary stage elsewhere)
6 technologies
  • ONNX (primary stage elsewhere)
  • RTS 6 (primary stage elsewhere)
5 technologies
  • FIX Latest
  • FIX 4.2 / 4.4
  • FIX 5.0 SP2 (status: Archived)
  • FIX Session / FIXT 1.1
  • FIXP
  • Orchestra
  • FIXatdl
  • OUCH
  • FIX tag=value
  • Rule 15c3-5 (Market Access Rule)
7 technologies
  • MIC
  • Reg NMS (status: Amendments deferred)
8 technologies
  • LEI
  • MMT
  • CAT
  • RTS 22
  • ISO 20022
5 technologies
  • MiFID II Art. 4(1)(39)-(40)
  • EU clock sync (ex-RTS 25) (status: Replaced RTS 25)
  • RTS 6
  • MAR Art. 12
  • FINRA RN 15-09
  • SR 26-2 (ex-SR 11-7) (status: Superseded SR 11-7)
5 technologies

All ten stages. Both registries below are shown in full. Standards Technologies

What changed

Status changes on record, as checked on 5 November 2026.

  1. Replaced RTS 25

    EU clock sync (ex-RTS 25)

    MiFID II RTS 25 (Delegated Regulation (EU) 2017/574) was repealed with effect from 2 March 2026 and replaced by Delegated Regulation (EU) 2025/1155.

  2. Superseded SR 11-7

    SR 26-2 (ex-SR 11-7)

    SR 11-7 was superseded and replaced by SR 26-2 on 17 April 2026.

  3. Amendments deferred

    Reg NMS

    Compliance with the 2024 tick-size and access-fee amendments is deferred until the first business day of November 2027 by an SEC order of 11 June 2026 (Release 34-105656).

  4. Archived

    FIX 5.0 SP2

    Archived by FIX Trading Community as a legacy specification (last errata 9 December 2013) and no longer supported; superseded by FIX Latest.

Three instruments,
computed in the page.

The two decoders run in your browser on tables parsed from the owners’ published files; the clock ladder draws the figures the registry recorded from the rule and protocol texts. Nothing is sent anywhere, and anything outside the tables is reported as not in the verified table. The two registries follow; every row opens to its summary, caveat and owner page.

Instrument 01 / order messaging

FIX tag=value decoder

Edit the message. Each field is named from the FIX Orchestra tables, and BodyLength(9) and CheckSum(10) are recomputed from the bytes you typed, so a changed quantity breaks both until they are recomputed.

Illustrative messages

A buy-side system sends a broker a day limit order to buy 500 units, with XNAS as the destination and automated handling requested. Illustrative: the symbol, counterparties, identifiers and prices are placeholders.

BodyLength (9)
Matchdeclared 166 / computed 166BodyLength(9) declares 166 bytes and 166 were counted between it and CheckSum(10).
CheckSum (10)
Matchdeclared 209 / computed 209CheckSum(10) is 209, the sum of all preceding bytes modulo 256.
Framing
Well-formedread with FIX 4.4 (FIX.4.4_EP311) / 35=D NewOrderSingle
Decoded fields 20
Tag and fieldValueMeaning
8BeginStringFIX.4.4FIX44
9BodyLength166BodyLength(9) declares 166 bytes and 166 were counted between it and CheckSum(10).
35MsgType (counted by BodyLength)DNewOrderSingle
49SenderCompID (counted by BodyLength)BUYSIDEString
56TargetCompID (counted by BodyLength)BROKERString
34MsgSeqNum (counted by BodyLength)215SeqNum
52SendingTime (counted by BodyLength)20261105-14:30:00.123UTCTimestamp
11ClOrdID (counted by BodyLength)ORD-0001String
21HandlInst (counted by BodyLength)1AutomatedExecutionNoIntervention
100ExDestination (counted by BodyLength)XNASNASDAQ - ALL MARKETS (operating MIC)
55Symbol (counted by BodyLength)DEMOString
461CFICode (counted by BodyLength)ESVUFREquities; Common/ordinary shares; Voting; Free; Fully paid; Registered
54Side (counted by BodyLength)1Buy
60TransactTime (counted by BodyLength)20261105-14:30:00.120UTCTimestamp
38OrderQty (counted by BodyLength)500Qty
40OrdType (counted by BodyLength)2Limit
44Price (counted by BodyLength)41.25Price
15Currency (counted by BodyLength)USDUS Dollar, minor unit 2
59TimeInForce (counted by BodyLength)0Day
10CheckSum209CheckSum(10) is 209, the sum of all preceding bytes modulo 256.

The marked fields are the bytes BodyLength(9) counts. CheckSum(10) sums every byte before it, delimiters included, modulo 256.

Source

Field names, datatypes and code values are parsed from the official FIX Orchestra repositories for FIX 4.2 (EP310), FIX 4.4 (EP311) and FIX Latest (EP312), each dated 2026-09-08 and downloaded on 2026-11-05. The table carries 54 fields, enough for order and execution messages. Any other tag is reported as not in the verified table. Currency and Exchange fields are decoded for FIX 4.4 and FIX Latest only. ISO 4217 List One as published by SIX, the Maintenance Agency, on 2026-09-17: 178 alphabetic codes. A nine-code sample of the ISO 10383 list as published on 12 October 2026, which held 2,313 active codes. A code outside the sample is reported as not in the verified table.

Instrument 02 / classification

CFI code decoder

ISO 10962 classifies an instrument in six letters. The first is the category, the second the group, and the meaning of the last four depends on both. Type a code or pick each letter.

Verified examples
  1. Position 1CategoryLetter E: Equities
  2. Position 2GroupLetter S: Common/ordinary shares
  3. Position 3Voting rightLetter V: Voting
  4. Position 4Ownership/transfer/sales restrictionsLetter U: Free
  5. Position 5Payment statusLetter F: Fully paid
  6. Position 6FormLetter R: Registered

ESVUFR Equities; Common/ordinary shares; Voting; Free; Fully paid; Registered. All six letters are in the verified table.

Source

Decoded with the ISO 10962 code list published by SIX, the Maintenance Agency, dated 2021-05-07 and downloaded on 2026-11-05: 14 categories, 78 groups, four attributes per group. Labels are the short names of the list. Tables can be updated between revisions of the standard. A code written with X placeholders, such as ESXXXX, reports those positions as not in the verified table, because the list does not give X as a value there.

Instrument 03 / clock synchronization

The clock-synchronization ladder

How closely a business clock must track reference time, and how finely an event must be stamped, from a manual order to a high-frequency one. The axis is logarithmic: each gridline is ten times finer than the one to its left.

  • Rule: maximum divergence
  • Rule: timestamp granularity
  • Protocol document: achievable accuracy
  • Repealed, shown for comparison
  1. 1 secondMaximum divergence

    Manual order events

    Clocks that stamp manual order events may diverge from NIST time by up to one second.

    FINRA Rule 6820, owner page, opens in a new tab

  2. 1 secondMaximum divergence

    Voice trading, request-for-quote systems that need human intervention or do not allow algorithmic trading, and negotiated transactions

    Maximum divergence from UTC of one second, with timestamps of one second or better.

    Delegated Regulation (EU) 2025/1155, Annex IV, owner page, opens in a new tab

  3. 50 millisecondsMaximum divergence

    Industry member business clocks

    Business clocks must stay within 50 milliseconds of NIST time.

    FINRA Rule 6820, owner page, opens in a new tab

  4. 1 millisecondTimestamp granularity

    Consolidated Audit Trail timestamps

    Timestamps at least to the millisecond, finer where a firm’s systems use finer increments.

    SEC Rule 613, owner page, opens in a new tab

  5. 1 millisecondMaximum divergence

    Trading venues and systematic internalizers with gateway-to-gateway latency above 1 millisecond

    Maximum divergence from UTC of one millisecond, with timestamps of one millisecond or better.

    Delegated Regulation (EU) 2025/1155, Annex IV, owner page, opens in a new tab

  6. 1 millisecondMaximum divergence

    Data reporting entities (DPEs, APAs and CTPs)

    Divergence of no more than one millisecond, with records to one millisecond or better.

    Delegated Regulation (EU) 2025/1155, Articles 14 and 15, owner page, opens in a new tab

  7. 100 microsecondsMaximum divergence

    Members and participants using a high-frequency algorithmic trading technique

    Maximum divergence from UTC of 100 microseconds, carried over from the repealed RTS 25.

    Delegated Regulation (EU) 2025/1155, Annex IV, owner page, opens in a new tab

  8. 100 microsecondsMaximum divergence

    Trading venues and systematic internalizers with gateway-to-gateway latency of 1 millisecond or less

    Maximum divergence from UTC of 100 microseconds, with timestamps of 0.1 microseconds or better.

    Delegated Regulation (EU) 2025/1155, Annex IV, owner page, opens in a new tab

  9. tens of microsecondsProtocol accuracy

    Modern workstations and fast LANs

    Potential accuracy in the tens of microseconds: the RFC’s stated potential under good conditions, not a guarantee. Drawn as the decade from 10 to 100 microseconds.

    RFC 5905 (NTPv4), owner page, opens in a new tab

  10. 1 microsecondTimestamp granularity, repealed

    High-frequency algorithmic trading technique

    The repealed RTS 25 required timestamps of 1 microsecond or better. Its successor asks for 0.1 microseconds.

    MiFID II RTS 25, repealed with effect from 2 March 2026, owner page, opens in a new tab

  11. sub-microsecondProtocol accuracy

    Clocks in packet-based networked systems

    The protocol supports sub-microsecond synchronization accuracy. What a network achieves depends on hardware timestamping and design.

    IEEE 1588-2019 (PTP), owner page, opens in a new tab

  12. 0.1 microsecondsTimestamp granularity

    High-frequency algorithmic trading technique, and venues with gateway-to-gateway latency of 1 millisecond or less

    Timestamp granularity of 0.1 microseconds or better, tightened from 1 microsecond under RTS 25.

    Delegated Regulation (EU) 2025/1155, Annex IV, owner page, opens in a new tab

  13. sub-nanosecondProtocol accuracy

    Time transfer in a properly designed network

    The 2019 edition states that sub-nanosecond time transfer is achievable “in a properly designed network”.

    IEEE 1588-2019 (PTP), owner page, opens in a new tab

A marker sits at the figure the source gives. The band to its right covers every value that satisfies it: a rule’s limit and anything tighter, or, for a protocol, the accuracy its document says can be reached. The NTPv4 band spans the order of magnitude the RFC names.

Source

Every figure is the registry’s reading of the rule or protocol document linked on its row. A requirement binds the regulated firms the rule names; a protocol figure is a capability, not a guarantee. The EU tolerance for algorithmic activity that is not high-frequency is left out. The 1-millisecond “any other trading activity” row of the repealed RTS 25 does not appear in Annex IV Table 2 of Delegated Regulation (EU) 2025/1155 as published in the Official Journal, so it awaits confirmation against the consolidated text.

40 of 40 standards and 80 of 80 technologies shown.

Standards, protocols
and rules.

What a trading system is engineered against: wire protocols, encodings, identifiers, classification schemes, time standards and the rules that set controls. The kind says what each entry is. A venue’s own specification, a licensed classification and an academic convention are labeled as such.

40 of 40 shown

What the seven kinds mean
Industry standard
Published by a standards body or an industry standards organization.
Open specification
An openly published format or language maintained by a community project.
Proprietary venue specification
Published by one venue for its own systems. Not an industry standard.
Licensed classification
A proprietary scheme whose data is used under its owners’ license.
Regulation
Binding law or rule. Its obligations fall on the regulated firms it names.
Supervisory guidance
Guidance from a supervisor or self-regulatory body. Not a rule.
Academic convention
A method from the research literature. Not a standard.
01

Market data

Venue feeds are received, decoded and sequenced, and every event is stamped against a synchronized clock.

  • ITCHNasdaq TotalView-ITCH 5.0CurrentProprietary venue specificationMarket data

    Nasdaq’s outbound direct data feed specification: a sequenced stream of binary messages that tracks the life of each displayed order, plus trades, net order imbalance and administrative events.

    Owner
    Nasdaq, Inc. (The Nasdaq Stock Market LLC)
    Category
    Market data feeds
    Stage
    Market data

    The feed carries order events rather than book snapshots: a book is rebuilt by applying Add (A/F), Executed (E/C), Cancel (X), Delete (D) and Replace (U) messages keyed by a day-unique order reference number, and an unattributed Add Order message is 36 bytes. Timestamps are 6-byte nanoseconds since midnight, prices are integers with implied decimals, and the stock locate code that addresses each instrument is reassigned every day.

    Caveat Proprietary venue specification, not an industry standard, and the link is a PDF. Transport options named in the document are SoupBinTCP (optionally compressed) and MoldUDP64.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    nasdaqtrader.com, owner page for ITCH, opens in a new tab
  • CME MDP 3.0CME Market Data Platform 3.0CurrentProprietary venue specificationMarket data

    CME Globex market data platform disseminating bid, ask, trade and statistical data as FIX-semantics messages in Simple Binary Encoding over UDP multicast, with market-by-order and market-by-price books and recovery feeds.

    Owner
    CME Group
    Category
    Market data feeds
    Stage
    Market data

    Every packet is published on redundant Feed A and Feed B, which clients arbitrate; gaps are repaired from UDP market-recovery snapshot feeds or a TCP replay limited to 2,000 packets from the last 24 hours. The incremental feed carries FIX message types such as MarketDataIncrementalRefresh (35=X) and SecurityDefinition (35=d), each decoded through the template ID in its SBE header against a single published XML schema.

    Caveat Proprietary venue documentation on CME’s Confluence wiki; CME states it may update SBE schemas and channels periodically, so pin the schema version in use.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    cmegroupclientsite.atlassian.net, owner page for CME MDP 3.0, opens in a new tab
  • SBESimple Binary Encoding (ISO/IEC 25390:2025)CurrentIndustry standardMarket data

    Schema-driven binary message encoding optimized for low latency, used for transactions and market-data dissemination; specifies the wire format and an XML message schema, for FIX and non-FIX messages alike.

    Owner
    FIX Trading Community (High Performance Working Group); ISO/IEC
    Category
    Wire encoding
    Stage
    Market data

    Prices are scaled decimals, a signed integer mantissa with an exponent (mantissa 123456 and exponent -4 is 12.3456), and byte order is declared once per schema, little-endian by default. Version 1.0 has been final since 9 February 2016, while 2.0 exists only as release candidates that are not wire-compatible with 1.0, so pin the schema version a venue publishes.

    Caveat The ISO/IEC 25390:2025 designation is as printed on FIX Trading Community’s technical standards page; the ISO catalog entry was not read.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for SBE, opens in a new tab
  • FASTFIX Adapted for STreamingCurrentIndustry standardMarket data

    Binary encoding for FIX market data designed to reduce bandwidth use and latency in high-volume dissemination; specification version 1.1 and the 1.2 extension are published by FIX Trading Community.

    Owner
    FIX Trading Community (Market Data Optimization Working Group)
    Category
    Wire encoding
    Stage
    Market data

    FAST targets bandwidth, whereas SBE was later designed for low latency; FIX Trading Community presents the two as complementary. The FAST page dates version 1.2 to February 2009 and also carries an intellectual-property agreement covering CME patented technology that affects the protocol.

    Caveat Which venues still disseminate FAST feeds was not verified; confirm per venue before describing it as current practice.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FAST, opens in a new tab
  • PTP (IEEE 1588)IEEE 1588-2019 Precision Time ProtocolCurrentIndustry standardMarket data

    Protocol for precise synchronization of clocks in packet-based networked systems, supporting sub-microsecond accuracy with minimal network and computing resources and customization through profiles.

    Owner
    IEEE Standards Association (Instrumentation and Measurement Society, TC9)
    Category
    Clock synchronization
    Stage
    Market data

    The 2019 edition (approved 7 November 2019, published 16 June 2020) supersedes IEEE 1588-2008 and states that sub-nanosecond time transfer is achievable “in a properly designed network”, so the design matters as much as the protocol. It already carries seven published amendments (1588a to 1588h), which means a PTP claim should name edition, amendments and profile.

    Caveat The standard text is paywalled; statements are from the IEEE SA abstract and status block. Achieved accuracy depends on hardware timestamping and network design, which the page does not quantify for trading networks.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    standards.ieee.org, owner page for PTP (IEEE 1588), opens in a new tab
  • NTPv4Network Time Protocol version 4 (RFC 5905)CurrentIndustry standardMarket data

    Internet Standards Track protocol for synchronizing computer clocks in the Internet; NTPv4 extends potential accuracy to the tens of microseconds on modern workstations and fast LANs.

    Owner
    IETF (RFC Editor)
    Category
    Clock synchronization
    Stage
    Market data

    The RFC’s own best-case figure, tens of microseconds, sits close to the 100-microsecond maximum divergence EU rules set for high-frequency techniques, leaving little margin once measurement error is counted; budget the whole timestamping chain before relying on NTP for sub-millisecond obligations. NTPv4 is backwards compatible with NTPv3 and obsoletes RFC 1305 and RFC 4330.

    Caveat The accuracy figure is the RFC’s stated potential under good conditions, not a guarantee; the comparison with the EU tolerance is an engineering reading.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    rfc-editor.org, owner page for NTPv4, opens in a new tab
02

Research data

Ticks, bars and reference data are identified, stored and joined as of the moment each value was known.

  • ISINISO 6166 International Securities Identification Number (with ISO 18774 FISN)CurrentIndustry standardResearch data

    Twelve-character identifier for financial and referential instruments: two-letter ISO 3166 country prefix, nine-character national number and a modulus-10 “double-add-double” check digit.

    Owner
    ISO (TC 68); ANNA as Registration Authority; issued by National Numbering Agencies
    Category
    Identifiers
    Stage
    Research data

    An ISIN identifies the instrument, not the listing: it is combined with an ISO 10383 MIC and an ISO 4217 currency code to pin down a tradable line, and OTC-derivative ISINs use the prefix “EZ”. Since 1 July 2017 each new ISIN is issued together with a CFI code and a FISN (ISO 18774), a short name of at most 35 characters that ANNA says is not meant to be machine-readable.

    Caveat FISN (ISO 18774) is folded into this entry because it is a descriptive alias rather than a key. The ISO catalog pages were not read (bot wall), so no edition year is stated.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    anna-web.org, owner page for ISIN, opens in a new tab
  • FIGIFinancial Instrument Global IdentifierCurrentIndustry standardResearch data

    Open-data identifier framework: a permanent, semantically meaningless twelve-character code linked to metadata that identifies a financial instrument at several levels of granularity; OMG specification version 1.3.

    Owner
    Object Management Group (OMG); Bloomberg as Registration Authority
    Category
    Identifiers
    Stage
    Research data

    Characters 1-2 name the certified provider, character 3 is always “G”, characters 4-11 are random alphanumerics without vowels and character 12 is a check digit; a retired FIGI is never reused. The framework relates different contexts of one instrument, for example a single obligation versus that obligation on specific exchanges, and FIX carries a FIGI as SecurityIDSource(22)=S.

    Caveat Regulatory acceptance of FIGI relative to ISIN or CUSIP differs by regime and was not assessed.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    omg.org, owner page for FIGI, opens in a new tab
  • CFIISO 10962 Classification of Financial InstrumentsCurrentIndustry standardResearch data

    Six-letter code classifying any financial instrument by its intrinsic characteristics: the first letter is the category, the second the group, and the remaining four are group-specific attributes.

    Owner
    ISO (TC 68/SC 8); SIX as Maintenance Agency; assigned with ISINs by National Numbering Agencies
    Category
    Classification
    Stage
    Research data

    The current code list has 14 categories (E equities, C collective investment vehicles, D debt, R entitlements, O listed options, F futures, S swaps, H non-listed and complex options, I spot, J forwards, K strategies, L financing, T referential instruments, M others), so ESVUFR decodes as a common share that is voting, unrestricted, fully paid and registered. A CFI can change during an instrument’s life, for example after a change in voting rights, and FIX carries it in CFICode(461).

    Caveat Decoding uses the published code list dated 2021-05-07; SIX states the standard is revised every five years and that tables can be updated between revisions. The ISO catalog entry was not read.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    six-group.com, owner page for CFI, opens in a new tab
  • Tick / Lee-Ready / BVCTrade-direction classification rules: tick test, quote rule, Lee-Ready and bulk volume classificationCurrentAcademic conventionResearch data

    Academic conventions, not standards, for inferring whether a trade was buyer- or seller-initiated from trade and quote data when the aggressor side is not reported.

    Owner
    Academic literature, not a standards body: Lee & Ready, Journal of Finance (1991); Easley, Lopez de Prado & O’Hara, Review of Financial Studies (2012)
    Category
    Classification
    Stage
    Research data

    The tick test signs a trade against the previous trade price; Lee-Ready signs against the prevailing quote midpoint and falls back to the tick test at the midpoint, and the 1991 paper already names its weak points: quotes recorded ahead of the trades that triggered them and trades inside the spread. Bulk volume classification, introduced with the VPIN metric in 2012, assigns a buy fraction to a whole bar of volume, so it estimates aggregate imbalance rather than individual trade signs.

    Caveat Conventions with known error modes; accuracy depends on market and data. The publisher page behind the DOI could not be read by any automated client, so the record was confirmed through Crossref and the plain-language rule definitions were cross-checked in a 2026 preprint rather than read in the paywalled originals. Where a feed states the resting order’s side (ITCH Add Order messages carry a buy/sell indicator), derive direction from the feed instead of inferring it.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    doi.org, owner page for Tick / Lee-Ready / BVC, opens in a new tab
  • ArrowApache Arrow columnar formatCurrentOpen specificationResearch data

    Language-agnostic specification of an in-memory columnar data structure, its metadata serialization and an IPC protocol for serialization and generic data transport; columnar format version 1.5.

    Owner
    Apache Software Foundation
    Category
    Data interchange
    Stage
    Research data

    Arrow trades cheap mutation for scan speed: the specification offers data adjacency, O(1) random access, a SIMD-friendly layout and relocatable buffers that allow true zero-copy access in shared memory, “in exchange for comparatively more expensive mutation operations”. Nulls live in a separate validity bitmap and 64-byte buffer alignment is recommended, which suits vectorized scans over tick and bar columns.

    Caveat It specifies memory layout and IPC, not a durable storage policy; pair it deliberately with a file format such as Parquet. The library version (v26.0.1 documentation) and the format version (1.5) are different numbers.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    arrow.apache.org, owner page for Arrow, opens in a new tab
  • ParquetApache Parquet file formatCurrentOpen specificationResearch data

    Open-source column-oriented data file format designed for efficient storage and retrieval, with compression and encoding schemes for complex data in bulk.

    Owner
    Apache Software Foundation
    Category
    Data interchange
    Stage
    Research data

    A file is framed by the 4-byte magic number “PAR1” at both ends, and the file metadata is written after the data so that a file can be produced in a single pass; readers therefore start from the footer to locate the column chunks they need. Because metadata is separated from data, one metadata file can reference many Parquet files, which is how multi-year tick archives stay queryable column by column.

    Caveat Encodings, logical types and index features vary by writer version; pin writer and reader versions for reproducible research data sets. The last clause of the detail is an engineering reading, not text from the page.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    parquet.apache.org, owner page for Parquet, opens in a new tab
03

Modeling

Statistical and learned models turn point-in-time features into forecasts, labels and probabilities.

  • IEEE 754IEEE 754-2019 Standard for Floating-Point ArithmeticCurrentIndustry standardModeling

    Specifies interchange and arithmetic formats and methods for binary and decimal floating-point arithmetic, including exception conditions and their default handling.

    Owner
    IEEE Standards Association (Computer Society, Microprocessor Standards Committee)
    Category
    Data interchange
    Stage
    Modeling

    The standard determines results from input values, the sequence of operations and destination formats, which means a different operation order (vectorized or parallel reductions) can legitimately change low-order bits, so reproducible research pins operation order as well as seeds. Market protocols avoid binary floats for prices: SBE uses an integer mantissa and exponent, ITCH and OUCH integers with implied decimals.

    Caveat The standard text is paywalled; statements come from the IEEE SA abstract. The reproducibility remark is an engineering inference from that abstract, not a quotation.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    standards.ieee.org, owner page for IEEE 754, opens in a new tab
  • ONNXOpen Neural Network ExchangeCurrentOpen specificationModeling · Deployment

    Open format for representing machine-learning models: a common set of versioned operators and a common protobuf-serialized file format that frameworks, runtimes and compilers can exchange.

    Owner
    ONNX community project (open governance); created by Microsoft and partners
    Category
    Model interchange
    Stages
    Modeling, Deployment

    Every graph records an opset version per operator domain and each operator follows the latest definition at or below that opset, so behavior is tied to the opset: pin opset and runtime version and keep a numerical parity fixture between training framework and runtime. Beyond neural networks, the ai.onnx.ml domain covers classical models such as tree ensembles, linear and SVM classifiers and scalers, although scikit-learn notes that not all models are supported.

    Caveat ONNX standardizes a representation, not identical numerics across runtimes and hardware; parity has to be tested.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    onnx.ai, owner page for ONNX, opens in a new tab
04

Portfolio and risk

Forecasts become target positions through optimization under risk, cost, currency and exposure constraints.

  • ISO 4217ISO 4217 Currency codesCurrentIndustry standardPortfolio and risk

    Code list assigning each currency and fund a three-letter alphabetic code, a three-digit numeric code and a minor-unit count; maintained by SIX and published free of charge.

    Owner
    ISO; SIX as Maintenance Agency secretariat
    Category
    Identifiers
    Stage
    Portfolio and risk

    The minor unit is not always two: in List One published 2026-09-17, 17 codes have none (JPY, KRW), seven have three (KWD, BHD) and two have four (CLF, UYW), so hard-coded cents corrupt notionals and P&L. The list also defines non-currency codes such as XAU (gold), XTS (testing) and XXX (no currency), and FIX’s Currency datatype uses these codes.

    Caveat Counts are a snapshot of the 2026-09-17 list. The ISO overview page for ISO 4217 sits behind a bot wall and was not read.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    six-group.com, owner page for ISO 4217, opens in a new tab
  • GICSGlobal Industry Classification StandardCurrentLicensed classificationPortfolio and risk

    Four-tier hierarchical industry classification (sectors, industry groups, industries, sub-industries) that assigns each company a single classification per tier according to its principal business activity.

    Owner
    MSCI and S&P Dow Jones Indices
    Category
    Classification
    Stage
    Portfolio and risk

    Revenues are the key factor in assignment, with earnings and market perception also considered, and the structure is reviewed annually (MSCI publishes historical structures and a 2023 reclassification), so sector labels are point-in-time data. A backtest that applies today’s codes to past dates imports look-ahead; store classification history with effective dates.

    Caveat Proprietary, licensed classification, not an open standard: systems are engineered around GICS data that the client has licensed. Counts of industry groups, industries and sub-industries are not on the page that was read and are deliberately omitted.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    msci.com, owner page for GICS, opens in a new tab
  • OpenQASM 3OpenQASM specification contributors (Qiskit development team and collaborators)CurrentOpen specificationPortfolio and risk

    Imperative quantum assembly language serving as an intermediate representation between higher-level compilers and quantum hardware; version 3 adds classical control flow, explicit timing and pulse-level definitions.

    Owner
    OpenQASM specification contributors (Qiskit development team and collaborators)
    Category
    Quantum interchange
    Stage
    Portfolio and risk

    A valid OpenQASM 3 program is not automatically an executable one: hardware implementations may restrict run-time processing to the operations they can perform efficiently in real time, so the portability of a QAOA circuit has to be tested per backend. A program may declare its version on the first non-comment line (OPENQASM 3.0;).

    Caveat A community language specification, not a formal standard from a standards body; its introduction page still describes itself as “draft version 3.0”.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    openqasm.com, owner page for OpenQASM 3, opens in a new tab
07

Order routing

Target positions become orders that pass pre-trade controls and travel to a broker or venue over a session protocol.

  • FIX LatestFIX Protocol - FIX Latest (application layer)CurrentIndustry standardOrder routing

    Application-layer standard defining the fields, components and messages for orders, executions, market data and post-trade workflows, independent of transport, session and encoding; evolves continuously through backward-compatible extension packs.

    Owner
    FIX Trading Community (FIX Protocol Ltd)
    Category
    Order messaging
    Stage
    Order routing

    The official machine-readable repository for FIX Latest (Extension Pack 312, dated 2026-09-08) defines 6,203 fields and 181 message types; in an ExecutionReport (MsgType 35=8) ExecType(150) describes the event while OrdStatus(39) always carries the current order state. FIX Trading Community strongly recommends FIX Latest and, of the earlier versions, still supports only 4.2 and 4.4.

    Caveat Counts are a snapshot of Extension Pack 312 and grow with every extension pack; FIX Trading Community’s downloadable documents cover the specification up to Extension Pack 284, with later packs listed separately.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FIX Latest, opens in a new tab
  • FIX 4.2 / 4.4FIX 4.2 and FIX 4.4 (supported legacy versions)Supported legacy versionIndustry standardOrder routing

    The two earlier FIX Protocol versions FIX Trading Community still supports; releases that predate the session/application split and identify themselves with BeginString(8) FIX.4.2 or FIX.4.4.

    Owner
    FIX Trading Community (FIX Protocol Ltd)
    Category
    Order messaging
    Stage
    Order routing

    FIX Trading Community still supports FIX 4.2 and FIX 4.4 alongside FIX Latest.

    The official repositories define 46 messages and 405 fields (tags 1-446) for FIX 4.2 against 93 messages and 912 fields (tags 1-956) for FIX 4.4. A 4.2 fill is reported with ExecTransType(20) plus ExecType(150)=1 or 2, whereas 4.4 has no ExecTransType and reports fills as ExecType(150)=F (Trade), so a 4.2-to-4.4 bridge must translate execution semantics, not just tag numbers (tag 22 is also renamed from IDSource to SecurityIDSource).

    Caveat Counts come from the Orchestra translations of the legacy repositories, which their README limits to message structures. Counterparties commonly add user-defined tags, so the counterparty’s rules of engagement, not the base version, define a real session.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FIX 4.2 / 4.4, opens in a new tab
  • FIX 5.0 SP2FIX 5.0 Service Pack 2ArchivedIndustry standardOrder routing

    Archived FIX application-layer release, carried over the separate FIXT.1.1 session layer and identified by ApplVerID(1128)=9; superseded by FIX Latest and no longer supported.

    Owner
    FIX Trading Community (FIX Protocol Ltd)
    Category
    Order messaging
    Stage
    Order routing

    Archived by FIX Trading Community as a legacy specification (last errata 9 December 2013) and no longer supported; superseded by FIX Latest.

    FIX Trading Community lists 5.0 SP2 (last errata 9 December 2013) among legacy specifications “archived here for reference purposes” and asks implementers to migrate to a supported version. It bundled 19 extension packs on top of FIX 5.0 SP1, including the CFTC trade-capture requirements (EP77).

    Caveat A counterparty specification that cites FIX 5.0 SP2 describes that counterparty’s rules of engagement, not a version the standards body still maintains.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FIX 5.0 SP2, opens in a new tab
  • FIX Session / FIXT 1.1FIX Session Layer and the FIXT session profile (ISO 3531 Part 2)CurrentIndustry standardOrder routing

    Session protocol giving two peers a reliable, recoverable, bidirectional stream of ordered messages in one continuous sequence-number series starting at 1, across successive connections; FIXT is its transport-independent profile.

    Owner
    FIX Trading Community (FIX Protocol Ltd)
    Category
    Order messaging
    Stage
    Order routing

    A session outlives its connections: peers may disconnect and reconnect many times and resynchronize by sequence number (MsgSeqNum(34), ResendRequest 35=2, SequenceReset 35=4, PossDupFlag(43)), so gateway restart logic is part of protocol conformance. FIX Trading Community publishes mandatory and optional session-layer compliance test cases (v1.0, June 2020).

    Caveat The ISO 3531 Part 2 designation is as printed on FIX Trading Community’s technical standards page; the ISO catalog page sits behind a bot wall and was not read.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FIX Session / FIXT 1.1, opens in a new tab
  • FIXPFIX Performance Session LayerCurrentIndustry standardOrder routing

    Lightweight point-to-point session-layer protocol for high-performance messaging that establishes and maintains a reliable session between two endpoints regardless of the reliability of the underlying transport.

    Owner
    FIX Trading Community (High Performance Working Group)
    Category
    Order messaging
    Stage
    Order routing

    FIXP is a derived work whose stated origins are the FIX session layer and Nasdaq’s SoupTCP, SoupBinTCP and UFO (UDP for Orders); its reference implementation demonstrates it together with SBE and the Simple Open Framing Header. Version 1.0 became a Technical Standard on 15 April 2021, while version 1.1, which adds guidance for FIXP over WebSocket, is a Draft Standard.

    Caveat Whether a venue uses FIXP is venue-specific and was not surveyed; confirm against each venue’s order-entry specification.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FIXP, opens in a new tab
  • OrchestraFIX OrchestraCurrentIndustry standardOrder routing

    Standard for machine-readable definitions of messaging protocols: messages, fields, validation rules, scenario-specific layouts, permitted workflows, and session, encoding and transport settings.

    Owner
    FIX Trading Community (FIX Protocol Ltd)
    Category
    Order messaging
    Stage
    Order routing

    An Orchestra file is an executable rules-of-engagement document: counterparty variants can be normalized from it and conformance tests generated from it, with fields marked mandatory, conditionally required, forbidden or ignored. FIX Latest itself is published as an Orchestra repository, and the standard is licensed under Apache 2.0.

    Caveat Whether a given broker or venue supplies an Orchestra file is counterparty-specific and was not surveyed.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for Orchestra, opens in a new tab
  • FIXatdlFIX Algorithmic Trading Definition LanguageCurrentIndustry standardOrder routing

    Vendor-neutral XML standard describing the parameters, controls, constraints, defaults and validation rules of algorithmic order types so order and execution management systems can render and validate them consistently.

    Owner
    FIX Trading Community (FIX Protocol Ltd)
    Category
    Order messaging
    Stage
    Order routing

    FIXatdl standardizes the human-to-system layer only: it describes how a broker algorithm’s parameters are presented and validated, not how the algorithm trades, and it requires no change to FIX infrastructure. FIX itself carries strategy choices in fields such as TargetStrategy(847) and the StrategyParameters group (957-960); version 1.1 is the current specification and 1.2 exists as a release candidate.

    Caveat It describes parameter presentation, not behavior, and is no evidence of how any broker algorithm executes. The page does not say which FIX fields a given FIXatdl file maps to; that is defined per algorithm.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FIXatdl, opens in a new tab
  • OUCHNasdaq OUCH order entry protocolCurrentProprietary venue specificationOrder routing

    Nasdaq’s low-level native order-entry protocol, with big-endian binary numeric fields, through which participants enter, replace and cancel orders and receive executions; supported versions are 5.0, 4.2 and 4.1.

    Owner
    Nasdaq, Inc.
    Category
    Order messaging
    Stage
    Order routing

    Host-to-client messages are sequenced over a lower-level protocol such as SoupBinTCP, but client-to-host messages are deliberately not guaranteed: each order carries a UserRefNum that must be unique and strictly increasing through the trading day so that messages can be “benignly resent” after a failure. Prices are unsigned integers with four implied decimal places.

    Caveat Proprietary venue protocol, not an industry standard. Details are from the OUCH 5.0 document; the 4.2 and 4.1 documents were not reviewed.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    nasdaqtrader.com, owner page for OUCH, opens in a new tab
  • FIX tag=valueFIX TagValue Encoding (ISO 3531-1:2022)CurrentIndustry standardOrder routing

    Original and most widely used FIX wire encoding: each field is serialized as numeric tag, equals sign and value, with fields separated by the Start of Heading (SOH) control character.

    Owner
    FIX Trading Community; ISO
    Category
    Wire encoding
    Stage
    Order routing

    Every message starts with BeginString(8) then BodyLength(9) and ends with the three-character CheckSum(10), which with its trailing SOH is the end-of-message delimiter. FIX float fields are decimal character strings that must accommodate up to fifteen significant digits, so parse prices into decimals or scaled integers rather than binary floats.

    Caveat The ISO designation is taken from the FIX Trading Community page; the ISO catalog pages sit behind a bot wall and were not read. The last clause of the detail is engineering advice, not standard text.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for FIX tag=value, opens in a new tab
  • Rule 15c3-5 (Market Access Rule)SEC Rule 15c3-5: risk management controls for brokers or dealers with market accessCurrentRegulationOrder routing

    Requires broker-dealers with or providing market access to maintain documented risk controls that reject orders breaching pre-set credit or capital thresholds or price and size parameters, and that ensure regulatory compliance.

    Owner
    U.S. Securities and Exchange Commission
    Category
    Risk controls and regulation
    Stage
    Order routing

    The controls must be under the broker-dealer’s “direct and exclusive control”, so a non-broker client’s own pre-trade checks complement the broker’s gate but cannot replace it. Erroneous-order checks apply order by order and over short periods, duplicative orders must be caught, and the chief executive certifies the controls annually.

    Caveat The obligation sits with the broker-dealer, not with a software vendor or research studio. “Market Access Rule” is the common name (FINRA uses it); it does not appear in the rule’s title.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    ecfr.gov, owner page for Rule 15c3-5 (Market Access Rule), opens in a new tab
08

Venue access

Orders cross the last hop to the matching engine, where market-structure rules and the latency of the path decide what executes.

  • MICISO 10383 Market Identifier CodeCurrentIndustry standardVenue access

    Four-character codes giving a universal method of identifying exchanges, trading platforms, regulated or non-regulated markets and trade reporting facilities as sources of prices and related information.

    Owner
    ISO (TC 68); SWIFT as Registration Authority
    Category
    Identifiers
    Stage
    Venue access

    The list separates operating MICs from market-segment MICs (ARCX and XNGS are segments of XNYS and XNAS) and is republished on the second Monday of each month, with changes effective on the fourth Monday. The 12 October 2026 publication holds 2,313 active codes (1,336 operating, 977 segment), each with a market category and, where available, the operator’s LEI; FIX’s Exchange datatype, used by ExDestination(100), carries MIC values.

    Caveat Counts are for the 12 October 2026 publication and change monthly.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    iso20022.org, owner page for MIC, opens in a new tab
  • Reg NMSRegulation NMS (17 CFR 242.600-242.614)Amendments deferredRegulationVenue access

    U.S. national market system rules for NMS securities, including the order protection rule against trade-throughs of protected quotations, access-fee caps, minimum pricing increments and consolidated market data.

    Owner
    U.S. Securities and Exchange Commission
    Category
    Risk controls and regulation
    Stage
    Venue access

    Compliance with the 2024 tick-size and access-fee amendments is deferred until the first business day of November 2027 by an SEC order of 11 June 2026 (Release 34-105656).

    Codified text can run ahead of market practice: eCFR already shows the 2024 amendments (a $0.005 increment for stocks whose time-weighted quoted spread is $0.015 or less, and a $0.001-per-share access-fee cap), but an SEC order of 11 June 2026 (Release 34-105656) defers compliance until the first business day of November 2027. Rule 611’s intermarket-sweep-order exception is what lets a router trade through a protected quote while simultaneously sweeping it.

    Caveat Compliance dates for the tick-size and access-fee amendments have been deferred twice (to November 2026, then November 2027); re-verify before describing half-penny ticks or the lower fee cap as live.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    ecfr.gov, owner page for Reg NMS, opens in a new tab
09

Post-trade and operations

Fills are reconciled, flagged and reported while metrics, traces and scheduled jobs keep the running system observable.

  • LEIISO 17442 Legal Entity IdentifierCurrentIndustry standardPost-trade and operations

    Unique 20-character alphanumeric code identifying a legal entity and linking it to verified reference data on who the entity is and who owns it, published in the Global LEI Index.

    Owner
    ISO (TC 68); Global Legal Entity Identifier Foundation (GLEIF), overseen by the Regulatory Oversight Committee
    Category
    Identifiers
    Stage
    Post-trade and operations

    MiFIR transaction reports require the executing firm to be identified with a “validated, issued and duly renewed” LEI, so a lapsed code is an operational failure rather than a formality. GLEIF describes the LEI as a public good, available free of charge to all users, and FIX carries LEIs as PartyIDSource(447)=N.

    Caveat The internal structure of the code (prefix and check digits) appears on the GLEIF page only as an image and is deliberately not restated.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    gleif.org, owner page for LEI, opens in a new tab
  • MMTMarket Model TypologyCurrentIndustry standardPost-trade and operations

    Protocol-agnostic standard for flagging post-trade data consistently across venues and asset classes, used to meet MiFIR/MiFID II (RTS 1 and RTS 2) and UK trade-flagging requirements.

    Owner
    FIX Trading Community (FIX Protocol Limited Trust); originated by the Federation of European Securities Exchanges
    Category
    Classification
    Stage
    Post-trade and operations

    MMT is the classification layer that says what kind of print a trade is before it enters a volume, VWAP or liquidity statistic. Version 5.0 took effect on 1 December 2025 for UK trade reporting and on 2 March 2026 for the EU, so trade-flag mappings are versioned data.

    Caveat Flag semantics per version were not transcribed; use the published MMT model documents for the mapping. The first sentence of the detail is an engineering reading of “flagging post-trade data”.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    fixtrading.org, owner page for MMT, opens in a new tab
  • CATConsolidated Audit Trail (SEC Rule 613 and the CAT NMS Plan)CurrentRegulationPost-trade and operations

    Requires a time-sequenced record of each NMS-security order from receipt or origination through routing, modification, cancellation and execution, reported to a central repository by 8:00 a.m. Eastern next trading day.

    Owner
    U.S. Securities and Exchange Commission; CAT NMS Plan participants (national securities exchanges and FINRA)
    Category
    Reporting
    Stage
    Post-trade and operations

    Under Rule 613 the plan must require business clocks synchronized to NIST time and timestamps at least to the millisecond, finer where a firm’s systems use finer increments; FINRA Rule 6820 sets the industry-member tolerance at 50 milliseconds (one second for manual order events) and requires a synchronization log kept for five years. That is 500 times looser than the EU’s 100-microsecond maximum divergence for high-frequency techniques.

    Caveat Reporting duties fall on exchanges, FINRA and their member broker-dealers, not on a research studio. The factor of 500 is arithmetic on the two cited tolerances (50 milliseconds against 100 microseconds), not a figure from either rule.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    catnmsplan.com, owner page for CAT, opens in a new tab
  • RTS 22MiFIR RTS 22: reporting of transactions to competent authorities (Delegated Regulation (EU) 2017/590)CurrentRegulationPost-trade and operations

    Sets the format of MiFIR transaction reports: a common ISO 20022 XML template populated with ISO-coded fields and designations for the person or algorithm responsible for the investment decision and execution.

    Owner
    European Commission / ESMA
    Category
    Reporting
    Stage
    Post-trade and operations

    Every trading algorithm needs a stable identity: when an algorithm makes the investment decision (field 57) or determines the execution (field 59), its designation must be unique per set of code or strategy, used consistently and unique over time. The same regulation pins the identifier stack: ISIN (ISO 6166), LEI (ISO 17442), MIC (ISO 10383), CFI (ISO 10962), ISO 4217 currencies and ISO 8601 timestamps.

    Caveat Read in the original Official Journal text. MiFIR itself was amended by Regulation (EU) 2024/791, so confirm the current consolidated version and field numbering before building against it.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    eur-lex.europa.eu, owner page for RTS 22, opens in a new tab
  • ISO 20022ISO 20022 Universal financial industry message schemeCurrentIndustry standardPost-trade and operations

    Multi-part ISO standard (TC 68) describing a common platform for developing financial messages: a syntax-independent modeling methodology, a central dictionary of business items, and XML and ASN.1 design rules.

    Owner
    ISO (TC 68 Financial Services); ISO 20022 Registration Authority
    Category
    Reporting
    Stage
    Post-trade and operations

    It is a method and repository rather than a wire protocol, and the Registration Authority states that the current edition has nine parts, published in April 2026. For a trading stack it surfaces at the regulatory edge: MiFIR transaction reports must be submitted “in a common XML template in accordance with the ISO 20022 methodology” (RTS 22, Article 1).

    Caveat The February 2022 introduction deck linked from the page still lists eight parts.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    iso20022.org, owner page for ISO 20022, opens in a new tab
10

Governance

Code, data and models are versioned, challenged and reviewed so that each result can be reproduced and each control evidenced.

  • MiFID II Art. 4(1)(39)-(40)MiFID II definitions of algorithmic trading and the high-frequency algorithmic trading techniqueCurrentRegulationGovernance

    Legal definitions: algorithmic trading means a computer algorithm automatically determines order parameters with limited or no human intervention; the high-frequency technique adds latency-minimizing infrastructure, system-determined orders and high intraday message rates.

    Owner
    European Union (Directive 2014/65/EU; Commission Delegated Regulation (EU) 2017/565); ESMA
    Category
    Classification
    Stage
    Governance

    “High message intraday rate” is quantified in Delegated Regulation (EU) 2017/565, Article 19: on average at least 2 messages per second in any single instrument on a venue, or at least 4 per second across all instruments on that venue. Pure order routing and post-trade processing are excluded from the algorithmic-trading definition, so the classification turns on what the software decides, not on how fast it is.

    Caveat EU law; the UK and other regimes define these terms separately. Wording was read in the original Official Journal texts, so check the current consolidated versions before quoting.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    esma.europa.eu, owner page for MiFID II Art. 4(1)(39)-(40), opens in a new tab
  • EU clock sync (ex-RTS 25)EU business-clock synchronization: Delegated Regulation (EU) 2025/1155, replacing MiFID II RTS 25Replaced RTS 25RegulationGovernance

    Requires trading venues, their members, systematic internalizers and data-reporting entities to synchronize business clocks to UTC within set maximum divergence and timestamp granularity, and to document traceability to UTC.

    Owner
    European Commission / ESMA (MiFIR Article 22c)
    Category
    Clock synchronization
    Stage
    Governance

    MiFID II RTS 25 (Delegated Regulation (EU) 2017/574) was repealed with effect from 2 March 2026 and replaced by Delegated Regulation (EU) 2025/1155.

    RTS 25 (Delegated Regulation (EU) 2017/574) was repealed with effect from 2 March 2026; its successor keeps the 100-microsecond maximum divergence for the high-frequency algorithmic trading technique but tightens timestamp granularity from 1 microsecond to 0.1 microseconds or better. Firms must identify the exact point at which a timestamp is applied, show that it stays consistent and review the traceability system at least once a year.

    Caveat In the Official Journal text, Annex IV Table 2 lists only high-frequency, voice, request-for-quote and negotiated activity; the 1-millisecond “any other trading activity” row of the repealed RTS 25 does not appear, so confirm the tolerance for non-HFT algorithmic activity against the consolidated text before relying on it.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    eur-lex.europa.eu, owner page for EU clock sync (ex-RTS 25), opens in a new tab
  • RTS 6MiFID II RTS 6: organizational requirements for investment firms engaged in algorithmic trading (Delegated Regulation (EU) 2017/589)CurrentRegulationGovernance · Simulation · Deployment

    Regulatory technical standards on governance, development and testing, controlled deployment, kill functionality, market-abuse surveillance, pre- and post-trade controls, real-time monitoring and order records for algorithmic trading firms.

    Owner
    European Commission / ESMA
    Category
    Risk controls and regulation
    Stages
    Governance, Simulation, Deployment

    The pre-trade controls are enumerated (price collars, maximum order values, maximum order volumes, maximum message limits; Article 15) and real-time alerts must be generated within five seconds of the event (Article 16). The annual self-assessment must stress-test systems at twice the highest message count and twice the highest trading volume of the previous six months, without affecting production (Article 10).

    Caveat Obligations fall on EU investment firms engaged in algorithmic trading; they are requirements software is engineered to support, not a compliance status a studio can claim. Read in the original Official Journal text, so check for amendments.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    eur-lex.europa.eu, owner page for RTS 6, opens in a new tab
  • MAR Art. 12Market Abuse Regulation, Article 12: manipulation by algorithmic and high-frequency strategies (Regulation (EU) No 596/2014)CurrentRegulationGovernance

    Defines market manipulation in EU law, expressly covering orders placed by algorithmic and high-frequency strategies that disrupt trading systems, obscure genuine orders or create false or misleading signals.

    Owner
    European Union (European Parliament and Council)
    Category
    Risk controls and regulation
    Stage
    Governance

    Article 12(2)(c) names concrete behaviors: overloading or destabilizing the order book, making genuine orders harder to identify, and entering orders “to initiate or exacerbate a trend”. RTS 6 Article 13 turns this into engineering work: firms must run automated surveillance of all orders and transactions against Article 12 and review it at least once a year.

    Caveat Quoted from the original Official Journal text of an act that has since been amended. Whether a given strategy is manipulative is a legal question for counsel, not something this registry or a code review can certify.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    eur-lex.europa.eu, owner page for MAR Art. 12, opens in a new tab
  • FINRA RN 15-09FINRA Regulatory Notice 15-09: supervision and control practices for algorithmic trading strategiesCurrentSupervisory guidanceGovernance · Simulation

    Guidance (26 March 2015) on effective supervision and control practices for firms using algorithmic strategies, organized into risk assessment, code development, testing and validation, trading systems and compliance.

    Owner
    Financial Industry Regulatory Authority (FINRA)
    Category
    Risk controls and regulation
    Stages
    Governance, Simulation

    It reads like an engineering checklist: track every code change through review and approval, archive code versions retrievably, keep a plain summary of each strategy so supervisors can understand its intended function without reading code, and provide a way to disable an algorithm “with a minimal number of steps”. FINRA stresses that the practices are not exhaustive and that following them does not by itself satisfy a firm’s supervisory obligations.

    Caveat Guidance addressed to FINRA member firms, not a rule and not applicable as such to a research studio.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    finra.org, owner page for FINRA RN 15-09, opens in a new tab
  • SR 26-2 (ex-SR 11-7)SR 26-2 Revised Guidance on Model Risk Management (supersedes SR 11-7)Superseded SR 11-7Supervisory guidanceGovernance

    Interagency supervisory guidance of 17 April 2026 on model risk management, covering development and use, validation and monitoring, governance and controls and vendor models; supersedes and replaces SR 11-7.

    Owner
    Board of Governors of the Federal Reserve System, OCC and FDIC
    Category
    Risk controls and regulation
    Stage
    Governance

    SR 11-7 was superseded and replaced by SR 26-2 on 17 April 2026.

    A “model” is a complex quantitative method applying statistical, economic or financial theories to produce estimates; simple arithmetic and deterministic rule-based processes are excluded, and generative and agentic AI are expressly out of scope while non-generative AI models are covered. Validation rests on conceptual soundness, outcomes analysis and ongoing monitoring, with “effective challenge” by people who have the expertise, independence and standing to effect change.

    Caveat Supervisory guidance for banking organizations, most relevant above $30 billion in total assets; it is a reference framework for validation practice, not a rule that binds funds or vendors. Do not cite SR 11-7 as current.

    Checked on 5 November 2026 against the owner’s page or the record named in the caveat. Version numbers and counts describe that date.

    federalreserve.gov, owner page for SR 26-2 (ex-SR 11-7), opens in a new tab

Technologies in
common use.

What a trading stack is commonly built from, stage by stage: what each tool is, what it does there and why it is a usual choice. This describes common practice. It is not a statement of what any firm runs.

80 of 80 shown

Open source
The named core is published under an open-source license, even where the vendor also sells an enterprise edition or a hosted service.
Commercial
A proprietary product or service.
Mixed
Source-available terms, a split-license code base, or editions and model weights under different terms.

License notes summarize each project’s published terms as read on 5 November 2026. They are not legal advice; read the license itself before relying on it.

01

Market-data ingest and transport

Stage: Market data

  • Apache KafkaPlatformOpen sourceMarket data

    Distributed, replicated event log. Carries normalized ticks, orders and fills between feed handlers, strategies and stores, and lets consumers replay a session from retained history.

    Why it is common Apache project; its protocol is also spoken by Redpanda and consumed by ClickHouse and QuestDB connectors.

    License Apache-2.0

    kafka.apache.org, project page for Apache Kafka, opens in a new tab
  • RedpandaPlatformMixedNoteMarket data

    Kafka-API-compatible streaming broker built on a thread-per-core model with Raft replication; used where a Kafka-style log is wanted without operating a JVM or ZooKeeper.

    Why it is common Producers and consumers use the Kafka API, so existing Kafka clients and tooling connect to it.

    Note Source-available under the Business Source License, not OSI open source; the license forbids offering Redpanda as a streaming or queuing service.

    License Business Source License 1.1 for the core (converts to Apache-2.0 four years after each release); Redpanda Community License for enterprise features

    docs.redpanda.com, project page for Redpanda, opens in a new tab
  • AeronLibraryOpen sourceNoteMarket data

    Reliable UDP unicast, UDP multicast and inter-process (IPC) transport with Java, C and C++ clients; Archive records streams for replay, Cluster replicates services with Raft.

    Why it is common Apache-2.0; designed for low, predictable latency; owned and operated by Adaptive Financial Consulting.

    Note Repository moved from real-logic/aeron to aeron-io/aeron; old links redirect.

    License Apache-2.0 (Aeron Premium adds proprietary features under a commercial license)

    github.com, project page for Aeron, opens in a new tab
  • ZeroMQLibraryOpen sourceMarket data

    Brokerless messaging library with pub-sub, request-reply and task-distribution socket patterns over in-process, inter-process, TCP and multicast transports; common glue between research processes and gateways.

    Why it is common MPL-2.0 core (libzmq) implementing ZMTP 3.1; a score of language APIs; runs on most operating systems.

    License MPL-2.0 (libzmq)

    zeromq.org, project page for ZeroMQ, opens in a new tab
  • Simple Binary Encoding (SBE)Protocol implementationOpen sourceNoteMarket data

    Schema-driven binary codec for fixed-layout messages, with reference implementations in Java, C, C++, C#, Go and Rust; decodes exchange market data and encodes internal events.

    Why it is common FIX Trading Community encoding standard; CME’s MDP 3.0 market data is SBE over UDP multicast.

    Note Repository moved from real-logic to aeron-io; old links redirect.

    License Apache-2.0

    github.com, project page for Simple Binary Encoding (SBE), opens in a new tab
  • Protocol BuffersProtocol implementation: serialization format, schema language and code generatorOpen sourceMarket data

    Schema-defined, language-neutral binary serialization with generated bindings; the message layer of gRPC services and of several broker APIs, and a compact format for internal events.

    Why it is common Used by the cTrader Open API and, from version 10.35.01, by Interactive Brokers’ TWS API.

    License BSD-3-Clause

    protobuf.dev, project page for Protocol Buffers, opens in a new tab
02

Storage and time-series databases

Stage: Research data

  • kdb+ / qDatabaseCommercialResearch data

    Columnar time-series database, in-memory engine and streaming processor programmed in the vector language q; the kdb+tick layout pairs a tickerplant with real-time and historical databases.

    Why it is common System under test in published STAC-M3 tick-analytics benchmark reports; as-of join (aj) is a built-in keyword.

    License KX commercial license; KDB-X Community Edition is free for personal and commercial use subject to usage restrictions

    code.kx.com, project page for kdb+ / q, opens in a new tab
  • ClickHouseDatabaseOpen sourceResearch data

    Column-oriented SQL database for analytical queries. Stores and aggregates long tick and bar histories, with ASOF JOIN for non-exact time matching and a Kafka table engine for ingest.

    Why it is common Apache-2.0 core; ASOF JOIN and the Kafka table engine are documented built-ins; Arrow and Parquet import/export.

    License Apache-2.0 (ClickHouse Cloud is a separate commercial service)

    clickhouse.com, project page for ClickHouse, opens in a new tab
  • QuestDBDatabaseOpen sourceNoteResearch data

    Time-series SQL database with column-oriented, time-partitioned storage. Ingests ticks over its wire protocol or InfluxDB Line Protocol and answers SAMPLE BY, LATEST ON and ASOF JOIN queries.

    Why it is common Apache-2.0 open-source edition; PostgreSQL-wire access for drivers and BI tools; documented Kafka and Databento connectors.

    Note Some features are Enterprise-only.

    License Apache-2.0 (QuestDB Enterprise adds commercial features)

    questdb.com, project page for QuestDB, opens in a new tab
  • TimescaleDBDatabaseMixedNoteResearch data

    PostgreSQL extension adding hypertables, a columnstore and continuous aggregates. Keeps bars, fills and reference data in one SQL system reachable with ordinary Postgres drivers.

    Why it is common Packaged as a Postgres extension, so standard SQL and tooling apply; maintained by Tiger Data.

    Note The vendor now trades as Tiger Data; the product name remains TimescaleDB.

    License Apache-2.0 core; Timescale License for code under tsl/

    github.com, project page for TimescaleDB, opens in a new tab
  • Apache ParquetLibrary: file format with reference librariesOpen sourceResearch data

    Column-oriented file format with per-column compression and encoding. The usual at-rest format for research datasets and backtest catalogs, readable without a database server.

    Why it is common Apache format read by pandas, Polars, DuckDB and ClickHouse; NautilusTrader’s data catalog stores Parquet.

    License Apache-2.0

    parquet.apache.org, project page for Apache Parquet, opens in a new tab
  • ArcticDBDatabaseMixedNoteResearch data

    Serverless DataFrame database from Man Group. Stores versioned pandas DataFrames on S3-compatible storage or LMDB and can read earlier versions back for point-in-time research.

    Why it is common Built for time-series data across billions of rows; source-available under BSL 1.1 with paid production licenses.

    Note Source-available under the Business Source License; its README states that production use requires a paid license from ArcticDB Limited.

    License Business Source License 1.1; each release converts to Apache-2.0 two years after publication

    docs.arcticdb.io, project page for ArcticDB, opens in a new tab
02

Research compute and dataframes

Stage: Research data

  • PythonLanguageOpen sourceResearch data

    General-purpose language hosting the research stack: data preparation, modeling, backtests and broker API clients, with compiled extensions doing the numerical work.

    Why it is common Official client language for IBKR, Alpaca, cTrader and MetaTrader 5 APIs, and for LEAN and NautilusTrader strategies.

    License PSF License

    docs.python.org, project page for Python, opens in a new tab
  • NumPyLibraryOpen sourceResearch data

    N-dimensional array library with vectorized arithmetic, linear algebra and random number generation; the in-memory array type pandas, SciPy, scikit-learn and Numba operate on.

    Why it is common Modified-BSD license; a NumFOCUS sponsored project; Numba is designed around NumPy arrays and functions.

    License BSD-3-Clause (modified BSD)

    numpy.org, project page for NumPy, opens in a new tab
  • pandasLibraryOpen sourceResearch data

    Labeled DataFrame and time-series library: resampling, rolling windows, time zones and merge_asof joins that align prices, fundamentals and events by availability time.

    Why it is common Development began at AQR Capital Management in 2008; open-sourced in 2009; NumFOCUS sponsored since 2015.

    License BSD-3-Clause

    pandas.pydata.org, project page for pandas, opens in a new tab
  • PolarsLibraryOpen sourceResearch data

    DataFrame library and query engine written in Rust with lazy, multi-threaded and streaming execution; builds features on tick-scale tables, including join_asof alignment, beyond available RAM.

    Why it is common MIT-licensed; consumes and produces Arrow data, often with zero-copy operations; its own Rust engine, not PyArrow-based.

    License MIT

    docs.pola.rs, project page for Polars, opens in a new tab
  • Apache ArrowLibrary: memory format with multi-language librariesOpen sourceResearch data

    Language-independent columnar memory format with libraries for zero-copy sharing, IPC and RPC transfer; moves tables between Python, Rust, C++ and databases without re-serializing.

    Why it is common Apache project; its adopter list includes pandas, Polars, ClickHouse and Spark.

    License Apache-2.0

    arrow.apache.org, project page for Apache Arrow, opens in a new tab
  • DuckDBDatabaseOpen sourceResearch data

    In-process analytical SQL database with a columnar-vectorized engine. Queries Parquet files and DataFrames in place and supports AsOf joins for point-in-time research tables.

    Why it is common MIT-licensed, with intellectual property held by the DuckDB Foundation; runs embedded, without a server process.

    License MIT

    duckdb.org, project page for DuckDB, opens in a new tab
  • NumbaLibraryOpen sourceResearch data

    Just-in-time compiler translating numerical Python and NumPy code to machine code through LLVM; speeds custom indicators, event loops and path simulations written in plain Python.

    Why it is common BSD-licensed; the compilation layer under VectorBT and hftbacktest’s Python API.

    License BSD-2-Clause

    numba.pydata.org, project page for Numba, opens in a new tab
03

Statistical and classical ML modeling

Stage: Modeling

  • scikit-learnLibraryOpen sourceModeling

    Estimators, pipelines and model selection for classical machine learning: linear models, tree ensembles, probability calibration, metrics and chronological splitters such as TimeSeriesSplit.

    Why it is common BSD-licensed; its fit/predict estimator interface is the convention hmmlearn and gradient-boosting wrappers follow.

    License BSD-3-Clause

    scikit-learn.org, project page for scikit-learn, opens in a new tab
  • XGBoostLibraryOpen sourceModeling

    Gradient-boosted decision trees with regression, classification, quantile and learning-to-rank objectives; a common tabular learner for cross-sectional return ranking and classification labels.

    Why it is common Apache-2.0; documented objectives include binary:logistic, multi:softprob, reg:quantileerror and rank:ndcg.

    License Apache-2.0

    xgboost.readthedocs.io, project page for XGBoost, opens in a new tab
  • LightGBMLibraryOpen sourceNoteModeling

    Histogram-based gradient boosting with leaf-wise tree growth and native categorical splits; suited to wide factor panels and supports a LambdaRank objective for ordering instruments.

    Why it is common MIT-licensed; histogram binning, leaf-wise growth and LambdaRank with NDCG are documented features.

    Note Repository moved from microsoft/LightGBM to lightgbm-org/LightGBM; old links redirect.

    License MIT

    lightgbm.readthedocs.io, project page for LightGBM, opens in a new tab
  • statsmodelsLibraryOpen sourceModeling

    Econometrics library: regression and GLMs, ARIMA and state-space models with Kalman filtering, Engle–Granger cointegration tests and Markov-switching regressions with filtered and smoothed probabilities.

    Why it is common BSD-3-Clause; QuantConnect’s regime-detection research guide fits its MarkovRegression model.

    License BSD-3-Clause

    statsmodels.org, project page for statsmodels, opens in a new tab
  • archLibraryOpen sourceModeling

    Financial econometrics toolbox: ARCH/GARCH-family volatility models, unit-root and cointegration tests, bootstraps, long-run covariance and multiple-comparison tests (SPA, StepM, Model Confidence Set) against data snooping.

    Why it is common NCSA open-source license; one maintained package covering volatility models and reality-check style tests.

    License University of Illinois/NCSA Open Source License

    bashtage.github.io, project page for arch, opens in a new tab
  • hmmlearnLibraryOpen sourceNoteModeling

    Hidden Markov models with a scikit-learn-like API, fitted by EM. Its posterior and Viterbi outputs use the whole sequence, so causal regime filters need a separate forward pass.

    Why it is common BSD-3-Clause; documented among QuantConnect’s research ML libraries.

    Note In limited-maintenance mode according to its README; the last release dates from October 2024.

    License BSD-3-Clause

    hmmlearn.readthedocs.io, project page for hmmlearn, opens in a new tab
  • QuantLibLibraryOpen sourceModeling

    C++ library exported to Python, C#, Java and R for pricing, curve construction, calendars and day-count conventions; supplies instrument valuation and sensitivities to risk and hedging code.

    Why it is common Modified-BSD license, stated as suitable for both free and proprietary applications; actively released.

    License QuantLib License (modified BSD)

    quantlib.org, project page for QuantLib, opens in a new tab
03

Deep learning

Stage: Modeling

  • PyTorchLibraryOpen sourceModeling

    Tensor and automatic-differentiation framework with GPU execution. Trains sequence models, order-book networks and RL policies, and runs pretrained forecasters such as Chronos-2 and TimesFM.

    Why it is common Hosted by the PyTorch Foundation under the Linux Foundation; dependency of Chronos, TimesFM and Stable-Baselines3.

    License BSD-3-Clause-style

    pytorch.org, project page for PyTorch, opens in a new tab
  • TensorFlowLibraryOpen sourceModeling

    Google’s machine-learning platform with the Keras API and deployment tooling (TFX pipelines, TensorFlow Lite); an alternative training and serving path where models already live in Keras.

    Why it is common Apache-2.0; documented as an end-to-end platform with Keras, TFX and TensorFlow Lite components.

    License Apache-2.0

    tensorflow.org, project page for TensorFlow, opens in a new tab
  • JAXLibraryOpen sourceNoteModeling

    NumPy-style array library with composable grad, jit and vmap transformations on CPU, GPU and TPU; used for differentiable simulations, batched Monte Carlo and custom optimization loops.

    Why it is common Apache-2.0; documented for accelerator-oriented array computation; TimesFM also ships a Flax (JAX) implementation.

    Note Repository is jax-ml/jax; documentation moved from jax.readthedocs.io to docs.jax.dev.

    License Apache-2.0

    docs.jax.dev, project page for JAX, opens in a new tab
  • Hugging Face TransformersLibraryOpen sourceModeling

    Model-definition and loading library for pretrained transformers. Supplies text encoders for filings and news, and time-series architectures such as PatchTST and TimesFM.

    Why it is common Apache-2.0; documented as the model-definition framework that training and inference tools interoperate through; a Chronos dependency.

    License Apache-2.0

    huggingface.co, project page for Hugging Face Transformers, opens in a new tab
  • Chronos-2Library: pretrained model with Python packageOpen sourceNoteModeling

    Amazon’s pretrained 120M-parameter time-series model giving zero-shot univariate, multivariate and covariate-informed forecasts; evaluated as a modeling prior against random-walk and local baselines.

    Why it is common Released October 2025; code and amazon/chronos-2 weights are Apache-2.0; installs as chronos-forecasting.

    Note Benchmark rankings on the model card are the vendor’s own statements; usefulness on financial data has to be tested independently.

    License Apache-2.0 (code and amazon/chronos-2 weights)

    github.com, project page for Chronos-2, opens in a new tab
  • TimesFMLibrary: pretrained model with Python packageMixedNoteModeling

    Google Research’s decoder-only pretrained forecaster (ICML 2024) returning point and decile forecasts; PyTorch by default, with a Flax version, for rolling-origin zero-shot evaluation.

    Why it is common Code and weights to 2.5 are Apache-2.0; 3.0 weights are restricted to non-commercial self-hosted use.

    Note TimesFM 3.0 weights (August 2026) carry a non-commercial license: commercial or production use of downloaded weights is not permitted, only use through Google Cloud services. Code and weights up to 2.5 are Apache-2.0.

    License Apache-2.0 for code and weights up to 2.5; timesfm-non-commercial-license-v1.0 for TimesFM 3.0 weights

    github.com, project page for TimesFM, opens in a new tab
  • Stable-Baselines3LibraryOpen sourceModeling

    PyTorch implementations of PPO, A2C, SAC, TD3 and DQN behind one interface; a reproducible baseline when testing learned execution policies inside a market simulator.

    Why it is common MIT-licensed; published in JMLR (2021); QuantConnect’s research documentation trains its PPO implementation.

    License MIT

    stable-baselines3.readthedocs.io, project page for Stable-Baselines3, opens in a new tab
04

Optimization

Stage: Portfolio and risk

  • CVXPYLibraryOpen sourcePortfolio and risk

    Python-embedded modeling language for convex problems. States mean–variance objectives with turnover, exposure and position constraints close to the mathematics, then dispatches to a solver.

    Why it is common Apache-2.0; distributed with Clarabel, OSQP and SCS; also interfaces Gurobi, MOSEK, CPLEX and HiGHS.

    License Apache-2.0

    cvxpy.org, project page for CVXPY, opens in a new tab
  • OSQPEngine: solverOpen sourcePortfolio and risk

    ADMM-based solver for convex quadratic programs with warm starting and embeddable C code generation; fits repeated rebalances where consecutive problems are similar.

    Why it is common Apache-2.0; the solver CVXPY calls by default for quadratic programs.

    License Apache-2.0

    osqp.org, project page for OSQP, opens in a new tab
  • HiGHSEngine: solverOpen sourceNotePortfolio and risk

    Solvers for linear, mixed-integer and quadratic programs (simplex, interior point, branch-and-cut); handles lot rounding and linearized selection models without a commercial license.

    Why it is common MIT-licensed; scipy.optimize.milp is documented as a wrapper of HiGHS; linprog exposes “highs” methods.

    Note Solves LP, MIP and convex QP; it is not a mixed-integer quadratic solver, so cardinality-constrained mean–variance still needs an MIQP solver or a linearization.

    License MIT

    highs.dev, project page for HiGHS, opens in a new tab
  • SciPy (scipy.optimize)LibraryOpen sourcePortfolio and risk

    General numerical optimization in Python: minimize with SLSQP or trust-constr, least_squares, linprog and milp; the everyday tool for calibration and small constrained allocations.

    Why it is common BSD-3-Clause; part of core SciPy; its linear and mixed-integer routines wrap HiGHS.

    License BSD-3-Clause

    docs.scipy.org, project page for SciPy (scipy.optimize), opens in a new tab
  • GurobiEngine: solverCommercialPortfolio and risk

    Commercial solver for LP, QP and mixed-integer models including MIQP; provides bounded-gap solutions for cardinality-constrained portfolios and the exact classical reference for QUBO experiments.

    Why it is common Documented model classes span LP, QP, QCP, MIP, MIQP and MIQCP; interfaced by CVXPY.

    License Commercial license; paid or academic.

    docs.gurobi.com, project page for Gurobi, opens in a new tab
  • MOSEKEngine: solverCommercialPortfolio and risk

    Commercial interior-point solver for linear, conic quadratic, semidefinite and mixed-integer problems; used for robust, factor-model and transaction-cost portfolio formulations.

    Why it is common Publishes a Portfolio Optimization Cookbook covering Markowitz, factor models, transaction costs and risk budgeting; interfaced by CVXPY.

    License Commercial license; paid or academic.

    mosek.com, project page for MOSEK, opens in a new tab
04

Quantum SDKs

Stage: Portfolio and risk

  • QiskitLibraryOpen sourceNotePortfolio and risk

    IBM’s open-source SDK for building, transpiling and running circuits through primitives; used for QAOA portfolio experiments on simulators and IBM hardware.

    Why it is common Apache-2.0; documented on IBM Quantum Platform with transpiler, primitives and QAOA tutorials.

    Note The separate Qiskit Optimization package was archived on 12 July 2026; IBM points to qiskit-addon-opt-mapper for problem mapping.

    License Apache-2.0 (hardware access is a separate IBM service)

    quantum.cloud.ibm.com, project page for Qiskit, opens in a new tab
  • PennyLaneLibraryOpen sourcePortfolio and risk

    Xanadu’s Python library for differentiable quantum programming; trains variational circuits with automatic differentiation and connects them to PyTorch, JAX and NumPy.

    Why it is common Apache-2.0; built-in automatic differentiation of quantum circuits; device plugins such as PennyLane-Rigetti.

    License Apache-2.0

    docs.pennylane.ai, project page for PennyLane, opens in a new tab
  • D-Wave Ocean SDKLibraryOpen sourceNotePortfolio and risk

    Python tools for building binary and constrained quadratic models and sampling them with classical simulated annealing, hybrid solvers or D-Wave annealers.

    Why it is common Apache-2.0 SDK; documented as the tool suite for D-Wave quantum computers and hybrid solvers.

    Note Its classical SimulatedAnnealingSampler is not a quantum computation.

    License Apache-2.0 SDK; annealer and hybrid-solver access through the commercial Leap service

    docs.dwavequantum.com, project page for D-Wave Ocean SDK, opens in a new tab
  • CUDA-QPlatformOpen sourcePortfolio and risk

    NVIDIA’s open-source platform for hybrid quantum-classical programs in Python and C++, with GPU-accelerated simulation for benchmarking variational algorithms.

    Why it is common Apache-2.0; C++ and Python support for heterogeneous quantum-classical workflows; multi-GPU and multi-QPU execution documented.

    License Apache-2.0

    nvidia.github.io, project page for CUDA-Q, opens in a new tab
  • CirqLibraryOpen sourcePortfolio and risk

    Google’s Python library for writing, optimizing and running circuits on simulators and quantum processors, with abstractions aimed at noisy intermediate-scale hardware.

    Why it is common Apache-2.0; the framework Google Quantum AI uses to run experiments on its processors.

    License Apache-2.0

    quantumai.google, project page for Cirq, opens in a new tab
05

Backtest and simulation engines

Stage: Simulation

  • LEANEngineOpen sourceSimulation

    QuantConnect’s event-driven engine for research, backtesting and live trading in Python or C#, with configurable fill, fee and slippage models and brokerage adapters.

    Why it is common Apache-2.0; documented live brokerages include Interactive Brokers, Alpaca, Tradier and Charles Schwab.

    License Apache-2.0

    lean.io, project page for LEAN, opens in a new tab
  • NautilusTraderEngineOpen sourceSimulation

    Rust-native, event-driven trading engine with a Python control plane. Replays L1–L3 order-book, quote and trade data at nanosecond resolution and runs the same strategy code live.

    Why it is common LGPL-3.0; documented adapters include Interactive Brokers, Databento, Betfair and Binance.

    License LGPL-3.0-or-later

    nautilustrader.io, project page for NautilusTrader, opens in a new tab
  • VectorBTEngineMixedNoteSimulation

    Vectorized backtesting on pandas and NumPy objects accelerated by Numba; evaluates large parameter grids as array operations with explicit fee and slippage inputs.

    Why it is common Apache-2.0 with Commons Clause for the open-source edition; the PRO edition is commercial; actively released.

    Note The Commons Clause withholds the right to sell a product or service whose value derives substantially from the software, and it names consulting and support fees.

    License Apache-2.0 with Commons Clause v1.0 (open-source edition); VectorBT PRO is a paid membership

    vectorbt.dev, project page for VectorBT, opens in a new tab
  • Zipline ReloadedEngineOpen sourceNoteSimulation

    Maintained fork of Quantopian’s event-driven backtester; simulates strategies on pandas data with built-in performance statistics.

    Why it is common Apache-2.0; maintained for compatibility with current Python versions.

    Note In maintenance mode: its documentation says new feature development has moved to ML4T Backtest and recommends evaluating that for new projects.

    License Apache-2.0

    zipline.ml4trading.io, project page for Zipline Reloaded, opens in a new tab
  • QlibPlatformOpen sourceNoteSimulation

    Microsoft’s AI-oriented quant research platform: point-in-time database, forecasting models, portfolio backtests, rolling retraining and QlibRL for order-execution reinforcement learning.

    Why it is common MIT-licensed; QlibRL builds on Tianshou and Gym; integrates RD-Agent for automated factor research.

    Note The latest PyPI release dates from August 2025; a research framework rather than production infrastructure.

    License MIT

    github.com, project page for Qlib, opens in a new tab
  • hftbacktestEngineOpen sourceNoteSimulation

    Tick-by-tick backtester that rebuilds the order book from L2 or L3 feeds and models feed latency, order latency and queue position for market-making research.

    Why it is common MIT-licensed; Python (Numba) and Rust APIs; latency and queue-position models are documented features.

    Note Community project whose examples and live connectors target crypto venues; the latest PyPI release dates from December 2025.

    License MIT

    github.com, project page for hftbacktest, opens in a new tab
06

Model packaging and serving

Stage: Deployment

  • ONNX RuntimeEngineOpen sourceDeployment

    Inference engine for models exported to ONNX from PyTorch, scikit-learn and other frameworks; takes the training framework out of the live scoring path.

    Why it is common MIT-licensed; execution providers for CPU, CUDA, TensorRT and OpenVINO; also a Triton backend.

    License MIT

    onnxruntime.ai, project page for ONNX Runtime, opens in a new tab
  • NVIDIA Triton Inference ServerPlatformOpen sourceNoteDeployment

    Inference server exposing HTTP and gRPC endpoints over a file-based model repository, with batching and metrics; suits shared GPU scoring services for several model frameworks.

    Why it is common BSD-3-Clause; backends include ONNX Runtime, PyTorch, TensorRT and FIL for tree ensembles.

    Note Suited to shared GPU serving for several models, not to a single-strategy deployment.

    License BSD-3-Clause

    docs.nvidia.com, project page for NVIDIA Triton Inference Server, opens in a new tab
  • gRPCProtocol implementationOpen sourceDeployment

    HTTP/2-based RPC framework with typed service definitions and bidirectional streaming; links strategy, risk and model-scoring services written in different languages.

    Why it is common CNCF incubation project; client libraries for many languages; Triton accepts inference requests over it.

    License Apache-2.0

    grpc.io, project page for gRPC, opens in a new tab
  • FastAPILibraryOpen sourceNoteDeployment

    Typed Python web framework generating OpenAPI schemas; serves model-scoring endpoints and receives, validates and deduplicates TradingView webhook alerts before they reach order controls.

    Why it is common MIT-licensed; built on Starlette and Pydantic; request validation from standard Python type hints.

    Note A general-purpose web framework, not a trading-specific component.

    License MIT

    fastapi.tiangolo.com, project page for FastAPI, opens in a new tab
  • DockerPlatformMixedDeployment

    Builds and runs container images that pin the OS, interpreter and native libraries, so a research replay and the deployed service execute the same environment.

    Why it is common Docker Engine is Apache-2.0; NautilusTrader documents Docker deployment and the LEAN CLI supports custom Docker images.

    License Docker Engine: Apache-2.0. Docker Desktop requires a paid subscription for larger organizations.

    docs.docker.com, project page for Docker, opens in a new tab
07

Execution and broker connectivity

Stage: Order routing

  • QuickFIXProtocol implementationOpen sourceOrder routing

    Open-source FIX engine in C++ with Python and Ruby bindings; manages sessions, sequence numbers, heartbeats and resends for order routing and drop-copy links.

    Why it is common Free under the QuickFIX Software License; sibling engines cover Java (QuickFIX/J), .NET and Go.

    License QuickFIX Software License 1.0 (permissive, with an attribution clause)

    quickfixengine.org, project page for QuickFIX, opens in a new tab
  • QuickFIX/JProtocol implementationOpen sourceOrder routing

    Pure-Java FIX engine covering FIX 4.0 to 5.0 SP2, FIXT 1.1 and FIX Latest; embeds session management and message validation in JVM order gateways.

    Why it is common 100% Java with no native libraries; QuickFIX Software License.

    License QuickFIX Software License 1.0

    quickfixj.org, project page for QuickFIX/J, opens in a new tab
  • Interactive Brokers TWS APIPlatform: broker APICommercialNoteOrder routing

    TCP socket API to Trader Workstation or IB Gateway with official Python, Java, C++ and C# clients; asynchronous order events must be reconciled against account positions.

    Why it is common Broker-maintained message protocol; LEAN and NautilusTrader both document Interactive Brokers integrations.

    Note The API is installed from Interactive Brokers; the PyPI package named ibapi is a stale copy from December 2020.

    License Proprietary (IB API Non-Commercial or Commercial license); requires an IBKR account

    interactivebrokers.com, project page for Interactive Brokers TWS API, opens in a new tab
  • Alpaca Trading APIPlatform: broker APICommercialOrder routing

    REST order and account API with WebSocket trade-update streams and a free paper-trading environment for end-to-end order-flow tests.

    Why it is common Official alpaca-py SDK is Apache-2.0 and actively released; listed among LEAN’s live brokerages.

    License Brokerage service; official SDK alpaca-py is Apache-2.0

    docs.alpaca.markets, project page for Alpaca Trading API, opens in a new tab
  • cTrader Open APIPlatform: broker APICommercialNoteOrder routing

    Spotware’s API for custom applications on the cTrader backend: JSON or Protobuf messages over TCP or WebSocket, with application authorization and a 10-second heartbeat.

    Why it is common Official SDKs for Python (OpenApiPy) and C# (OpenAPI.Net); Protobuf message references are published.

    Note The official Python SDK has had no stable release since June 2024; a 0.9.3 release candidate followed in August 2024.

    License Proprietary service; official SDKs (OpenApiPy, OpenAPI.Net) are MIT-licensed

    help.ctrader.com, project page for cTrader Open API, opens in a new tab
  • MQL5LanguageCommercialOrder routing

    C++-like language built into MetaTrader 5 for Expert Advisors, indicators, scripts and services; a successful OrderSend call still needs confirmation from subsequent trade events.

    Why it is common Native language of the MetaTrader 5 terminal; MetaQuotes also publishes a Python integration package.

    License Proprietary; bundled with the MetaTrader 5 terminal

    mql5.com, project page for MQL5, opens in a new tab
  • Pine Script and TradingView webhooksLanguageCommercialOrder routing

    TradingView’s cloud-run scripting language for indicators and strategies; alerts can POST webhooks to an external service that validates and routes orders.

    Why it is common Pine Script is TradingView’s documented language; scripts run on TradingView servers under stated resource limits.

    License Proprietary TradingView service

    tradingview.com, project page for Pine Script and TradingView webhooks, opens in a new tab
08

Low-latency engineering

Stage: Venue access

  • C++LanguageOpen sourceVenue access

    ISO-standardized systems language with deterministic memory management; implements feed handlers, order gateways and latency-sensitive strategy cores where garbage-collection pauses are unacceptable.

    Why it is common ISO-standardized; implementation language of QuickFIX, QuantLib, Redpanda and libzmq.

    License ISO standard; GCC (GPL) and Clang/LLVM (Apache-2.0 with LLVM exception) toolchains are open source

    isocpp.org, project page for C++, opens in a new tab
  • RustLanguageOpen sourceVenue access

    Systems language without a runtime or garbage collector whose ownership model enforces memory and thread safety at compile time; used for engine cores, parsers and adapters.

    Why it is common MIT/Apache-2.0; implementation language of NautilusTrader’s core, Polars, hftbacktest and the Clarabel solver.

    License MIT or Apache-2.0

    rust-lang.org, project page for Rust, opens in a new tab
  • Java (JVM)LanguageOpen sourceVenue access

    JVM language with mature concurrency tooling; with allocation-free hot paths it runs matching engines, messaging layers and FIX gateways.

    Why it is common OpenJDK is GPL-2.0 licensed; implementation language of LMAX Disruptor, Aeron and QuickFIX/J.

    License OpenJDK: GPL-2.0 with Classpath Exception

    dev.java, project page for Java (JVM), opens in a new tab
  • LMAX DisruptorLibraryOpen sourceVenue access

    Lock-free ring-buffer library for passing events between threads without queue contention; sequences market-data, strategy and order stages on dedicated cores.

    Why it is common Apache-2.0; open-sourced by LMAX Exchange from its trading platform, with a published technical paper.

    License Apache-2.0

    lmax-exchange.github.io, project page for LMAX Disruptor, opens in a new tab
  • DPDKLibraryOpen sourceVenue access

    User-space libraries and poll-mode drivers that take packets directly from the network card, bypassing the kernel network stack; a base for custom feed handlers and gateways.

    Why it is common Linux Foundation project; BSD-3-Clause core; named in the kernel’s CPU-isolation guide for low-latency packet processing.

    License BSD-3-Clause core libraries and drivers; kernel components GPL-2.0

    doc.dpdk.org, project page for DPDK, opens in a new tab
  • Kernel-bypass networking (OpenOnload, ef_vi)Hardware techniqueOpen sourceNoteVenue access

    User-level TCP and UDP stack that accelerates unmodified BSD-socket applications; its ef_vi interface gives feed handlers direct access to AMD Solarflare adapters.

    Why it is common Open source (GPL-2.0 and BSD-2-Clause); README states binary compatibility with existing applications.

    Note Native acceleration needs AMD Solarflare adapters; an AF_XDP mode covers other network cards.

    License GPL-2.0, with ef_vi and selected components under BSD-2-Clause

    github.com, project page for Kernel-bypass networking (OpenOnload, ef_vi), opens in a new tab
  • FPGA feed handlersHardware techniqueCommercialNoteVenue access

    Market-data decoding, book building and pre-trade risk checks implemented in FPGA logic beside the network port, taking software and operating-system delay out of the tick-to-trade path.

    Why it is common STAC’s FPGA group describes FPGAs as mainstream in financial markets for network I/O, market data and pre-trade risk.

    Note A technique, not a product; vendor latency figures are vendor claims and are not repeated here.

    License Proprietary hardware, toolchains and vendor IP cores

    docs.stacresearch.com, project page for FPGA feed handlers, opens in a new tab
  • Linux CPU isolation and core pinningHardware techniqueOpen sourceVenue access

    Kernel features (cpuset isolated partitions, nohz_full, IRQ affinity) that dedicate cores to a single busy thread, removing scheduler ticks and interrupts from the latency tail.

    Why it is common Documented in the Linux kernel admin guide, which cites low-latency network processing with DPDK as a use case.

    License Linux kernel (GPL-2.0)

    docs.kernel.org, project page for Linux CPU isolation and core pinning, opens in a new tab
09

Observability and operations

Stage: Post-trade and operations

  • PrometheusPlatformOpen sourcePost-trade and operations

    Pull-based metrics server with a labeled time-series model, PromQL and Alertmanager; tracks order latency, reject rates, feed gaps and position drift.

    Why it is common Apache-2.0; joined the CNCF in 2016 as its second hosted project after Kubernetes.

    License Apache-2.0

    prometheus.io, project page for Prometheus, opens in a new tab
  • GrafanaPlatformOpen sourcePost-trade and operations

    Dashboards and alert rules over Prometheus, SQL databases and other sources; the operator’s single view of strategy, connectivity and infrastructure health.

    Why it is common AGPL-3.0 open-source edition; QuestDB documents Grafana access over its PostgreSQL wire protocol.

    License AGPL-3.0 (Grafana Enterprise is a separate commercial edition)

    grafana.com, project page for Grafana, opens in a new tab
  • OpenTelemetryLibrary: specification, SDKs and CollectorOpen sourcePost-trade and operations

    Vendor-neutral APIs, SDKs and Collector for traces, metrics and logs; follows one order from signal to acknowledgement across services through propagated context.

    Why it is common Apache-2.0; governed under the CNCF; open specifications for APIs, SDKs and the OTLP wire protocol.

    License Apache-2.0

    opentelemetry.io, project page for OpenTelemetry, opens in a new tab
  • KubernetesPlatformOpen sourceNotePost-trade and operations

    Container orchestration for declarative deployments, health probes, restarts and scheduled jobs; runs research batch work and trading services that are not latency-critical.

    Why it is common Apache-2.0; hosted by the CNCF, which also hosts Prometheus, gRPC and OpenTelemetry.

    Note Suited to research batch work and supporting services; latency-critical paths normally run on pinned bare-metal cores instead.

    License Apache-2.0

    kubernetes.io, project page for Kubernetes, opens in a new tab
  • Apache AirflowPlatformOpen sourcePost-trade and operations

    Python-defined workflow scheduler; orchestrates daily data loads, point-in-time snapshots, retraining and report jobs with retries and a record of every run.

    Why it is common Apache-2.0 project built to programmatically author, schedule and monitor workflows.

    License Apache-2.0

    airflow.apache.org, project page for Apache Airflow, opens in a new tab
10

Experiment tracking and reproducibility

Stage: Governance

  • MLflowPlatformOpen sourceGovernance

    Experiment tracking, model packaging and registry; records parameters, metrics, code version and artifacts for each backtest or training run so results can be reproduced.

    Why it is common Apache-2.0 project under LF Projects (Linux Foundation); documents tracking, packaging, registry and deployment components.

    License Apache-2.0

    mlflow.org, project page for MLflow, opens in a new tab
  • DVCPlatform: command-line toolOpen sourceNoteGovernance

    Git-based versioning for datasets, models and pipelines; pins the exact data snapshot behind each experiment while large files stay in object storage.

    Why it is common Apache-2.0; works as a Git extension; repository now maintained under treeverse/dvc alongside lakeFS.

    Note Repository moved from iterative/dvc to treeverse/dvc; documentation is at doc.dvc.org.

    License Apache-2.0

    doc.dvc.org, project page for DVC, opens in a new tab
  • OptunaLibraryOpen sourceGovernance

    Define-by-run hyperparameter optimization with pruning of unpromising trials and parallel studies; every trial is recorded, which keeps the count of configurations tried honest.

    Why it is common MIT-licensed; introduced at KDD 2019; samplers, pruners and study storage are core modules.

    License MIT

    optuna.readthedocs.io, project page for Optuna, opens in a new tab
  • RayPlatformOpen sourceGovernance

    Distributed Python runtime with libraries for data, training, tuning (Ray Tune), serving and reinforcement learning (RLlib); fans backtests and sweeps out across cores or nodes.

    Why it is common Apache-2.0; listed among projects hosted by the PyTorch Foundation under the Linux Foundation.

    License Apache-2.0

    docs.ray.io, project page for Ray, opens in a new tab
  • GitPlatform: version-control toolOpen sourceGovernance

    Distributed version control; the commit hash recorded with each experiment ties a result to exact code, configuration and lockfiles.

    Why it is common GPL-2.0; the versioning layer that DVC extends for data and pipelines.

    License GPL-2.0

    git-scm.com, project page for Git, opens in a new tab

How this reference is kept.

Verified on a date
Every standard was checked on 5 November 2026 and every technology on 5 November 2026, against the owner’s page or the official record the entry’s caveat names. Version numbers, counts and license notes describe that date.
Statuses change
Rules are repealed, guidance is superseded and versions are archived. The changes on record are listed above, and an entry that is current today can change without notice here.
The owner page is the authority
Each row links to it. Where this page and an owner’s page differ, the owner’s page is right. Nothing here is legal, regulatory or licensing advice.
What the list is
The specifications and tools the studio engineers against. It is not a list of affiliations: no entry indicates a certification, membership, partnership, endorsement or license.