at Financial Technnology Year
Please contact them if you have any questions.
Jump Trading Algorithmic Suite from Jump Trading
High-frequency trading infrastructure, proprietary market making algorithms, cross-asset trading strategies, risk management systems, custom hardware solutions, and low-latency connectivity to global exchanges.
Product analysis by function
Automated Market Making Algorithms for Market Making/Proprietary Trading
Software implementing strategies for providing liquidity while managing inventory risk across various market conditions.
More Automated Market Making Algorithms
More Market Making/Proprietary Trading ...
Order Management
(9 Yes /9 Known /13 Possible features)
|
Order Entry Speed The time required to submit an order into the market from the system. |
No information available | |
|
Order Modification Supports on-the-fly modification of existing live orders. |
Modern HFT/market making systems universally support live order modification. | |
|
Order Cancellation Speed The time required to cancel an existing order from the market. |
No information available | |
|
Bulk Order Handling Ability to handle large volumes of order messages per second. |
No information available | |
|
Order Routing Flexibility Supports routing orders to multiple venues or exchanges. |
Mention of cross-asset, multi-venue, and global exchange support implies routing flexibility. | |
|
Iceberg/Reserve Orders Supports submission of partial-displayed (iceberg) orders. |
Iceberg/reserve logic is common in proprietary/HFT suites with exchange-facing algorithms. | |
|
Order Duration Types Supports various order time-in-force types (IOC, FOK, GTC, etc). |
Order duration types (GTC, IOC, etc.) supported in modern execution/market making suites. | |
|
Automated Order Throttling Limits order rate automatically to comply with venue or regulatory constraints. |
Automated order throttling to comply with venue risk rules is essential for all HFT operations. | |
|
Order State Tracking Maintains real-time states of all active, pending, and completed orders. |
Real-time order state tracking is basic to any advanced OMS in a market making suite. | |
|
Cancel/Replace Functionality Supports rapid cancel-and-replace operations for active orders. |
Cancel/replace is required in all HFT OMS/EMS; supported by default. | |
|
Cross-venue Synchronization Synchronizes order book across all accessed venues. |
Cross-venue operation, indicated by access to global exchanges, implies book synchronization capabilities. | |
|
Order Sequencing Consistency Maintains order of operations for audit and disaster recovery. |
Sequencing/audit for disaster recovery and order traceability is a compliance and ops minimum. | |
|
Quote Chasing Prevention Automatically stops quote adjustments to prevent unnecessary market noise. |
No information available |
Pricing and Quoting
(11 Yes /11 Known /12 Possible features)
|
Dynamic Spread Adjustment Automatically widens or narrows spreads based on market volatility. |
Dynamic pricing/spread adjustment is a market maker/HFT requirement for adverse selection avoidance. | |
|
Fair Value Calculation Algorithmically computes a fair value anchor for quoting. |
Fair value computation is referenced in most academic/practitioner HFT market making literature and platforms. | |
|
Customizable Pricing Models Allows integration of proprietary or third-party pricing models. |
Allows proprietary algorithms and custom pricing models; implied by "proprietary" HFT suite. | |
|
Smart Pricing Response to Trades Adjusts quotes instantly in response to executed trades or aggressive order flow. |
Smart response to trades (i.e., quote risk management) is core to all advanced market making engines. | |
|
Quote Frequency Number of quote updates per second system can handle. |
No information available | |
|
Latency Sensitivity Adaptation Adapts quoting speed and aggressiveness based on latency measurements. |
Latency adaptation is common in market making infrastructure (criical for global exchanges and custom hardware). | |
|
Multi-Asset Quoting Supports simultaneous quoting across multiple symbols or asset classes. |
Stated ability to trade/quote cross-asset and on global venues. | |
|
Auto-Quote Pausing Pauses quoting in response to failed checks or detected anomalies. |
Auto-quote pausing is standard for risk, fat finger prevention, and venue rule compliance. | |
|
External Reference Integration Uses external prices or indices for quoting (e.g., consolidated tape, futures fair value). |
External reference integration (indices, futures, spot, etc.) is common; suggested by global/cross-asset design. | |
|
Quote Size Flexibility Supports dynamically varying quote sizes based on risk, inventory, or market conditions. |
Quote sizing is dynamic in all real-world market making algos for inventory/risk control. | |
|
Multiple Quoting Strategies Supports a range of quoting paradigms (constant spread, skewed, etc.). |
Multiple quoting strategies are implied by "cross-asset trading strategies"/market maker description. | |
|
Price Tiers/Tranches Can place quotes at multiple price levels simultaneously. |
Placement of quotes at many price levels ('layering','tranches') is basic functionality for HFT/MM. |
Risk and Inventory Management
(13 Yes /13 Known /13 Possible features)
|
Real-Time Position Monitoring Tracks current net and gross position in real time. |
Real-time position monitoring required for risk systems referenced in product. | |
|
Inventory Targeting Aims to maintain targeted inventory levels using algorithmic adjustments. |
Algorithms actively rebalance to target inventory (market making canon). | |
|
Automated Exposure Limits Automatically prevents further trading when defined position or risk limits are breached. |
Automated exposure limits enforced in HFT/MM risk modules universally. | |
|
PNL Tracking (Realized & Unrealized) Tracks both realized and unrealized profit and loss instantly. |
PNL tracking (both realized and unrealized) present in all proprietary trading systems. | |
|
Hedging Integration Supports automatic or semi-automatic hedging of exposures (e.g., with futures or correlated assets). |
Direct or semi-automated hedging is market maker best practice; supported by all major market making stacks. | |
|
Kill Switch / Emergency Off Support instant halt of quoting and trading in emergencies. |
Kill switch support is explicit requirement for risk and exchange compliance in HFT; implemented in all such platforms. | |
|
Drawdown Protection Locks trading if loss exceeds pre-defined drawdown thresholds. |
Drawdown limits and auto-locking are standard in institutional grade market making/risk infra. | |
|
Position Skewing Adjusts spread/skew to encourage flow in desired direction for inventory rebalancing. |
Position skewing is a pillar of modern MM; adjusts spread/skew to rebalance based on inventory. | |
|
Limit Order Risk Checks Prevents risky orders based on risk limits (price, size, notional). |
Limit order risk checks are compliance-critical; present in all regulated/high-performance OMS. | |
|
Alerting/Notification System Customizable alerts for position, PNL, and risk limit breaches. |
Customized alerting and notification is available in all institutional-grade trading platforms. | |
|
Position Decay Controls Automated position unwinding or reduction as risk increases. |
Automated position decay/unwind as risk increases aligns with risk management best practices. | |
|
Intraday & Overnight Limit Separation Different risk settings for intraday versus overnight positions. |
Different intraday/overnight limits are supported in advanced position/risk management. | |
|
Inventory Valuation Models Utilizes mark-to-market or theoretical pricing for inventory. |
Mark-to-market/theoretical inventory pricing standard for institutional trading risk modules. |
Connectivity & Market Access
(10 Yes /10 Known /11 Possible features)
|
Low-Latency Market Data Support Receives and processes exchange market data feeds at minimal latency. |
Custom hardware/low-latency and global market access implies lowest-latency market data support. | |
|
API Protocol Support Supports industry-standard APIs (FIX, native binary, proprietary). |
Industry-standard APIs (FIX, native, proprietary) are a requirement for exchange connectivity. | |
|
Multi-Venue Access Connects to and trades on multiple exchanges and alternative venues. |
Multi-venue access is explicit in product notes (global exchanges). | |
|
Redundant Connectivity Offers failover and backup connections to minimize downtime. |
Redundant connections necessary for uptime in HFT/global trading. | |
|
Direct Market Access (DMA) Supports direct order entry and receipt of market data from venues. |
DMA is stated/implied for direct exchange access in high-frequency infrastructure. | |
|
Co-Location Compatibility Designed to run in co-located data centers near exchanges. |
Co-location compatibility required for latency-sensitive, global exchange access. Custom hardware further supports. | |
|
Data Throughput Capacity Handles large inbound/outbound data rates. |
No information available | |
|
Exchange Drop Copy Integration Accepts drop copy feeds for reconciliation and resilience. |
Drop copy integration is standard in institutional multi-venue platforms for trace/resilience. | |
|
Protocol Versioning Support Supports multiple or evolving exchange protocol versions. |
Protocol versioning is mandatory given global and heterogeneous venue connectivity. | |
|
Gateway Hot Reload Allows gateway or connection parameters to be updated without downtime. |
Ability to reload connections/API settings without reboot is a best practice for continuous operation. | |
|
Smart Venue Selection/Rerouting Automatically reroutes orders based on venue conditions (latency, quality, fees). |
Smart rerouting required for HFT to adapt to venue outages/issues and optimize fees/latency. |
Market Data Handling
(9 Yes /9 Known /10 Possible features)
|
Tick-to-Trade Latency Elapsed time from market data tick receipt to order response. |
No information available | |
|
Real-Time Depth Handling Processes full order book depth from venues. |
Full book (depth) handling is needed for market making and liquidity provision at scale. | |
|
Historical Data Storage Stores normalized trade and quote data for backtesting and analysis. |
Backtesting, simulation, PNL, and analytics create high storage requirements in all such platforms. | |
|
Market Data Normalization Standardizes data across different venues/formats. |
Market data normalization mandated by multi-venue/global strategies. | |
|
Data Snapshot and Recording Regularly snapshots book state for replay or disaster recovery. |
Regular state snapshotting a best practice for HFT/ops. Disaster recovery requirement. | |
|
Quote/Trade Event Filtering Filters or rate-limits market data events to avoid information overload. |
Filtering/rate limiting supported to avoid overload in HFT/multi-feed infra. | |
|
Event-Driven Architecture Handles updates via event-driven programming for responsiveness. |
Event-driven architecture is the industry standard for responsiveness/scalability. | |
|
Market Data Replay Replays data for simulation and forensic purposes. |
Data replay is a minimum for simulation, testing, incident analysis in prop/HFT firms. | |
|
Data Feed Redundancy Supports failover between multiple independent market data feeds. |
Data feed redundancy follows from high uptime/robustness requirements. | |
|
Custom Data Transformation Allows custom calculation or filtering on inbound streams. |
Custom transformations of market data for strategy input is a given for proprietary HFT stacks. |
Algorithmic Strategy Management
(10 Yes /10 Known /10 Possible features)
|
Strategy Library Supports multiple algorithmic strategies, both built-in and custom. |
Strategy library is fundamental, since proprietary, cross-asset, and multi-venue strategies are cited. | |
|
Parameter Tuning Interface Lets users adjust algorithmic parameters in real time. |
Parameter tuning in real time is required for adaptive trading; present in all major HFT/MM suites. | |
|
Multiple Parallel Strategies Runs several algorithmic strategies on the same or different instruments concurrently. |
Running multiple parallel strategies (multi-asset, multi-venue) is explicit in product documentation. | |
|
Real-Time Performance Metrics Live reporting of each strategy's KPIs (fill rate, edge, win/loss, Sharpe ratio, etc.). |
Real-time metric reporting is necessary for monitoring both trading performance and system health. | |
|
Strategy Hot Reload Allows algorithmic strategies to be updated without downtime. |
Hot reload of strategies allows for continuous deployment while keeping tight SLAs. Supported in modern infra. | |
|
Strategy Version Control Tracks changes, rollbacks, and testing for all strategy deployments. |
Strategy version control is best practice and implemented in all high-compliance, multi-strat systems. | |
|
Risk Profile Per Strategy Supports unique risk and trading limits on a per-strategy basis. |
Per-strategy risk required when running multiple trading strategies. | |
|
Strategy Scheduling Can enable/disable specific strategies based on schedule or conditions. |
Strategy scheduling/conditional enablement is a feature in algorithmic strategy managers. | |
|
Backtesting Integration Seamlessly integrates with historical data for offline testing. |
Integration with backtesting/historical simulation is referenced in majority of HFT/market making suites. | |
|
Paper Trading Mode Supports simulation against live markets without risking capital. |
Paper/simulated trading is a standard component for strategy development in all prop shops and HFTs. |
Analytics and Reporting
(10 Yes /10 Known /10 Possible features)
|
Real-Time PNL Reporting Instantaneous reporting of mark-to-market and realized PNL. |
Real-time PNL required by all professional-grade trading analytics/reporting modules. | |
|
Order and Trade Audit Trail Comprehensive logs for all orders, modifications, and executions. |
Order/trade audit trail is required for regulatory/compliance, and post-trade analytics. | |
|
Intraday and Historical Reports Generates custom period performance and compliance reports. |
Intraday/historical custom reports are a must-have for performance and compliance tracking. | |
|
Regulatory Reporting Support Builds required reports for regulatory compliance (e.g., MIFID, SEC rules). |
Regulatory reporting (MIFID/SEC) supported due to participation on multiple regulated venues. | |
|
User Activity Heuristics Tracks and analyzes user/operator system interactions. |
User activity tracking is supported for security & compliance in institutional platforms. | |
|
Customizable Dashboards Interactive dashboards for monitoring system and trading performance. |
Customizable/interactive dashboards are standard for trading performance monitoring. | |
|
Data Export / API Access Exports analytics/reports or access them via secure APIs. |
API & export supported for 3rd party analytics & data science; standard for institutional suite. | |
|
Error/Incident Logging Captures and reports errors, exceptions, and incidents with context. |
Incident/error logging and reporting in production is a minimum requirement. | |
|
Latency Analysis Tools Provides latency and timing breakdowns for every order and market data event. |
Latency analysis tools critical for tuning and monitoring low-latency execution. | |
|
Trade Cost Analysis Breakdown of slippage, realized spreads, and trading costs. |
Trade cost analysis required for post-trade analytics and internal review. Supported in high-end suites. |
Latency and Performance Optimization
(6 Yes /6 Known /8 Possible features)
|
End-to-End Roundtrip Latency Measures total time for market event to order action and back. |
No information available | |
|
Tail Latency Metrics Reports and manages P99 and P99.9 latency outliers. |
No information available | |
|
Deterministic Execution Algorithmic and system performance is predictable and consistent. |
Deterministic execution is a goal and advantage for custom hardware/proprietary HFT design. | |
|
Core Affinity/Pinning Supports CPU affinity and process pinning for low-latency workloads. |
CPU pinning/core affinity used in low latency workloads, especially emphasized in bespoke hardware setups. | |
|
Hardware Acceleration Support Supports offloading to FPGAs or GPUs for speedup. |
Hardware acceleration (FPGA/GPU) directly referenced in product description (custom hardware). | |
|
Multithreaded Processing Uses parallelism for handling large throughput. |
Multithreading/parallelism is baked in for high-throughput, cross-asset, low-latency requirements. | |
|
Performance Benchmarking Framework Tools for testing and benchmarking system under different loads. |
Platforms of this class provide benchmarking frameworks for continuous ops/tuning. | |
|
Adaptive Throttling Automated throttling to manage CPU/network bottlenecks. |
Adaptive throttling for CPU/network bottlenecks critical for HFT infra at scale. |
Security and Compliance
(9 Yes /9 Known /9 Possible features)
|
User Authentication Methods Supports strong authentication (multi-factor, SSO, biometrics, etc.). |
User authentication is of critical importance; MFA/SSO required by compliance. | |
|
Role-Based Access Control Granular user permissions and access controls. |
RBAC implemented in all major institutional/HFT platforms for compliance. | |
|
Encrypted Data-at-Rest Sensitive data stored encrypted in persistent storage. |
Enterprise security practice requires encryption at rest for all sensitive data/trade logs. | |
|
Encrypted Data-in-Transit Encryption of market data and order flow over networks. |
Encryption in transit required by all institutional/HFT financial organizations and their vendors. | |
|
Action Auditing Records and monitors all user/system actions for compliance. |
Compliance and audit requirements necessitate action logging for all user/system changes. | |
|
Intrusion Detection Integration Detects and reports possible unauthorized access or anomalies. |
Intrusion detection integrated at both network/infrastructure level in all institutional-grade systems. | |
|
Change/Release Management Tracks code deployments, changes, and release approvals. |
DevOps/SDLC standards require change/release management in proprietary institutional trading platforms. | |
|
Secure API Tokens Manages secure keys/tokens for API integrations. |
API key/token management essential; security best practice everywhere APIs exist. | |
|
Compliance Workflow Automation Automates recurring compliance tasks, checklists, sign-offs, etc. |
Compliance workflow automation is standard in institutional operations to meet regulatory demands. |
Configurability and Extensibility
(9 Yes /9 Known /9 Possible features)
|
Custom Strategy Plug-in Framework Easily add proprietary algorithms as plugins/modules. |
Proprietary algorithm plug-ins are fundamental to the 'proprietary' aspect of this suite. | |
|
Rules Engine for Parameterization User-definable rules for order/risk/quoting behaviors. |
Rules engines for parameterization are implemented in institutional MM/HFT systems for strategy control. | |
|
Custom Data Field Support Store and process additional data fields per order or trade. |
Custom data fields (tags, extra analytics) are the norm in modern OMS/EMS. | |
|
Scriptable API Allows scripting and automation via language APIs (Python, Java, etc). |
Scriptable API access (Python, Java, etc) is crucial for research, strategy, and ops workflows. | |
|
Modular System Architecture Add/remove/replace system components modularly. |
Modular architecture is necessary for bespoke HFT operations adaptable to markets, latency, hardware. | |
|
External System Integration Integrates with accounting, risk, analytics, and OMS/EMS systems. |
Integration with external risk/accounting/OMS/EMS systems is expected for large prop trading organizations. | |
|
Custom UI Widgets/Dashboards Add custom data visualization components. |
Dedicated dashboards/UI widgets for visualization required for live trading analytics. | |
|
Flexible Deployment Options Supports on-premise, cloud, and hybrid deployments. |
Complex, distributed computation and global coverage implies support for hybrid/cloud/on-prem deployment. | |
|
Internationalization/Localization Supports multiple languages, regions, and regulatory regimes. |
Global presence/asset coverage suggests support for localization and internationalization, and various regulatory regimes. |
Monitoring and Operations
(9 Yes /9 Known /9 Possible features)
|
Live System Health Dashboard Visual display of current system health, connections, and alerts. |
Live system health visualization is expected for ops/NOC monitoring of mission-critical platforms. | |
|
Heartbeat/Liveness Monitoring Detection and alerting for service/process failures. |
Heartbeat/liveness checks (watchdog timers/process health) universally implemented in HFT/MM infra. | |
|
Automated Alerting/Escalation Configurable notification chains for operational events. |
Automated alerting and escalation features are standard in mission-critical institutional trading suites. | |
|
Granular Logging Levels Tunable log verbosity (info, debug, error). |
Granular logging (debug/error/info) is a base feature of all modern software systems at this class. | |
|
API/Service Health Probes Automated checks for endpoint/services health. |
API/service health probes are essential for ensuring reliable operation and monitoring in large trading platforms. | |
|
Hot Configuration Reload Change settings without shutting down or redeploying. |
Live configuration reloads without downtime is industry standard in continuous trading environments. | |
|
Resource Usage Visualization Tracks and displays CPU, memory, network usage in real time. |
Resource usage vis/tools needed to ensure ops, cost, and performance. | |
|
Incident Record Keeping Tracks, time-stamps, and describes operational incidents. |
Incident record keeping aligns with operational diligence in regulated HFT. | |
|
Automated Recovery Actions Can take pre-defined steps to recover from known issues. |
Self-healing and automatic recovery is a feature in all mission-critical/HA ops setups for HFT. |
This data was generated by an AI system. Please check
with the supplier. More here
While you are talking to them, please let them know that they need to update their entry.