Hermes 原生加固路径 · 本地运行 · 先计划再执行Hermes-native hardening path · Runs locally · Plan first before apply
Hermes 常见问题 购买、升级和运行前最常问的事项
Hermes FAQ The questions people ask before they buy, upgrade, or run it
如果你在 Lite 和 Core 之间犹豫,或者想先确认付款、边界和恢复路径,这一页会把最关键的问题讲清楚。
If you are deciding between Lite and Core, or you want payment, boundary, and restore-path questions answered first, this page is the fastest place to start.
Lite is enough when you still need clarity. It stops being enough when you already know the issues exist and you are still pushing remediation forward by hand. It does not execute the remediation, backup, or restore path for you.
Because the paid value is not another findings pass. Core reduces hand-edit churn, rollback risk, and memory-based recovery. You are buying a steadier execution path, not repeated diagnosis.
不是。Core 的价值是把能稳定处理的动作做短、做稳、做可恢复。它不是万能自动修复器。
No. Core is built to make the remediation work that can be handled safely shorter, steadier, and recoverable. It is not a universal auto-fixer.
不会。当前公开边界是本地执行、零默认联网、零默认回传。它不是把环境转交给远端代管的产品。
No. The public boundary is local execution, zero default network behaviour, and zero default call-back design. It is not a product that transfers runtime control to a hosted service.
Because real remediation is not just “change the file and move on.” It has to account for mistakes, rollback, and repeatability. Automation without recovery is not worth trusting.
当前直接数字购买路径下,付款确认后会发送交付说明与下载方式。具体支付方式以购买页为准。
Under the current direct digital purchase path, delivery instructions and access details are sent after payment confirmation. The exact payment path is defined on the order page.
Please use the refunds page first. Technical, delivery, or download issues should be raised with support@m78armor.com before refund handling is considered.