Fintech and payments Case study

Rainbow: options trading and risk platform

RainbowClient: Rainbow Capital

A .NET trading engine, API and Next.js control console for Rainbow Capital that runs configurable US equity options strategies under per-underlyer risk limits, with daily profit and loss reports to Slack.

  • Next.js
  • React
  • TypeScript
  • ASP.NET Core
  • .NET
Client
Rainbow Capital
Service
Web apps, Integrations
Years
2023–2024
Stack
Next.js, React, TypeScript, ASP.NET Core and 8 more
Platforms
Web

Overview

Rainbow runs automated options strategies on US equities. A .NET 8 engine finds option spreads, generates target positions and works out risk scenarios, and an API and a Next.js console let operators sign in, see their strategies and change their parameters. A separate tracker posts the daily profit and loss report to Slack.

The challenge

Several strategies run against live market data, each with strict risk limits per underlying. Operators need to start, stop and tune them safely from a browser, and the team needs the day's results without checking by hand.

What we built

  1. A strategy engine with lifecycle states and a market open and close monitor
  2. Spread finding for call, put and complex option spreads
  3. A target position generator with a work queue
  4. A position risk manager and risk scenario calculator
  5. An integration layer with the market data and order vendor
  6. A REST API with JWT sign-in for starting, stopping and configuring strategies
  7. A PostgreSQL schema with versioned migrations
  8. A Next.js console: sign-in, environment, strategy list and a strategy detail editor
  9. A profit and loss tracker with a daily job, file reports and Slack posting
  10. Handling of NYSE market holidays
  11. A deployment pipeline with GitHub Actions, Docker Compose and nginx with TLS, and automated tests

How a system like this fits together

Reference architecture: options trading and risk platform

Simplified reference architecture, not a client schematic.

Reference architecture: options trading and risk platformZones from left to right: clients (the operator console), the application (the strategy API and the strategy engine), background jobs (the profit and loss tracker), data (PostgreSQL) and third-party services (a market data and order vendor, and Slack). Full description in the numbered list below the diagram.ClientsApplicationBackground jobs (async)DataThird-party servicesRESTstart / stopmarket data, ordersread / writedaily reportOperator consoleNext.js: sign-in,strategy editorStrategy APIASP.NET Core:JWT sign-in, controlStrategy engine.NET: spreads, targetpositions, risk limitsProfit and loss trackerDaily job, file reportPostgreSQLConfiguration,results, usersMarket data, order vendorThird-party data andorder providerSlackDaily profit and lossreportReference architecture: options trading and risk platformZones from left to right: clients (the operator console), the application (the strategy API and the strategy engine), background jobs (the profit and loss tracker), data (PostgreSQL) and third-party services (a market data and order vendor, and Slack). Full description in the numbered list below the diagram.ClientsApplicationDataBackground jobs (async)Third-party servicesRESTstart / stopread / writedaily reportmarket data, ordersOperator consoleNext.js: sign-in,strategy editorStrategy APIASP.NET Core: JWTsign-in, controlStrategy engine.NET: spreads, targetpositions, risk limitsPostgreSQLConfiguration,results, usersProfit and loss trackerDaily job, file reportSlackDaily profit and loss reportMarket data, order vendorThird-party data and orders
Operators control strategies from a web console and an API; a .NET engine finds spreads, sizes positions under risk limits and trades through a market data and order vendor, and a daily tracker posts profit and loss to Slack.
  1. An operator signs in to the Next.js console, and the console calls the ASP.NET Core strategy API over REST with a JWT.
  2. The operator starts, stops or tunes a strategy; the API passes the command to the strategy engine.
  3. The engine finds option spreads in live market data from the market data and order vendor and sends orders back through it.
  4. It works out target positions and risk, keeps each underlying within its risk limits, and reads and writes configuration and results in PostgreSQL.
  5. A separate profit and loss tracker runs a daily job, writes a file report and posts the day's profit and loss to Slack.

Technology used

Technology named in the project records, by layer
LayerChoicePurpose
Front endNext.js, React, Tailwind CSSoperator console
APIASP.NET Core, JWTstrategy control and sign-in
Engine.NET librariesspreads, positions and risk
DataPostgreSQL, Entity Framework Coreconfiguration, results and users
OperationsDocker Compose, nginx, GitHub Actions, Slackdeploy and alert

What happened next

  • Delivered

    The work described above was delivered to the client.

  • Operational facts
    • Our work on this project spanned 2023–2024.

Could this be your project?

  • You need a web application with user accounts, admin tools and reporting. Website and web app development
  • Your product has to connect to payment, accounting, messaging or other third-party systems.
  • You work in fintech and payments and want a team that has built for it before. Fintech and payments work

Request similar work

Questions about this project

How long did this project take?

Our work on it ran from 2023 to 2024.

What technology was used?

Next.js, React, TypeScript, ASP.NET Core, .NET, C#, PostgreSQL, Docker, Entity Framework Core, Tailwind CSS, nginx, GitHub Actions.

Similar work

AutoAccount sign-in screen

Also React and PostgreSQL, same industry

AutoAccount: financial management and accounting platform

  • Fintech and payments
  • Business software and compliance
  • Web apps
  • Integrations

2025–2026

A React and FastAPI accounting platform for multi-location repair shops: bank and Tekmetric data, AP/AR, bill scheduling, payroll and ledger entries, dashboards and reports.

Reactor: AI assistant and Web3 data back end screenshot

Also PostgreSQL, same industry

Reactor: AI assistant and Web3 data back end

  • Fintech and payments
  • Web apps
  • Integrations
  • AI

2024–2025

A Node.js back end for Reactor, an AI chat assistant with Web3 tools: streaming chat and voice, a keyed language-model API for businesses, and a crypto service for token audits, swaps and rewards.

Froono: customer loyalty platform screenshot

Also React and PostgreSQL, also a web app

Froono: customer loyalty platform

  • Retail and eCommerce
  • Web apps
  • Mobile apps
  • Integrations
  • AI

2023–2026

A multi-tenant customer loyalty platform: web admin, customer API, a mobile app and a PWA, with receipt checking, lucky draws, WhatsApp campaigns, AI image generation and online payments.

Building something similar?

Tell us what you need and your industry. We will tell you what is realistic, what it would take, and show you the closest work we have done.

Are you ready to partner with us?

Our good-natured team is waiting to hear your business requirements.

Book a free project call