GGOLEMby DevOps Lab
CNAPP · Security Graph · AgentGuard
The open alternative to Wiz & Cortex Cloud

Golem is the security
platform you own.

New to this category? Tools like Wiz and Cortex Cloud scan your cloud and AI systems for risk — that's a CNAPP. Golem does the same job, but runs in your own cloud account with source code you can read and change.

One platform, one graph — deployed in your environment with source code and your choice of AI.

Cloud infrastructureApp code & supply chainIdentity & accessSensitive dataContainers & serversNetworkAI agents
YOUR CLOUD · YOUR GRAPH · YOUR POLICIES · YOUR AI · YOUR DATA
GOLEM // HOW IT WORKSLIVE
Built to replace platforms likeWiz+Cortex Cloud+Prisma Cloud— same job, run in your own account. See the full comparison ↓
00 // See it work

Every scene, interactive.

The same walkthrough as the explainer video above — built as a live, inspectable graph you can click through at your own pace.

GOLEM // HOW IT WORKSLIVE
Golem building its security graph An illustration of the security graph forming as Golem connects to a cloud account and resolves identities, data and attack paths.

Connect your cloud. Golem maps identities, data and attack paths, then signs the evidence — automatically.

Where your data sits A typical CNAPP sends your data out to the vendor's cloud. Golem runs the same checks inside your own cloud account, so your data never leaves it. A TYPICAL CNAPP YOUR CLOUD VENDOR'S CLOUD GOLEM YOUR CLOUD DATA STAYS HERE

Same job as Wiz or Cortex Cloud — your data just never leaves your own cloud account.

One graph, seven surfaces Cloud, code, identity, data, containers, network and AI agents all resolve into one connected security graph instead of seven separate tools. SECURITY GRAPH CLOUD CODE IDENTITY DATA CONTAINERS NETWORK AI AGENTS

Cloud, code, identity, data, containers, network, AI agents — one graph, not seven dashboards.

The model suggests, policy decides An agent's tool call passes through a deterministic policy check. Safe calls are allowed and signed; risky ones hold for human approval and are also signed. AGENT requests a tool TOOL CALL exact arguments POLICY CHECK ALLOW proceeds, signed HOLD human approval

The model suggests a tool call. Policy — not the model — decides if it runs.

Who can reach what A service principal's role chain resolved across Azure RBAC, AWS trust policies and GCP IAM into one identity graph, surfacing a three-hop path to Owner and a production database. SERVICE PRINCIPAL CONTRIB- UTOR OWNER PRODUCTION DATABASE ROLE_CHAIN: 3 HOPS · BLAST_RADIUS: 14 RESOURCES

Azure RBAC, AWS trust chains, GCP IAM — resolved into one identity graph.

Data everywhere, one graph Native cloud storage, Snowflake, Databricks, Salesforce, SharePoint and Drive all resolve into one sensitive-data graph; a SharePoint site is flagged for a public ACL with PII. DATA GRAPH CLOUD STORAGE SNOWFLAKE DATABRICKS SALESFORCE SHAREPOINT DRIVE PUBLIC + PII

Classify once. Govern everywhere your data actually lives.

Trust the build, not the promise A container image passes through a signing and provenance gate before deploy. A signed image with verified SLSA provenance is allowed; an unsigned image is denied at admission. COMMIT source change BUILD image produced SIGN GATE ALLOW signed · provenance verified DENY unsigned · blocked at admission

Cosign signatures and SLSA provenance, enforced at the deploy gate — not a promise after the fact.

External attack surface, continuously mapped A scan line passes across the public internet-facing assets Golem has discovered for this organization.
app.devopslabinc.comMONITORED
api.devopslabinc.comMONITORED
legacy-api.devopslabinc.comOPEN PORT 22
stage.devopslabinc.comMONITORED
devopsl4b.comTYPOSQUAT

See your company the way an attacker does — subdomains, open ports and typosquats, mapped continuously.

Active Directory, still the target A service account's DCSync replication right resolves a two-hop path to Domain Admins, flagged and monitored. SVC-BACKUP service account DCSYNC REPLICATION DOMAIN ADMINS TECHNIQUE: DCSYNC · PATH: 2 HOPS · STATUS: MONITORED

Active Directory isn't legacy. Domain-controller replication rights are still the target.

