Racks built for agents, AI code breaking production, and a quantum firm buys agent security
AMD unveiled a rack designed around AI agents rather than model training, a survey of 300 engineering leaders found AI coding tools behind most recent production incidents, and IonQ agreed to buy a zero-trust company that controls what AI agents can talk to. Agents are now shaping hardware, software quality and security deals alike.
Key takeaways
- AMD's Helion rack packs up to 32,768 Zen 6 cores for agent workloads, with an enterprise version adding up to 16 MI350P GPUs.
- 81% of 300 engineering leaders reported an AI-coding-linked production incident in six months, and engineers now spend 16.9 hours a week debugging.
- IonQ will pay up to $1.3B in stock for Elisity, whose zero-trust platform governs users, devices and AI agents on enterprise networks.
AMD unveils Helion, an open rack design built for AI agents with up to 32,768 CPU cores
At the OCP Global Summit in San Jose on October 12, AMD CEO Lisa Su unveiled Helion, an open rack reference design for agentic AI. It comes as a CPU-only hyperscale version with up to 32,768 Zen 6 cores, or an enterprise version that adds up to 16 Instinct MI350P GPUs.
AMD unveiled Helion on October 12 at the Open Compute Project Global Summit in San Jose. CEO Lisa Su presented it as a rack reference design for agentic AI that extends Helios, AMD's GPU-heavy rack-scale platform launched earlier this year. AMD plans to contribute the Helion specification to the Open Compute Project.
Helion comes in two configurations. The hyperscale version is CPU-only, with up to 32,768 Zen 6 cores from sixth-generation EPYC 'Venice' processors, and hands model inference off to separate accelerator racks. The enterprise version mixes EPYC CPU blades with up to 16 Instinct MI350P GPUs in a single rack, adding GPU capacity in pairs of 8-GPU servers.
Both use a 21-inch OCP ORv3 rack with standard modular compute boards, liquid or air cooling, up to 102Tbps of programmable networking and an open-source software stack. AMD described server types tuned for different agent workloads: dense 256-core servers for personal agents, balanced servers for enterprise agents and high-frequency 96-core servers for technical agents. Configurations from Cisco, Dell, HPE, Lenovo, Supermicro and others are expected from November.
Why CPUs? AI agents spend much of their time not running the model but doing everything around it: calling tools, running code, querying databases, browsing, waiting on APIs and orchestrating sub-tasks. That work runs on general-purpose cores. A rack designed around thousands of cores for agent 'busywork', with GPUs or separate racks for the model itself, reflects how agent workloads actually behave.
No independent benchmarks or detailed availability dates were published at launch. But Helion signals that hardware vendors now see agents as a distinct workload class, which will shape data-centre purchases, cloud instance types and software design over the next few years.
Why it mattersHardware is now being designed around how agents behave, with lots of tool calls and orchestration, which will change what AI infrastructure costs and how it's bought.
👀 What to watch
OEM pricing in November, cloud instances built on Helion, and how Nvidia and Intel position against CPU-heavy agent racks.
3 opportunities from this story
Agent workload profiling
Most companies don't know how much of their agent cost is model inference versus tool calls and orchestration. Offer profiling that measures where time and money go, and recommends cheaper infrastructure.
- Best for
- Performance engineers and cloud consultants
- First step this week
- Instrument one agent workflow and publish a breakdown of time spent in the model versus tools.
Open the full playbook
Launch steps
- Add tracing to an agent pipeline
- Separate model, tool and wait time
- Model infrastructure options
- Deliver a cost-saving plan
Tools
Risks
Clients may lack instrumentation. Bring ready-made tracing templates.
On-premises agent infrastructure for mid-sized firms
Enterprises with data-sovereignty needs will want agent racks on site. Become a reseller or integrator that designs, installs and supports agent-ready infrastructure for mid-sized companies.
- Best for
- IT integrators and MSPs
- First step this week
- Partner with one server OEM and prepare a reference design for a 'private agent cluster'.
Open the full playbook
Launch steps
- Get OEM partner status
- Design small, medium and large reference setups
- Bundle open-source agent software
- Sell support contracts
Tools
Risks
Capital-intensive and competitive. Specialise in one region or industry.
Agent infrastructure newsletter and buyer guides
Racks, CPU-versus-GPU decisions and agent workloads are confusing for buyers. Run a focused newsletter and publish buyer guides, monetised through sponsorships and consulting.
- Best for
- Industry analysts and tech writers
- First step this week
- Publish a comparison of AMD Helion, Nvidia and cloud options for agent workloads.
Open the full playbook
Launch steps
- Pick a clear audience (CIOs, infra leads)
- Publish weekly analysis
- Create downloadable buyer guides
- Sell sponsorships to vendors
Tools
Risks
Vendor sponsorship can look biased. Disclose clearly and keep analysis independent.
Survey: 81% of engineering leaders hit production incidents linked to AI coding tools
A survey of 300 senior engineering leaders at large US and UK companies, published by debugging vendor Undo, found 81% had a production incident or outage linked to AI coding tools in the past six months, and 93% said an AI hallucination had led to a misdiagnosed root cause.
AI coding tools are speeding up how fast code gets written, but not how fast it gets safely shipped. That's the conclusion of a survey published by Undo, a company that makes debugging tools, of 300 senior engineering leaders at large US and UK companies building mission-critical software. Questions were fielded in July and August 2026, and LeadDev reported the results.
The headline numbers are stark. 81% of leaders said their organisation had a production incident or outage linked to AI coding tools in the past six months. More than nine in ten reported serious defects, poorly optimised code or test escapes reaching production, and 93% said an AI hallucination had led their team to misdiagnose a root cause.
The productivity picture is mixed at best. 79% said their release cycles are no faster than before AI. Engineers now spend an average of 16.9 hours a week debugging versus 9.8 hours writing code, and 35% of AI-generated code reaches production before teams fully understand it. Undo's CTO Mark Williamson summed it up: AI has helped the input end of the pipeline a lot, the output end not so much, at times acting like a 'code machine gun'.
The survey comes from a vendor that sells debugging tools, so it has an interest in the problem, and it reports aggregate results rather than specific incidents. But the findings match a broader pattern: AI has moved the bottleneck from writing code to verifying, understanding and maintaining it, especially in long-lived systems full of undocumented assumptions.
The recommendation is to measure what matters, defect rates and time to resolution rather than lines of code produced. For businesses, it's a signal that review, testing and observability skills are rising in value just as code generation gets cheaper.
Why it mattersAs AI writes more code, the value shifts to the people and tools that verify it, which is where demand and budgets will follow.
👀 What to watch
Independent studies that confirm or challenge these numbers, and AI coding tools adding stronger built-in testing and verification.
3 opportunities from this story
AI-code review and hardening service
Teams shipping lots of AI-written code need experienced reviewers who catch subtle bugs before production. Offer a review-as-a-service retainer focused on AI-generated pull requests.
- Best for
- Senior developers and small consultancies
- First step this week
- Offer three free reviews of AI-generated pull requests and document the bugs you catch.
Open the full playbook
Launch steps
- Define a review checklist for AI-written code
- Set turnaround times
- Track defects caught
- Report value to the client monthly
Tools
Risks
Hard to scale personally. Build a small vetted reviewer network.
Engineering metrics dashboards for the AI era
Leaders are measuring the wrong things (lines of code, PR counts). Build a dashboard tracking defect rates, incidents and time-to-resolution, split by AI-assisted versus human-written changes.
- Best for
- Developer-tools builders
- First step this week
- Prototype a dashboard on a public repository's issues and pull requests.
Open the full playbook
Launch steps
- Integrate with Git and issue trackers
- Tag AI-assisted changes
- Calculate defect and resolution metrics
- Build executive summaries
Tools
Risks
Tagging AI-assisted code reliably is hard. Start with self-reported tags and commit metadata.
Training: debugging and verifying AI-written code
Engineers now spend more time debugging than writing. Create a practical course on reviewing, testing and debugging AI-generated code, including how to spot hallucinated APIs and false root causes.
- Best for
- Engineering educators and senior developers
- First step this week
- Publish a free checklist titled 'Seven bugs AI coding tools love to write'.
Open the full playbook
Launch steps
- Collect real examples of AI-introduced bugs
- Build hands-on exercises
- Record short lessons
- Sell team licences
Tools
Risks
Content dates quickly as tools improve. Focus on durable verification habits.
IonQ to buy Elisity for up to $1.3 billion to secure networks where AI agents roam
Quantum computing company IonQ agreed on October 12 to acquire Elisity, a zero-trust security firm whose platform controls which users, devices, workloads and AI agents can talk to each other, in an all-stock deal worth up to $1.3 billion.
IonQ, the quantum computing company, announced on October 12 that it will acquire Elisity, a zero-trust network security company, in an all-stock deal worth up to $1.3 billion, including up to $150 million in performance-based earnouts. The share count will be set at closing from a 20-day volume-weighted average price within a fixed range, and the deal is expected to close in the fourth quarter of 2026, subject to regulatory approval.
Elisity's platform applies least-privilege rules to control which users, devices, workloads and, increasingly, AI agents and other non-human identities can communicate on an enterprise network. Founded in 2019, Elisity says it has more than 100 customers, including a growing number of Fortune 500 companies. It will keep its leadership and brand after closing.
IonQ's rationale combines two security shifts. One is post-quantum cryptography: IonQ plans to pair its quantum-safe encryption and quantum key distribution work with Elisity's platform, extending Elisity's IdentityGraph with an inventory of cryptographic risk. The other is the explosion of non-human identities, as AI agents, bots and service accounts multiply inside corporate networks and each needs its own access rules.
IonQ also points to access to the microsegmentation market, which it sizes at more than $10 billion. Some secondary coverage reports rapid revenue growth at Elisity, but that comes from less authoritative sources than IonQ's own announcement and filing.
The deal is another sign that 'agent identity', meaning knowing what each AI agent is, what it may access and who it may talk to, is becoming a core security category. Expect more acquisitions as large vendors race to own the control layer for non-human identities.
Why it mattersAI agents are becoming network identities that need their own access rules, and security vendors are paying billion-dollar prices for that control layer.
👀 What to watch
Regulatory approval and closing, IonQ's integration roadmap, and further acquisitions in non-human identity security.
3 opportunities from this story
Non-human identity inventories
Most companies can't list all their AI agents, bots and service accounts, let alone their permissions. Offer an inventory and clean-up project that finds every non-human identity, its access and its owner.
- Best for
- Identity and access consultants
- First step this week
- Create a spreadsheet template for cataloguing non-human identities and run it with one client.
Open the full playbook
Launch steps
- Scan cloud accounts and SaaS apps for service identities
- Map each to an owner and purpose
- Remove unused or over-privileged accounts
- Set a review cadence
Tools
Risks
Discovery can be political across teams. Get an executive sponsor first.
Post-quantum readiness assessments
Regulators are pushing organisations to prepare for quantum-safe encryption. Offer a cryptographic inventory showing where vulnerable algorithms are used, with a phased migration plan.
- Best for
- Security consultants and cryptography specialists
- First step this week
- Publish a free 'post-quantum readiness checklist' for mid-sized companies.
Open the full playbook
Launch steps
- Learn the standard post-quantum algorithms and timelines
- Build a discovery approach for crypto usage
- Create a prioritised migration template
- Pilot with one client
Tools
Risks
Long sales cycles. Lead with regulated industries that face deadlines.
Agent access-policy templates
Teams deploying agents need ready-made least-privilege policies: what a support agent, a coding agent or a sales agent should be allowed to reach. Sell a library of policy templates and setup help.
- Best for
- Security engineers and DevOps freelancers
- First step this week
- Write and publish three free policy templates for common agent types.
Open the full playbook
Launch steps
- Define common agent roles
- Write least-privilege policies per role
- Map them to major cloud and network tools
- Sell packs with implementation help
Tools
Risks
Every environment differs. Price setup help as the main revenue, templates as the hook.
Get these as a PDF every 3 days
Free. One email every 3 days. Unsubscribe any time.