Design partner programme
Need a module that doesn't exist yet?
Build it with us.
Co-fund the next Everix module and get it first — shaped around your portfolio, validated on your data, at a fraction of the cost of building it alone or buying an enterprise suite.
What partners get
- First use of the module, with release milestones agreed in writing
- Direct influence on scope, priorities and acceptance criteria
- Validation on your own data with the engineers who build it
- Preferential licence terms once the module ships
- On-site, Private Cloud, or the hosted services where they fit
Modules open for co-funding
What we can build next
Each card shows what Everix offers today and what we would build with a partner.
FRTB-SA — remaining risk classes
Today: Sensitivities-based method built for GIRR, FX and commodities, with CRR3 parameters.
With a partner: Equity, credit spread, default risk charge (DRC) and residual risk add-on (RRAO), plus own-funds reporting.
MCP write tools & agent workflows
Today: Read-only MCP server with scoped keys, audit trail, row and byte caps and rate limits.
With a partner: Approved write actions — launch what-if runs, schedule workflows — with human-in-the-loop approval.
Murex, Calypso & Endur connectors
Today: Finastra Summit and Orchestrade connectors, plus CSV and CRIF inputs available.
With a partner: Trade, market-data and sensitivity extraction from Murex, Calypso or Endur — built against a partner's real extracts.
Power BI connector
Today: ClickHouse data mart with Superset and an OData feed; the Power BI connection is a prototype.
With a partner: A tested, documented Power BI connection with ready-made risk dashboards.
BA-CVA under CRR3
Today: XVA (CVA/DVA) in production since 2018; SA-CCR exposures available as an input.
With a partner: Basic-approach CVA capital (reduced and full) with hedging recognition.
Something else on your list? Tell us — the programme is not limited to these modules.
Four steps, no surprises
01
Scope call
30 minutes on your regulation, portfolio and deadline. We tell you what exists, what we would build next for you and whether we are the right team.
02
Written proposal
Scope, milestones, acceptance criteria, data needs and the co-funding split. No surprises later.
03
Build in milestones
Short iterations, each validated on your data — regulatory examples first, then your portfolio.
04
Go live, then share
You run it first and get preferential terms. The module joins the product, so its maintenance cost is shared too.
What we ask of partners
- A business sponsor and a hands-on contact in risk or IT
- Access to representative data for validation (anonymised is fine)
- A share of the development cost, agreed per milestone
- Feedback at each milestone — and, if it works for you, a reference
What we bring
- A risk engine with XVA in production since 2018
- Regulatory validation on published examples (BCBS SA-CCR, ISDA SIMM unit tests, EBA xBRL assertions) wired into CI
- A full audit trail and a software bill of materials for your security and vendor-risk review
- Quants and engineers who answer your questions directly
Tell us what you need built
A few lines are enough: the regulation or capability, your timeline, and roughly what your portfolio looks like. We reply within one business day.
Investors & strategic partners
Everix is open to conversations with investors and strategic partners — software vendors, integrators and data providers who want regulatory-grade risk analytics in their stack. Use the form and pick "Investor" or "Fintech / integrator" as company type, or write to [email protected].
Frequently asked questions
What does co-funding mean in practice?+
A partner contributes part of the development cost of a module that matters to them. In return they use it first, shape its scope and get preferential licence terms once the module is part of the product. We agree the scope, milestones and acceptance criteria in writing before any work starts.
Who owns the resulting code?+
Everix keeps the product IP so the module can be maintained and offered to others; that is what keeps the cost shared. Partner data, configurations and anything specific to the partner remain the partner's.
How long does a module take?+
It depends on scope. We agree scope, validation criteria and release dates in the written proposal. Each milestone ends with something the partner can run and validate on their own data.
Do we need to be an existing client?+
No. Many design partners start with a module they cannot find at a reasonable price elsewhere. A first call is enough to see whether the scope makes sense.
Can we run it on-premises?+
Yes. Modules built in the programme ship the same way as the rest of Everix: On-site, Private Cloud, or in the hosted services where they fit.