Delivery Guarantees
What a stream promises about each record reaching you: at most once, at least once, or effectively exactly once.
A delivery guarantee is the contract a stream offers about duplication and loss. At-most-once may drop a record but never repeats one. At-least-once never loses a record but may deliver it twice, usually after a retry the sender could not confirm. Exactly-once is what everyone wants and nobody gets for free: in practice it is at-least-once delivery combined with a consumer that discards repeats, which is why idempotency is part of the guarantee rather than an implementation detail.
Reading the guarantee matters because the failure is silent on the consumer's side. A pipeline that treats an at-least-once stream as if it were exactly-once double-counts events, and every aggregate built on it - a volume figure, a signal strength, a training label - inherits the inflation without an error ever being raised. Stable record identifiers, deduplication inline, and a documented replay path are what make the guarantee usable rather than theoretical.
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.