Capital markets platform

Four layers. One platform.

Nexora’s flagship build for capital markets: execution, connectivity, compliance and market data behind one API, for brokers, fintechs and trading firms. It is being built with a small number of design partners, and it is not in production.

In buildPre-productionAPI not yet callableNo production customersNo attestations held

Many rails in. One contract out.

A broking business in India holds live connections to five exchanges, two depositories and a bank for every payment method it supports, each with its own protocol, certification cycle and failure mode. The software has to be correct to the paisa and explainable to a regulator years later.

The platform holds those connections for you, behind one API and one agreement.

NexoraOne APIOne contract

Your productYour brand · your clients

NexoraOne API

Your product

Nine systems on the far side, one contract on yours. Point at a name, tap it or tab to it to see which layer of the platform carries it.

First call

POST /v1/orders

01POST /v1/orders

Execution

The order-and-risk engine.

The OMS, a deterministic pre-trade risk engine and a venue-aware router, built on a single event log so every order, every fill and every modification can be reconstructed exactly as it happened.

Pre-trade risk inline on every order: margin, exposure, SPAN, concentration
Order routing across NSE, BSE and MCX in each venue's own protocol
Order lifecycle: amend, replace, cancel, parent and child — every step audited
Event-sourced, so any session, day or account can be replayed
Multi-leg, basket and bracket orders as first-class primitives

p99 ack target: < 5ms
Order types: Multi-leg · basket · bracket
Replay: Event-sourced

02stream venues.*

Connectivity

One adapter. Every venue.

The exchange, depository and bank-rail connections, held on your behalf behind a single contract — protocols, failover and observability included — so you build to one surface rather than one per venue. Certification is granted by each venue, one at a time, and none is held yet.

Exchange sessions in each venue's native protocol, managed end to end
Depositories: NSDL and CDSL holdings, pledges and corporate actions
Bank rails: UPI, NEFT, RTGS and IMPS for payouts, collections and reconciliation
MSEI, NCDEX and MCX as first-class venues alongside NSE and BSE
Active-active across regions, with failover designed to be deterministic

Exchanges in scope: NSE · BSE · MCX · NCDEX · MSEI
Depositories: NSDL · CDSL
Recon target: T+0

03audit.export()

Compliance

Compliance, built in.

KYC onboarding, AML screening, trade surveillance and reporting, wired together against an append-only audit trail — designed so the record can be handed to a regulator as it stands rather than assembled for the occasion.

Digital KYC: PAN, Aadhaar eKYC, the CKYC registry, OCR and liveness
AML screening against PEP and sanctions lists, with ongoing monitoring
Trade surveillance for layering, spoofing, wash trades and insider patterns
An append-only, hash-chained audit trail designed for ten-year retention
Exchange and SEBI report templates, exported from the same record

KYC rails: PAN · Aadhaar · CKYC
Screening: AML · PEP · sanctions
Audit retention: 10 yr design

04SELECT * FROM ticks

Market data

Every tick. One schema.

Real-time ticks, snapshots and L2 depth across the Indian venues, joined to point-in-time fundamentals and corporate actions, under one schema that stays put when a venue changes its own.

Tick-by-tick and L2 depth across equities, F&O, commodities and currency
History that is point-in-time correct, with depth growing from launch
Fundamentals, filings and corporate actions joined to live prices
Delivery over WebSocket, gRPC or Kafka — whichever your desk runs
Configurable conflation, and replay from any timestamp

Venues: NSE · BSE · MCX
Transport: REST · WS · gRPC
Schema: One across venues

One order, end to end

What happens to an order.

01
Received
One API surface
The order arrives over REST or the streaming session — the same contract whichever venue it is bound for, and whichever of your desks sent it.
PENDING · unvalidated
02
Risk checked
Inline, before routing
Margin, exposure, SPAN and concentration are evaluated in the order path rather than beside it. An order that fails a check never reaches a venue, which is the only version of pre-trade risk that means anything.
VALIDATED · limits applied
03
Routed
Venue-specific protocol
The order is translated into whatever the destination speaks — an exchange's own protocol, not a lowest-common-denominator abstraction — and sent on the session held open for it.
IN FLIGHT · exchange bound
04
Acknowledged
Exchange order ID bound
The venue's acknowledgement is joined back to your order ID, so one identifier follows the order from your system to the exchange and back without a reconciliation step in between.
LIVE · resting on book
05
Filled
Streamed, not polled
Fills arrive on the same stream as everything else, partial or complete, in sequence. Positions and margin move with them rather than on a timer.
EXECUTED · position updated
06
Booked
Written once, kept
The trade is written to an append-only audit trail designed for ten-year retention, alongside the contract note and the obligations that follow from it.
BOOKED · audit trail written
07
Settled
Depository and bank rails
Securities move through NSDL or CDSL and funds through the bank rails, reconciled against the same record the order started in. One system of record, end to end.
SETTLED · reconciled

