Request a walkthrough
Market software / order flow infrastructure

Every price. Every order. One system.

Closing Edge builds the software layer between market data and execution: normalized feeds, transparent pricing, smart order routing, and the controls that keep every order accountable. Licensed to market participants. Operated by your team.

REST + WebSocket Private cloud or on-prem Software only

Product interface shown for illustration.

CORE STACK
01 / What we do

Software for the space between price and order.

Closing Edge is a market software company. Our products connect to venues, normalize data, compute reference prices, and route orders — giving professional teams one control plane for the full order lifecycle.

We don't trade for customers, and we don't provide investment advice. Our customers are market participants who operate the software themselves, under their own permissions, limits, and risk frameworks.

ISSoftware · Infrastructure · APIs · Event logs
IS NOTA broker · A trading service · An investment adviser
01 / MODEL

One instrument model

Every venue, contract, and quote resolves to the same object.

02 / STATE

One order state machine

Every action is explicit, inspectable, and idempotent.

03 / EVIDENCE

One event log

Every change can be replayed, audited, and reconciled.

02 / The platform

Four modules. One order flow.

Use the full stack or license the modules you need. Every product uses the same instrument model, event log, and control plane.

COMMON CORE

Every module runs on the same instrument model, order state machine, and event log. License the full stack or one module.

INSTRUMENTS ORDERS EVENTS
DATA LAYER01 / 04

Market data, normalized.

Connectors ingest order books, trades, and venue status from the APIs you already use. One instrument model, one stream, one source of truth for everything downstream.

CONNECTORS
Venue adapters for books, trades, and status.
INSTRUMENT MASTER
One model across contract types and venues.
REPLAY
Deterministic historical reconstruction.
DELIVERY
REST snapshots and WebSocket streams.
Discuss CE Feed ↗
PRICING LAYER02 / 04

A reference price you can inspect.

Configurable models compute fair value, implied probability, and dispersion from live and historical inputs. Every output carries its inputs, version, and confidence so your team can see how the number was made.

MODELS
Reference, probability, and spread models.
INPUTS
Live books, history, and your own axes.
CONFIDENCE
Dispersion and quality on every output.
VERSIONING
Model versions, parameters, and change history.
Discuss CE Price ↗
FLOW LAYER03 / 04

Orders with a state machine.

CE Route turns intent into orders and tracks every transition: validated, routed, acknowledged, partially filled, filled, cancelled, or rejected. Pre-trade checks and route selection run before anything leaves your environment.

SMART ROUTING
Best-price, venue-priority, and custom policies.
STATE MACHINE
Explicit states for every order and child order.
PRE-TRADE CHECKS
Size, price, permissions, and venue health.
IDEMPOTENCY
Safe retries with client-supplied order IDs.
Discuss CE Route ↗
CONTROL PLANE04 / 04

The control plane.

Set permissions by team, venue, and instrument. Apply limits, throttles, and kill switches. Read an immutable event log. CE Control is the place where operations, risk, and engineering see the same view.

PERMISSIONS
Role-based access by desk, venue, and instrument.
LIMITS
Size, notional, rate, and exposure controls.
KILL SWITCH
Immediate stop and cancel across connected venues.
AUDIT LOG
Immutable request and state history.
Discuss CE Control ↗
03 / Order flow

Every order has a path. We make it visible.

Closing Edge turns order flow into a sequence of explicit, inspectable states. Each stage has an owner, a check, and an event. Nothing happens off the record.

01

Connect

Venue APIs, credentials, and entitlements are configured per environment.

02

Normalize

Books, trades, and contract metadata resolve to one instrument model.

03

Price

Reference price, spread, and confidence are computed from the inputs you choose.

04

Route

Policy selects a venue; pre-trade checks validate size, price, and permissions.

05

Reconcile

Acknowledged, filled, cancelled, and rejected states are written to the event log.

ORDER TRACE / 8F2A-19 SAMPLE EVENT LOG
09:41:22.114RECEIVEDorder.created
09:41:22.118VALIDATEDchecks.passed 7/7
09:41:22.121PRICEDref.mark 0.473 · conf 0.91
09:41:22.126ROUTEDroute.select venue=VENUE_B
09:41:22.147ACKEDvenue.ack id=V-77219
09:41:22.302PARTIALfill 600 @ 0.473
09:41:22.418FILLEDfill 600 @ 0.473
RECEIVED VALIDATED ROUTED ACKED FILLED CANCELLED REJECTED
CHECKS7 / 7 PASSED
ROUTE TIME18 MS
EVENTS11 LOGGED

Every transition is an event. Every event is replayable. Rebuild the full order path at any time.

04 / Interfaces

Built to be integrated, not worked around.