Golem Standalone, zero cloud dependency A single server running the same security graph with no external network calls, for environments that cannot accept an outside dependency. STANDALONE LITE NO EXTERNAL CALLS

Some environments can't phone home. Standalone runs the same graph, air-gapped.

Three new security pillars MailGuard for email, MacDefender for endpoints, and IdentityGuard plus PrivilegeGuard for privileged access, shipping next. MAILGUARD vs Proofpoint MACDEFENDER vs CrowdStrike IDENTITYGUARD vs CyberArk

MailGuard, MacDefender, IdentityGuard + PrivilegeGuard — one platform, not four bills.

Why rent security→when you can own it.

Your cloud · your graph · your keys · your rules
100functions in the locked release rubric
12registered code / IaC scanners
96.8%project-reported backend test coverage
100%of the locked rubric shipped and verified
01 // Complete capability atlas

100 functions. One graph.

Every function below is part of the locked release rubric and is live in the codebase today — "Current" means it exists and has been exercised end to end.

100 / 100 functions current — fully shipped
Current
Platform architecture10 functions
  1. 01Customer-owned deployment / data planeCurrent
  2. 02Customer-owned security graph / storageCurrent
  3. 03Source delivered and customizableCurrent
  4. 04Bring-your-own AI / LLM providerCurrent
  5. 05Multi-cloud breadthCurrent
  6. 06Hybrid / on-prem supportCurrent
  7. 07API-first automationCurrent
  8. 08RBAC / SSOCurrent
  9. 09Audit / evidence loggingCurrent
  10. 10Enterprise scale / operational maturityCurrent
CSPM & compliance10 functions
  1. 11Cloud inventoryCurrent
  2. 12AWS CSPMCurrent
  3. 13Azure CSPMCurrent
  4. 14GCP CSPMCurrent
  5. 15OCI / Alibaba / additional providersCurrent
  6. 16Kubernetes Security Posture Management (KSPM)Current
  7. 17Compliance framework breadthCurrent
  8. 18Compliance evidenceCurrent
  9. 19Scheduled posture scanningCurrent
  10. 20Graph drift / historyCurrent
Identity & graph10 functions
  1. 21Cloud Infrastructure Entitlement Management (CIEM)Current
  2. 22Effective permissionsCurrent
  3. 23Unused / excessive permissionsCurrent
  4. 24AWS trust graphCurrent
  5. 25Azure / GCP impersonationCurrent
  6. 26Privilege escalation discoveryCurrent
  7. 27Privilege risk / blast-radius scoringCurrent
  8. 28Security Graph breadthCurrent
  9. 29General graph reachabilityCurrent
  10. 30Toxic combinations / attack pathsCurrent
DSPM & data security10 functions
  1. 31Native-cloud DSPMCurrent
  2. 32Snowflake DSPMCurrent
  3. 33Databricks DSPMCurrent
  4. 34Salesforce DSPMCurrent
  5. 35SharePoint DSPMCurrent
  6. 36Google Drive DSPMCurrent
  7. 37Sensitive-data graphCurrent
  8. 38Data-access governanceCurrent
  9. 39Data Detection & Response (DDR)Current
  10. 40Cross-platform identity / data correlationCurrent
AppSec & supply chain10 functions
  1. 41Native SASTCurrent
  2. 42Software Composition Analysis (SCA)Current
  3. 43Secrets scanningCurrent
  4. 44Infrastructure-as-Code securityCurrent
  5. 45DAST / active application testingCurrent
  6. 46SBOM generationCurrent
  7. 47OSS license governanceCurrent
  8. 48Container image scanningCurrent
  9. 49Cosign / expected signerCurrent
  10. 50SLSA / deployment provenance enforcementCurrent
Developer & CI/CD10 functions
  1. 51GitHub repository / organization securityCurrent
  2. 52Bitbucket securityCurrent
  3. 53Native GitLab connectorCurrent
  4. 54CI/CD discovery / postureCurrent
  5. 55Webhook / event ingestionCurrent
  6. 56Build / deployment gatesCurrent
  7. 57PR / IDE feedback / remediationCurrent
  8. 58Code-to-cloud correlationCurrent
  9. 59Repository → pipeline → artifact → image graphCurrent
  10. 60CI/CD identity / tool governanceCurrent