One order, end to end

What happens to an order.

Received

One API surface

The order arrives over REST or the streaming session — the same contract whichever venue it is bound for, and whichever of your desks sent it.

Risk checked

Inline, before routing

Margin, exposure, SPAN and concentration are evaluated in the order path rather than beside it. An order that fails a check never reaches a venue, which is the only version of pre-trade risk that means anything.

Routed

Venue-specific protocol

The order is translated into whatever the destination speaks — an exchange's own protocol, not a lowest-common-denominator abstraction — and sent on the session held open for it.

Acknowledged

Exchange order ID bound

The venue's acknowledgement is joined back to your order ID, so one identifier follows the order from your system to the exchange and back without a reconciliation step in between.

Filled

Streamed, not polled

Fills arrive on the same stream as everything else, partial or complete, in sequence. Positions and margin move with them rather than on a timer.

Booked

Written once, kept

The trade is written to an append-only audit trail designed for ten-year retention, alongside the contract note and the obligations that follow from it.

Settled

Depository and bank rails

Securities move through NSDL or CDSL and funds through the bank rails, reconciled against the same record the order started in. One system of record, end to end.

Sample orderIllustrative

{
  "id":     "ord_SAMPLE01",
  "venue":  "NSE",
  "status": "received"
}

PENDING · unvalidated

01 / 07 · keep scrolling

Where we are

Built in Nagpur.
Wired to Mumbai.

All five exchanges the platform is built against, and both depositories, sit in one city. We are 680 kilometres east of it, in the city whose Zero Mile Stone was cut to mark the centre of the country. Distance is a design constraint, so we designed for it: the platform is built to be operated from anywhere and connected where the venues actually are.

In Mumbai · 680 km · 250°

Exchange · NSE

National Stock Exchange of India

Equities, equity derivatives, currency and debt.

Our standing: Not yet certified — conformance is done venue by venue.

Why build on it

Three ways to launch.Only one of them is our problem.

Anyone launching a broking business in India is choosing between the same three paths. Here is the honest shape of each — including where building it yourself is still the right answer, and where a new vendor is the wrong risk to take.

Comparison of building in-house, assembling point vendors, and building on the Nexora capital markets platform as designed
Dimension	Build in-house	Point vendors	Nexora, as designed
Where the first year goes	Venue plumbing and certification, one exchange at a time	Making the vendors agree with each other	Your product, against one contract
Vendors under contract	Exchange memberships only	Five to seven	One
Who answers when it breaks	Your team, every venue	Split — and disputed at 09:15	Us, under one agreement
Compliance surface	Built and certified in-house	Bolted on after the fact	Inline, audited by default
Adding a venue	A project of its own	A new contract	Configuration, once the venue is certified

Where the first year goes

Build in-house: Venue plumbing and certification, one exchange at a time
Point vendors: Making the vendors agree with each other
Nexora, as designed: Your product, against one contract

Vendors under contract

Build in-house: Exchange memberships only
Point vendors: Five to seven
Nexora, as designed: One

Who answers when it breaks

Build in-house: Your team, every venue
Point vendors: Split — and disputed at 09:15
Nexora, as designed: Us, under one agreement

Compliance surface

Build in-house: Built and certified in-house
Point vendors: Bolted on after the fact
Nexora, as designed: Inline, audited by default

Adding a venue

Build in-house: A project of its own
Point vendors: A new contract
Nexora, as designed: Configuration, once the venue is certified

As designed — the platform is pre-production. This column describes what it is being built to do, not a record of what it has done for anyone.

One contract, one throat to choke

Every venue, depository and bank rail sits behind a single commercial and technical relationship. When something breaks at 09:15, there is no vendor triangle to arbitrate — the escalation path is one page long.

Compliance is structural, not additive

Surveillance, AML and the audit trail are being built as properties of the order path itself, not as a reporting layer downstream of it. Every order is reconstructible from an append-only log.

New, and open about it

Nexora is a new firm, and says so. The platform is being designed against real venue protocols and real regulatory obligations rather than a feature list, and the first firms to build on it will shape what it becomes.

You keep the differentiated part

The platform ships no front end of its own and never owns your customer. The plumbing becomes a primitive, so your engineers spend their quarters on the product your users actually see.

The platform is in build. Two products ship today.

The platform is the capital markets practice’s long build. What distributors, brokers and depository participants can use now are these.

Part of Nexora’sCapital markets practice Where the firm started, and the one industry it ships products for today.Twelve industries, one engineering houseNexora builds for every industry

