All Systems Operational
Our core services are running normally. AI signals, .set updates, analytics, and deliveries are ready for you.
This page showcases our architecture and operational targets. Live status indicators are coming soon.
Components Overview
We run a multi-service architecture in the cloud. Each component has a clear responsibility and well-defined operational targets.
Typical target: p95 signal latency ≤ 300 ms (illustrative)
Typical target: p95 API latency ≤ 250 ms (illustrative)
Typical target: ingestion freshness ≤ 60 s (illustrative)
Typical target: analytics lag ≤ 5 min (illustrative)
Typical target: connector health ≥ 99% (illustrative)
Typical target: new/updated .set files every ≤ 30 min (illustrative)
Typical target: global delivery success ≥ 99.9% (illustrative)
Typical target: uptime ≥ 99.9% monthly (illustrative)
Typical target: near real-time alerting (illustrative)
What We Monitor (Targets)
We define internal service level objectives (SLOs) to keep your trading experience smooth. Below are our core targets (illustrative).
- •Signal latency (AI): p95 ≤ 300 ms
- •API latency: p95 ≤ 250 ms; low error rates
- •Trade ingestion freshness: ≤ 60 s
- •Analytics compute lag: ≤ 5 min
- •.set publication cadence: every ≤ 30 min
- •Public web uptime: ≥ 99.9% monthly
Reliability & Operations
Roadmap to Live Status
What's next:
- Live component indicators with refresh
- Incident feed and maintenance schedule
- 90-day uptime history and SLO adherence
[PLACEHOLDER: Live status widgets — coming soon]
Contact & Subscribe
Have a question or noticed something odd? We're quick to respond.