Choose a bounded source
Send events through the ingestion API or connect a read-only ClickHouse dataset. Give each occurrence a stable identity so retries can be recognized.

· Signals
Cbox · Signals
Repeated access denials. Unusual account activity. Changes that disappear in a stream of individual events.
Give your events a common shape, run reusable detectors, and inspect the evidence behind each signal.
In development · Production validation is in progress.
One processing model
Your names, fields and entity IDs.
product events / customer datasetMap subjects, resources and outcomes to observations a detector understands.
See the measurement, source references and configuration behind the result.
Processing model · source → observation → signal.
From individual events to evidence
Send events through the ingestion API or connect a read-only ClickHouse dataset. Give each occurrence a stable identity so retries can be recognized.
Define which fields identify the actor, resource and outcome. The mapping connects your application’s vocabulary to a generic observation.
Follow the measurement back to its source and detector version. Evaluate results in shadow mode before choosing active delivery.
Designed for operational control
A signal is useful when you can explain it, check its inputs and decide what happens next.
Part of the Cbox family
Signals uses the same Cbox service interfaces available to external customers. Its engine is being validated with customer-defined events as well as Cbox events.
Signals is under active development. General availability, pricing and service commitments have not been announced.
About Cbox