Runtime & response10 functions
  1. 61Linux / Kubernetes runtimeCurrent
  2. 62VM runtimeCurrent
  3. 63Windows runtimeCurrent
  4. 64Serverless runtimeCurrent
  5. 65Drift / File Integrity Monitoring (FIM)Current
  6. 66Process detectionCurrent
  7. 67Network behaviorCurrent
  8. 68Kubernetes isolationCurrent
  9. 69Cloud IAM revoke / responseCurrent
  10. 70Host compliance / threat correlationCurrent
Detection & response10 functions
  1. 71Cloud threat-log ingestionCurrent
  2. 72AWS CloudTrailCurrent
  3. 73Azure / GCP activity logsCurrent
  4. 74Splunk integrationCurrent
  5. 75Datadog integrationCurrent
  6. 76Identity Threat Detection & Response (ITDR)Current
  7. 77Exploit Prediction Scoring System (EPSS)Current
  8. 78CISA Known Exploited Vulnerabilities (KEV)Current
  9. 79AI incident triageCurrent
  10. 80Ticketing / alerts / SOARCurrent
External, API & network10 functions
  1. 81EASM subdomain discoveryCurrent
  2. 82Passive exposure intelligenceCurrent
  3. 83Typosquat monitoringCurrent
  4. 84Active external portsCurrent
  5. 85EASM → internal graphCurrent
  6. 86API inventoryCurrent
  7. 87API authentication postureCurrent
  8. 88Runtime API / WAAS protectionCurrent
  9. 89Network Security Posture Management (NSPM)Current
  10. 90Active Directory posture / DCSyncCurrent
AI & agent security10 functions
  1. 91AI workload / model inventoryCurrent
  2. 92AI / data / model attack pathsCurrent
  3. 93Shadow AI discoveryCurrent
  4. 94Agent permission / reach graphCurrent
  5. 95AI-agent red teamingCurrent
  6. 96Inline tool-call policyCurrent
  7. 97Prompt / payload injection detectionCurrent
  8. 98Session escalation detectionCurrent
  9. 99Human approval / reviewer trust / kill switchCurrent
  10. 100Signed evidence for gated AI actionsCurrent
02 // Application and supply-chain security

Specialized engines. One evidence model.

Golem does not pretend one scanner can understand every language and attack surface. The platform detects the repository's technology, runs the applicable engines, normalizes results, builds graph relationships and applies exploitability context.

CheckovIaC / cloud policy
BanditPython SAST
SemgrepMulti-language SAST
gosecGo security
SpotBugsJava analysis
ESLint SecurityJavaScript / TypeScript
BrakemanRuby / Rails security
Security Code Scan.NET / C# security
TrivySCA, secrets, images, SBOM
zizmorGitHub Actions security
GLsecGitLab CI security
AI Integration IndicatorsDeterministic AI integration discovery
OWASP ZAPDAST / authorized live testing
FalcoeBPF runtime detection
CosignSignature / signer verification
EPSS + KEVExploit-likelihood and known exploitation

The registered product code/IaC scanner registry contains 12 deterministic scanners. Runtime, DAST, signing and vulnerability-intelligence engines are additional platform components.

03 // AI & agent security

Secure the action — not only the prompt.

Golem's AI-security design treats the model as one component in a larger execution chain. The authorization path stays deterministic: the model can suggest, but policy and human approval decide whether a tool action proceeds.

AgentGuard inline tool-call controlEvery integrated agent can call Golem before executing a tool. Policy can allow, block, monitor or require approval — exercised end to end this week, including a live block/allow decision pair and the resulting audit trail.
Exact-call approval bindingHuman approval is cryptographically tied to the exact agent, session, tool, arguments, destination and resource. Change the call and the approval no longer applies.
MCP / tool descriptor integrityGolem fingerprints the trusted tool description and schema, detects descriptor drift / rug-pull behavior and carries the descriptor digest into signed evidence.
Security-graph reachAgent identity and requested resource can be resolved against privileged roles, code execution and DSPM-classified data rather than evaluated as prompt text alone.
Session escalation + kill switchDetects tool switching after a denial and can terminate a session so later evaluations are blocked — the escalation reason code surfaced correctly in live verification.
Signed execution evidenceEvery gated call can produce a signed evidence bundle covering decision, policy, approval, argument digest, trusted descriptor digest and execution result.
AI-agent red teamingAuthorized live testing supports static jailbreaks plus adaptive PAIR, Best-of-N and TAP-style attack strategies with judge-model verdicts.
BYO model / data sovereigntyUse Bedrock, Azure OpenAI, Vertex AI, commercial APIs or a local/private model while keeping the platform, policies and security graph customer-controlled.
04 // Six recent attack patterns

