Theseus Capital Markets

Real-time pricing and risk for trading desks.

Theseus Capital Markets replaces fragmented desk tooling with a single governed runtime. Deterministic execution, full lineage, self-serve change control, and decision latency of microseconds to milliseconds, target for qualifying production workflows. Built for buy-side and sell-side operations.

4–8 weeks

New desk to production
Design target, validated in parallel-run pilots.

Same day

Logic to production
Self-serve within governed controls. No ticket required.

μs–ms

Decision latency
Target for qualifying production workflows.
A live risk application on Theseus: FX market data on the left, versioned calculations in the middle, portfolio VaR, PnL and exposure on the right.
A live risk application on Theseus: FX market data on the left, versioned calculations in the middle, portfolio VaR, PnL and exposure on the right. Every node shows its current value, and the inspector streams each event the selected node produces. What you see is what runs.
The status quo

Today, a logic change is an expedition.

A single change touches three to five teams: dev, quant, risk, ops and compliance, coordinated by hand. Request to production takes two to six weeks, and the audit trail is incomplete throughout. After an incident, evidence is rebuilt from logs, spreadsheets and email trails. All of it runs on a per-desk tooling stack that was assembled, not designed.

Comparison

Legacy versus Theseus.

 
Typical fragmented stack
Theseus
Time to first desk live
3–12 months
4–8 weeks (target)
Change cycle, logic to production
2–6 weeks
Same day, self-serve (target)
Teams touched per change
3–5, plus sign-offs
1, no ticket required
Decision latency
Varies widely by stack; often tens of milliseconds to seconds on vendor platforms
μs–ms (target, qualifying workflows)
Audit trace after an incident
Hours to days of manual reconstruction
Deterministic replay, in minutes

Theseus figures are design targets. Every parallel-run pilot validates them on your workflows before anything touches production.

Workflows

Four workflows. One runtime.

Theseus Capital Markets covers the core operational surface of a trading desk: pricing, risk, limits and data transformation. Each workflow is deterministic, auditable and governed from a single platform.

Real-time pricing

Deterministic price calculations across instruments and scenarios. Market move to desk response with no hidden state and full lineage on every output.

Intraday risk

Continuous risk assessment with versioned logic and complete execution lineage. Every risk figure is traceable to its exact inputs and the model version that produced it.

Limits monitoring

Automated, governed limit enforcement with instant breach alerting. Rules are versioned, auditable and visible to compliance, not buried in application code.

Market data transformation

Deterministic data pipelines feeding operational logic. No silent transformation failures. No discrepancies between what the desk sees and what risk is using.

The desk workflow

Built for the whole desk.

Strats and quants connect market data or simulate it, write calculations in the languages they already use, and compose them into a live application by linking nodes in a graph. Traders adapt and customise their dashboards themselves, with no developer queue and no ticket. Risk and compliance read the record the system wrote as it ran, not a reconstruction assembled afterwards.

When a number looks wrong, replay the graph at the exact moment in question, find the cause in seconds, and ship the fix without taking the desk down. And every component built for one desk can be shared with the next, so the same curve, the same limit logic and the same dashboard never get rebuilt twice.

See the build workflow
Desk outputs from the running graph: position values, exposure, PnL and VaR.
Desk outputs from the running graph: position values, exposure, PnL and VaR. The scrubber at the top is a recording being replayed; drag it and the report shows the desk's numbers exactly as they stood at that moment.
The pilot

Three numbers decide it.

Every pilot runs Theseus Capital Markets in parallel with your existing stack and reports three things: decision latency, change lead time and audit completeness against the legacy system. If the numbers do not hold on your workflows, you will know early. So will we.

How a parallel run works
Why finance first

Why trading is the starting point.

Trading and risk combines the tightest latency budgets, the strictest audit obligations and the most public cost of failure of any sector. Control failures draw nine-figure fines. If the platform holds here, it holds anywhere. Finance is the beachhead, not the ceiling.

FAQ

Technical questions.

What deployment models does Theseus support?

On-premises, private cloud and edge. Multi-tenant SaaS is not offered. Every production deployment is isolated by design, which is a requirement in regulated environments, not an afterthought.

How is determinism enforced?

Calculations run as sandboxed WebAssembly modules inside a single runtime that owns scheduling, event ordering and every input a module can observe. Nothing reaches your logic except through the recorded event stream, so there is no wall clock, thread timing or hidden I/O to diverge on. Every run is journaled, and any recording can be re-executed and checked for identical outputs, so the guarantee is verified on real runs rather than assumed.

What production latency should we expect?

Theseus Capital Markets targets microseconds to milliseconds for end-to-end decision latency on qualifying production workflows. Exact figures depend on logic complexity and deployment topology, and every pilot measures them on your workflows rather than ours. A qualifying workflow is one whose full decision path runs inside the runtime, from recorded input to produced output, without a round trip to an external system.

How do quant and risk teams manage changes?

Logic changes are self-serve, versioned and governed. Every promotion creates an auditable record. Teams can deploy, roll back or replay any logic version independently, without waiting in an engineering queue.

Does a pilot touch production?

No. Design partner pilots run in parallel with your existing systems. Theseus Capital Markets receives the same inputs, runs the same logic, and its outputs are measured against the legacy stack. Nothing is switched over during the pilot.

Where does a pilot run, and what data leaves our environment?

The parallel run deploys into your environment, on premises or in your own cloud tenancy, inside your network and access controls. Market data, positions and outputs stay within your perimeter. When a pilot ends, the deployment is decommissioned and its data deleted.

Which languages can we write calculations in?

Calculations are ordinary functions compiled to WebAssembly, so the runtime is language-neutral by design. Python is supported today.

How do live feeds and downstream systems connect?

Inbound adapters capture market data and internal system events with timestamps at the boundary. Outbound, every node's outputs are available as streams and APIs to downstream systems. During build and test, synthetic ticking sources and constants stand in for live feeds.

How are inputs like time and randomness handled?

They enter as recorded inputs. Clocks, seeds and external events are captured in the event stream, so logic observes them as data rather than ambient state, and a replay sees exactly the same values.

Run it against what you run today.

Request a pilot conversation