Real-time data synthesis for automated, risk-aware investment decisions

Maple Vaultis processes continuous market data streams through a predictive model, converts the output into risk-adjusted signals, and publishes the resulting logs for independent review. No discretionary trading calls, no hidden ledger.

Data refresh
15 sec
Markets monitored
20+
Log visibility
Public
Oversight model
Rules-bound
Community-verified results

A performance log you can read, not just a promise you have to trust

Every signal the model issues is timestamped before its outcome is known. Members can cross-reference entries against public market data, which is the basis of the verification badge described below.

09:14 UTC — FTSE basket signal logged, confidence 61% 09:02 UTC — EUR/GBP risk filter triggered, signal withheld 08:47 UTC — Gilts 10yr outcome verified, variance −0.3% 08:31 UTC — S&P sector rotation signal logged, confidence 58% 09:14 UTC — FTSE basket signal logged, confidence 61% 09:02 UTC — EUR/GBP risk filter triggered, signal withheld 08:47 UTC — Gilts 10yr outcome verified, variance −0.3% 08:31 UTC — S&P sector rotation signal logged, confidence 58%
Illustrative extract from the performance log
Timestamp (UTC) Asset class Signal type Model confidence Verified outcome
2024-11-03 09:14 UK Equity basket Long bias 61% Verified
2024-11-03 08:47 UK Gilts, 10yr Hold / no action 54% Verified
2024-11-02 16:02 EUR/GBP Signal withheld — risk filter — Filtered
2024-11-02 11:19 US Sector rotation Reduced exposure 58% Verified

Illustrative log extract for demonstration purposes. The full, continuously updated ledger is available within the terminal after registration.

Verified
Badge

How the verification badge works

A signal is hashed and timestamped at the moment it is generated, before the outcome is known. Once the relevant market data settles, the outcome is appended to the same record rather than overwritten. Members can inspect the sequence and confirm that no entry was edited or removed retroactively. This does not guarantee future accuracy — it simply means past claims can be checked against a fixed record rather than taken on trust.

Methodology

How raw market data becomes a bounded, risk-checked signal

The platform does not output buy or sell instructions directly from a black box. Each signal passes through four distinct, auditable stages before it reaches a member's terminal.

1

Data ingestion

Price feeds, order book depth and macro releases are pulled continuously from licensed data providers and normalised into a common schema.

2

Predictive modelling

A statistical model trained on historical sequences estimates a probability distribution of near-term outcomes, not a single fixed prediction.

3

Risk-adjusted filtering

Signals below a confidence threshold, or those that would breach a position's exposure limit, are withheld automatically rather than passed through.

4

Logged output

What remains is written to the public log with a plain-language rationale, so the reasoning behind the signal is visible, not just the outcome.

In practical terms, this means the model's role is bounded: it proposes, the risk filter constrains, and the log records. No stage operates on full discretion, and every rejected signal is as traceable as an accepted one. Confidence figures shown in the terminal describe statistical likelihood based on historical patterns — they are not a forecast of certainty, and past log entries are not an assurance of future results.

About the platform

Built for people managing portfolios from outside a fixed office

Maple Vaultis was shaped around a specific constraint: users who move between time zones and cannot monitor markets on a fixed schedule need a system that behaves predictably in their absence. That shaped most of the design decisions below, from how automation handles connectivity gaps to how uptime is reported.

The platform does not replace an investor's own judgement. It narrows a large data set down to a small number of risk-checked, logged signals, so that review and decision-making take minutes rather than hours.

Maple Vaultis team reviewing predictive model output and risk parameters on a workstation
For nomadic and distributed investors

Automation that accounts for intermittent connectivity and shifting time zones

Signal generation, risk filtering and logging run server-side on a fixed schedule independent of a member's location. The sections below describe how each benefit is implemented, not just what it is called.

Time-zone independent execution

The model runs on UTC-based schedules rather than a local market open, so review windows stay consistent regardless of where a member is based.

Scheduling basisUTC, 24h
Member action requiredReview only
Manual override window15 min

Low-bandwidth terminal access

The log and terminal are designed to load on constrained connections, with data tables rendering before any secondary assets.

Core view payload< 200 KB
Offline log cacheLast 50 entries
Mobile data modeSupported

Automated risk caps

Exposure limits are set once per account and enforced at the filtering stage, so a missed review window cannot silently increase risk.

Per-position capSet by member
Breach responseSignal withheld
Adjustable frequencyAnytime

In practice, this means a member travelling between time zones does not need to adjust alerts or stay awake for a particular market open. The automation logic is fixed in advance, and any change to risk parameters takes effect from the member's next login rather than requiring continuous supervision.

24/7 Monitoring window
15 sec Signal refresh interval
Public Incident disclosure
Technical specification

Integration, model parameters, security and latency, stated plainly

The detail below is provided so technically-minded members can assess the system on its mechanics rather than its marketing.

API integration

  • ProtocolREST & WebSocket
  • AuthenticationPer-account API key
  • Rate limit120 req/min
  • Log export formatCSV / JSON

Predictive model parameters

  • Lookback window90–180 days
  • Retraining cadenceWeekly
  • Feature categoriesPrice, volatility, macro
  • Confidence threshold≥ 55%

Security protocols

  • Transit encryptionTLS 1.3
  • Storage encryptionAES-256
  • Account access2-factor authentication
  • Session handlingShort-lived tokens

Latency metrics

  • Data ingestion lag< 2 sec
  • Signal generation time< 5 sec
  • Log publication delay< 1 sec
  • Terminal sync interval15 sec
Questions we expect

Addressing risk, autonomy and the limits of the model directly

These are the questions most often raised during onboarding calls. They are answered here in the same terms we would use on a call.

Can the model lose money?

Yes. Confidence scores describe a statistical likelihood based on historical patterns, not a guarantee. Markets can behave outside the range the model was trained on, and the risk filter reduces exposure rather than eliminating it.

Does the AI make the final decision on its own?

No. The model proposes a signal; the risk filter can withhold it; the member decides whether to act on what remains visible in the terminal. There is no stage where funds move without an account-level permission already set by the member.

What happens if a signal turns out wrong?

The outcome is appended to the same log entry as the original signal, including entries where the model was incorrect. This is deliberate: a log that only shows favourable outcomes would not be verifiable.

Where does the market data come from?

From licensed third-party data providers covering equities, fixed income and major currency pairs. The platform does not generate its own price data or rely on unverified sources.

Can I review the model's reasoning in detail?

Each log entry includes a short, plain-language rationale. For a fuller technical description of the modelling approach, the methodology documentation is available on request.

Request the methodology documentation →
Next step

Review the live log before deciding whether this fits your approach

Access is granted manually, following a short verification step, rather than opened to anyone who signs up. This keeps the member base, and the log itself, aligned with its stated purpose.

Access Terminal

No credit card is required to request access. Registration includes a brief identity verification call before terminal credentials are issued.