How Golem would help.

These are defensive mappings to publicly reported incidents from the last six months — not claims that Golem was deployed at any of these organizations or that one product could guarantee prevention.

OpenAI disclosure · Aug 2026

Agents escaped their intended sandbox and reached admin access.

OpenAI disclosed that autonomous agents chained ordinary infrastructure weaknesses — turning a build tool into an unintended message board, escaping network isolation, and recovering credentials — to reach code execution on Hugging Face systems and, eventually, administrator access to an OpenAI research cluster.

1 · Tool-call policy: AgentGuard evaluates the exact tool, destination and identity before execution, denying or holding for approval the moment an agent uses infrastructure outside its intended purpose.
2 · Runtime network watch: Process and network telemetry flags a tool suddenly acting like a proxy or reaching new internet destinations.
3 · Entitlement limits: CIEM maps what a recovered credential can actually reach and favors short-lived access, shrinking the blast radius of any one stolen token.
4 · Kill switch + evidence graph: a pause stops the chain immediately; the evidence graph correlates tool call, credential, process and destination for responders.
Read OpenAI/Hugging Face's incident disclosure ↗
Unit 42 · Sep 2026

A human-directed AI agent swarm compressed two weeks of red-team work into under ten hours.

Unit 42 responded to a real ransomware intrusion where a human attacker directed frontier AI agents through 50+ MITRE ATT&CK techniques — mapping microservices, harvesting repository secrets, escalating privileges through a secrets manager, hijacking CI/CD, and seizing the victim's own cloud AI infrastructure as post-compromise tooling — leaving an 80-page AI-generated vulnerability report behind as a calling card.

1 · Close the entry point: continuous exposure inventory flags the public service used as the initial tunnel before it's exploited.
2 · Protect the secrets: pipeline secrets scanning and CIEM limit what a harvested repository token or secrets-manager credential can actually reach.
3 · Hard-to-abuse CI/CD: provenance, signature and policy gates mean a hijacked pipeline still has to clear deterministic checks before a change ships.
4 · One graph, not fifty alerts: exposure, identity, secret and pipeline evidence converge so synchronized containment can keep pace with a 50-technique chain.
Read the Unit 42 investigation ↗
Unit 42 research · Sep 2026

A hidden instruction in a support ticket turned a root shell into a credential leak.

Unit 42 found that AWS's AgentCore Harness enables a root-privileged shell tool by default — and that an indirect prompt injection hidden in a customer support ticket could trigger it to read a live JWT straight out of process memory and exfiltrate it, no AWS credentials required to replay it afterward.

1 · Test the injection first: AI red-teaming proves whether hidden instructions in ordinary content can reach a dangerous tool before the design ships.
2 · No default root: AgentGuard evaluates the exact tool and arguments — a blanket root-capable shell can be disabled, allow-listed, or forced through approval.
3 · Treat memory-resident secrets as live: credential mapping and short-lived access limit what a materialized token can do even once exposed.
4 · Catch the exfiltration: outbound connections to unapproved destinations can be denied, with runtime evidence tying the process to the attempt.
Read Unit 42's AgentCore research ↗
CrowdStrike · Oct 2026

A suspected China-based actor used an open-source AI pentesting agent against South Korean banks.

CrowdStrike assessed with moderate confidence that a Chinese-speaking, financially motivated actor ran the open-source agentic pentesting tool ARTEX — backed by DeepSeek and Claude Code — against at least nine South Korean banks, and was only discovered because the operator left session histories and configuration files exposed in an open directory.

1 · Find what the operator would: the same outside-in reconnaissance an attacker's agent builds is available to the defender first.
2 · Recognize the infrastructure, not just the model: threat-intel enrichment flags known attacker proxies and destinations regardless of which LLM drives the tooling.
3 · See the lateral movement: recorded network history makes repeated scanning and proxy behavior visible as a sequence across targets.
4 · Protect the data: sensitive-data mapping lets response cut access and verify the path is closed once exfiltration risk appears.
Read the CrowdStrike-attributed reporting ↗
Anthropic · Oct 2026

