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.
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.
Product interface shown for illustration.
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.
Every venue, contract, and quote resolves to the same object.
Every action is explicit, inspectable, and idempotent.
Every change can be replayed, audited, and reconciled.
Use the full stack or license the modules you need. Every product uses the same instrument model, event log, and control plane.
Every module runs on the same instrument model, order state machine, and event log. License the full stack or one module.
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.
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.
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.
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.
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.
Venue APIs, credentials, and entitlements are configured per environment.
Books, trades, and contract metadata resolve to one instrument model.
Reference price, spread, and confidence are computed from the inputs you choose.
Policy selects a venue; pre-trade checks validate size, price, and permissions.
Acknowledged, filled, cancelled, and rejected states are written to the event log.
Every transition is an event. Every event is replayable. Rebuild the full order path at any time.
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.
Snapshots for current state; streams for every update.
Client-supplied order IDs make repeated calls safe.
Replayable market data and a simulated venue.
Rebuild any order, quote, or venue state from the log.
Structured logs, request IDs, and latency metrics.
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",
});
One instrument model across venues, contract types, and market structures. Configure what you connect; the software handles the rest.
Binary and multi-outcome contracts with expiries, rules, and reference metadata.
Live books, quotes, and event metadata from regulated venues.
Exchange connectivity for order books, trades, and venue status.
Negotiated and voice-assisted flow, modeled as structured orders.
Price and route against your own inventory and risk axes.
Adapter development for proprietary APIs and protocols.
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.
The platform is built for the unglamorous parts of market operations: permissions, limits, replay, and evidence.
Orders move through explicit states. Retries are idempotent. Nothing is inferred.
Every request and state change is appended to an immutable event log.
Run in your private cloud, VPC, or on-prem. Your data stays in your environment.
Venue health, latency, rejects, and flow metrics in one control plane.
Separate permissions for operators, engineers, and risk.
Rebuild any session, order, or venue view from the event log.
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.
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.