# Build vs Buy AI Agents for Security: What Decides It

Test four things before comparing cost: whether a product exists for the job, whether you can set its approval gate per action, whether you can export its logs, and whether the model can change without you knowing. As of 19 Nov 2026 the use-case map lists 28 vendors for triage but 2 for access reviews.

## What the published build accounts state

Three builders have published accounts, read 19 Nov 2026. None states headcount or engineer weeks, so the cost line below uses an assumed figure.

Quotations from each builder's post, read 19 Nov 2026.

| Builder | What it reports | Job |
|---|---|---|
| Google DeepMind (vendor), CodeMender | "Over the past six months that we've been building CodeMender, we have already upstreamed 72 security fixes to open source projects" | Code fixes |
| Slack Engineering (third party, describing its own tool) | A rudimentary prototype at the end of May 2025, "not much more than a 300 word prompt"; the service grew to use low, medium and high-cost models for its expert, critic and director roles | Alert investigation |
| Trail of Bits (third party) | The decompiler was the largest tooling effort: "over 100 AI-generated commits over multiple months"; "a failed side project only costs tokens" | Audit tooling, not triage |

Read across the rows: a prototype is a prompt and a few tools, and months are spent on what surrounds it. Slack's post adds that analyzing returned data "can be very token-intensive", so model spend and harness upkeep continue after launch. Sizing those is the job of the [cost guide](/guides/cost-of-running-security-agents/).

## Does a product exist for the job

Buying needs a product that does the job. The directory counts vendors with a published named agent for each of six jobs; a vendor covering several jobs counts in each. Counts are of published agents, not of quality.

Counted from the vendor lists in the use-case map as of 19 Nov 2026 (39 vendors in all, 69 listings).

| Job | Vendors with a published agent |
|---|---|
| Vulnerability triage and remediation | 28 |
| Code and dependency fixes | 16 |
| Response to a new disclosure | 10 |
| Cloud posture | 7 |
| Threat modeling | 6 |
| Access reviews | 2 |

Where two vendors exist, a buyer has little room to walk away from a gap in approval controls or logs, and the build option carries more weight. Where 28 exist, the other three tests do the sorting.

## Three tests on what you control

These tests apply to both routes. A build answers them by design; a buy answers them by contract and documentation. Write the answers down, then ask the supplier for the same in writing ([supplier controls when buying](/evaluation-checklist/supplier-controls-when-buying/) lists the questions).

| Test | If you build | If you buy: what to find out |
|---|---|---|
| Approval gate per action | You design which actions wait for a person | Whether each action can be set to automatic or approval. Aikido documents this per action (Fully Automated or Human Approval); for any other supplier, find the page that says so or ask |
| Logs and evidence | You choose where records live and who can edit them | Whether per-run records can be exported to a store the supplier cannot alter, and for how long |
| Model change | You pick the model and rerun your eval before switching | Whether the supplier tells you before the model or prompt changes, so your own rerun can happen first |

