ES 5,621.00 +0.42% NQ 19,834.25 +0.61% NVDA 118.42 +2.14% AAPL 214.18 -0.33% AMD 107.55 +1.87% SPY 562.40 +0.29% QQQ 481.12 +0.55% GC 3,024.50 -0.18% CL 71.84 -0.92% TSLA 248.70 -1.44% META 592.30 +0.78% YM 42,180 +0.31% ES 5,621.00 +0.42% NQ 19,834.25 +0.61% NVDA 118.42 +2.14% AAPL 214.18 -0.33% AMD 107.55 +1.87% SPY 562.40 +0.29% QQQ 481.12 +0.55% GC 3,024.50 -0.18% CL 71.84 -0.92% TSLA 248.70 -1.44% META 592.30 +0.78% YM 42,180 +0.31%
iOS App · Personal use · App Store

Market monitoring
built around signal.

FM Alerts is a personal iOS app for real-time market monitoring — curated equities watchlist, institutional pressure scoring, live CME futures signals, and push alert delivery. Built for a single focused operator, not a trading desk.

FM Alerts ● Live
Equities Pressure · sorted by score
NVDA
range_expansion · trend_persistence
+2.14%
score 88
AMD
news_bullish · relative_volume_high
+1.87%
score 71
TSLA
news_bearish · range_expansion
−1.44%
score 58
Futures Live · U.S. Session
ES
Entry: active · bull
+0.42%
flow 28
Real-time monitoring Futures live Push delivery

What FM Alerts does

Four integrated layers working together — equities coverage, pressure scoring, futures live signals, and direct push delivery to your iPhone.

📊

Equities watchlist

Curated NASDAQ-100 + S&P 500 universe. Full and movers-only modes. Tickers shown with intraday move percentages. Alert rules trigger on configurable move thresholds with per-rule cooldowns.

Institutional pressure proxy

Per-symbol pressure score (0–100) derived from price move, volume, persistence, and Benzinga news sentiment. States: accumulation, distribution, caution, neutral. Honest proxy — not a dark-pool tracker.

📈

Futures live signals

Real-time CME Globex signals for ES, NQ, YM, RTY, CL, and GC via Databento GLBX.MDP3. Breakout entry, risk warning, and exit guard states with live order-flow metrics.

🔔

Push notifications

Alert delivery via AWS SNS → APNs to your iPhone. Sound routing maps direction to distinct bullish or bearish tones. Events logged with full status history — sent, retrying, dropped.

🛡

Rule management

Create, enable, disable, and delete rules per ticker. Bulk operations across the full watchlist. Cooldowns enforced at minimum 300s in production. Test rules protected from prod environment.

💚

Backend health

Live health dashboard showing backend status, data freshness, and delivery health. CloudWatch alarms monitor infrastructure availability continuously.

Data and infrastructure

Built on licensed prosumer-grade data sources. Every component is explicitly chosen for what it can honestly deliver — not overclaimed.

Market data

Alpaca Markets (iex feed) — real-time equities snapshots, intraday moves, volume. Shadow cache ensures resilience across restarts.
Databento GLBX.MDP3 — CME Globex live stream for futures. ohlcv-1s + trades + mbp-1 schemas. Session-aware signal suppression.
Benzinga API v2 — news title and teaser sentiment scoring per ticker. Cached 5 minutes. Feeds off-exchange context score.

Infrastructure

AWS EC2 — FastAPI backend in us-west-2. Background worker processes rules on a regular interval.
AWS RDS PostgreSQL — alert rules, events, and device registrations stored with reliable delivery semantics.
AWS SES + SNS → APNs — email delivery with automatic retry. Push notifications via SNS platform endpoints.
FastAPI PostgreSQL Alpaca Databento Benzinga AWS SES AWS SNS APNs CloudWatch React Native Expo EAS
Honest positioning. FM Alerts is an institutional pressure proxy — it uses publicly licensed data to approximate directional interest. It does not provide real-time dark-pool visibility, HFT-grade execution, or full market microstructure access. The value is in high-signal, focused monitoring within the prosumer data tier.

How alerts work

A worker process evaluates all active rules on every tick and delivers matched events through configured channels.

01

Rules evaluate

On a regular interval, the worker checks all enabled rules against current mover data. A rule fires when |move%| ≥ threshold and cooldown has elapsed.

02

Event created

An event is written to the database. Cooldown logic prevents duplicate events within the same window.

03

Delivered

The event is delivered via configured channels — log stream, email (AWS SES), or push notification (AWS SNS → APNs). Retried with exponential backoff on failure.