Connectivity
Venue adapters, credential handling expectations, and the practical details needed to connect the desks and venues that matter to your workflow.
// docs
Documentation is shared directly during onboarding.
Forged does not run a public self-serve queue. Teams that want reference material, workflow details, or integration notes can request the current brief directly.
What the overview covers.
The initial brief is meant to answer whether Forged matches the desk workflow before anyone spends time on implementation detail.
Execution model
A shared order lifecycle for intent, routing, acknowledgment, and fill events so teams can reason about multiple venues in one language.
Reporting and replay
Replay trails, exports, and operational context that stay tied to the flow that generated the trade instead of living in a separate reporting stack.
Need the current routing brief?
Send the venues and products you care about. Forged will reply directly with the relevant overview material.