Vektor · One Platform · Three Delivery Models
One platform.
Three ways to work with it.
The methodology, signal generation, ML validation, portfolio construction logic, and audit trail are identical in every deployment. What differs is the commercial relationship through which it reaches you — and the operational context in which it runs.
Three delivery models were designed into the platform architecture from the start — not as a commercial afterthought, but as a recognition that the same product serves three genuinely different relationships in the wealth management ecosystem. The data governance framework, deployment architecture, and commercial terms for each model were developed alongside the platform — not applied retrospectively.
- HowDirect subscription — you operate the platform
- DeploymentStandard cloud, Data Processing Agreement
- RelationshipDirect with InvestPuppy
- HowDirect subscription at institutional scale
- DeploymentStandard cloud or hybrid identity vault
- RelationshipNamed account management, institutional SLA
We are actively building this path and looking for the right institutional partner to shape it with us.
- HowPlatform licence via OpenWealth API
- DeploymentYour infrastructure — EAM clients are your clients
- RelationshipInvestPuppy ↔ your institution only
A specific question? For example:
"How does each delivery model differ in terms of what data InvestPuppy holds about my clients?"
Direct factual response. No data-gathering. No bullshit.
Your client data across the three models
The most substantive functional difference between the three delivery models is what happens to your clients' identifying information. This is the data that privacy law protects, banking secrecy obligations govern, and institutional procurement teams ask about first.
| Model | What InvestPuppy holds | In practice | When this drives model selection |
|---|---|---|---|
| Vektor : Boutique | Client names and identifying information, held in InvestPuppy's cloud under a Data Processing Agreement. | InvestPuppy is a data processor. A cloud breach constitutes a personal data breach. | Appropriate where standard cloud data processing is acceptable under your regulatory framework. |
| Vektor : House (standard) | Same as Boutique. Client names and identifying information in InvestPuppy's cloud under a DPA with stronger institutional terms and audit rights. | Same breach and notification position as Boutique. Institutional DPA. | Appropriate for institutional clients whose data governance requirements are satisfied by a robust DPA and regional cloud deployment. |
| Vektor : House (hybrid) | Pseudonymised portfolio data only. Client names and identifying information never enter InvestPuppy's systems at any point. | A breach of InvestPuppy's cloud does not constitute a personal data breach. InvestPuppy can state: "We have never seen your clients' names." | Required when client identity must not leave your infrastructure — constitutional, regulatory, or professional requirement. |
| Vektor : Wrapped | InvestPuppy holds no EAM client data whatsoever. The bank manages all client identity. | InvestPuppy is not a data processor for EAM end clients. No DPA between InvestPuppy and the EAM is required. | Applies by nature of the licensing model. EAMs receive the strongest structural data protection by default. |
The hybrid deployment is not a separate tier or premium variant. It is a data governance configuration available to any Vektor : House client whose requirements make it appropriate. Contact InvestPuppy during scoping to determine the right configuration.
Regulatory frameworks: MAS (Singapore — PDPA, MAS TRM Guidelines) · FCA/PRA (UK) · FINMA (Switzerland — nFADP/DSG) · SFC/HKMA (Hong Kong). Regional cloud deployment (AWS eu-central-1 for Switzerland, eu-west-2 for UK, ap-southeast-1 for Singapore) is configurable for data residency requirements. Contact InvestPuppy to confirm the right configuration for your jurisdiction.
A specific question? For example:
"I operate under Swiss nDSG — which deployment configuration applies to me?"
Direct factual response. No data-gathering. No bullshit.
Which path is right for your operation?
The right delivery model is determined by the nature of your commercial relationship, your intended use of the platform, and your data governance requirements — not by your size or AUM alone.
| Question | Direction |
|---|---|
| Does your operation require the platform to run on your own infrastructure rather than a cloud-hosted environment? | Vektor : House — hybrid deployment. Contact InvestPuppy. |
| Are you a practitioner-scale operation: one to a small team, boutique firm, or independent practice? | Vektor : Boutique → Proof Partners |
| Are you an institutional-scale operation: investment team, formal governance, institutional SLA and account management requirements? | Vektor : House → Alloy Partners |
| Does your custodian bank already offer Vektor through its EAM services platform? | Vektor : Wrapped via your bank. Or subscribe directly as Boutique or House. Contact InvestPuppy to confirm. |
| Are you a custodian bank or wealth platform evaluating Vektor as a licensed capability for your EAM clients? | Vektor : Wrapped — the licensing channel. contact@investpuppy.com → |
| Does your institution operate both an internal DPM function and an EAM services platform for external clients? | Both Vektor : House and Vektor : Wrapped — one master agreement, two schedules. Contact InvestPuppy. |
Not sure which path applies? Contact us with a brief description of your operation and we will tell you honestly. The full reference document — One Platform, Three Delivery Models → — is also available in the document suite.
One product across all three models
Regardless of delivery model or deployment configuration, every Vektor client accesses the same platform.
Methodology
The same quantitative framework documented across the research series (WP-01 through WP-11).
Portfolio configurations
10,000 portfolio configurations per strategy — identical across all deployments.
Capital allocation
98.94% capital allocation efficiency (SGX reference mandate, 100-share board lots) — 99.97% demonstrated on a NASDAQ mandate — single-share lot markets consistently exceed 99.94%. WP-03 ↗ · See platform output ↗. The same allocation engine across all delivery models.
ML validation
The same XGBoost signal validation layer. No position proceeds without portfolio manager approval.
Audit trail
The same systematic signal-to-execution workflow and full compliance documentation.
Institutional connectivity
The order and trade API is pre-configured to OpenWealth standards — the connectivity framework increasingly adopted by Tier 1 custodian banks across Europe, the Middle East, and Asia. Any OpenWealth-compatible institution connects without bespoke integration work.
Multi-currency
Eight exchanges configured and active: SGX, LSE, NYSE, NASDAQ, HKEX, SIX, ASX, TSE — run simultaneously across SGX, LSE, and NASDAQ on 21 May 2026. Any listed equity market is a configuration, not a development task. Any currency. Any number of concurrent mandates. See multi-market output ↗
The delivery model determines the commercial relationship, the deployment architecture, and the support model. It does not determine the quality, capability, or scope of the platform.
