Demo

The language of real-time data.

Plain, practitioner definitions across real-time, alternative, market, and satellite data - and machine learning.

A working vocabulary for desks and teams that trade and train on data: what each term means, why it matters, and how it shows up in real-time data. Every definition links to the terms it depends on, so you can follow an idea rather than look up one word at a time.

The vocabulary is where this industry hides its ambiguity.

Every data vendor says real time, and almost none of them mean the same interval. The same is true of freshness, provenance, coverage, and quality: they are all words a buyer is expected to interpret generously. A glossary is the cheapest form of honesty available to a vendor, because a definition written down can be held against the product later.

So these are practitioner definitions rather than marketing ones. Where a term has a precise meaning, we give it: event time is not processing time, point-in-time history is not a corrected archive, and an at-least-once delivery guarantee is not exactly-once no matter how it is described in a datasheet. Where a term is genuinely contested, we say that too.

Each definition links to the terms it depends on, which is what makes this usable rather than alphabetical. A reader who arrives at latency can follow it to round-trip time, to event time, and to what a backtest needs from both, without leaving to search for the next word.

Three ways in.

You met a word and want it defined

Use site search or the category sections below. Every definition opens with a one-line answer before it explains anything.

You are evaluating a data vendor

Read event time, delivery guarantees, point-in-time, and data provenance. Those four decide whether a dataset can be trusted in research.

You are reviewing us on security

Start at post-quantum cryptography and hybrid key exchange, then the post-quantum page for what our transport negotiates.

Machine Learning

Signal

The predictive, actionable information extracted from noisy raw data - what remains after the noise is removed.

Ground Truth

A direct, verified observation of the real world, used as the reference against which models and estimates are checked.

Training Data

The dataset a machine-learning model learns from - and usually the single biggest lever on how well the model performs.

Natural Language Processing (NLP)

Techniques for turning unstructured text - news, filings, transcripts - into structured, machine-usable data.

Named Entity Recognition (NER)

Identifying and tagging the real-world entities in text - companies, tickers, people, places - so unstructured content becomes linkable.

Entity Resolution

Linking records that refer to the same real-world entity across different sources, spellings, and identifiers.

Model Drift

The gradual decay of a model's accuracy as the world shifts away from the data it was trained on.

Signal-to-Noise Ratio

How much of a dataset carries information relative to how much is clutter - the measure that decides whether volume is an asset or a cost.

Retrieval-Augmented Generation (RAG)

Giving a language model current, sourced material at query time instead of relying on what it memorized during training.

Model Grounding

Anchoring a model's output to verifiable external facts, so what it produces can be checked rather than only believed.

Feature Engineering

Turning raw data into the inputs a model actually learns from - the step where most of a model's real performance is decided.

Data Engineering

Data Pipeline

The chain of steps that moves data from source to consumer - ingest, transform, and deliver - reliably and on schedule.

Streaming API

An interface that pushes new records to consumers the instant they arrive, rather than making them poll for updates.

Webhook

A server-to-server callback that pushes data to a URL you register when an event fires - push delivery without a held-open connection.

Data Normalization

Reconciling data from many sources into one consistent schema, units, timezone, and set of identifiers.

Deduplication

Removing duplicate and near-duplicate records so each real event is counted once, not many times.

Data Quality

The fitness of a dataset for use, across accuracy, completeness, timeliness, and consistency - for a data vendor, it is the product.

Data Lineage

The traceable map of where data came from, how it was transformed, and where it flowed - the backbone of debugging and audit.

Backfill

Populating a dataset's history - loading past data for a new or changed source - while preserving point-in-time correctness.

REST API

A request-and-response HTTP interface - the standard way to pull a defined range of history, as opposed to receiving records as they happen.

API Key

A credential identifying the caller on every request - and, handled properly, the boundary of what that caller can reach.

Idempotency

The property that handling the same record twice produces the same result as handling it once - what makes retries safe.

Backpressure

A consumer telling a producer to slow down - the mechanism that makes a stream degrade predictably instead of collapsing under a burst.

Data Observability

Monitoring the data itself - freshness, volume, distribution, schema - so a source failing silently is detected before a consumer acts on it.

Schema Evolution

Changing the shape of a dataset over time without breaking the systems already reading it.

Data Governance

The rules and records covering who may use a dataset, for what, and how its handling can be demonstrated later.

Real-time data, at edge speed.

A live evaluation measures EdgeOrigin against your coverage requirements: decision-ready real-time data, delivery latency into your systems, and record-level provenance.