# What Blitzy announced Blitzy launched a free sandbox that lets eligible DevOps teams reverse-engineer large codebases and generate tested remediation or new code. The sandbox accepts up to one million lines of code and can produce up to 25,000 lines of end-to-end tested code at no cost.
# Insights works Blitzy's Proactive Insights platform brings three elements together:
- Thousands of automated agents working in parallel to build, validate, and test code.
- A knowledge graph that links architecture, dependencies, business logic, and data flows back to the source code.
The knowledge graph is queryable and continuously updates as the codebase changes. Known and newly discovered vulnerabilities are traced along execution paths, checked against dependencies, and assessed for fixability.
# What the sandbox produces Insights analyzes a codebase it produces:
- Vulnerability findings with reachability assessment (how likely the vulnerability is to be exercised).
- Risk-prioritized remediation recommendations.
- Generated remediation code and validated tests packaged as pull requests for human review and approval.
# Use cases the sandbox supports The sandbox is positioned for tasks common to DevOps and DevSecOps teams:
- Reverse-engineering undocumented legacy applications to understand structure and flows.
- Adding new features to existing systems using context-aware code generation.
- Upgrading services to modern frameworks while preserving behavior.
- dependencies.
# Security and compliance controls Blitzy states that customer code is never used to train its AI models. All data in the sandbox is encrypted in transit and at rest, a detail intended to support compliance requirements.
# Why Blitzy is offering a free sandbox now Blitzy says many DevSecOps teams are urgently hunting for vulnerabilities that could be discovered and exploited using AI tools. By offering a free trial environment, Blitzy aims to get its analysis and remediation workflow into more teams' hands so they can assess how the platform performs on real, large-scale codebases.
# How teams interact with results The platform automates much of the technical lift by having agents generate and test code in parallel. Final outputs are presented as pull requests organized by risk level. Human software engineers retain review-and-approval responsibility before changes reach production.
# Practical implications for teams Teams evaluating the sandbox should expect:
- A way to get a broad, architecture-level view quickly via the knowledge graph.
- Automated tracing of vulnerabilities to show whether an issue is actually reachable.
- Generated remediation that can reduce developer time to produce and test fixes, but still requires human review.
# Final note