000 Content intelligence platform

Read the world like one room.

InsightStorm turns the open web — news, filings, Telegram channels, PDFs, structured feeds — into one queryable, attributed corpus. Configure your sources and taxonomy. We run the rest.

Sources
0
Docs / day
0
Languages
0
Tenants live
0
InsightStorm alerts: a ransomware incident at a German manufacturer, flagged sixteen minutes after publication, with the record open beside the list
An alert fires 16 minutes after the source publishes. The record, its entities and its provenance open beside it.
STORM · LIVE

001 Gap

Every team is drowning in signal,
starving for meaning.

The open web is where the answers live — and where the big platforms cannot, or will not, reach. Three doors, three problems.

  • Blocked by policy

    Enterprise chat assistants

    Cannot crawl websites their customers don't own. Domain verification is a hard policy gate, so open-web ingestion is structurally off-limits — the answer is only as wide as the index.

  • Expensive by design

    Closed intelligence feeds and data platforms

    Curated feeds with five-figure floors; platform deployments that arrive with a forward-deployed engineering team. New sources mean change orders, not config.

  • What InsightStorm is

    Headless SaaS, configured by you

    Open-web, third-party, multilingual sources — declared per tenant, ingested in one pipeline, normalized into one record model. Hours to first data. No FDE team in the loop.

002 Capabilities

One pipeline,
three movements.

Collect everywhere. Read structure. Answer with proof. Six capabilities, one platform — no Forward Deployed Engineers required.

  • Listen everywhere

    Web articles, RSS, JSON APIs, encrypted messaging channels, PDFs with right-to-left OCR, even legacy form-based web catalogs that no SaaS crawler reaches. Declarative config per tenant; no platform release required.

    • RSS
    • Web
    • PDF + OCR
    • Telegram
    • JSON APIs
    • ASP.NET forms
  • Autonomous discovery

    A Gemini-driven agent runs hourly per tenant — hunts new candidates on the open web, validates relevance against your taxonomy, queues the keepers for one-click approval.

  • Extraction in any language

    Right-to-left and complex non-Latin scripts first-class. PDFs go binary-to-JSON in a single model call. Original text preserved; English translation, summary, entities indexed for cross-lingual search.

  • One record model

    Every source resolves into one canonical record, typed by the record types you declare — an incident, a tender, a filing, a telemetry frame, a headline. One analytical layer across all of them: search, aggregate, group-by on any field path.

    • article
    • incident
    • tender
    • filing
    • telemetry
  • Semantic + analytical search

    BM25 keyword and pgvector similarity in a single hybrid query. Filter, aggregate, group-by on any data.* field path. One engine, every record type.

    Search results with filters by date, category, country and entity, the detected query mode, and the sources present in the result set
  • Answer with proof

    Natural-language questions over the whole archive. The analyst chatbot knows your taxonomy, your source counts, your data.* paths. Every claim cites a URL.

    The assistant answering which German manufacturers were hit by ransomware, each line citing its source

003 Source discovery

It hunts.
You approve.

An autonomous Gemini agent runs hourly per tenant — looking for sources you don't know about yet. Scores them against your taxonomy. Surfaces the keepers for one-click approval. No competitor has this productized.

