GGOLEMby DevOps Lab
Docs / Getting Started

From first conversation to first scan.

Golem is currently in guided early access — there's no public self-serve signup yet. Every deployment starts with a short scoping conversation so we apply the right Terraform into the right account, with the right integrations, from day one.

What to expect

Four steps, start to first findings.

01

Scoping call

We talk through your environment — which clouds, which source control, which SIEM/ticketing tools you already run — so the deployment plan fits what you have, not a generic template.

02

Apply into your own account

You (or your platform team) run the Terraform that deploys Golem into your own AWS, Azure or GCP account. We're on the call to walk through it live.

03

Connect your first sources

Cloud accounts, source control (GitHub/GitLab/Bitbucket), container registries, and any SIEM/ticketing integrations get connected one at a time, read-only by default.

04

Review findings together

We walk through your first CSPM/CIEM scan and attack-path correlation results together, so your team knows what they're looking at before going further on their own.

What helps to have on hand

Nothing exotic — just access to what you already run.

A cloud account

AWS, Azure or GCP, with someone who can apply Terraform (or review and apply it through your own change process).

Source control access (optional)

GitHub, GitLab or Bitbucket org access, if you want code and CI/CD scanning in scope from the start.

An AI provider (optional)

Your own AWS Bedrock, Azure OpenAI or GCP Vertex AI endpoint, if you'd rather bring your own model than use Golem's default.

Your alerting stack (optional)

Slack, Jira, ServiceNow or PagerDuty details, so findings can route to where your team already works.

Ready when you are

Book a scoping call and we'll take it from there.