Natera’s SWARM automates lab instrument support
AWS reports that Natera built SWARM, an agentic AI system on Amazon Bedrock AgentCore, to capture institutional knowledge and support diagnostics for laboratory instruments. During a 90-day production evaluation, average first response time fell from 17.4 hours to roughly eight minutes, and 96.2% of incoming tickets received an automated diagnostic report before engineer review, according to Natera and AWS. The evaluation covered 524 tickets, but only 269 had confidence labels and engineer-verified resolutions available for comparison; the 37 low-confidence cases were too few for statistically meaningful conclusions.
The production case study documents how Natera used a structured skill library, managed agent runtimes and evaluation loop to address lab-support knowledge loss. It also highlights limitations in the available evaluation data and provides architectural patterns for similar operational workflows.
At Natera, a leader in cell-free DNA (cfDNA) testing, keeping lab instruments up and running is critical, because equipment downtime disrupts sample processing. Natera’s lab engineering team, led by Ariel Jirau worked with AWS to build SWARM (Systematic Workflow Analytics and Resolutions Manager), an agentic AI system for lab operations.
This post walks through how the Natera team built an agentic AI system for lab operations using Amazon Bedrock AgentCore that captures and deploys institutional knowledge at scale. It describes the full architecture, from knowledge base construction to automated system deployment and evaluation, so you can apply the same patterns to your own operational workflows.
SWARM delivers about 130x faster first response time and 96.2 percent automated coverage across support tickets, giving engineers immediate access to institutional knowledge the moment a ticket arrives.
The challenge: Knowledge continuity
Natera’s lab operations rely on a wide range of precision instruments spanning multiple equipment families, each with its own failure modes, vendor documentation, and resolution patterns. The service engineering team responsible for maintaining this infrastructure is organized around deep individual expertise rather than standardized playbooks. When a senior technician who had spent years diagnosing a particular instrument family departed, the institutional knowledge they carried was effectively lost. No system existed to capture, organize, or deploy that expertise at scale.
#Natera#SWARM#Amazon Bedrock AgentCore#Amazon Bedrock Knowledge Bases#Amazon DynamoDB#Amazon SQS#Amazon X-Ray#Amazon Titan Text Embeddings#AWS#Jira#Confluence