Security teams

# Investigate the code   from more directions.

Use a fleet to explore your authorized test environment, reproduce defects and develop regression tests.

Built around your project

## More approaches.  Working at once.

Give agents the repositories, test fixtures and boundaries for the investigation. They can explore independent areas, share reproducible failures and develop changes for your specialists to review.

01 

## Software correctness

Explore edge cases, reproduce failures and develop regression tests.
[Put a fleet on it ](/use-cases/software-correctness/) 

02 

## Agent evaluation

Investigate traces and develop code changes for recurring failures.
[Put a fleet on it ](/use-cases/agent-evaluation/) 

03 

## Technical exploration

Build working tests of the approaches you are considering.
[Put a fleet on it ](/use-cases/technical-diligence/) 

## Work that returns  to your team.

Your existing agent brings back code, tests and findings from the fleet. Review the changes in the project where you need them, then choose what to ship or investigate next.
[See work from real fleet runs ](/examples/) 

## Put a fleet on your project.

256 agents. Four hours. $1,000 for your first run, with model inference, computers and fleet operation included.

[Explore your first fleet ](/first-fleet/) [Ask your agent what to run ](/evaluate/)