From research question to evidence-backed finding
Anvil brings application context, experiments, agent work, and reporting into one workspace. Built by Danieloizo to keep complex security investigations connected and reviewable.
Sign inExplore Anvil
Investigate
Organize related requests and inspect their responses in the same workbench.
HTTP Forge
Request tabs, named request contexts, and response status stay visible together.
Live requests · sample product data. The selected search shows a 200 response while two unselected missing-product tabs retain 404 feedback.
Explore
Move from captured traffic to the endpoints and context that frame the next question.
Traffic Atlas
Inspect the recorded requests behind a route instead of treating the inventory as a flat list.
Sample workspace data. Expanded DummyJSON routes expose their recorded observations and response status codes.
Coordinate
Track review tasks and inspect agent discussions alongside the research context.
Plans and tasks
A task list keeps completed work and next steps easy to inspect.
Completed documentation tasks. Three Done tasks record the capture, comparison, and documentation work behind the product review.
Agent discussions
Use bounded discussions to compare the supplied evidence, question a conclusion, and prepare a handoff.
Completed agent discussion · supplied sample data. The evidence-review discussion separates the matching product fields from claims the supplied responses do not establish.
Review
Bring review records, their source context, and report drafts together.
Finding review
Keep the observation, expected behavior, and proposed follow-up beside the review status.
Illustrative finding · awaiting review. An illustrative UI-validation proposal keeps its context and review notes in one view.
Reports
Carry the observed result and its source trail into a report.
Observed sample-data review. The product review keeps its observed result, source trail, and decision together.