# Customers | Chainsaw

> Case studies from teams running Chainsaw on the install path. Published only with written permission — no invented logos, names, or quotes.

Source: https://chain305.com/customers/

---

Customers

# Case studies are coming.

Teams run Chainsaw on the install path today. No customer name, logo or quote goes up without written permission, and none is invented to fill the page.

Want to be featured? A 30-minute story session; you review every word and can pull it any time.

[Book a demo →](https://cal.com/chain305/30min) [Be the first named case](mailto:sales@chain305.com?subject=Case%20study%20interest)

Want to see it on your stack?

## Fifteen minutes, your terminal, a real refused install

Bring a package manager. We point it at Chainsaw, run monitor mode against your repo and walk through what would have failed.

[Get started](https://chain305.com/chainsaw/signup) [Talk to sales](https://cal.com/chain305/30min)

---

## Long form

The full text behind this page, including detail the page itself leaves out.

Customers

### Case studies are coming.

Teams are running Chainsaw on the install path today. We won't publish a customer's name, logo, or quote without written permission, and we won't fabricate one to fill the page. The first named case study lands here once the paperwork is on file.

Want to be featured? The deal is simple: a 30-minute story session, you review every word before it ships, you can pull it any time. Email [sales@chain305.com](mailto:sales@chain305.com?subject=Case%20study%20interest) or book a demo below.

[Book a demo →](https://cal.com/chain305/30min) [Be the first named case](mailto:sales@chain305.com?subject=Case%20study%20interest)

What we can share now

#### Case shapes — anonymized until NDA-gated references unlock

Two procurement-relevant shapes from teams running Chainsaw on the install path today. No names, no logos, no fabricated quotes. Reference calls are available under NDA after MSA signature.

Case shape · Delivery / logistics holdco

##### European delivery platform, 25k engineers, 40 BUs

One org-wide policy set with repository-scoped rules, rolled out across business units. The proxy refuses on the install path; each refused install lands as a signed audit row in the shared evidence ledger. A Shai-Hulud-class compromise hit a peer the same quarter a customer security questionnaire asked how install-time package risk is prevented — that pair drove the rollout.

Representative deployment shape — illustrative, not a named customer.

Case shape · FinTech

##### FinTech, 8k engineers, EU residency-required

VPC deployment with EU-only data residency. The proxy enforces 25 supply-chain signals beyond CVE on every install path, with signed audit rows streamed to the in-region SIEM. One binary covers SaaS-equivalent functionality inside the customer's perimeter.

Representative deployment shape — illustrative, not a named customer.

Want to see it on your stack?

#### Fifteen minutes, your terminal, a real refused install

Bring a package manager. We'll point it at Chainsaw, run monitor mode against your repo, and walk you through what would have failed. No commitment, no slide deck.

[Get started](https://chain305.com/chainsaw/signup) [Talk to sales](https://cal.com/chain305/30min)