About
The engineer behind KAI Terminal
I'm Suvrajit Ray. I designed and built KAI Terminal end to end — a multi-broker desk for Indian index-options sellers: a .NET 10 real-time risk engine that monitors live positions and auto-exits or rolls strikes on rule triggers, and a React 19 / Next.js cockpit streaming live Greeks, option-chain analytics, and blended P&L over SignalR.
Principles on display here
Functional core, imperative shell
Every decision — risk rules, strike selection, P&L roll-ups — lives in a pure, dependency-free function that's deterministic and unit-testable without a mock. The I/O shell stays dumb: fetch, hand a snapshot to the core, write the result back.
Pick boring, proven infrastructure
Redis pub/sub as the tick bus, Postgres for durable state, ASP.NET Data Protection for secrets at rest. The interesting part of a trading system is the domain logic; the plumbing should be unremarkable and reliable.
Abstractions that isolate blast radius
The risk engine depends only on interfaces and never sees a concrete broker. The equity surface runs on a fully parallel plane so a feed fault there can't disturb the option risk path. Faults stay contained.
Observability is a feature
Structured, tagged logging with per-request user attribution; correlated engine actions; levels shaped so the console stays clean and the firehose is one switch away. You can't operate what you can't see.
Open to the right opportunity
I like hard problems at the intersection of low-latency systems and real money — trading infra, real-time data, risk. If that's what you're building, I'd be glad to talk.
Get in touch