How It Works

Direct Provider Hooks

We maintain active WebSocket connections to primary sports data providers (Opta, Sportradar, and official league APIs). When an event occurs—a goal, a yellow card, a pit stop—we receive the raw JSON payload within milliseconds.

// Example Ingest Payload (Simulated)
{
  "event_id": "evt_847291",
  "type": "goal",
  "match_id": "m_992",
  "team": "Arsenal",
  "player_id": "p_7",
  "timestamp_utc": "2024-03-09T15:22:04Z"
}

Unlike major networks that route this through editorial desks to write a "Here's what this goal means for the title race" article, we skip the desk entirely.

The Rules Engine

This is where your dashboard configuration comes in. We run the raw firehose of sports data through a deterministic rules engine based entirely on your explicit preferences.

• If you follow the NBA, but explicitly blocked "Trade Rumours", the engine drops the payload.
• If you requested "F1 Timing Only", we drop driver quotes and push only sector time arrays.

There is no machine learning model trying to guess what you'll click on. It is a strict boolean filter.

WebSocket Push

Once a payload survives your filters, it is pushed directly to your client via a persistent WebSocket connection. Your dashboard updates without a page refresh, often before the broadcast feed updates on your television.