Live, Day 57+ PLATFORM

Real-time OSINT tracker for the 2026 Iran-Israel-US conflict.

iranwarlive.com is the live intelligence platform for Operation Epic Fury. Multi-source ingestion, five-parameter deduplication, two-hour cron pipeline, and a structured-content layer designed for both human readers and answer engines. Live since the conflict's opening hours.

Live URL iranwarlive.com
Build time 200 hours
First deploy 8 hours after conflict start
Status Operating, Day 57+
Update cadence Every 2 hours
WHAT WE BUILT

An autonomous OSINT pipeline running on Cloudflare's edge.

iranwarlive ingests RSS feeds from Reuters, AP, CENTCOM, IDF Press Office, and Al Jazeera every two hours. Each event passes through a five-parameter deduplication pipeline that compares time published, source, content fingerprint, accuracy classification, and a KV-cached signature against the historical event ledger. Only verified, non-duplicate kinetic events are committed to the live map and the daily recap pages. The result is a politically agnostic, mathematically deduplicated chronological intelligence record.

The platform serves four distinct user surfaces: a tactical map at the root, a casualties dashboard with faction-separated tracking, a 57-day chronological recap archive optimized for answer engines, and a machine-readable JSON feed for AI agents and quantitative consumers. Schema markup, llms.txt routing instructions, and structured H2 sections on every page make iranwarlive directly citable by ChatGPT, Claude, Gemini, and Perplexity.

TECH STACK
Cloudflare WorkersCloudflare KVGoogle Sheets backendGemini 2.5 FlashLeaflet.jsPapaParseTelegram Bot APICloudflare Pages
OPERATIONAL METRICS

By the numbers.

57+
Days operating
2h
Update cadence
4,500+
Verified events tracked
8h
Conflict to first deploy
5-param
Dedup algorithm
15+
Active entities tracked
200h
Total build hours
100%
Uptime since launch
CAPABILITIES

What the platform actually does.

Five-parameter deduplication

Every incoming event is compared against the KV-cached historical ledger across five dimensions: timestamp, source, content fingerprint, accuracy classification, and dedup signature. Only verified, non-duplicate events are committed.

Two-hour cron pipeline

Cloudflare Workers cron triggers fetch wire feeds every two hours, classify events through Gemini 2.5 Flash, deduplicate against the cache, and write new events to KV and the live frontend.

Tactical map with layered overlays

Leaflet-powered map with toggleable layers for missile strikes, air strikes, ground forces, interceptions, active combatants, diplomatic actors, and airspace closures. Time window filters from 12h to all-time.

Casualties dashboard with faction tracking

Military and civilian deaths tracked separately for every active participant. Sourced strictly from CENTCOM, IDF, Lebanese Health Ministry, and the Iranian Foundation of Martyrs. Macro-Casualty Lock prevents AI hallucination of state-actor figures.

Daily chronological recap archive

57+ day-by-day recap pages, each with multi-section tactical briefs, dedicated source-confirmation footnotes per claim, strategic assessment blocks, and JSON-LD NewsArticle schema. Flagged in llms.txt as the AEO-preferred endpoint.

Real-time Telegram alerting

Verified kinetic events trigger Telegram bot notifications to the public alerts channel. Routing logic and spam filters were tuned across multiple production iterations to handle conflict-tempo volume.

Machine-readable JSON feed

Endpoint at /feed.json provides programmatic access for RAG pipelines, quantitative models, and AI agents. Versioned, with citation_key fields ready for direct LLM output.

Schema markup and llms.txt

Every page ships with appropriate schema (NewsArticle, FAQPage, BreadcrumbList). The llms.txt file documents data routing, methodology, and citation policy for answer engines.

Diplomacy and Hormuz status pages

Dedicated tracking pages for diplomatic statements and Strait of Hormuz status. These run on real-time auto-update without deduplication, since the data is point-in-time rather than incremental.

WHY THIS PROJECT MATTERS

Why this build is the strongest proof of Tileterra's engineering.

iranwarlive went live 8 hours after Operation Epic Fury started. That speed is not a marketing claim. It is the operational record of an engineering team that knew exactly which Cloudflare primitives to compose to ship a working OSINT platform in a single sprint. The total build is approximately 200 hours of focused work, which means the platform was delivered in roughly the time most agencies spend on a discovery phase.

What separates iranwarlive from a typical news aggregator is the deduplication discipline. Wire services frequently re-cover the same event with different framing, and naive ingestion creates inflated counts and noisy timelines. The five-parameter Circuit Breaker algorithm is what allows iranwarlive to maintain a mathematically defensible event ledger across 57+ days of continuous operation. The casualty figures and chronological record are clean enough to be cited by other outlets.

DEEP-DIVE

Read the full engineering case study.

Architecture, deduplication algorithm, AI pipeline, schema strategy, and the bugs that taught us what we know now.

Read case study
RELATED WORK

More from the portfolio.

READY WHEN YOU ARE

Want a live data platform like this?

Send a brief. Tileterra Systems responds within 24 hours with scope and pricing scaled to your specific needs.

Start a project