Quantisentry
MT5 account & EA monitoring. See the fleet, don’t touch the trade.
Monitor every MT5 account and expert advisor you run — on any broker, VPS or prop firm — from one read-only dashboard. Telemetry from your MT5 experts lands in Sentinel Cloud, gets validated against a strict contract, and is served back read-only. Every route that could change trading state answers 403.
The system, in numbers
Nothing here is a placeholder.
Each figure below is a constant in the running product, not a marketing rounding.
29
telemetry fields accepted per payload
31 stored, incl. server-side identityKey
48
mutating routes blocked in observation mode
overrides, apply, config, registry repair
5 min
freshness window before an expert reads stale
measured server-side from last ingest
0
routes that can place, size, or close a trade
observation-only enforced at startup
Fail-closed
It doesn’t decline to trade. It can’t.
Observation is not a setting an operator can flip in production. If the platform is configured with observation mode off, startup validation throws and the process does not come up. There is no running state in which Quantisentry holds trading authority.
- ObservationOnly = true
- startup validation
- no apply path
{
"ok": false,
"code": "COMMERCIAL_OBSERVATION_ONLY",
"mode": "observation",
"applied": false,
"message": "Sentinel Cloud V1 does not execute
operational or trading actions."
}
What you actually get
Three things, done properly.
-
A strict wire contract
Six hard-required fields, five permitted strategy families, a bounded risk multiplier and lot rounding to four decimals. Malformed telemetry is rejected at the door with a reason, not silently absorbed. See the contract →
-
Obedience evidence
The lot audit compares the size Sentinel expected against the size your broker actually filled, within a 5% tolerance. You get OK, MISMATCH or MISSING_DATA — proof, not assumption.
-
Advisory intelligence, boxed in
Health scoring is a transparent 100-point deduction model where every penalty carries a written reason. Advisory output is contractually stripped of anything actionable. How that works →
What we don’t claim. There is no rate limiting in the product today, no telemetry history — the store keeps the latest value per expert and overwrites the rest — and no trained model shipped inside Quantisentry.
On the roadmap, not in the box. Payload signing exists as a schema (payloadHash, signature) but nothing signs or verifies it yet. Today’s transport is TLS with header-key authentication, and we describe it that way.
Why say so. Operators running live capital check claims. A site that survives the check is worth more than one that doesn’t.
FAQ
MT5 fleet monitoring, answered plainly.
Can Quantisentry place or modify trades?
No. Commercial routes that could mutate trading state return HTTP 403. The product is observation-only by construction.
What makes telemetry trustworthy?
A strict contract with required fields, freshness windows, and lot-audit tolerance checks. Invalid payloads are rejected with explicit reasons.
Is this suitable for prop firm operations?
Yes for monitoring and compliance evidence. It helps teams prove execution discipline; it does not replace broker or prop firm rule enforcement.
From the blog
Guides for running MT5 fleets in production.
Operator-level writing on telemetry contracts, freshness SLAs, drawdown alerts and prop firm evidence.
FTMO Daily Drawdown: How to Monitor It Before the Firm Does
How the daily loss limit is calculated, why EAs breach it, and the alert ladder that leaves time to act.
My MT5 EA Stopped Trading: 8 Causes and a Monitoring Checklist
Eight reasons an MT5 expert advisor silently stops, a two-minute triage, and the heartbeat that tells you next time.
10 Prop Firm Rules an EA Breaks by Accident (and How to Audit Them)
Ten rules automated strategies break by accident, what each looks like in telemetry, and a nine-step self-audit.
MT5 Fleet Monitoring: A Practical Guide for Live Operations
Learn how to monitor multiple MT5 accounts in production using telemetry contracts, freshness SLAs, lot audits, and observation-only architecture for safer live operations.
Next step
Ready when your fleet is.
Read the telemetry contract, then request access. There is no self-serve deploy from this site.