Tell us howyour businessactually runs.

Bring the forms, the registers and the workarounds. We will tell you plainly what we would build first, and what we would leave alone.

Book a demo

Scope your build

Or write to hello@nexoratechnologiesnagpur.com

Capital markets platform

Four layers. One platform.

In buildPre-productionAPI not yet callableNo production customersNo attestations held

Many rails in. One contract out.

The platform holds those connections for you, behind one API and one agreement.

NexoraOne APIOne contract

Your productYour brand · your clients

NexoraOne API

Your product

Nine systems on the far side, one contract on yours. Point at a name, tap it or tab to it to see which layer of the platform carries it.

First call

POST /v1/orders

01POST /v1/orders

Execution

The order-and-risk engine.

The OMS, a deterministic pre-trade risk engine and a venue-aware router, built on a single event log so every order, every fill and every modification can be reconstructed exactly as it happened.

Pre-trade risk inline on every order: margin, exposure, SPAN, concentration
Order routing across NSE, BSE and MCX in each venue's own protocol
Order lifecycle: amend, replace, cancel, parent and child — every step audited
Event-sourced, so any session, day or account can be replayed
Multi-leg, basket and bracket orders as first-class primitives

p99 ack target: < 5ms
Order types: Multi-leg · basket · bracket
Replay: Event-sourced

02stream venues.*

Connectivity

One adapter. Every venue.

Exchange sessions in each venue's native protocol, managed end to end
Depositories: NSDL and CDSL holdings, pledges and corporate actions
Bank rails: UPI, NEFT, RTGS and IMPS for payouts, collections and reconciliation
MSEI, NCDEX and MCX as first-class venues alongside NSE and BSE
Active-active across regions, with failover designed to be deterministic

Exchanges in scope: NSE · BSE · MCX · NCDEX · MSEI
Depositories: NSDL · CDSL
Recon target: T+0

03audit.export()

Compliance

Compliance, built in.

Digital KYC: PAN, Aadhaar eKYC, the CKYC registry, OCR and liveness
AML screening against PEP and sanctions lists, with ongoing monitoring
Trade surveillance for layering, spoofing, wash trades and insider patterns
An append-only, hash-chained audit trail designed for ten-year retention
Exchange and SEBI report templates, exported from the same record

KYC rails: PAN · Aadhaar · CKYC
Screening: AML · PEP · sanctions
Audit retention: 10 yr design

04SELECT * FROM ticks

Market data

Every tick. One schema.

Real-time ticks, snapshots and L2 depth across the Indian venues, joined to point-in-time fundamentals and corporate actions, under one schema that stays put when a venue changes its own.

Tick-by-tick and L2 depth across equities, F&O, commodities and currency
History that is point-in-time correct, with depth growing from launch
Fundamentals, filings and corporate actions joined to live prices
Delivery over WebSocket, gRPC or Kafka — whichever your desk runs
Configurable conflation, and replay from any timestamp

Venues: NSE · BSE · MCX
Transport: REST · WS · gRPC
Schema: One across venues

One order, end to end

What happens to an order.

01
Received
One API surface
The order arrives over REST or the streaming session — the same contract whichever venue it is bound for, and whichever of your desks sent it.
PENDING · unvalidated
02
Risk checked
Inline, before routing
Margin, exposure, SPAN and concentration are evaluated in the order path rather than beside it. An order that fails a check never reaches a venue, which is the only version of pre-trade risk that means anything.
VALIDATED · limits applied
03
Routed
Venue-specific protocol
The order is translated into whatever the destination speaks — an exchange's own protocol, not a lowest-common-denominator abstraction — and sent on the session held open for it.
IN FLIGHT · exchange bound
04
Acknowledged
Exchange order ID bound
The venue's acknowledgement is joined back to your order ID, so one identifier follows the order from your system to the exchange and back without a reconciliation step in between.
LIVE · resting on book
05
Filled
Streamed, not polled
Fills arrive on the same stream as everything else, partial or complete, in sequence. Positions and margin move with them rather than on a timer.
EXECUTED · position updated
06
Booked
Written once, kept
The trade is written to an append-only audit trail designed for ten-year retention, alongside the contract note and the obligations that follow from it.
BOOKED · audit trail written
07
Settled
Depository and bank rails
Securities move through NSDL or CDSL and funds through the bank rails, reconciled against the same record the order started in. One system of record, end to end.
SETTLED · reconciled

One order, end to end

What happens to an order.

Received

One API surface

The order arrives over REST or the streaming session — the same contract whichever venue it is bound for, and whichever of your desks sent it.

Risk checked

Inline, before routing

Routed

