Keep fact and assumption distinct.
Do not hide the logic behind a final number. Scenario analysis separates observations, assumptions and the checks still required.
ODIN
KVANT Capital flagship
All the context.
One terminal.
Bonds, curves, events and scenarios. A workspace that keeps each instrument connected to its market context.
Working prototype. Personal demonstration on request.
ODIN 2.1 / THE WORKSPACEBuilt at KVANT Capital
- 59issues in the current prototype
- 4connected workspaces
- 1context for analysis
01 / The workspace
Individual numbers.
A connected picture.
Explore the screens: from issue comparison to the curve, from events to scenario analysis. One approach, different perspectives.
Comparison starts with one view.
Price, yield, spread, duration and liquidity, side by side. Sorting and filters help narrow the selection; an issue card provides the detail.
- Currency and coupon filters
- 10 / 15 columns
- Issue-level detail
These are interface illustrations, not a running terminal. The fourth tab presents the agent architecture, not a connected model. The terminal interface shown is in Russian.
02 / Product principles
Confidence starts
with a clear basis.
Compare like with like.
Fixed-rate, floating-rate, inflation-linked and perpetual instruments need different reference bases. A shared line colour does not make them comparable.
Date every layer.
Exchange fields can refresh separately from model calculations. Snapshot dates and request times remain explicit, so different vintages do not blur into one.
03 / The product in motion
Twenty seconds.
More than a long description.
A short tour of ODIN: from the issue list to a demonstration scenario. The next step is to see the product at work.
04 / Your team’s workflow
From a question
to a useful conversation.
- 01 /
Set the frame.
Choose the currency, coupon type and issues that can meaningfully be compared.
- 02 /
Read the context.
Compare metrics, curve position and events. Examine what each conclusion rests on.
- 03 /
Discuss the scenario.
Review assumptions and turn the result into a clear document for the team’s discussion.
Product stage
Show what is built.
Be clear about what is not.
What exists in version 2.1?
A desktop prototype covering 59 Gazprom and Gazprom Capital issues: a table, curves, an event feed and four local demonstration scenarios. A separate refresh layer for exchange fields is implemented.
What are the limits of the demo?
The agent architecture is designed for a local model on client infrastructure, with approved sources and tools. The supplied version 2.1 HTML currently uses local formulas for scenario responses. Model and access integration are configured for a pilot; the prototype’s model metrics do not automatically recalculate against refreshed prices.
What comes before a pilot?
First, we discuss the team’s workflow. Data rights, calculation methodology, integration and security requirements must be confirmed before external access. This page does not distribute or open the terminal itself.
ODIN × YOUR TEAM
First, a demonstration.
Then, your workflow.
Tell us which instruments and decisions your team works with. Founder Semyon Odintsov will personally demonstrate the product and discuss the next step.
No “deployment in a day” promises. A conversation about a real workflow.