Monitoring live deployments and holdings

When to use this guide

Use this guide once you have:

• At least one strategy with one or more revisions.
• One or more confirmed trading accounts assigned to strategies.

By the end, you will:

• Understand how to read deployment status.
• Know where to see which accounts each strategy uses.
• Be able to interpret holdings and positions across your portfolio.

Key concepts

• A live deployment has lifecycle state such as drafting, provisioning, running, stopping, stopped, or failed.
• Trading accounts are the concrete venue accounts your live deployments trade through.
• Account position state includes balances, positions, margin context, and venue health where available.
• Holdings aggregate the latest available account state into a portfolio‑style table.

View your strategies overview

Navigate to the Strategies section. For each strategy you will typically see:

• Name and description.
• Current deployment status:
  • drafting – the deployment parameters are being specified by the user.
  • provisioning – Structure is preparing the selected revision and runtime path.
  • running – the deployment is active.
  • stopping – Structure is shutting the deployment down.
  • stopped – the deployment is no longer running.
  • failed – the deployment could not start or continue.
• Latest revision and the revision selected for any current deployment.
• Linked trading accounts (by display name and venue).

Use this list to answer:

• “Which deployments are currently live?”
• “Which revision powers each deployment?”
• “Which accounts does each strategy control?”

Drill into a single strategy

Click into a strategy to see its detail page, which may include:

• High‑level metadata:
  • Name, description, tags.
  • Owner (your user account).
• Revisions:
  • A table of all revisions with:
    • Version name.
    • Revision version, creation time, and description.
• Deployments:
  • Current and historical deployments with lifecycle state, selected revision, connected account, and venue.
    • Creation time and description.
• Accounts:
  • Which trading accounts are assigned.
  • Each account’s venue, type, and confirmation status.
• Recent activity (where available):
  • Recent orders or trades.
  • Status transitions and errors.

From here you can:

• Confirm that the expected accounts are attached.
• Verify that the deployment uses the intended revision.
• Decide whether to stop the deployment or start a new deployment from a different revision.

Understand holdings and positions

Structure surfaces position and balance state from each confirmed trading account where the venue provides it. The Holdings view presents the latest available account state in trader‑friendly form.

On the holdings page you’ll typically see, for each line:

• Venue – for example, Hyperliquid during launch.
• Venue account – which trading account this position or balance belongs to.
• Asset or instrument:
  • For spot, a token such as SOL or USDC.
  • For derivatives, an instrument such as SOL‑PERP.
• Quantity – the size of the holding, normalized using the correct decimals.
• Optional fields such as:
  • Mark‑to‑market value.
  • Unrealized P&L.
  • Margin metrics (maintenance, initial).

Conceptually, holdings are your portfolio view:

• “How much of each asset do I own, and where?”
• “Which strategies and accounts contribute to this exposure?”

Filter and slice your portfolio

To understand risk and exposure, you will often want to slice holdings by:

• Strategy – show only holdings associated with a given strategy’s accounts.
• Venue – see all accounts and positions on a specific exchange or chain.
• Trading account – inspect an individual venue account in detail.

Typical workflows:

• Filter by strategy to see the net effect of that strategy across its accounts.
• Filter by venue to understand how you are allocated across exchanges or protocols.
• Drill down to a single trading account when investigating specific trades or issues.

Interpret changes over time

While holdings show the latest account state available to Structure, you can pair them with:

• Strategy‑level activity (order activity and fills where available).
• Time‑series views of P&L and exposure (where available).

This helps you answer questions like:

• “Why did my net SOL exposure change in the last hour?”
• “Which strategy is responsible for this new futures position?”
• “Is a particular venue or account driving most of my risk?”

For deeper investigation:

• Use strategy detail pages to see which revisions powered live deployments at a given time.
• Cross-reference with backtest job results to understand whether live behavior matches expectations.

Respond to alerts and health signals

If Structure or your venues surface health warnings (for example, low margin or high leverage), you can:

• Identify which strategy and trading account are affected.
• Consider:
  • Stopping or reducing exposure for the relevant strategy.
  • Manually adjusting positions at the venue.
  • Adding collateral or reducing leverage.

If a deployment health warning appears, investigate immediately:

• Check holdings and positions for the affected accounts.
• Review recent fills, order activity, and strategy behavior.
• Use deployment controls to stop the deployment when appropriate.
• Manage open positions at the venue if the situation requires direct venue action.

Next steps

Running backtest jobs

Simulate changes before live operation.

Connecting trading accounts

Adjust how strategies are wired to accounts.