INTYGA Intelligence · Getting started
One deployment.
One service to start with.
Start with a system you understand and a signal you already trust. Get that source collecting successfully before adding more integrations or enabling notifications.
What you need before you start.
- Infrastructure you operate
- A host for the Node.js application, a PostgreSQL database and a scheduler for collection and detection. Follow the repository's current runtime requirements and production guide.
- An INTYGA workspace
- Administrator access to configure the application's service identity, approval rules and member application. Members link their membership and create an application passkey for Intelligence.
- A first source
- Credentials or webhook configuration for one provider. Use only the access its connector requires, and start with a separate test service or known test event where the provider supports it.
- A reachable origin
- A stable application URL for sign-in and approval. External webhook providers need a reachable HTTPS endpoint; they cannot deliver directly to a private localhost address.
The path to your first finding.
- Run the application and database.Install from the source repository, configure the encryption key and database, apply migrations and start the application. Keep credentials in private deployment configuration. The production guide covers the operating requirements.
- Connect the INTYGA approval identity.Create a service and its key, configure approvers, and register the application's origin under Member applications. Verify ownership, link your membership and create the application passkey. Export the application's trust anchor after enrollment and configure it on the server.
- Create a service and add a source.Name a system such as “Production API.” Add a connector with the required credentials, assign it to that service and follow its setup instructions. The new connector starts switched off.
- Approve activation and run the scheduler.Review and sign the change. Keep the scheduler running for polling and detection; a successful webhook delivery alone does not run every detector. Check connector health to confirm data is arriving.
- Verify a known condition.Use a representative event or provider test that the connector supports. Check the stored activity, then the resulting finding where its rule applies. For native alerts, verify explicit recovery too. An unsupported test payload may verify delivery without creating a finding.
- Tune the signal before notifying others.Configure targets and thresholds for the detectors you need. Inspect evidence and mark expected behavior. Add and approve an alert destination only when the findings are useful.
Connected, but no findings yet?
“Awaiting first poll”
The source has not completed its first scheduled collection since activation. Confirm the connector is active and the scheduler is running. Then inspect the connector's last-poll status for credentials, permissions or provider errors.
Delivery verified, with no finding
Authentication and delivery can work even when the payload contains no supported alert. Check Activity and the connector's coverage. A detector still needs its required condition, targets and history; not every event should become a finding.
A merged PR appears under Observations
This is expected for a sensitive-path match. Review observations provide code-change context. A routine merge alone is not an anomaly and does not trigger alerts or model scoring.
Passkey accepted, but the action is still waiting
Your workspace may require another approver. Share the approval link with an eligible member. The action is complete only when Intelligence confirms it was approved and applied.
Operate it deliberately.
Intelligence is an Apache 2.0 application. Hosting, backups, updates and provider access are your responsibility. There is no support SLA; your INTYGA workspace plan is separate from the application's license.
Optional model judgment sends projected data to a third-party processor. Alert destinations receive finding details. Review these data flows before enabling them.