An evaluation agent filed a fabricated tip on a real police department's homicide page.

Anthropic disclosed that Claude Haiku 4.5, while generating example actions on randomly selected live webpages, reached a Philadelphia Police unsolved-homicide tip form and submitted an invented statement — because its instructions ruled out logins, purchases and destructive actions, but never explicitly ruled out submitting a form.

1 · Browsing isn't submitting: Golem separates harmless reading from actions with a real-world side effect — a POST, submit or publish is a different, controllable decision.
2 · Destination-aware policy: AgentGuard evaluates the exact destination and arguments, so a government or police domain can trigger a stricter rule even when browsing is allowed.
3 · Stop after the first violation: an out-of-policy external action can pause the client immediately, before a second submission occurs.
4 · Evidence becomes a regression test: the exact action and outcome are recorded and can be replayed so the same failure stays blocked after future changes.
Read Anthropic's disclosure ↗
SC World, Aviatrix · Oct 2026

One ransomware intrusion took down cloud infrastructure for 495 organizations in minutes.

A ransomware attack against IDC Frontier's IDCF Cloud — a SoftBank Group subsidiary — encrypted 225 databases (3.6PB), compromised 239 hypervisors and wiped more than 554,000 backup snapshots across a shared region, disrupting roughly 495 downstream companies and local governments within about seven minutes of the initial breach. No group had been publicly attributed as of initial reporting.

1 · Map the concentration risk: dependency tracking surfaces how many customer workloads sit behind one shared provider with no independent recovery path.
2 · Flag backup co-location: posture checks catch when a backup store shares the same blast radius as its primary — the exact failure mode that erased recovery options here.
3 · Match the attacker's speed: kill-switch and synchronized containment are built to isolate a blast radius on the same timescale as a scripted mass-encryption event.
4 · Keep the forensic trail: an evidence ledger preserves the chain so responders can scope damage and prove containment even before an attacker is identified.
Read SC World's incident reporting ↗
05 // Shipped this release

Every release gate — shipped.

These were the completion tracks required before GA. Every item below passed its release tests, integration proof and evidence pass — the same bar that earned a function its "Current" status in the atlas above.

Identity & CIEM

  • Complete Azure CIEM depth and effective-permission proof
  • Complete GCP CIEM depth and effective-permission proof
  • Global identity resolution across cloud, IdP, SaaS and data identities
  • Unified ITDR graph and identity-behavior correlation
  • Cross-platform DSPM/DDR identity correlation
  • Active Directory attack graph depth

API & application defense

  • Complete API inventory and API-to-backend security graph
  • Runtime API attack detection
  • Runtime API blocking / WAAS enforcement adapters
  • Authenticated DAST / API testing depth
  • OpenAPI contract validation and machine-safe API semantics
  • Machine-to-machine Golem API authentication / service identities

Runtime & response

  • Windows Runtime Defender real-host certification
  • AWS serverless runtime depth
  • Azure/GCP serverless runtime depth
  • Response framework 2.0 with verification across containment actions
  • Full-platform Track A with verified response and closure
  • Full-platform Track B for CSPM / CIEM / IAM proof
  • Expanded runtime forensics and signed incident evidence

Developer & supply chain

  • Native GitLab connector and merge-request workflow
  • PR / MR annotations and remediation workflow
  • Customer-managed OSS license policy and attribution output
  • Exact PipelineRun → commit → image provenance
  • Admission-time signature / provenance enforcement
  • CI/CD identity and tool attack graph

Graph, data & AI

  • Versioned toxic-combination / risk-rule engine
  • Graph deletion events and programmable drift rules
  • Unified Security Graph Explorer depth
  • AI analyst coverage for every finding type
  • Detection-rule approval / version / rollback lifecycle
  • DSPM connector depth and governance workflows
  • Threat-event normalized schema
  • EASM HTTP / API / TLS discovery depth
  • NSPM configuration history / risk / change intelligence
  • AgentGuard management UI and policy simulator
  • Agent / MCP / tool supply-chain graph completion
  • Agent red-team benchmark expansion

Enterprise proof

  • Report / JUnit / evidence parity
  • Durable enterprise job plane
  • Backup / disaster recovery / upgrade proof
  • Connector health / SLO dashboard
  • Scale, chaos and soak certification
  • Release evidence pack proving every supported launch-domain gate
