PRODUCTS AND CAPABILITIES

Independent modules. Coordinated operation.

ASTRIVERA organises its product capabilities into three areas: research, portfolios and risk; execution, accounts and accounting; and Strategy Assembly with the Quantitative Immune System. Each specialist component has its own interface, version and responsibility boundary. The Local Control Plane governs their connections, authority and operational state. Existing client strategies, data sources and trading infrastructure can remain in use within the supported scope.

ASTRIVERA is currently in research and internal validation. This page describes product direction, modular architecture and capabilities available for demonstration at the present stage. Supported markets, data, strategies, brokers, accounts and deployment environments depend on the current version and agreed scope.

01 | Research, portfolios and risk

Turn research judgment into a constrained portfolio target Data, algorithms, backtesting, portfolio construction and risk controls operate within one research structure. The data, code, parameters and market rules used by a strategy retain corresponding versions. Model output passes through portfolio construction and risk constraints before it becomes a target for execution.

Data and research

Connect authorised data while controlling availability times, security identity, versions and the compute environment. ASTRIVERA-developed algorithms can run as strategy components, while existing client strategies can connect through confirmed interfaces.

Backtesting and evaluation

Record strategy versions, parameters, trading calendars, costs, slippage and evaluation periods. Return, drawdown, turnover and cost are presented on consistent conventions and retained with the relevant operating configuration.

Portfolio construction

Translate model output into asset selection and portfolio weights. The portfolio component combines multiple signals, current positions and funding conditions into a defined target structure.

Portfolio and risk controls

Apply cash buffers, position limits, concentration, risk budgets and other constraints. Risk results adjust the portfolio target directly and accompany it into execution.

Primary records

Data and configuration snapshots, research runs, backtest results, portfolio targets, risk results and research reports. Versions of data, strategies and parameters can be compared independently or reviewed again from their original configuration.

02 | Execution, accounts and accounting

Take portfolio targets to market and bring trading facts back into the system The execution component receives a portfolio target and prepares an order plan from current positions, available cash, market rules and account authority. Once orders reach a broker, the system continues to track market responses, fills, positions, cash, fees and profit and loss.

Execution planning

Prepare orders from trading units, price conditions, available funds, account state and the execution window. The original portfolio target is preserved and execution adjustments are recorded separately.

Brokers and accounts

Manage account bindings, order submission, fill reports, open orders and connection state. When a broker or account changes, its connection is configured independently while strategy logic remains unchanged.

Order lifecycle

Record the path from planning and submission through acceptance, rejection, partial fill, cancellation and completion. If a connection is interrupted or market state remains unresolved, affected orders retain a separate state pending confirmation from account facts.

Reconciliation and attribution

Reconcile orders, fills, positions, cash and profit and loss against broker and account records. Price, fees, foreign exchange, corporate actions, execution and accounting differences are attributed separately.

Operational reporting

Organise trading results, portfolio changes, costs, risk and operating deviations. Reports support daily review, internal oversight, risk communication and audit records.

03 | Strategy Assembly and the Quantitative Immune System

Govern the connections and state of specialist components Strategy Assembly connects strategies, data, market rules, risk policies, execution channels and accounts. The Quantitative Immune System checks state and results across components, recording evidence gaps, operational deviations and the basis for recovery.

Component registration

Record each capability's responsibility, interface, version, dependencies, authority and applicable scope. A component that is not yet integrated or lies outside current support remains disabled.

Operational assembly

Select the strategy, data, rules, risk, execution and account components required for the current run. The assembly becomes a separate configuration that preserves connections, versions and responsibility boundaries.

Compatibility verification

Check data semantics, market rules, execution capabilities, account authority and environment versions. A change to a critical component or connection requires the current operating arrangement to be verified again.

Structured evidence

Research, targets, orders, fills, positions, cash and profit and loss retain continuous relationships. Operating results can be traced through component connections to the relevant data, configuration, strategy and rules.

Operational assurance

The Quantitative Immune System reads operating evidence to form a diagnosis and records deviations, affected scope and recovery basis. Production permission is governed by an Independent Production Gate.

Modularity preserves room for long-term evolution

Specialist components can be connected, upgraded and replaced independently. New markets, data sources, strategies and brokers enter through the corresponding component. Unrelated components retain their existing versions and operating relationships. Existing client capabilities can remain in use, while additional research, portfolio, risk, execution, accounting or immune capabilities are assembled where required. Modules remain independent. The system remains coherent.

Local deployment boundary

ASTRIVERA is deployed on devices and storage controlled by the client. Strategy code, model parameters, data, account credentials, operating records and reports remain in the local environment. Research, diagnosis, verification, production writes and external export require separate authority. Standard components connect within the current support scope. Technical and delivery boundaries for additional adapters, markets, brokers and custom components are confirmed separately.

PRODUCT DEMONSTRATION

See how ASTRIVERA can connect to an existing operating environment and which components and assembly methods the current version can demonstrate.

Book a Product Demonstration