The architecture features a CLI that interacts with a backend orchestrator, which manages various testing components known as emissaries. These emissaries, such as Owasp zap and nikto, are dynamically spun up based on job files and routes provided by the user. Utilizing AWS Lambda and Redis for messaging, the system is designed for flexibility, allowing the community to contribute additional testers as needed.
