GGOLEMby DevOps Lab
Docs / Integrations

Fits into the stack you already run.

Golem connects to the clouds, source control, observability and ticketing tools most security and platform teams already have in place — so adopting it isn't a forklift upgrade of your existing tooling.

Clouds & orchestration
AWSAzureGCPAmazon EKSAzure AKSGoogle GKESelf-managed Kubernetes
Source & CI/CD

Scanning connects at both the repo and the pipeline level, in both directions.

GitHubGitLabBitbucketGitHub ActionsJenkins

Org-wide scanning

One token discovers and clones every repository in a GitHub/Bitbucket org or a GitLab group — including subgroups — and runs whichever scanners apply, rather than connecting repo by repo.

CI/CD gates

Copy-paste-ready pipeline templates trigger a scan from your own CI, poll for completion, and fail the build on a critical/high finding — the same trigger/poll/gate shape works in GitHub Actions, Jenkins or a GitLab CI script step.

Webhook ingestion

The reverse direction: GitHub calls Golem directly. Every delivery is signature-verified, and a completed build or a published container image updates the same graph entity a registry scan would create for it — so a CI event and a scan result converge on one record instead of two.

Read-only where it matters

The GitLab connector is read-only by design — there's no issue-creation path for it at all. Optional grouped-issue filing is available for GitHub and Bitbucket specifically.

Observability & SIEM
SplunkDatadogAWS CloudTrailAzure Activity LogGCP Cloud Logging
Ticketing & alerting

Two distinct flows, not one blended "notifications" feature.

JiraServiceNowPagerDutySlackEmail

Ticketing — file it for later

Findings above a severity threshold you set are filed automatically, deduplicated per scan window so a recurring finding doesn't spam a new ticket every run.

Alerting — page right now

Real-time dispatch the moment any pillar records a matching finding. Routing rules can match on scan type, severity, category or rule ID, and every matching rule fires — not just the first one that hits.

AI providers (bring your own)

AI-assisted investigation calls a model endpoint you choose — your own account, your own prompts, never a copy of your security context sent to a third party by default. If you don't configure one, Golem falls back to its own hosted key so there's always a working starting point.

AWS BedrockAzure OpenAIGCP Vertex AILocal / on-prem model endpoint
Registries
Any OCI-compliant container registry
Don't see something you need?

Tell us what's in your stack — most integrations are a short conversation away.