ArkNite PULSE
Drop copy · by ArkNite Solutions

Every order and fill, the moment it happens.

PULSE holds a live FIX connection to your brokers and exchanges, captures order and trade data in real time, maps it to your back-office codes, and streams it to FORGE and your downstream systems - with transfer exceptions surfaced as they occur.

FIX drop copy Real-time capture Mapped to back-office codes Fans out downstream
PULSE FIX gateway monitoring dashboard
FIX sessions · initiator & acceptor Broker & exchange · TT · CQG · CME · ICE Orders · fills · rejects Real-time transfer exceptions
Why real-time matters

Batch files at end of day aren't fast enough anymore.

When order and trade data arrives late, everything downstream waits - the back office, surveillance, and risk all work from yesterday's picture.

End-of-day lag

Batch extracts mean the back office and risk only see the day once it's over.

Mapping by hand

Broker account and symbol codes are translated to internal codes manually, and inconsistently.

Every system, its own feed

Surveillance and risk each build a separate connection, so the data never quite agrees.

Silent failures

A dropped session or an unmapped account goes unnoticed until a trade goes missing.

How it works

Capture once. Map. Send everywhere.

PULSE sits upstream of your back office, taking a FIX drop copy straight from the source and turning it into clean, mapped data your systems can use immediately.

01

Connect

A FIX session to each broker & exchange - initiator or acceptor.

02

Capture

Orders and fills read off the wire in real time.

03

Map

Accounts and symbols translated to your back-office codes.

04

Distribute

Streamed to FORGE and every downstream system at once.

One capture, mapped once, delivered everywhere - in real time.
New orders
Fills
Rejects
Session health
Sequence numbers
Architecture

One upstream feed. Every downstream system.

PULSE is the single point of capture between the market and your operation - so FORGE, surveillance, and risk all work from the same real-time data.

FIX real-time Broker / Exchange TT · CQG · CME · ICE ArkNite PULSE capture · map · distribute FORGE back office Trade surveillance monitoring Risk management real-time limits
Monitoring

Every session, every message - in view.

FIX gateway dashboard

Know the health of every connection at a glance.

Live counts of new orders, fills, and rejects, an overall system status, and a row for every FIX session - its platform, initiator or acceptor role, logged-on state, sequence numbers, and last message time.

  • Orders · fills · rejects · pending mapping
  • Session state: LoggedOn · LoggedOut · PendingConnect
  • In/out sequence numbers & last message
FIX sessions and message counts
Account & symbol mapping

Broker codes in. Your codes out.

Account and symbol mapping
Mapping

Translate every account and symbol on the way through.

Map each trading account (the broker or exchange's client ID) to its back-office account, and each broker symbol or prefix to your instruments - so what reaches FORGE and downstream is already in your language.

  • Trading account → back-office account
  • Symbols & prefixes → your instruments
  • Unmapped items flagged as pending
Real-time exceptions

Nothing goes missing quietly.

PULSE watches the flow as it moves and raises an exception the instant something needs attention - not at end of day, when it's already a problem.

REJECT

Order rejects

A rejected order is counted and surfaced the moment the exchange returns it.

PENDING MAPPING

Unmapped account or symbol

Anything without a back-office mapping is held and flagged, not dropped.

SESSION

Degraded session

A logged-out or stalled FIX session shows immediately, before trades slip.

Why brokers run PULSE

Real-time in. Real-time out. Nothing lost.

Real-time, not end-of-day

Orders and fills reach your systems as they happen, straight off the FIX wire.

One feed, many systems

Capture once and fan out to FORGE, surveillance, and risk from a single source.

Mapped to your codes

Accounts and symbols land in your back-office language, ready to use.

Nothing slips

Rejects, unmapped items, and dropped sessions are caught in real time.

FAQ

Questions teams ask.

What is a drop copy, and what does PULSE capture?

A drop copy is a real-time FIX feed of your order and trade activity from a broker or exchange. PULSE holds those sessions and captures new orders, fills, and rejects as they happen, along with session health and sequence numbers.

How does it connect?

Over FIX, as either initiator or acceptor, to each broker and exchange - for example TT, CQG, CME, and ICE. Each session is monitored for its logged-on state, sequence numbers, and last message.

How does mapping work?

PULSE maps each trading account (the broker's client ID) to your back-office account, and broker symbols or prefixes to your instruments, so data arrives already in your codes. Anything unmapped is flagged as pending rather than dropped.

Where does the data go?

Into FORGE as the back-office system of record, and out to downstream systems such as trade surveillance and risk management - all from the one captured feed, in real time.

What happens when something fails?

PULSE raises real-time transfer exceptions - order rejects, unmapped accounts or symbols, and degraded FIX sessions are surfaced immediately, so issues are caught before a trade goes missing.

Let's talk

See your order flow, live.

We'll connect PULSE to a FIX session and show orders and fills arriving, mapped, and fanning out to your systems in real time.

Thanks - we'll be in touch shortly to arrange your demo.
info@arknite.com  ·  +91 99209 34442  ·  arknite.com