Follow a service
Group related deployment, monitoring and operational sources around a service such as your production API. Keep unrelated products and environments separate.
INTYGA Intelligence
Bring deployments, monitoring, cloud alerts and authorization activity into one place. INTYGA Intelligence turns connected signals into a focused list of findings, with the evidence you need to decide what to investigate.
Requires an INTYGA workspace. You run the application and its database as a single instance.
Your CI tool knows a build failed. Your monitor knows errors increased. Your cloud provider knows an alarm fired. Intelligence brings the signals you connect into a common view and applies explicit detection rules.
Group related deployment, monitoring and operational sources around a service such as your production API. Keep unrelated products and environments separate.
See measured counts, comparison windows and source references where available. Distinguish a correlated regression from a provider-reported alert.
Mark a finding as investigating, expected or fixed, and leave a note. Route selected findings to Slack or a signed webhook when you need notifications.
The catalogue includes 21 connectors across code hosting, cloud operations, observability, identity and business systems. Start with one useful signal, then add the sources that give it context.
Find repeated CI failures, missed jobs, service degradation and unusual refusal patterns. Import selected provider alerts, or investigate error increases after a production deployment. Each integration has a specific scope.
Browse integrations and their coverage โ
A routine PR merge is not an anomaly. Changes to sensitive paths appear as review observations unless other evidence supports a finding.
One example ยท Authorization activity
A release service starts attempting permission changes. Its requests are refused, but the volume and action types differ from its observed history. Intelligence surfaces that difference with the evidence attached.

Refusals exceeded the configured count and baseline thresholds. Twelve attempts involved a permission-change action absent from this subject's earlier observed refusal history.
The finding is a reason to investigate. It does not establish that access was granted or that the service was compromised. No model is needed to produce it.
Detection runs on connected activity. Optional model judgment can add an assessment to eligible findings, but does not originate them or authorize a response. Intelligence does not automatically remediate your systems.
Activating sources, changing detection settings and enabling alert destinations require INTYGA approval bound to the change. Passkey acceptance and a successfully applied change are separate states.
Follow a signal through detection, evidence and human review.
Find your tools and understand exactly what each source supplies.
Prepare your deployment and connect your first service.
Apache 2.0 application, operated on your infrastructure. Your INTYGA workspace plan is separate. There is no support SLA.