Connect the right identity
Associate an order with the responsible client and algorithm.
WHY IT MATTERS
An order should have a traceable origin.
Support inspection workflows
Make authorisation context easier to review alongside order evidence.
Respect registration boundaries
Use the assigned identifier without claiming to register independently.
THE OPERATING MODEL
What happens, and in what order.
Register
The broker follows the applicable exchange process.
Record
Administer the exchange-assigned identifier.
Associate
Attach the appropriate identity to eligible order activity.
Trace
Review the order, client and algorithm context together.
MAKE THE EVALUATION CONCRETE
Ask to see it.
Use these demonstrations to test the fit with your institution. Capability descriptions are a starting point, not independent assurance.
- Follow an assigned identifier into order evidence.
- Inspect the handling of a missing authorisation.
- Confirm responsibilities with the broker’s compliance team.
QUESTIONS, ANSWERED
The questions that matter.
Bring the next question to a focused product and architecture conversation.
Does Stretus register algorithms?
No. The documented capability administers identifiers assigned through the broker and exchange process.
Does an identifier guarantee execution?
No. Account eligibility, risk checks and execution controls still apply.
Are requirements identical across markets?
No universal claim is made. Confirm the relevant venue and jurisdiction requirements during evaluation.
CONNECTED CAPABILITIES
Continue the evaluation.
START WITH YOUR REQUIREMENTS
Bring your operating model.
Let’s map the fit.
Discuss the client journey, enabled scope and institutional controls that matter to your team.