Partner and institutional platform
NexusTrade is the execution rail and research engine behind other people's products. You keep the brand, the customer, and the policy layer. We bring brokerage connectivity, backtesting, and agents — with a live-order approval boundary your compliance team controls.
Auditable research · human-gated by default · deploy to your trust boundary
Execution adapters
Asset classes
Optimization runs on training windows only. Candidates are selected on validation. The winner is promoted once to each out-of-sample fold, so the final number is not one the optimizer was allowed to see.
Where the line sits
The hardest part of any partnership is agreeing who owns what. This is the split we run in production, and the one we will hold ourselves to in writing.
What you are actually buying
Ordered by how long each one takes to build yourself. Execution connectivity is first for a reason.
A single order object routes to any connected brokerage. Auth, reconciliation, partial fills, and position accounting are already solved and already in production.
Run anchored or rolling walk-forward studies in the Rust engine with a strict train, validation, and out-of-sample sequence.
Aurora plans, researches, and authors strategies. Every step is recorded, so when someone asks why an order existed the answer is a record rather than a reconstruction.
Stated plainly: per-strategy automatic approval is available. When it is enabled no human reviewed that order, and NexusTrade does not imply otherwise. Institutions requiring manual review keep it disabled.
Choose the operating model
Most partners start whitelabelled and go deeper only when their regulator or their board requires it. The first choice does not lock you in.
| WhitelabelMost partnersYour brand, our infrastructure | Private deploymentOur stack, your infrastructure | Direct integrationYour stack, our APIs | |
|---|---|---|---|
| Time to first live order | Weeks | Months | Weeks |
| Who sees the customer | You, exclusively | You, exclusively | You, exclusively |
| Where strategies live | Our environment, exportable in full | Yours | Our environment, via API |
| Brokerage relationship | Ours or yours | Yours | Yours |
| Engineering lift on you | Low — embed and brand it | High — or contract us to build it | Medium — you build the UI |
| Commercials | Revenue share | Licence and support | Usage based |
| Proven in production | Yes — signed partner | Not yet | Yes — public SDKs |
Integration spec
Written so it can go straight into a diligence memo, including the parts that are not finished. This page is not claiming a compliance certification; it states the technical boundaries a compliance program can evaluate.
approvedByUser is false → true only after approval, with the decision persisted to the event ledgernexustrade on PyPI and npm · REST · MCP server · embeddable agent UIANCHORED or ROLLING, foldCount 2–8, GENETIC or SYSTEMATIC_SWEEP, with progress · checkpoint · cancel · persisted resultsEngagement model
Four phases, each ending in something you can hold. If phase two fails you have spent weeks and learned the answer, which is the point of running it second.
Phase 01
Map identity, data ownership, brokerage relationships, and who signs off on a live order.
You leave withA written split of responsibility and the integration surface.
Phase 02
Prove the single hardest thing — usually identity federation or the brokerage handoff — against one narrow workflow.
You leave withA working path, or a clear no before anyone spends real money.
Phase 03
The same code path with the approval gate on and real reviewers. Scoped sessions and telemetry in place.
You leave withOrders flowing end to end under your brand.
Phase 04
Walk your risk and compliance team through real agent traces, real approvals, and real portfolio events.
You leave withA go or no-go with evidence attached, and commercial terms.
Diligence
Answering these here shortens your internal review, which is the only thing that actually moves a deal forward.
Yes, and it is the shape we prefer. Your engine evaluates before the approval gate; we enforce the gate and route the order. We do not require you to adopt our sizing or allocation controls, and we never overwrite your verdict.
Agent-originated orders are created in an unapproved state. The check that releases an order to a brokerage lives inside the brokerage layer itself, so it runs no matter which caller initiated the request — the API, the UI, an agent, or a scheduled job.
Per-strategy automatic approval can be enabled deliberately. We will not describe an auto-approved order as human-reviewed, and we will ask you not to either.
Upon request. Equities, options, and crypto ship today. Futures and FX are available when scoped into the engagement — raise them on the first call so adapter work lands in the right phase rather than as a late surprise.
Your customers, and by extension you. On the private deployment path strategies never leave your infrastructure. On the whitelabel path they live in our environment under partner-scoped access and are exportable in full at any time.
Whitelabel is a revenue share on the integrated offering rather than a licence fee, so our incentive is that your product works. Private deployment is licence plus support. Direct integration is usage based. Exact numbers come out of the boundary review, once the shape is known.
No. Existing agreements are non-exclusive. If exclusivity in a defined segment matters to you, that is a commercial conversation rather than a technical one.
Next step
Tell us where NexusTrade needs to run, what it needs to connect to, and who must approve live execution. We will walk the approval gate, the adapter layer, and the event ledger with your architect.
No sales sequence. If it is not a fit we will say so on the call.
NexusTrade provides technical controls that may support an institution's compliance program. It does not represent regulatory approval, compliance certification, legal advice, or investment advice. Institutions remain responsible for configuring and supervising their own policies, permissions, and execution workflows.