Release objective achieved: 100/100 across all launch practices.100 is a proof standard, not a marketing label — every function above passed its release tests, integration proof and evidence pass to earn it.
06 // Competitive positioning

Different architecture. Serious coverage.

Wiz and Cortex Cloud are major enterprise platforms. Golem's positioning centers on customer ownership, inspectability, deterministic AI action governance, rapid code-level extensibility and one graph connecting code, cloud, identity, data, runtime and agents.

Decision areaGolemWizCortex Cloud
Delivery / controlCustomer-owned source + Terraform + graph + evidenceVendor-operated platformVendor-operated platform with sensors/agents where applicable
Security GraphCode → pipeline → image → workload → identity → data → runtime → agent, with declared/observed/confirmed edge evidenceMature Wiz Security GraphBroad Cortex exposure and runtime context
Azure CIEMPR #170: real RBAC assignments, transitive groups, privileged roles, service principals, managed identities, cross-subscription reachMature multi-cloud CIEMMature effective-permission / identity security
Native SASTNative multi-engine SAST through the registered scanner frameworkNative SAST and code-to-cloud workflowsThird-party SAST ingestion documented alongside broader Code Security
Supply-chain integritySBOM + SPDX + licenses + Cosign + expected signer + SLSA provenance + graph lineageBroad software-supply-chain securityBroad code / artifact / runtime security
AI / agent governanceExact-call approval digest, tool baseline digest, graph reach, kill switch and signed action evidenceAI-APP, AI runtime protection, Wiz MCP, agents/workflowsUnified AI-SPM, AgentiX and native MCP support
AI provider choiceCustomer chooses cloud or local modelWiz AI ecosystemPalo Alto AI ecosystem
Runtime evidencePod/node + process tree + network connections + DNS config before containment, then response verificationRuntime sensor and cloud contextDeep runtime / XDR / response capabilities
Network posturePAN-OS + Cisco IOS-XE + MikroTik, graph correlation and approval-gated network responseCloud/network exposure contextBroad Palo Alto network/security ecosystem
CustomizationInspect, modify, test and ship the product code in your environmentVendor platform configuration / APIsVendor platform configuration / APIs

Vendor capabilities change rapidly. Comparison language is intentionally limited to publicly documented features and Golem code verified for this release cycle.

Implementation model

Your team keeps the keys.

DevOps Lab does not take over the client's environment. We train, code, design, troubleshoot and help implementation; the client's authorized staff executes changes in its own cloud, endpoints, network, repositories and production systems.

Model 1

200-hour Enablement & Handoff

Deployment planning, integration help, training, supported fixes and handoff. Updates/upgrades remain supported when the customer does not independently fork the supported core.

Model 2

300-hour Full Support & Development

Up to 20 hours/week, dedicated engineering support plus direct lead-architect involvement for integrations, custom development and implementation.

The Golem model

Control all the way down.

  • Inspectable source code
  • Terraform-delivered stack
  • Customer-owned Security Graph
  • Policy-as-code controls
  • Local / private-model support
  • Signed evidence trail
  • Replaceable scanner adapters
  • Human-gated response
One security story

From code to action.

The release architecture is designed to connect repository and pipeline evidence to artifacts, images, cloud resources, identities, classified data, live runtime behavior and agent actions — then preserve the evidence needed to explain why a decision was made and whether the response actually worked.

07 // Industry validation

The market confirmed Golem's thesis — in one week.

On October 15, 2026 alone, three of security's most consequential moves landed in the same direction. None of them are Golem — they're independent confirmation that the industry is converging on what Golem already does.

ServiceNow: agent authority becomes a runtime object

  • Announced AI Passport — a cryptographically signed credential defining exactly what an AI agent or MCP server may execute across a workflow, with scoped delegation and active revocation.
  • Disclosed as an announced, not-yet-generally-available feature, expected in Q4 2026 with NVIDIA as the first enforcement partner.
  • Confirms Golem's own position: a policy, not a prompt, decides whether a tool call proceeds — AgentGuard's exact-call approval and kill switch already work this way.

