daros / modules / oems
daros://modules/oems

Order and execution management for controlled trading operations.

DAROS OEMS manages strategy orders, manual orders, basket orders, execution routing, broker order status, positions and execution logs — so every order in your operation moves through one controlled, auditable pathway.

FAIL STATE THIS MODULE PREVENTS

Execution logic scattered across broker terminals fails silently — an operator fat-fingers a quantity, a strategy double-fires, and nobody can reconstruct why. DAROS OEMS puts every order — manual, automated or basket — through one gated, logged pathway, so execution errors are caught in the pipeline instead of discovered in the P&L.

problem it solves

What breaks without it

These are the failure patterns DAROS OEMS is built to remove:

  • Manual execution errors creeping into live operations
  • Scattered broker workflows across terminals and tabs
  • Poor visibility into order state after submission
  • No audit trail when something needs to be reviewed
  • Difficulty scaling to multiple strategies and accounts
who it is for

Built for

  • Individual traders automating execution
  • Prop desks running multiple strategies and operators
  • Brokers and fintechs building execution workflows
  • Quant teams moving research into live routing
technical profile

Spec sheet & configuration

Where this module sits in the pipeline, what it handles, and what its configuration looks like. Figures marked as design targets are benchmarked per deployment.

ROUTING OVERHEADLow single-digit-millisecond design target in the order path — measured and reported per deployment
SUPPORTED ASSETSEquities · F&O · Commodities · Currencies · Crypto (venue-dependent)
ORDER TYPESMarket · limit · stop · basket / multi-leg · staged release
API PROTOCOLSREST + WebSocket via DAROS Connect · FIX where broker-supported
DEPLOYMENTCloud or on-prem / VPS · per-desk isolation

Values are design targets and depend on deployment environment, broker APIs and data sources. Nothing here is a performance or return claim.

oems.routing.json
{
  "strategy": "daily-opt-01",
  "route": {
    "accounts": ["MAIN-01", "MAIN-02"],
    "broker": "brk-2",          // via daros://connect
    "order_type": "limit",
    "basket_release": "gated"   // operator confirms
  },
  "pre_trade": "rms.default",    // never bypassed
  "retry": { "max": 2, "on": ["timeout", "broker_5xx"] }
}
core capabilities

What DAROS OEMS does

Strategy order routing

Signals from automated strategies become structured orders with defined routing rules.

Manual + automated workflows

Desk operators and algorithms work through the same controlled execution layer.

Basket orders

Stage, gate and release multi-leg or multi-symbol baskets as one unit.

Position tracking

Account-wise and strategy-wise positions synced against broker state.

Order status sync

Placed, acknowledged, partially filled, filled, rejected — tracked in real time.

Broker API routing

Orders route through DAROS Connect to the brokers you configure.

Execution audit logs

Every order event is logged with timestamps for post-trade review.

Admin controls

Pause strategies, block symbols, or hold routing at the desk level.

Error handling & retry logic

Structured handling for rejections, timeouts and partial failures.

Account-wise execution visibility

See exactly what executed where, per account and per strategy.

example workflows

How it runs in practice

workflow_01

Strategy-to-broker routing

A validated strategy emits a signal → OEMS builds the order → RMS pre-trade checks pass → order routes to the configured broker → status and fills sync back → the event is logged.

workflow_02

Desk basket release

An operator stages a 12-leg options basket → reviews margin and risk gates → releases the basket → OEMS tracks each leg to completion and flags partials for retry.

workflow_03

Multi-account scaling

One strategy runs across several accounts → OEMS keeps per-account order state separate → DAROS Monitor shows a single consolidated execution view.

daros://platform

How it connects with other DAROS modules

No module runs alone. DAROS OEMS plugs into the rest of the platform:

DAROS RMSEvery order passes pre-trade risk checks before routing.
DAROS ConnectBroker APIs, order endpoints and status feeds.
DAROS CopyMaster fills fan out to child accounts through the same execution layer.
DAROS MonitorOrder events, fills and errors stream into dashboards and logs.

All modules:

Walk through your execution workflow with an engineer.

Bring your current order flow — manual steps included. We will map it onto OEMS routing, gates and logs, and show you where errors stop.