discovery@storm:~$ hunt --tenant=$TENANT --taxonomy=$CODEBOOK RUNNING
candidates —
    scoring —
      approved · queued —
        last hunt · 00:00:00 0 candidates inspected this hour

        004 Process

        How a tenant
        goes live.

        Four steps from blank slate to running storm. Days, not quarters.

        1. 01

          Declare your taxonomy

          Codebooks, extraction profiles, dashboards, chatbot prompts — declarative JSON per tenant. No engineer required.

        2. 02

          The storm finds sources

          Source discovery runs hourly, proposes new feeds. You approve the keepers in the admin UI.

        3. 03

          Pipeline ingests and extracts

          Gemini produces title, summary, entities, classifications. Multilingual in, English index out, full provenance preserved.

        4. 04

          Search, chat, alert, decide

          Analyst surface goes live: hybrid search, BI dashboards, maps, AI chat, alerts — all scoped to your tenant.

        005 Golden Record & Entity Resolution

        Many claims.
        One Golden Record.

        Sources disagree. A trade site, a registry and a company statement each say something slightly different about the same company. InsightStorm keeps every claim, picks one value per fact by rules you declare — trust the registry, prefer the newest, take the majority — and shows the source and the confidence next to the result.

        Three sources, three answers to one question: where is Rheinwerke GmbH based?

        • industrienews-dach.de · trade press · 16 Mar 07:14 “…the Neuss-based industrial group…” Extracted from the article · confidence 0.72
        • handelsregister · company registry · 2025 Registered seat: Düsseldorf, North Rhine-Westphalia Structured field · confidence 1.00
        • rheinwerke.example · company statement · 16 Mar 09:40 “Rheinwerke GmbH, Düsseldorf, confirms production stops at Düsseldorf, Neuss and Krefeld.” Extracted from the statement · confidence 0.95
        One fact on the entity, with its reasons
        HeadquartersDüsseldorf, North Rhine-Westphalia100 %
        SitesDüsseldorf · Neuss · Krefeld95 %

        The registry outranks the press for a registered seat; the press claim named a site, not a seat, and lands under Sites together with the company's own statement. Every value keeps the source it came from, so an analyst can disagree with the rule and see why it chose.

        Entity dossier for Rheinwerke GmbH: facts with confidence and source, relationships grouped by kind, and a graph of the strongest links
        The entity as the analyst sees it: each fact with its confidence and its source, relationships grouped by kind.

        006 Atlas

        If it's published,
        we hear it.

        Numbers reflect live production tenants today — across multiple analyst-driven verticals from investigative intelligence to market-signal research. The atlas grows hourly.

        0 active sources, growing hourly
        • RSS 0 feeds
        • WEB 0 sources
        • PDF 0 docs / day
        • TELEGRAM 0 channels
        • JSON·API 0 endpoints
        • FORM 0 catalogs
        • Google Cloud
        • SSO · OIDC
        • DPoP enforced
        • Per-tenant isolation

        006 Compare

        Where everyone else stops,
        InsightStorm starts.

        Three competitors, one platform-of-record. What ships, what costs, what takes.

        Enterprise chat Data platforms Intel feeds InsightStorm
        Open-web ingestion Blocked by policyCustom code per sourceCurated only Yes
        Customer-defined sources NoYes — with FDE teamNo Yes — self-serve
        Autonomous source discovery NoNoManual analyst work Yes — hourly per tenant
        Per-tenant taxonomy NoYes — with FDE teamNo Yes — declarative
        Multilingual + RTL LimitedYesLimited First-class
        Pricing $30–100 / seat$1M+ contracts$50k+ floors Contract-based SaaS
        Time to first data Days — internal docs4–8 weeksOut of your control Hours

        008 Workspaces

        One pipeline.
        Every desk.

        InsightStorm is domain-agnostic. A tenant declares its sources, record types and taxonomy; the boards, alerts and briefings follow from that declaration. The screens below are the product on one tenant's data.

        Cyber threat landscape board: a map of Europe with incident counts, incidents by country, attack types and the top affected companies
        Every tenant sees its own boards, built from its own record types. Nothing here is shared between tenants.
        Timeline: article published at 07:14, alert translated and prioritised at 07:30, first call at 09:00, proposal on the table Wednesday, competitor finds out Thursday

        A morning in a cybersecurity sales team

        The deal Yaron missed.

        Yaron sells security software. A regional trade site reports a ransomware attack on a manufacturer at 07:14, in German. On the other side of town, a rival team running InsightStorm has the record extracted, translated, matched against one keyword rule and on a rep's phone by 07:30. First call at 09:00, proposal on the table Wednesday, $180,000 closed within weeks. Yaron hears about the attack on Thursday, from a Google Alert. He was never in the race.

        • 16 min from publication to alert
        • 4 days before the news reached the other vendor
        • 1 rule — ransomware · DACH · manufacturing

        009 Pilot

        Read the world
        like one room.

        30-day pilot. One desk, one watchlist, one decision per week — measured against your current process. Sign in to access your tenant, or talk to us about provisioning one.