APIs are the product. Use the same primitives our own console uses: streams for change, snapshots for state, and an order model that behaves the same in every environment.

REST + WEBSOCKET

State and change

Snapshots for current state; streams for every update.

IDEMPOTENCY

Safe retries

Client-supplied order IDs make repeated calls safe.

SANDBOX

Test before production

Replayable market data and a simulated venue.

EVENT REPLAY

Reconstruct anything

Rebuild any order, quote, or venue state from the log.

OBSERVABILITY

Built-in telemetry

Structured logs, request IDs, and latency metrics.

OPENAPI

Typed contracts

Schemas that generate clients and catch drift early.

const stream = ce.feed.subscribe({
  instruments: ["EVT-0428", "MKT-117"],
  channels: ["book", "trades", "status"],
});

stream.on("book", (book) => {
  console.log(book.bids[0], book.asks[0]);
});
const quote = await ce.price.quote({
  instrument: "EVT-0428",
  model: "reference-v3",
  horizon: "live",
});

// { fair: 0.473, spread: 0.002, confidence: 0.91 }
const order = await ce.orders.create({
  instrument: "EVT-0428",
  side: "buy",
  qty: 1200,
  limit: 0.473,
  route: "best-price",
  idempotencyKey: "ord_8f2a19",
});
REST + WEBSOCKET OPENAPI 3.1 · SANDBOX · EVENT REPLAY
SURFACEREST + WebSocket
AUTHScoped API keys
DEPLOYVPC or on-prem
05 / Market coverage

Any market with a price and an API.

One instrument model across venues, contract types, and market structures. Configure what you connect; the software handles the rest.

01

Event contracts

Binary and multi-outcome contracts with expiries, rules, and reference metadata.

02

Prediction markets

Live books, quotes, and event metadata from regulated venues.

03

Listed venues

Exchange connectivity for order books, trades, and venue status.

04

OTC & dealer venues

Negotiated and voice-assisted flow, modeled as structured orders.

05

Internal books

Price and route against your own inventory and risk axes.

06

Custom integrations

Adapter development for proprietary APIs and protocols.

One instrument model. One order state machine. One audit trail. Talk about a venue ↗
06 / Flow connectivity

Bring your flow. Keep your controls.

Closing Edge Connect is a private connectivity layer for teams that originate or make order flow. It gives each side one integration point for message schemas, permissions, and order exchange — without giving up control of their book.

Counterparty permissions
Schema and entitlements
Venue-agnostic routing
Full event audit
Discuss connectivity
SCHEMA PERMISSIONS ROUTING AUDIT FLOW ORIGINATOR PRICING / INTENT MARKET MAKER QUOTES / INVENTORY VENUE A ORDER BOOK VENUE B ORDER BOOK CE CONNECT ORDER FLOW LAYER
PERMISSIONS SCHEMA ROUTING AUDIT TRAIL
07 / Production

Control is a feature.

The platform is built for the unglamorous parts of market operations: permissions, limits, replay, and evidence.

01

Deterministic order state

Orders move through explicit states. Retries are idempotent. Nothing is inferred.

02

Audit by default

Every request and state change is appended to an immutable event log.

03

Deploy your way

Run in your private cloud, VPC, or on-prem. Your data stays in your environment.

04

Observable end to end

Venue health, latency, rejects, and flow metrics in one control plane.

05

Role-based access

Separate permissions for operators, engineers, and risk.

06

Replayable by design

Rebuild any session, order, or venue view from the event log.

08 / Questions

The short answers.

Still deciding whether the platform fits your stack? Start with a technical conversation, not a sales deck.

Ask a question ↗

No. Closing Edge is a software company. We license market infrastructure to professional teams. Customers configure and operate the software under their own permissions, limits, and risk frameworks.

No. Orders are initiated and controlled by the customer's own systems and operators. CE Route provides the order management and routing layer; the customer decides when and how to use it.

Any market with a programmatic interface: event contracts, prediction markets, listed venues, OTC and dealer venues, and internal books. We also build custom adapters for proprietary APIs.

Yes. The platform is designed for private cloud, VPC, and on-prem deployment. Hosted environments are available for evaluation and smaller teams.

Modular annual licenses scoped to the products, venues, and deployment model you need. We'll size the stack with your team.

Yes. Evaluate the APIs against replayable market data and a simulated venue before connecting production credentials.

A technical scoping session, venue and schema mapping, sandbox integration, then a controlled production rollout.

Get in touch

Put your order flow on better infrastructure.

Tell us what you trade, where you connect, and how your team operates. We'll map the platform to your stack and walk through the flow end to end.

Request a technical walkthrough
EMAIL
[email protected]
TELEGRAM · FASTEST REPLY
@Blang11
For professional market participants. Closing Edge provides software and infrastructure only.