Legal
Security Disclaimer
Please read this carefully before relying on DeployReady's output. It defines what the tool can and cannot do for you.
DeployReady is not the final word on security
No guarantee of completeness
No automated scanner can detect every vulnerability. DeployReady checks for a defined set of common issues and patterns. A clean scan or a high readiness score means the checks it ran did not surface problems — it does not mean your application is free of security vulnerabilities, bugs, or compliance gaps.
Human review is required
You should always have a qualified security professional or experienced engineer review:
- The findings DeployReady reports
- Any code changes proposed by AI before applying them
- Your overall application architecture and threat model
- Compliance requirements specific to your industry or region
AI suggestions can be wrong
When AI features are enabled, explanations and proposed fixes are generated by language models. These outputs may be incomplete, inaccurate, or inappropriate for your specific context. DeployReady always requires your explicit approval before applying a change and creates a backup first, but the responsibility for reviewing and testing every change is yours.
You are responsible for your application
- Verify all findings and fixes independently
- Run your own tests after applying any change
- Use version control so changes can be reviewed and reverted
- Follow your organization’s security and compliance policies
No warranty
DeployReady is provided "as is" and "as available", without warranties of any kind, whether express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement. To the maximum extent permitted by law, Belsoft and its contributors are not liable for any damages, losses, or security incidents arising from your use of, or reliance on, DeployReady or its output.
Use against systems you own
Only run DeployReady — especially its dynamic testing features — against applications and systems that you own or are explicitly authorized to test. You are solely responsible for ensuring you have permission.
Questions?