Typed strategy boundary
External portfolio or strategy systems emit TradeCycleIntent and idempotent TradeCycleCommand messages. Venue order IDs and exchange-specific lifecycle details stay inside the execution runtime.
Pre-incorporation founder project
Strategy-native execution engine for API trading.
Alpha-Astra is an account-owner-operated execution engine for API trading. It takes bounded trade-cycle intents from strategy systems and nets per-cycle exposure into a single, safety-gated venue residual — with a fully replayable operating trail.
For technical and exploratory conversations only — not an offer of software, signals, investment advice, or any financial service.
Boundary
TradeCycleIntent
typed Portfolio Manager input
Allocator
NetPlan
entries / reduce-only / stops
Execution
Multi-broker
including MiCAR-compatible brokers
Truth
WebSocket + REST
deduped reconciliation
01
External Portfolio Manager systems emit bounded trade-cycle intent
No exchange order IDs cross the strategy boundary.
admitted
02
Allocator keeps virtual cycle ownership separate
Same-symbol long/short cycles can net before venue exposure.
netted
03
Executor sends only the controlled residual
Freshness, protection, and mode gates run before orders.
gated
04
Snapshots and journals preserve operating history
Operator state, event tails, checkpoints, and replay inputs.
recorded
Virtual cycle exposure
venue residual
BTC trend cycle
+0.42
BTC mean reversion
-0.25
Broker-facing net
+0.17
Strategy formulas stay outside.
The runtime receives bounded intent and commands, not alpha logic.
The venue sees residual exposure.
Internal cycle ownership is reconciled against broker net state.
Operators get a replayable trail.
Snapshots, event tails, journals, checkpoints, and incident replay.
Mechanism
Not an alpha story. Not a generic OMS.
The internal architecture is built around a narrow Portfolio Manager boundary and a strategy-native OMS core. Portfolio systems ask for bounded trade-cycle behavior; the runtime handles virtual ownership, netting, venue-order construction, reconciliation, and safety containment.
How netting works
Two virtual cycles net into one venue residual
Virtual trade-cycle ledger
Each cycle keeps requested quantity, effective target, virtual position, real fills, fees, exit levels, closure state, and recent event history without pretending the exchange has per-cycle accounting.
Netting allocator
Same-symbol cycles are combined, internally matched, handed off, or flattened before the venue sees work. Instead of forcing each strategy to build venue orders, the allocator emits entry orders, reduce-only orders, and protective reduce-only stop legs as a NetPlan.
Stable snapshot surface
OmsSnapshot and TradeCycleView expose broker positions, account summary, grouped errors, health alerts, broker-owner targets, and event tails to the Portfolio Manager path and operator tooling.
Runtime
A live loop between decisions and exchange feedback.
The trading orchestration loop calls the Portfolio Manager on a roughly one-minute cadence. Beneath it, the OMS runtime runs continuously — ingestion, allocation, execution, supervision, snapshot publication, journaling, checkpoints, and shutdown — on a sub-second heartbeat, folding in exchange events in real time.
The orchestration loop
Minute decisions, sub-second execution
Market and OMS state
Minute-bar market data and the latest OmsSnapshot are sent to the Portfolio Manager service so decisions see current execution state, not just price history.
Intent admission
The Portfolio Manager response stays narrow: trade-cycle intents, cycle commands, and diagnostics. The scheduler submits them only when freshness and timing windows still qualify.
OMS heartbeat
Running continuously beneath the decision loop, the supervisor drains queued work, calls the executor heartbeat, applies reports to allocator state, republishes plans, and emits a fresh snapshot.
Exchange feedback
User-stream events are primary. Async REST snapshots backstop positions, open orders, config, entry gates, reduce-only reconcile, and fill recovery.
Operator read model
Minute snapshots, grouped errors, health alerts, positions, account summaries, and recent event tails become the operational view without replaying every journal by default.
Safety posture
Failure handling is part of the execution model.
The system is designed for deterministic behavior, reviewability, and safe failure containment. Some states block entries. Some raise alerts. Some intentionally cancel, flatten, and stop instead of continuing quietly.
Before fresh entries
- Flat-start hygiene checks one-way mode, REST availability, no stray open orders, and flat positions before trading begins.
- Entry gates require fresh position state, fresh REST coverage, and sufficient protective stop visibility.
- Flat-first flip handling suppresses opposite-side entries until existing real broker exposure is flattened and confirmed.
When venue reality drifts
- WebSocket, REST API, and synthetic events are mapped into a deduped reducer stream so stale events cannot revive terminal legs.
- Late fills after cycle closure move into an unattributed bucket rather than mutating closed cycle state.
- Unexpected broker exposure with no active cycle triggers orphan-cleanup reduce-only work.
When containment matters
- Breakers escalate persistent abnormal states such as WebSocket silence, blind mode, stuck flattening, and unexpected external positions.
- Hard paths can cancel exposed order state, initiate emergency exit handling, and stop the engine when invariants are no longer trustworthy.
- An out-of-process watchdog/deadhand path can escalate repeated silence or errors into emergency exit orchestration, with staged, venue-aware liquidation as the intended containment model.
Technical evidence
Private execution-control learnings, not return marketing.
Internal documentation tracks system behavior, reconciliation quality, risk events, incident recovery, and replayability. Metrics describe engineering exposure and operating history, not public performance claims.
500+
internal execution cycles documented
2
parallel technical test setups
10+
internal strategy-intent producers deployed in parallel
Replay
allocator and executor behavior reconstructable from journals
Boundaries
Precise about what exists and what is not offered.
The engineering story is intentionally infrastructure-first. Alpha-Astra is not positioned as a signal provider, trading adviser, broker, custodian, or asset manager.
What it is
- Strategy-native OMS with integrated netting and execution-engine behavior.
- Typed portfolio-manager boundary for bounded trade-cycle intents and commands.
- Virtual trade-cycle ledger and netting allocator for one-way exchange execution.
- Multi-broker exchange executor (including MiCAR-compatible brokers) with WebSocket/REST API reconciliation, fill deduplication, safety gates, and breaker paths.
- Journaling, checkpoints, replay, and operator read models for incident review.
What it is not
- No strategies, signals, recommendations, return promises, or financial analysis offered through this website.
- No custody, brokerage, portfolio management, asset management, investment advice, or order-transmission service offered through this website.
- No public software sale, subscription, investment opportunity, or regulated financial service offered here.
- No claim of hot-failover, multi-writer, or multi-OMS concurrency as a current design target.
- No guarantee that gates, stops, reconciliation, or watchdog paths prevent losses or venue failures.
Discussion fit
Useful conversations are technical and boundary-aware.
The current page exists as a reference point for exploratory conversations during the pre-incorporation phase.
Experienced API operators
Self-directed users or teams operating their own systems, strategies, accounts, and risk decisions.
Exchange and broker API teams
Discussions around integration boundaries, venue constraints, reconciliation behavior, and operational controls.
Infrastructure partners
Technical validation around execution tooling without becoming a signal provider, adviser, broker, or asset manager.
Contact
Start with the execution-control problem.
Reaching out starts an exploratory founder-project conversation only — nothing is sold or offered through this website.