🩺 Vitals
- 🟢 Last active: 2026-07-10
- 📦 Latest release: v3.2.0 (2026-06-28)
- 🐞 Open issues: 45
- 🌟 Stars: 21
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent tagged, packaged version the maintainers published. Not every healthy project tags releases.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: tradista.finance
- Source: github.com/eclipse-tradista/tradista
- License: Apache 2.0
- Deployment: On-Premise
- Data Model: Relational Database (JPA)
- Jurisdiction: Belgium 🇧🇪 (Eclipse Foundation AISBL)
- Compliance (SaaS): N/A
- Compliance (Self-Hosted): Self-Hosted (User Managed)
- Complexity: High (5/5) - Jakarta EE stack (WildFly), financial data feeds, regulatory configuration
- Maintenance: High (4/5) - Small contributor base; requires financial engineering domain knowledge
- Enterprise Ready: Low (2/5) - No commercial SLA, no formal compliance certifications; third-party support via OmniFish
1. The Executive Summary
What is it? Eclipse Tradista is a modular capital markets and treasury operations platform designed for banks and financial institutions. It handles trade capture, profit-and-loss calculation, position management, and market data analysis across multiple asset classes, including FX, interest rate derivatives, bonds, and equities. Governed by the Eclipse Foundation (Belgium), the project's intellectual property is foundation-protected under the Eclipse IP Policy, ensuring no single vendor can relicense or restrict access. Commercial support is available through third-party integrators such as OmniFish.
The Strategic Verdict:
- 🔴 For Institutions Without Jakarta EE Engineering: Not a fit. Deployment requires WildFly, JPA expertise, and integration with financial market data providers (Bloomberg, Quandl). No managed SaaS offering exists. This is an engineering-intensive self-hosted commitment.
- 🟢 For Banks Building Sovereign Trading Infrastructure: Strategic opportunity. Foundation-governed IP, zero licence fees, and Apache 2.0 permits proprietary extensions without disclosure, a rare combination in regulated financial software where incumbent licence costs routinely exceed seven figures.
2. The "Hidden" Costs (TCO Analysis)
| Cost Component | Murex MX.3 (Enterprise) | Tradista (Self-Hosted) |
|---|---|---|
| Licence Fee | Multi-year enterprise contract | $0 (Apache 2.0) |
| Vendor Lock-in | Proprietary codebase | Full source access (Foundation IP) |
| Customisation | Professional services engagement | Direct source modification |
| Implementation | Vendor-led deployment cycle | Self-directed (engineering investment) |
3. The "Day 2" Reality Check
🚀 Deployment & Operations
- Installation: Maven-based build deployed to a WildFly (Jakarta EE) application server. Requires a relational database (JPA-managed) and integration with market data providers for pricing and risk calculations. No Docker-first workflow. Expect a traditional enterprise Java deployment process.
- Scalability: Modular architecture allows selective deployment of asset class modules (FX, IR, bonds). Standard FIX-based interfaces support trade import/export interoperability with existing trading systems.
🛡️ Security & Governance (Risk Assessment)
- Jurisdiction & Geopolitics (Belgium 🇧🇪): The Eclipse Foundation AISBL is incorporated in Belgium, a full EU member state with no US CLOUD Act exposure. Foundation governance means the project's IP is held in trust by a non-profit, not a single corporate entity. This eliminates the acquisition risk that plagues commercially-backed open source projects in financial services, where a vendor buyout can trigger relicensing.
- The Compliance Shift: Tradista provides no formal compliance certifications: no SOC 2, ISO 27001, or financial regulatory attestations. For institutions subject to MiFID II, Basel III/IV, or internal audit frameworks, this means the deploying bank bears full responsibility for access controls, encryption at rest, audit trail integrity, and regulatory reporting at the infrastructure level. The software provides the computational framework; the compliance posture is entirely user-managed.
- License Risk (Apache 2.0: No Traps): Apache 2.0 imposes no copyleft requirements and no network use restrictions. Institutions can modify, extend, and embed Tradista into proprietary trading systems without disclosure obligations. The Eclipse Foundation's Contributor License Agreement provides additional protection against patent claims from contributors, a material safeguard for financial institutions building mission-critical infrastructure on open source foundations.
4. Market Landscape
🏢 Proprietary Incumbents
- Murex MX.3: The dominant capital markets platform globally, with deep functionality across front-to-back office. Institutions evaluate Tradista when Murex's multi-year licence costs and vendor dependency become strategic liabilities, particularly for specific asset class modules where full MX.3 functionality is unnecessary.
- Calypso (Adenza/LSEG): Enterprise treasury and derivatives platform now owned by the London Stock Exchange Group. Organisations assess Tradista to avoid concentration risk from a single exchange-owned vendor controlling both market infrastructure and trading technology.
🤝 Open Source Ecosystem
- OpenBB: The open source financial research and data terminal. Complementary to Tradista: OpenBB provides the market intelligence and analysis layer that feeds into Tradista's trade capture and position management workflows.
- Ghostfolio: A privacy-first wealth management dashboard for portfolio tracking. Operates at the individual/Family Office level where Tradista targets institutional capital markets, different tiers of the same financial sovereignty stack.