Pico: Corvil analytics, Redline trading software and managed market infrastructure

Pico supplies technology for capital-markets firms through three related businesses: Corvil analytics, Redline trading and data software, and Market Services infrastructure. The combination can support an institution’s trading stack from market-data receipt to execution monitoring and ongoing operations. A customer can also purchase a narrower component.[1]

Corvil’s passive network-tap architecture captures, timestamps, decodes and correlates traffic without inserting an application agent into that capture path. Its wider product family also includes optional sensors and application instrumentation. That distinction matters when deciding what a proposed deployment will install and which events it can observe.[2]

InRush maintains in-memory order books and produces normalised updates through an application interface. Its NBBO and EBBO calculations consider quote conditions and trading status. Subscriber filtering limits unnecessary delivery, while recorded PCAP data can be replayed through the same API used by the live feed. The published deployment is a Linux server; the selected feed and application configuration determine actual performance.[4]

Execution Gateway can run embedded with an application or as a central execution hub. It normalises venue interfaces, persists execution state and supports reconnecting and recovering transaction sequences. The documented recovery includes reconciliation of multi-day good-till-cancelled orders. Higher-level OMS functions, such as broader workflow and allocation, remain a separate application role.[6]

Corvil’s API and SDK expose real-time and historical metrics, trading messages and underlying packets. PCAP exports can be filtered by time, protocol, session or metric, and custom decoders extend interpretation. This provides an evidence path from an aggregate latency symptom to the messages and packets behind it. Connectors can feed existing observability and incident-management tooling.[8]

Venue Access offers dedicated or shared connections, with 10, 40 or 100 Gbps handoffs depending on the venue and requirement. Shared connectivity can act as a primary route or backup. Pico also describes aggregating venue drop copies into a central location. These services establish technical access paths; a firm’s trading, clearing and data entitlements remain part of the relevant commercial arrangements.[13]

The reviewed product pages provide architecture and service choices rather than a standard monetary rate card. A proposal needs to identify the software, venues, data delivery, hardware, hosting and operational scope. Comparing only a headline software fee would omit material parts of a fully managed deployment.[3]

Pico’s public website terms apply to use of the website. Their website liability and usage provisions are not a production service agreement. Renewal, early termination, service credits, data-export assistance, post-termination access and destruction deadlines should be established in the actual order and service schedules. No uniform public customer exit timetable was identified in the reviewed material.[21]

Pico’s delivery process assigns a project manager, documents requirements and plans around long-lead components and circuit terminations. Implementation includes physical, logical, security and user-acceptance testing. A knowledge-transfer document and formal client sign-off precede the handover to Service Operations. Projects can include customer-managed or third-party infrastructure, with early access to individual components where the plan permits.[16]

Device Management accepts customer-owned or Pico-procured hardware. Build work includes BIOS configuration, core pinning, network and operating-system setup and validation. Customers can stop at handover or select continuing patching and monitoring. Pico retains the customer’s patch schedules and approval workflows; the page’s typical one-to-three-day deployment estimate starts after equipment receipt, rather than at contract signature.[15]

In Redline’s managed model, the supplier tracks exchange protocol changes, tests them and deploys updates. Historical recording and replay are an optional service component. The customer should specify that scope when it requires a reproducible record for investigations or testing; managed connectivity alone does not imply purchase of an archive.[14]

Service Operations describes 24/7 coverage across the Americas, EMEA and Asia-Pacific. Its workflow includes start-of-day and start-of-week checks, incident response, venue and equipment-vendor liaison, and customer-specific maintenance windows. Changes have pre-change tests, post-change verification and rollback procedures. Those operational practices are more specific than a general uptime claim, but the public page does not publish a universal severity-based restoration commitment.[17]

Monthly service reviews cover tickets, reasons for outages, time to resolve incidents, latency and bandwidth. Pico also uses “mean time to innocence” to describe how quickly telemetry can establish whether an issue originates in its infrastructure or elsewhere. Corvil’s packet-level evidence supports that distinction. Monitoring connectivity can allow the operations service to cover infrastructure that Pico did not build.[17]

The enquiry page says a solution architect responds within one business day. That is a commercial-contact expectation and should be kept separate from the response obligations for an existing production incident.[25]

Pre-trade checks run inline with execution and can cover quantity, price, positions and trading state. Embedded, centralised and distributed deployments are documented. The broker controls the policies: Execution Gateway describes broker access to risk parameters through a relational-database interface. These controls support a financial firm’s obligations; purchasing the technology is not itself a financial-services permission.[7][6]

Corvil Actions has active operational capabilities as well as analytical views. Configured integrations can trigger tasks, modify configurations or restrict access, while other actions retrieve partner dashboards and visualisations. Access to analytics therefore needs to be distinguished from permission to run an operational action. The product page does not describe a general autonomous trading agent.[9]

