Nasdaq Calypso upgrade to V19
Cohash upgrades Nasdaq Calypso estates to V19. We map the V19 changes, including server consolidation, new services, properties managed in the database and the WebUI, to your engines, custom code and interfaces. Then we automate regression on trades, positions, cash flows and accounting postings, rehearse the new deployment process and cut over at a weekend or period close.
- 01Estate and customization review
- 02V19 impact mapping
- 03Deployment and properties rebuild
- 04Automated regression
- 05Rehearse and cut over
The story
Told without the client's name or anything that could identify them.
A bank's capital markets technology team was running an older Nasdaq Calypso release with hand-tuned engines, property files that differed between environments and a deployment process held together by one engineer's scripts. Regression meant comparing trade and accounting extracts in spreadsheets, and custom Java front-end extensions stood in the way of the WebUI. We listed every engine, extension, property file and interface with an owner, then mapped V19's server consolidation, new services and database-held properties against that topology. Properties were reconciled across environments, the deployment pipeline was rebuilt for the V19 process, and an automated pack compared trades, positions, cash flows and accounting postings between versions. The cut-over ran at a weekend after rehearsals on production volumes, with a rollback point held.
why it was urgentNasdaq's certification program describes Calypso V19 as released in 2026, with topics covering new servers and services, server consolidation, consolidated properties stored in the database, a new deployment process and the WebUI. On 29 September 2026 Nasdaq also announced agentic AI capabilities for Calypso, including an MCP-based layer for clients' own AI tools.
- openEngines tuned by hand, and property files that don't match between environments.
- recurringThe deployment process depends on scripts one engineer wrote and maintains.
- blockedRegression means comparing trade and accounting extracts in spreadsheets.
- openUsers want the WebUI but custom Java front-end extensions block the move.
The estate, before and after
Before: hand-tuned Calypso with file-based properties
Each environment ran its own engines with property files edited by hand, deployed by scripts one engineer maintained. Regression was a spreadsheet comparison of trade and accounting extracts.
Read the diagram as text
- Deployment scripts → Calypso servers: deploy
- Property files → Engines: manual edits
- Calypso servers → Engines: events
- Custom Java extensions → Calypso servers: custom logic
- Engines → Accounting and GL: postings
- Accounting and GL → Spreadsheet regression: manual extract
After: Calypso V19 with database-held properties
V19 runs on a consolidated server layout with properties stored in the database and a rebuilt deployment pipeline. An automated regression pack compares trades, positions and postings before each release.
Read the diagram as text
- Deployment pipeline → Calypso V19: deploy
- Database-held properties → Calypso V19: configuration
- Calypso V19 → WebUI: user sessions
- Calypso V19 → Accounting and GL: postings
- Automated regression → Calypso V19: version compare
- Automated regression → Risk and finance sign-off: diff report
How we run it, phase by phase.
5 phases take you from Nasdaq Calypso (earlier version) to Nasdaq Calypso V19. Each one ends with something you can check before the next starts. As you scroll, the blocks show the estate moving across.
- phase 01
Estate and customization review
List engines, servers, scheduled tasks, custom Java extensions, property files, interfaces and reports, with the owner for each.
- phase 02
V19 impact mapping
Map server consolidation, new services and database-held properties to your topology. Decide how each custom extension and front-end change moves.
- phase 03
Deployment and properties rebuild
Move property management to the V19 model, rebuild the deployment pipeline for the new process, and make environments differ only by data.
- phase 04
Automated regression
Compare trades, positions, valuations, cash flows and accounting postings between versions on a copy of production, with tolerances agreed with risk and finance.
- phase 05
Rehearse and cut over
Rehearse the upgrade and engine start-up on production volumes, run user acceptance on the WebUI, then cut over with a rollback point.
What the client got
What changed for the client once the work was done. Described, not scored: we don't publish client figures.
- result 01
Calypso runs on V19
We moved engines and servers to the V19 consolidated layout and reworked monitoring, failover and sizing for what runs where now.
- result 02
Environments differ only by data
We reconciled properties between test and production and moved them into the database under the V19 model, so the drift from hand-edited files is gone.
- result 03
Deployment no longer depends on one person
We rebuilt the pipeline around the V19 deployment process. It's documented and the team runs it, so nobody depends on one engineer's scripts any more.
- result 04
Regression is automated
We compare trades, positions, valuations, cash flows and accounting postings across versions, using tolerances agreed with risk and finance. The same pack works for the next upgrade.
- result 05
Users are on the WebUI
We tested the custom Java front-end extensions against V19 and moved or replaced each one. Users passed acceptance on the WebUI before cut-over.
Risks we plan for
-
Topology assumptions breaking
Server consolidation changes what runs where. Monitoring, failover and engine sizing built for the old layout need rework.
-
Property drift between environments
Moving properties into the database exposes years of differences between test and production files. They are reconciled before migration.
-
Custom extensions on old APIs
Java extensions written against older Calypso APIs may not compile or behave the same. Each is tested against V19 early.
-
Support and roadmap terms
Calypso is now owned by Nasdaq after its acquisition of Adenza. Support terms and roadmap commitments are checked as part of the plan.
Where AI helps, and where it needs guardrails
Nasdaq's 29 September 2026 announcement adds a natural language assistant for querying Calypso data and documentation, hosted on Amazon Bedrock, with an MCP-based layer for clients' own AI. We help banks decide which data that layer may expose, give each connecting agent its own identity and read-only scopes, and log every query for model risk and compliance review.
forward deployed engineers →What you're left with
We write these for your setup, and they're working documents. Your team should be able to keep things running from them long after we've gone.
- inventory01
Estate inventory of engines, extensions, properties and interfaces
yours to keep - code02
V19 impact map against your topology and custom code
yours to keep - document03
Database-held properties reconciled across environments
yours to keep - code04
Rebuilt deployment pipeline for the V19 process
yours to keep - tests05
Automated regression pack for trades, positions and accounting
yours to keep - runbook06
Cut-over runbook with rehearsal timings
yours to keep
Platforms and services on this move
Certified engineers, wherever you need them.
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Onsite
Engineers at your sites in the US
Nearshore
Overlapping hours with US teams
Offshore
Overnight progress on your backlog
All time zones
Coverage handed over across time zones
01How long does a Calypso V19 upgrade take?
It depends on your starting version, the number of custom extensions and interfaces, and how regression is done. The deployment and properties changes add work that a like-for-like upgrade wouldn't have.
02Do we have to move to the WebUI?
Plan for it, but the timing is yours to agree with users and Nasdaq. Custom front-end extensions are the usual blocker, so we inventory them early.
03Can the new agentic features connect to our own AI tools?
Nasdaq says clients can connect their own AI through a layer built on the Model Context Protocol. We help define what data is exposed, which identities connect and how access is logged.
04Can you staff Calypso engineers?
We do. That covers Calypso technical and functional consultants as well as test automation engineers. Onsite, nearshore or offshore, and on contract, contract-to-hire or permanent terms.
Often on the same roadmap
On-premises Active Directory to cloud-first Microsoft Entra ID
We shrink on-premises Active Directory one application at a time, moving groups, users and app authentication to Microsoft Entra ID as each app is ready.
read the case studyAD FS federation to Entra ID authentication
Converting federated domains from AD FS to Entra ID cloud authentication, moving relying parties app by app and retiring the AD FS farm.
read the case study
Apache Airflow 2 to Airflow 3
Upgrading self-managed Apache Airflow 2, now past end of life, to Airflow 3, and fixing removed features, auth and scheduling changes before DAGs move.
read the case study61185ad2 - 01Nasdaq Calypso certification: Technical V19 Bridge exam (V19 released 2026)calypsocertification.nasdaq.com ↗
- 02Nasdaq: Calypso launches agentic capabilities across the trade lifecycle (29 Sep 2026)mfn.se ↗
- 03Nasdaq press release (SEC filing): Nasdaq completes acquisition of Adenza, 1 November 2023sec.gov ↗
Planning this move?
A 30-minute working session with a senior engineer. No slides.
- The platform and the version you're on
- Where you need to get to, and by when
- What's custom: rules, plugins, integrations
- Any audit finding or deadline driving it