Open Source Risk Engine

opensourcerisk.org ↗

Run configurable pricing, risk and valuation-adjustment studies

SI Score
75/100
Pricing
Open Source AI reading, not confirmed
Free plan
Yes AI reading, not confirmed
Sign-up required
Not required AI reading, not confirmed

Ask SI about Open Source Risk Engine

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Open Source Risk Engine homepage

What it does

Open Source Risk Engine, or ORE, provides pricing, portfolio-risk analytics and valuation adjustments. It extends QuantLib with instruments, simulation models, data structures and reporting workflows. Its modified BSD licence permits free use, with command-line and programming interfaces for technical teams.

ORE accepts portfolio and market data, applies the selected model and analytics configuration, then writes reports for further analysis. Its components separate instrument and model extensions, data handling and analytics. Spreadsheet, Python and Jupyter launchers provide additional ways to work with the engine.

A practical starting point is a public release archive for Windows, Linux or macOS. It includes executable files and examples, with a helper script available to fetch the example set when needed. Run a supplied case first to understand its file layout, then replace the portfolio, market inputs and configuration for the intended study. No ORE account is needed for the public downloads.

The documentation index gives each reference a distinct purpose. The User Guide covers installation, workflow settings and market conventions. The Product Catalogue maps instruments to trade and pricing-engine configurations. The Methods reference explains the analytics.

Outside the supplied examples, data preparation is your responsibility. ORE requires its own portfolio XML and market-data formats; it has no standard provider connector or ready-made FpML converter. A team can build mapping code, use files with the command-line executable, or integrate through the C++ interface. Reports are written to the filesystem for downstream tools. ORE also supports a smaller instrument set than the entire QuantLib library.

Strengths

  • Separates data preparation, model configuration and analytics
  • Includes executable releases and examples for major desktop systems
  • Supports file-based runs and direct C++ integration

Watch out for

  • External portfolio and market data need mapping into ORE formats
  • ORE does not expose every instrument available in QuantLib

Best for

  • Technical teams researching pricing and portfolio risk
  • Developers building configurable valuation and risk-reporting workflows

Sources