Services & customers
Sections ↑BMLL supplies granular historical market data and institutional analytics. Customers can study order-book events rather than only daily prices or completed trades. Its published T+1 service is not a replacement for the live executable quote feed needed by a trading application.[1]
The three principal product routes
| Product | Main role | Typical workflow |
|---|---|---|
| Data Lab | Managed cloud research environment with Python-based tools and access to data. | Develop and run analyses near the dataset.Source 2 |
| Data Feed | Historical data and derived analytics delivered into customer systems. | Use the customer’s own storage, warehouse or analytical infrastructure.Source 3 |
| Vantage | No-code visual application for market-structure analysis. | Explore liquidity, fragmentation and venue-quality measures without building a notebook.Source 5 |
The published model distinguishes Level 1 best prices, Level 2 price-aggregated depth and Level 3 individual order events. Those views answer different questions; reconstructing an order lifecycle requires identifiers and granular events, not just a larger file.[1]
Platforms & integrations
Sections ↑Delivery and access options
| Route | Published mechanism | Boundary |
|---|---|---|
| Cloud and file delivery | APIs, files and cloud-storage distribution are described for Data Feed. | Delivery format and storage destination are part of the selected service.Source 3 |
| Data-platform integration | Databricks and Snowflake are among the published access routes. | A warehouse connection does not itself grant every dataset or redistribution right.Source 3 |
| Research environment | Python tools, notebooks, scheduling and scalable compute in Data Lab. | A managed research runtime is different from an unrestricted external raw-data export.Source 2 |
| Visual analysis | Vantage permits chart and data export and supports integration with the other BMLL products. | Export functionality is not a blanket licence to republish the underlying dataset.Source 5 |
A harmonised schema reduces the amount of venue-specific decoding a customer must maintain. It does not remove economic differences between venues or trading mechanisms. The feed documentation remains relevant to interpreting fields and dataset scope; a familiar column name should not be taken to mean that every venue produces an identical event stream. A sound comparison retains market, instrument and time conventions alongside the numerical observations.[4][1]
Pricing & commercial terms
Sections ↑The reviewed pages provide product and trial routes but not a complete public enterprise price schedule. A meaningful quotation needs the markets, history, granularity, users, compute and delivery model to be clear. Comparing a research environment with a data-only feed as though both were the same subscription would conceal substantial differences in what is purchased.[6][3][2]
Commercial scope that changes what is being purchased
| Dimension | Published distinction | Pricing implication |
|---|---|---|
| Research versus delivery | Data Lab supplies an environment; Data Feed supplies data to another environment. | Compute and operating responsibility are not necessarily priced in the same way.Source 2Source 3 |
| Trial versus production | The Data Lab comparison shows smaller trial resources and different enterprise capabilities. | A successful trial does not establish the resources or entitlements in a production offer.Source 2 |
| Dataset access | Some markets are unavailable in the trial because of exchange licensing. | Trial access is not evidence that every advertised market is included free of additional conditions.Source 2 |
| Visual application | Vantage is a separate no-code analytical route. | Its user workflow and export permissions need to be distinguished from feed access.Source 5 |
Implementation & delivery
Sections ↑For a feed deployment, the implementation centres on receiving the chosen datasets, loading them into the intended environment and keeping their versions and identifiers consistent. For Data Lab, more of the data engineering and runtime is supplied by BMLL. Those operating models move work between vendor and customer; they do not eliminate the need to document the analysis and verify that its inputs match the research question.[3][2]
Data interpretation boundaries
| Question | Useful distinction |
|---|---|
| Is the input executable now? | The published T+1 historical offering is not a live quote commitment.Source 1 |
| What does a row represent? | Order-level events, price-level depth and derived analytics answer different questions.Source 4 |
| Which market mechanism is being compared? | Vantage separates mechanisms such as auctions, continuous trading and other venue categories.Source 5 |
| Can a result be reproduced? | Data Lab’s notebook and scheduling functions support repeatable workflows, but the customer must still retain its code, parameters and dataset selection.Source 2 |
Analytical interpretation: a historical test can be precise about the event sequence while still be unrealistic about execution. A customer needs to distinguish information available at the simulated decision time from information learned later, and a displayed queue from a guaranteed fill. BMLL supplies research inputs and tools; the reviewed material is not independent evidence that a particular customer model would have achieved its simulated results.[4][5]
Support & contacts
Sections ↑Trial, commercial and privacy contacts
Data Lab distinguishes standard trial support from dedicated enterprise support. The public comparison does not specify a universal response or recovery-time guarantee.[2]
Permissions & service scope
Sections ↑BMLL’s vendor-of-record statement addresses supplied exchange licences. It does not establish unlimited buyer redistribution, affiliate access or post-termination retention rights; those depend on the purchased use rights.[1]
The privacy notice distinguishes BMLL’s own controller activities from processing on behalf of an organisation when its personnel use the service. That distinction concerns personal information such as user and account records, not ownership of exchange market data. A data licence and a personal-data processing arrangement address different subjects even when both are part of the same service relationship.[7]
Operator & evidence
Sections ↑The privacy notice identifies BMLL Technologies Limited and gives its London address as the fifth floor of Bentima House, 168–172 Old Street. The company’s 2026 updates describe Nordic Capital’s October 2025 acquisition, with management and Optiver retaining a minority position. This is an ownership description from company-published material; no inference about an undisclosed current ownership percentage is made.[7][9]
The September 2026 company update describes a business founded in 2014 and a product scope extending beyond its earlier equities focus. The current coverage categories include equities, ETFs, futures, options and prediction markets. A category appearing in the catalogue should not be confused with complete coverage of every venue and instrument in that category.[8]
- Operator
- BMLL Technologies Limited
- Service scope
- BMLL supplies historical granular market data through Data Feed, a managed Data Lab and the Vantage visual application. This profile examines delivery choices, data granularity, trial limitations, licensing boundaries and institutional research use.
- Customer types
- Banks and brokers; Asset managers; Systematic trading and research firms; Exchanges and trading venues; Regulators
- Delivery
- Hosted; API; SaaS
- Pricing publication
- Quote only
- Platforms
- BMLL Data Feed; BMLL Data Lab; BMLL Vantage
- Implementation
- Data Feed enters a customer environment; Data Lab supplies a managed research environment. Dataset scope, delivery and computational resources differ.
- Support
- Published UK, US and APAC enquiry routes. Data Lab distinguishes standard trial and dedicated enterprise support.
- Permissions and regulatory scope
- Market-data licensing is distinct from financial authorisation. BMLL’s vendor-of-record statement does not establish unrestricted customer redistribution rights.
Provider metadata checked 20 Oct 2026Source 1Source 3Source 6Source 7
Additional Information
Sections ↑Vantage and Data Lab serve different research users. A no-code analyst may need a repeatable venue comparison and exported chart, while a quantitative team may need custom code over granular observations. Keeping both within one provider profile avoids presenting them as unrelated vendors, but their commercial and technical entitlements should remain distinct.[5]
An exchange-history dataset does not necessarily contain an OTC broker’s internal quotes, last-look decisions or client fills. Those records need their own source before the broker’s complete execution process can be analysed.[1][3]
Sources & further reading
- BMLL historical data and analytics model BMLL · Accessed 20 Oct 2026
- BMLL Data Lab and trial/enterprise capabilities BMLL · Accessed 20 Oct 2026
- BMLL Data Feed delivery routes BMLL · Accessed 20 Oct 2026
- BMLL Data Feed documentation BMLL · Accessed 20 Oct 2026
- BMLL Vantage no-code market-structure analytics BMLL · Accessed 20 Oct 2026
- BMLL contact and trial enquiries BMLL · Accessed 20 Oct 2026
- BMLL privacy notice and legal identity BMLL · Accessed 20 Oct 2026
- September 2026 company and product update BMLL · 18 Sep 2026 · Accessed 20 Oct 2026
- Company update following Nordic Capital acquisition BMLL · Accessed 20 Oct 2026
This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.