Architecture, integration and security

Short answer

Vektor runs on AWS. The current deployment is in Singapore (ap-southeast-1).

The region is a configuration choice, not a structural dependency, and data does not leave the configured region as part of normal platform operation.

Markets, currencies and lot sizes are configuration, not development.

Access is role-based, with five roles and permissions fixed by database migration, and every user action is logged.

Order routing is validated against an Interactive Brokers paper-trading gateway. Live execution, a Bloomberg B-PIPE connector, an OpenWealth-standard order and trade API and external PMS integration are not yet in place.

What we can show

• Eight exchanges configured. New markets take minutes, not projects.
• Eight exchanges are configured and active today. Adding another listed-equity exchange follows the same configuration workflow and does not require platform redevelopment.
• SGX, LSE and NASDAQ were run in one session on 21 May 2026. The platform applies the correct lot-size rule per exchange with no developer involvement and no deployment.
• Data residency: Singapore (current), UK (eu-west-2), Switzerland (eu-central-2), Hong Kong (ap-east-1), UAE (me-central-1). Regional deployment is contractually specifiable at subscription, agreed at signing and written into the Data Processing Agreement.
• Alongside your stack: Bloomberg stays for price monitoring, news and corporate-action alerts, client reporting, fixed income and compliance screening. Vektor replaces universe screening, portfolio optimisation, indicator selection and allocation calculation.
• Working today: deterministic max-Sharpe optimisation, XGBoost signal validation, order queuing with Slack notifications, multi-currency FX infrastructure, role-based access control.

What this means

Integration is where the distance between built and designed is widest. Market, currency and region configuration work today. The connectors that would tie Vektor to your data, execution and portfolio-system estate are specified or scheduled, not live.

Vektor does not replace Bloomberg. It replaces the Excel-based or Bloomberg-screen-based construction workflow that sits alongside it.

What remains unproven

• Live execution: IBKR connectivity is validated on paper trading. Live order submission begins with the first Proof Partner’s first production period.
• Bloomberg-quality data needs the B-PIPE connector, which is the first build item, developed with the first Proof Partners.
• OpenWealth: the architecture is specified, and the connector build is a scheduled near-term item.
• External PMS integration via API is on the roadmap. Real-time position updates after fills, live P&L dashboards and a client reporting portal are listed as coming next.
• Security, resilience and dependencies: no open document describes authentication, encryption, network protection, backup or third-party dependencies. The Technical Architecture paper (WP-07) covers security, data residency by region, scalability, integration options and a table of capabilities designed but not yet live. It requires one-time registration, and we are not summarising it here.