Data Inc.

The IDIA Hub · Audit-as-a-Service

The Vulture: the one way in to the Verified Truth ledger.

The Vulture is IDIA's data ingestion gateway and Audit-as-a-Service pipeline. It is designed as the single way in for outside data: autonomous edge nodes, and partner software such as law enforcement records systems or point-of-sale systems, all reach the IDIA Hub's Verified Truth ledger through it and nothing else.

Built on zero-trust principles: no node or system is trusted by default. Every sender needs its own node key, and a key can be limited to allowed IP addresses.

Live nowCompany-stated design. Not yet independently assessed. Anchoring proves a record has not changed since it was written; it does not prove the data is accurate.
Integrate with The Vulture Back to The IDIA Hub
The IDIA Hub — Vulture · Mesh Node Integration. The Vulture tab in the Hub's Data Marketplace. The Mesh Gateway Airlock banner reads PII-stripped, hashed, ledgered. Partners label a node, optionally limit it to allowed IP addresses, generate a node key, then post to the ingest endpoint. Uploader and Ledger sit beside Mesh Nodes.

Real screenshotThe IDIA Hub

Vulture · Mesh Node Integration

Credit balance shown is from a team account.

What The Vulture does

Take in anything, keep no one's identity, prove every record.

  1. 01

    Multiplexed stream interception

    Takes in fast, continuous streams over APIs, webhooks and websockets, straight from edge devices and from enterprise back-end systems, through one gateway.

  2. 02

    Liability Shield Protocol · in-memory sanitization

    Data is held in memory while The Vulture strips personal details and raw sensitive fields. Only the cleaned version is ever written to a database; the raw payload is not stored.

    This sanitization step shares a name with the Liability Shield buyer coverage, but it is the cleaning step, not the coverage.

  3. 03

    Identity federation · the GUID match

    Identity is proved in Life by IDIA, not in The Vulture. The gateway logs only the person's IDIA GUID, a random ID with no personal details in it. Later, an agency can check cryptographically that a GUID took an action, without any identity ever being stored on the ledger.

  4. 04

    Dynamic payload shaping

    Shapes each payload for where it came from: compact 40-byte LoRa binaries for hardware telemetry, or richer JSON event records for enterprise software.

  5. 05

    Tamper-evident anchoring · built for CJIS

    Cleaned metadata is anchored permanently to the ledger with an exact timestamp and a cryptographic proof of its state, so any later change shows. The audit trail is designed to support the FBI CJIS Security Policy that law enforcement agencies work under.

Company-stated design. Not yet independently assessed. Anchoring proves a record has not changed since it was written; it does not prove the data is accurate.

How a payload moves

From the edge to the ledger in six steps.

  1. 1

    Receive

    A node or partner system sends data with its node key.

  2. 2

    Clean in memory

    Personal details are stripped before anything is stored.

  3. 3

    Match the GUID

    The person is referenced only by their Life by IDIA GUID.

  4. 4

    Shape

    40-byte LoRa binary or JSON event, depending on the sender.

  5. 5

    Anchor

    Hashed, timestamped and written to the Verified Truth ledger.

  6. 6

    Meter

    Synapse Credits are deducted from the partner's wallet.

Metering in Synapse Credits

Pay for what you send.

The Vulture is paid by use, not by subscription. As payloads arrive, the gateway sorts them by weight, a light LoRa binary or a heavier JSON event, and deducts Synapse Credits from the partner organization's wallet in real time. Deductions run in the background, so metering does not slow the stream down.

PayloadSizeUsed for
LoRa binary40 bytesHardware telemetry from edge nodes
JSON eventVariesEvents from enterprise software

Credit rates per payload type are not published on this site yet. They are shared with partners when keys are issued. Synapse Credits are bought in The IDIA Hub.

What is checked and what is not

  • Live now

    Gateway and Mesh Node keys in the Hub

    The Vulture tab, node keys and ingest endpoint are in The IDIA Hub today (see the screenshot).

  • Planned

    Independent test of the PII stripping

    No outside party has tested whether the sanitization catches every kind of personal data. Automated stripping can miss things, which is why only GUIDs are meant to reach the ledger.

  • Planned

    CJIS audit

    Not done. CJIS compliance is judged by each agency's CJIS Systems Agency, through audit and a signed CJIS Security Addendum. IDIA has not been audited yet, so we do not call The Vulture CJIS-certified.

Why provenance is not the same as truth

Integrate with The Vulture

Route your system's data through The Vulture.

  • B2B partners and developers

    Request API keys

    Get node keys and the ingest endpoint for your edge nodes or back-end systems.

    Request API keys

  • Developers

    Review the JSON payload schemas

    See the event and LoRa payload formats before you build.

    Review the JSON payload schemas

  • Government and law enforcement agencies

    Start a Security Addendum

    Begin the security addendum your agency needs before routing system data through The Vulture.

    Start a Security Addendum
Already have a Hub account? Generate a node key in the Vulture tab.Open The IDIA Hub