A detector finding
A measured condition crossed a rule: for example, refusals increased relative to observed history. Counts, windows and available source references explain why.
INTYGA Intelligence · How it works
Intelligence collects the activity you connect, looks for specific conditions and keeps the supporting evidence alongside each finding. You decide whether it needs a response.
Choose a source and the service it describes.
Apply rules to observed events and measurements.
Read the evidence and its limits.
Investigate, record context or mark it expected.
Create a service such as “Production API” and assign its related sources. A deployment and an error signal need to belong to the same service before they can support a regression finding. Separate connections keep unrelated environments apart.
Some sources send authenticated webhooks. Others are polled by the scheduler. Activation requires approval; creating a connector does not begin collection. The connector view distinguishes setup, waiting for data, healthy collection and failures.
Targets and settings matter. CI checks need selected repositories, branches and workflows. Job checks need expected completion intervals. Service-level checks need objectives and enough complete measurements. A connected source does not make every detector applicable.
A measured condition crossed a rule: for example, refusals increased relative to observed history. Counts, windows and available source references explain why.
A connected provider reported a condition. Its severity is useful context, but does not independently prove an anomaly, compromise or customer impact.
A change touched a sensitive code path. It appears under Observations; a path match or routine PR merge alone does not trigger an anomaly assessment or alert.
A deploy-regression finding joins a successful production deployment to a subsequent increase in error or incident signals. It reports timing and the available connection to code changes. Root cause still needs investigation.
Filter by service, status, severity or category. Open the evidence, record a note and mark the finding as investigating, expected, a false positive or fixed. Repeated observations of a condition are grouped instead of becoming an unrelated list of alerts.
Optional alert rules send matching findings to Slack or a signed webhook, with severity thresholds and cooldowns. Review observations do not trigger those alerts. Intelligence does not execute a fix in the connected provider.
The detectors work without a model. You can configure TypeSafe AI (Jev), OpenAI or Anthropic as a review provider. Once you approve turning reviews on, eligible findings can receive an advisory review based on a restricted projection of their evidence. You can also ask another configured provider for a second opinion after inspecting the exact request.
Guidance reflects the evidence group: code and delivery, identity, cloud operations, monitoring, payments or other sources. A routine merge is expected activity; a refused request can mean a control worked; a dispute can need attention without being unusual.
Anomaly likelihood, human attention and severity are separate questions. Missing context stays uncertain. A review never creates a finding or changes its severity, status or alerts, and it cannot authorize a change. Prior opinions are not fed back as evidence. Operational and native-provider detectors do not request model reviews.