Pico says its security programme includes SOC 2 Type 2 attestation, role-based access, MFA, network segmentation and security monitoring. It publishes TLS 1.2+ and AES-256 controls, and secure destruction aligned with NIST 800-88. The actual attestation report and customer-specific control scope were not inspected. Incident notification is explicitly tied to severity and contractual obligations, so no fixed universal notification deadline is inferred.[18]

The network acceptable-use policy applies to covered services and is incorporated into the customer’s agreement. It makes customers responsible for their users, prohibits unauthorised resale and security testing, and requires compliance with capacity limits. Pico normally attempts notice before restricting service, but serious security threats, fraud, denial-of-service activity or repeated violations can lead to suspension without notice. This is an operational condition distinct from routine contract expiry.[19]

The global privacy policy, last modified in February 2020, addresses personal data in Pico’s business interactions, including websites, events, support and billing. Its retention approach follows business purposes and legal needs. It does not specify a universal retention period for a customer’s captured trading packets or market-data archive; production-data handling and deletion require the applicable customer terms.[20]

Pico dates its capital-markets technology business to 2009. Its public website terms identify Pico Quantitative Trading LLC and affiliates. The group structure and product portfolio make the exact contracting affiliate and service schedule important: a Corvil software purchase, Redline deployment and managed network service can have different delivery responsibilities.[1][21]

The current Golden Gate Capital portfolio lists Pico Quantitative Trading Holdings LLC as an active investment, with 2022 as its investment year. This verifies the investor relationship without treating the portfolio entry as evidence that Golden Gate owns every share.[22]

Pico announced the completed acquisition of Redline Trading Solutions on 4 January 2022, adding market-data, execution and pre-trade risk technology to its infrastructure and analytics portfolio. That announcement also referred to the earlier integration of Corvil. Corvil and Redline are therefore relevant product businesses within this profile, rather than separate new provider identities.[23]

The office directory identifies New York headquarters at 32 Old Slip, with regional headquarters at 155 Bishopsgate in London and Prudential Tower, 30 Cecil Street, in Singapore. These locations support the group’s regional operating model; the directory’s office numbers are distinct from the regional enquiry numbers above.[24]

Operator

Pico Quantitative Trading LLC and affiliates

Service scope

Corvil analytics, Redline market-data and execution software, and managed infrastructure.

Customer types

Banks; Brokers; Trading firms; Market operators

Delivery

On premises; Hosted; Managed service; Hybrid; API

Pricing publication

Quote only

Platforms

Corvil Analytics; InRush Ticker Plant; RedlineFeed; Order Execution Gateway; PicoNet

Integrations

Normalised market-data and execution APIs; Corvil API/SDK; PCAP; REST APIs; Splunk; Elastic; Kafka; kdb+

Pricing scope

Scope-specific quotations; SDK annual subscription, hardware and venue charges have distinct treatment.

Implementation

Software, partner-managed or fully managed delivery, with formal testing and operations handover.

Support

24/7 regional operations; incident obligations depend on the selected service agreement.

Permissions and regulatory scope

Infrastructure and software controls supporting financial firms; venue and financial-service entitlements remain separate.

Provider metadata checked 20 Oct 2026Source 1Source 21Source 10Source 3Source 12Source 14Source 2Source 8Source 27Source 6Source 11Source 16Source 17Source 13

For the 12000, Pico separately advertises sustained capture of 200 Gbps and effective storage up to 1.49 PB with compression. The effective figure should not be confused with raw disk capacity. These are supplier specifications for that appliance, not measured performance of a customer’s selected traffic mix, decoders or retention policy.[11]

Corvil Analytics 10.2 became generally available on 15 September 2026, according to Pico’s release announcement, with software available through the client portal. Its REST APIs and connectors expose network-derived metadata to observability and LLM workflows. That is a documented data-access and analysis role; the release does not give an AI system independent authority to submit trades or change the broker’s risk limits.[10]

The FX-specific Corvil workflow measures pricing-engine tick-to-quote latency, client quote-to-order timing, liquidity-provider response time and market-data quality. Packet records can help distinguish stale pricing, slow execution and a network problem. Pico also lists connectors for Splunk, Elastic, Kafka and kdb+. Those measurements support execution investigation and reporting, while the financial firm still determines the compliance conclusion drawn from them.[27]

Pico Raw Historical Data is a separate source of recorded market information: the published coverage describes US and European equities, options and futures venues, with history since 2016. Native exchange PCAP files retain A/B-feed capture and hardware PTP timestamps, delivered through S3. That archive coverage should not be read as an assertion that the same historical FX dataset is bundled with Corvil’s FX analytics.[26]