Clues to your original code
Source maps connect compressed code to original files. Public maps can make the structure easier to understand.
Inspect and remove public source mapsChoose your project folder to check for exposed source files and secret patterns.
Get a clear path from analysis to protection and post-deployment checks.
my-first-project
Find files with original source
and potential secret patterns.
Back up your configuration
and create a protective build.
Check public files again
using your live website URL.
Websites send some code to visitors to display the page.
Original source files or accidental secrets can give analysis and imitation a head start.
Source maps connect compressed code to original files. Public maps can make the structure easier to understand.
Inspect and remove public source mapsServer secrets can accidentally end up in public files. Pattern checks highlight the places you need to review.
Secret pattern checks and review pointsYour live site may differ from your local settings. Check its public files and security headers after deployment.
Live website checks and next stepsReverse engineering tools such as REA can inspect public code and behavior. REAShield reduces unnecessary exposure and makes analysis harder. It cannot prevent all visual cloning or reverse engineering.
Start with your website’s original project folder.
See what to do next, with a guided workflow.
Run the Windows installer. Sign in with the account you used to pay to access your license.
Download and open the appChoose your original folder with “Connect project”. Review the findings and create a supported protective build.
Analyze → back up → buildReview the result, then deploy through your existing host. Enter the live URL to check public exposure again.
Deploy with your hosting providerAnalysis and protective builds run on your PC. A website URL alone cannot modify a website.
Every plan includes the same protection capabilities.
Choose the project capacity and access period you need.
For your first website
For multiple projects
For everything you keep building
Project limits apply across your account. Sign in to pay with PayApp or PayPal.
Public source map cleanup, secret pattern checks, configuration backups, supported protective builds and post-deployment checks. Vite supports optional code obfuscation.
Keep core logic on the server, authorize API access, and configure production request limits and bot protection. The report shows applicable scope for Next.js and static sites.
No. Visuals and code delivered to a browser remain observable. REAShield checks for exposed source maps and secret patterns, and applies supported protective builds to reduce unnecessary exposure and make code analysis harder. Core features and data still need server-side authorization.
All plans include the same protection capabilities. Starter covers 1 project for 30 days, Studio covers 3 projects for 90 days, and Annual has no project cap for 365 days. Device limits are 2, 3 and 5 respectively. Choose based on project capacity and duration.
Install the Windows program and select your project folder. REAShield detects the environment and guides you through analysis and protective builds. Installing project dependencies, designing server security, and deploying through your hosting provider may still require development knowledge.
Vite web projects support protective builds and optional JavaScript obfuscation. Next.js supports cleanup of public static source maps. Static web files can also be inspected; your report identifies the applicable scope. Native apps and executable binaries are outside this product’s current protection scope.
Source analysis and protective builds run on your computer. The server manages account, license, registered-device and project identifiers needed to operate the service. Post-deployment checks request the public page and a limited set of public static files at the URL you provide.
REAShield backs up configuration before making changes and records the change history. You can restore it from the workspace. Review the protected build locally before deployment, then enter your live URL to check public source maps and security headers.
Start by seeing what your project could be exposing.
Start protecting my projectWindows · free analysis · a license is required for protection and builds