Venue-specific protocol

The order is translated into whatever the destination speaks — an exchange's own protocol, not a lowest-common-denominator abstraction — and sent on the session held open for it.

Acknowledged

Exchange order ID bound

The venue's acknowledgement is joined back to your order ID, so one identifier follows the order from your system to the exchange and back without a reconciliation step in between.

Filled

Streamed, not polled

Fills arrive on the same stream as everything else, partial or complete, in sequence. Positions and margin move with them rather than on a timer.

Booked

Written once, kept

The trade is written to an append-only audit trail designed for ten-year retention, alongside the contract note and the obligations that follow from it.

Settled

Depository and bank rails

Securities move through NSDL or CDSL and funds through the bank rails, reconciled against the same record the order started in. One system of record, end to end.

Sample orderIllustrative

{
  "id":     "ord_SAMPLE01",
  "venue":  "NSE",
  "status": "received"
}

PENDING · unvalidated

01 / 07 · keep scrolling

Where we are

Built in Nagpur.
Wired to Mumbai.

In Mumbai · 680 km · 250°

Exchange · NSE

National Stock Exchange of India

Equities, equity derivatives, currency and debt.

Our standing: Not yet certified — conformance is done venue by venue.

Why build on it

Three ways to launch.Only one of them is our problem.

Comparison of building in-house, assembling point vendors, and building on the Nexora capital markets platform as designed
Dimension	Build in-house	Point vendors	Nexora, as designed
Where the first year goes	Venue plumbing and certification, one exchange at a time	Making the vendors agree with each other	Your product, against one contract
Vendors under contract	Exchange memberships only	Five to seven	One
Who answers when it breaks	Your team, every venue	Split — and disputed at 09:15	Us, under one agreement
Compliance surface	Built and certified in-house	Bolted on after the fact	Inline, audited by default
Adding a venue	A project of its own	A new contract	Configuration, once the venue is certified

Where the first year goes

Build in-house: Venue plumbing and certification, one exchange at a time
Point vendors: Making the vendors agree with each other
Nexora, as designed: Your product, against one contract

Vendors under contract

Build in-house: Exchange memberships only
Point vendors: Five to seven
Nexora, as designed: One

Who answers when it breaks

Build in-house: Your team, every venue
Point vendors: Split — and disputed at 09:15
Nexora, as designed: Us, under one agreement

Compliance surface

Build in-house: Built and certified in-house
Point vendors: Bolted on after the fact
Nexora, as designed: Inline, audited by default

Adding a venue

Build in-house: A project of its own
Point vendors: A new contract
Nexora, as designed: Configuration, once the venue is certified

As designed — the platform is pre-production. This column describes what it is being built to do, not a record of what it has done for anyone.

One contract, one throat to choke

Compliance is structural, not additive

Surveillance, AML and the audit trail are being built as properties of the order path itself, not as a reporting layer downstream of it. Every order is reconstructible from an append-only log.

New, and open about it

You keep the differentiated part

The platform ships no front end of its own and never owns your customer. The plumbing becomes a primitive, so your engineers spend their quarters on the product your users actually see.

The platform is in build. Two products ship today.

The platform is the capital markets practice’s long build. What distributors, brokers and depository participants can use now are these.

Part of Nexora’sCapital markets practice Where the firm started, and the one industry it ships products for today.Twelve industries, one engineering houseNexora builds for every industry

Tell us howyour businessactually runs.

Bring the forms, the registers and the workarounds. We will tell you plainly what we would build first, and what we would leave alone.

Book a demo

Scope your build

Or write to hello@nexoratechnologiesnagpur.com

Four layers. One platform.

Many rails in. One contract out.

Execution

Connectivity

Compliance

Market data

What happens to an order.

Received

Risk checked

Routed

Acknowledged

Filled

Booked

Settled

What happens to an order.

Built in Nagpur.Wired to Mumbai.

Three ways to launch.Only one of them is our problem.

One contract, one throat to choke

Compliance is structural, not additive

New, and open about it

You keep the differentiated part

The platform is in build. Two products ship today.

Tell us howyour businessactually runs.

Four layers. One platform.

Many rails in. One contract out.

Execution

Connectivity

Compliance

Market data

What happens to an order.

Received

Risk checked

Routed

Acknowledged

Filled

Booked

Settled

What happens to an order.

Built in Nagpur.Wired to Mumbai.

Three ways to launch.Only one of them is our problem.

One contract, one throat to choke

Compliance is structural, not additive

New, and open about it

You keep the differentiated part

The platform is in build. Two products ship today.

Tell us howyour businessactually runs.

Built in Nagpur.
Wired to Mumbai.

Built in Nagpur.
Wired to Mumbai.