kimo
Intelligence

OSINT Feeds + Kimo

Curated open-source feeds with entity extraction, geotags and source reliability scores, streamed in real time.

Auth
API key
Sync
Real time
Setup
≈ 3 min
Request access

Live demo workspace with fictional data · no signup, no credentials needed

kimo / connectors / osintSyncing
Sync logreal time
  • Succeeded:articles+2,043 rowsnow
  • Succeeded:events+424 rows2m ago
  • Succeeded:entities+481 rows4m ago
  • Succeeded:articles+1,262 rows6m ago
Rows synced · 30 days
134.8M
Workspaces
19%
Simulated demo data
What you can do

What teams build with OSINT Feeds

OSINT Feeds on its own answers half the question. Joined with the rest of your stack in Kimo, it answers the other half.

01

Activity by area of interest

Geotagged items aggregated per AOI with confidence radii and time sliders.

AOI heatmap
02

Entity graph

People, organisations and places extracted and linked across sources and languages.

14 languages
03

Narrative surge alerts

Detect when an entity or topic accelerates beyond its baseline in a region.

Velocity z > 3
Objects & tables

Exactly what gets synced

Kimo maps OSINT Feeds into clean, typed tables with primary keys and incremental cursors, so syncs stay fast and joins just work.

3 tables · 17 fields

articles

Streaming≈ 20,100 rows
FieldTypeNotes
ididPrimary key
outletstring
published_attimestampIncremental cursor
langstring
titlestring
summary_enstring
Custom fields and extra objects are discovered automatically on each sync. Row counts are illustrative.
Sample model

From raw OSINT Feeds tables to a certified metric

This model ships with the Defense Intelligence demo. Open it to see every join and measure.

Threat correlation

OSINT signals and SIEM events correlated by entity, zone and time window.

In the demo
  • OSINT Feeds
    signals
  • Splunk
    events
  • AIS Maritime
    positions
Model
entity = asset
Measuressignalseventsalerts
Signals ingested · last 30 days
216.3K+3.1% wk/wk

Fictional data · hover the chart for daily values

Setup

Connect OSINT Feeds in 3 min

No engineers, no pipelines to maintain. Kimo asks for the minimum access it needs and tells you exactly what it will read.

  1. 1

    Create a read-only key in OSINT Feeds

    Use a dedicated key scoped to read access, so it can be rotated independently.

  2. 2

    Paste it into Kimo

    Keys are encrypted with a per-workspace key and never shown again.

  3. 3

    Choose streams

    Pick which objects to sync, starting with articles.

  4. 4

    Validate and sync

    Kimo tests the key, backfills history and keeps it fresh (real time).

Read-only, encrypted, revocable. Credentials are encrypted with a per-workspace key, never logged, and can be rotated without breaking your models.

Connect OSINT Feeds
Step 2 of 3 · Kimo demo workspace
  • Reaching host
  • Authenticating
  • Reading schema
Read-only access
Illustration only · placeholder values, never real secrets
FAQ

OSINT Feeds questions, answered

OSINT Feeds is ingested as a stream. New records typically appear in models and maps within a few seconds.

OSINT Feeds · API key · Real time

See your OSINT Feeds data in Kimo in 3 min.

Try it on the live demo workspace first, then connect your own account when you are ready.

Request access