Customer stories

How security teams use EDAMAME to protect repositories, CI runners, and internal apps — while accelerating humans.

How Northbridge built deeper enterprise trust with developer-first Endpoint Security

Northbridge

US

Tech

Northbridge is building innovative solutions for modern enterprises. As it moved up‑market, it strengthened endpoint assurance for enterprise reviews—without deploying traditional MDM—by pairing EDAMAME with its existing SOC 2 + Vanta compliance backbone.

Vanta, SSO/IdP, company endpoints (key roles)

“Vanta is great for SOC 2 and frameworks. But customers were clearly looking for stronger, more detailed controls on the laptops and machines people actually use every day. We wanted to be able to answer with real‑time data—not just policy language.”

Driving innovation in safety equipment data with fully secured code and pipelines

PPE analytics

EU

Tech

PPE analytics is a Paris-based platform for the safety equipment (EPI) market. As it scaled to major customers, it secured laptops, repos, and GitLab CI/CD with developer-first Zero Trust—without MDM or productivity-killing lockdowns.

Linux Mint, GitLab, GitLab CI/CD

“Our platform’s credibility hinges on trust. We manage sensitive product data for our clients, so protecting our code and infrastructure is non-negotiable. At the same time, I didn’t want to shackle our engineers with heavy-handed controls that slow them down.”

Success story: A robotics company closes the token loophole with developer-first Zero Trust

A fast-growing robotics company

US

Tech

A fast-growing robotics company protected source code and CI/CD by closing the “token loophole” in traditional device trust—using EDAMAME to continuously verify device posture on every Git interaction, without slowing developers.

GitHub Enterprise, device-trust IdP, macOS + Linux endpoints

“It’s night and day — we went from hoping our device checks worked to knowing our code is untouchable from anything but a secure device.”

How a telecom software company secured self-hosted, VPN-based pipelines with device-aware Zero Trust

A telecom software company

EU

Tech

An anonymized telecom software company secured a self-hosted GitLab pipeline behind a mesh VPN—then added EDAMAME to make the VPN conditional on continuously verified device posture across dev laptops and CI runners.

Self-hosted GitLab, Alpine Linux CI runners, mesh VPN (NetBird)

“A VPN gives you network isolation, but it doesn’t tell you whether the device itself should be trusted.”

How an automotive company covered what its EDR could not: AI agents and the software supply chain, side by side with Netskope

AutoRobots

EU

Tech

AutoRobots, an automotive company, was told by incumbent vendors that their EDR already covered AI agents. It did not. The company deployed EDAMAME side by side with Netskope to catch software supply-chain attacks as behavior and to cover the new AI agent attack surface on the endpoint.

Netskope, existing EDR, EDAMAME Security, EDAMAME Hub

“Every incumbent vendor told us their EDR already covered AI agents. It didn’t — not what the agents do with our engineers’ access, and not a poisoned package that only misbehaves after it installs. EDAMAME runs next to our EDR and Netskope and closes exactly that gap.”

How a telecom hardware vendor governs Claude Code and Codex across engineering, sales and marketing

Communitech

EU

Tech

Communitech, a telecom hardware vendor, standardized on Claude Code for its developers and Codex for sales and marketing. Its CISO used EDAMAME to govern how every agent uses tools — MCP servers and high-reach commands such as ssh, docker and shells — company-wide, and to bind access to that evidence through the company's ZTNA.

Claude Code, OpenAI Codex CLI, MCP servers, ZTNA conditional access, EDAMAME Security, EDAMAME Hub

“Claude Code for engineering and Codex for sales and marketing arrived faster than any policy could follow. EDAMAME let us say yes to both: we see every agent, the MCP servers and commands it uses, and our ZTNA only grants access while a machine and its agents stay within policy.”