Building in parts keeps one option open. Anthropic describes separating the session log, the harness and the sandbox so that "the implementation of each" can "be swapped without disturbing the others" ([Scaling Managed Agents](https://www.anthropic.com/engineering/managed-agents)). A team that builds in that way can change the model later without rewriting the rest.

## A cost line with assumed figures

The arithmetic is engineer time against a licence. Every figure below is an assumption chosen for the example, not a quote or a measurement: replace them with your own. Token spend uses the Task A figure from the [cost guide](/guides/cost-of-running-security-agents/): $240 a month for 2,000 triage findings on Claude Sonnet 5.5. People are priced at $100 an hour, as on that page.

Invented inputs; the arithmetic is what carries over. Token figure from the cost guide, read 19 Nov 2026.

| Line | Build | Buy |
|---|---|---|
| One-off work | 8 weeks x 40 hours x $100 = $32,000 (one engineer, to a first production version) | 40 hours of integration x $100 = $4,000 |
| Yearly upkeep | 4 hours a week x 52 x $100 = $20,800 (prompt, tools, eval reruns, model changes) | None assumed beyond the licence |
| Yearly tokens | $240 x 12 = $2,880 | Inside the licence (assumed) |
| Licence | None | $48,000 a year (invented; replace with the supplier's quote) |
| Year one | $32,000 + $20,800 + $2,880 = $55,680 | $4,000 + $48,000 = $52,000 |
| Each later year | $20,800 + $2,880 = $23,680 | $48,000 |

On these inputs buying is $3,680 cheaper in year one and building is $24,320 cheaper in each later year. The licence at which year one is level is $55,680 - $4,000 = $51,680. A cheaper line is worth taking only when the option also passes the pilot below: a licence that fails the gate costs the full year for nothing, and a build that fails costs the $32,000. Replace these figures with your measured review minutes and your quote.

## A worked decision: a pilot with dates

Assume a six-person security team that wants an agent for vulnerability triage. A bought candidate that passes the first two tests exists, and the team is unsure about building. The pilot runs on the same findings for both routes so that the result, not the pitch, decides. A person labels 40 findings from the team's own backlog. Half, 20 findings, are the development set used to tune; the other 20 are held back and frozen, and the gate runs on those 20 only ([how to build the set](/guides/evaluate-a-security-agent-on-your-findings/)).

1. 30 Nov to 4 Dec 2026: label the 40 findings with the right outcome, split them 20 and 20, and write the gate before any run.
2. 7 Dec to 10 Dec: run the bought candidate and a prototype built from a short prompt and three read-only tools on the 20 development findings; tune prompts, tools and settings. 11 Dec: freeze both versions.
3. 14 Dec: run each frozen version on the 20 held-back findings, 3 trials each (60 trials per route), apply the gate as in [AI agent evals](/guides/ai-agent-evals/), and record minutes of human checking per accepted change.
4. 18 Dec: decide from the table below. Use the measured minutes in place of the assumed ones before anyone quotes a payback.

Decision table for the pilot. Dates are the example's.

| Result on the held-back 20 | Supplier meets the three control tests? | Decision |
|---|---|---|
| Bought candidate passes; prototype fails | Yes | Buy. Put the three control tests into the contract |
| Bought candidate passes; prototype fails | No | Buy only with the missing clauses written in; if the supplier refuses, do not deploy |
| Both pass | Yes | Take the lower year-one and later-year cost from the cost line above, using the measured review minutes |
| Both pass | No | Build, or buy only with those clauses written in |
| Prototype passes; no product passes | Not applicable | Build, and take the harness items on the [harness page](/agent-harness/) as the project plan |
| Neither passes | Not applicable | Do not deploy either. Keep the 40 findings as the next trial set |

The pilot leaves one record, kept with the run logs: the frozen model ID, prompt and tool list for each route; the 40 labels with the split; the 60 trial outcomes per route; minutes of human checking per accepted change; the gate as written before the runs; and the decision with its date and the name of who made it.

## Sources

- [Google DeepMind, Introducing CodeMender](https://deepmind.google/discover/blog/introducing-codemender-an-ai-agent-for-code-security/), read 19 Nov 2026
- [Slack Engineering, security investigations with agents](https://slack.engineering/streamlining-security-investigations-with-agents/), read 19 Nov 2026
- [Trail of Bits, Auditing in the age of good enough AI (18 September 2026)](https://blog.trailofbits.com/2026/09/18/auditing-in-the-age-of-good-enough-ai/), read 19 Nov 2026
- [Anthropic, Scaling Managed Agents](https://www.anthropic.com/engineering/managed-agents), read 19 Nov 2026
- [Aikido, CVE Exploitability Analysis (help center)](https://help.aikido.dev/aikido-agent/cve-exploitability-analysis.md), read 19 Nov 2026

Last reviewed 19 Nov 2026

Canonical: https://agenticaiincybersecurity.com/guides/build-vs-buy-ai-agents/
