Digital twin (service virtualization)
A behavioral copy of an external service, such as a payment or identity API, that agents and tests can call safely, repeatedly and at any volume.
Agents need to try things, and trying things against a real payment provider, CRM or identity system is slow, rate-limited, costly or dangerous. A digital twin reproduces the externally visible behavior of that service (its API, data shapes, errors and edge cases), so the agent can run thousands of attempts in an agent sandbox with repeatable results. The older name is service virtualization.
The StrongDM software factory calls its set of twins a Digital Twin Universe and runs its holdout scenarios against it. Coding agents have made twins cheaper to build, since a twin is mostly a well-specified API. The risk is drift: when the real service changes and the twin does not, everything passes and production fails.
Sources
- Wikipedia: Service virtualization en.wikipedia.org
- StrongDM: Software Factory techniques factory.strongdm.ai
Related terms
- Holdout scenarios: End-to-end user scenarios kept outside the codebase, so the coding agent never sees them and cannot write code that only passes the check.
- Agent sandbox: An isolated environment where an AI agent runs code and commands without access to your network, secrets or real files.
- Software factory (AI agents): A pipeline where agents write and fix most of the code while people write specs, set guardrails, design the checks and decide what ships.
- Validation loop (agent backpressure): Commands a coding agent runs after every change (tests, types, lint, build) and fixes against until they pass, so it checks itself before a person looks.