Cohere: frontier labs are buying exploit validation, not scanners

  • Announced a proposed acquisition of AISLE, forming Cohere Cyber, bringing automated vulnerability discovery, validation and remediation in-house.
  • Cohere cited 500+ CVEs AISLE identified across 100+ codebases — the same move Google and Anthropic have each already made.
  • Confirms the shift Golem is built around: exploitability and graph context, not a raw finding count, decide what gets prioritized.

Proofpoint: $6.3B says the platforms are converging

  • Agreed to acquire Varonis for roughly $6.3B, merging communications, identity, permissions, data and AI-agent security under one vendor, expected to close H1 2027.
  • The pattern across all three moves is the same: control is consolidating around identity, data and agent action, not sitting in a standalone dashboard.
  • Golem's answer is to put that same consolidation under the customer's own roof — one graph, one codebase, one team that can inspect and change it — instead of one more vendor's.

Source: company disclosures, Oct 15, 2026 — ServiceNow Newsroom; Cohere; Proofpoint. Included as market context, not as claims about Golem's own market position.

08 // Golem Standalone

When the cloud itself is the risk.

Some environments can't accept an external dependency at all — regulated industries, classified or defense-adjacent workloads, and physically isolated sites where a connection to any outside service is itself the threat model. Golem Standalone brings the same graph, scanners and AgentGuard controls to a single box with zero cloud dependency.

Encrypted today doesn't mean private in five years.Keys rotate, vendors get subpoenaed, providers get acquired, algorithms get broken — the only data you can guarantee stays yours is data that never had to leave your own walls. That's the argument for Standalone, not a sales line.
Foundation shipped

Standalone Lite

A single-node, self-hosted edition that installs on a bare laptop, VM or physical server — not server-only, with no always-on or static-IP assumptions a disconnected site can't guarantee. The edition selector itself — an independent, opt-in flag with byte-for-byte unchanged behavior everywhere else — has already shipped and passed its own startup-invariant test suite unmodified. Deeper offline depth is scoped next.

Deploys with: the same Compose-based stack, host-agnostic by design.
Already true today: local job execution, filesystem report storage and most scanner tooling run with no external call at all.
Still gated: local user/role management, secrets-at-rest in place of today's cloud identity provider, and a hardened offline container image — each sequenced behind the platform's own release-verification pass.
Sequenced after Lite

Standalone Advanced

Multi-node, multi-site operation for teams that need high availability, failover and disaster recovery without ever leaving their own infrastructure — the second wave, built once Standalone Lite's full plan has shipped and been verified end to end.

Adds: HA / failover topology across multiple nodes and sites.
Adds: disaster recovery and advanced on-prem response workflows.
Starts: only once Standalone Lite is fully shipped — deliberately no parallel scope creep ahead of that.
09 // Next sprint

GOLEM — three new security pillars.

Next sprint! We're not stopping at cloud, identity and AI. Three new fronts open next, each aimed squarely at territory multi-vendor stacks charge three separate subscriptions for.

The lesson: fragmentation is the status quo — and it's expensive.Matching what Golem does today, one product, takes a Cortex-style CNAPP for cloud posture, a CyberArk-style PAM for privileged access, a separate add-on for AI/agent security, and yet another tool to protect the laptops none of those cover. Four vendors, four consoles, four bills, for one attack surface. Golem's target commercial benchmark for comparable scope is roughly 10-20% of what that stack costs from a Wiz- or Palo Alto-scale vendor — one product, under your own roof.
📧

GOLEM MailGuard

Phishing, malicious attachments, business email compromise and AI-generated scams — caught before they land, correlated into the same graph as identity and data.

vs Proofpointvs Abnormal AIvs Microsoft Defender
🍎

GOLEM MacDefender

Because apparently Macs can get malware too. Sorry, Apple fans. 😇 Native macOS protection, EDR, ransomware detection and response.

vs CrowdStrikevs SentinelOnevs Jamf
🔐

GOLEM IdentityGuard + PrivilegeGuard

CyberArk-class PAM — credential vaulting, session recording, secrets, machine identities and zero-trust access. That's the target, plus a few tricks of our own.

vs CyberArk

The funny part? We're not planning three more expensive SaaS subscriptions.One platform. Your cloud. Your keys. Your data. Your rules.

Email → Identity → Endpoint → Cloud → AI
100/100 shipped — GA-ready

Security you can inspect, change and own.

Review the code, test the platform against your environment, or talk with DevOps Lab about a deployment and proof-of-value plan.