Eazfuscator.NET gained the ability to perform deterministic obfuscation since version 2021.1.
Deterministic obfuscation allows to produce an assembly whose binary content is identical across obfuscations for identical inputs.
By default, obfuscator output from a given set of inputs is unique, since the obfuscator uses randomly generated cryptographic material for every obfuscation, which is a good thing.
But sometimes, you may want to perform deterministic obfuscation. In that case, the obfuscator will produce a deterministic assembly, the one whose binary content is identical across obfuscations as long as the input remains the same.
Here is a bit more information from Eazfuscator.NET documentation: learn.gapotchenko.com/eazfuscator.net/docs/sensei-features/deterministic-obfuscation
Deterministic obfuscation is a complementary feature to deterministic compilation provided by some .NET languages. Deterministic obfuscation is solely an industrial feature, the one that allows you to inspect the results with the finest precision.
The areas of possible use are shaped by your needs and imagination. From what we have heard from the users, this is mainly a quality assurance (QA). For example, deterministic compilation and obfuscation allow to ensure that two separate build servers produce identical outputs, thus rulling out non-deterministic behaviors such as soft errors.
But the deterministic mode is not designed exclusively for QA. For example, one can imagine a deployment model that relies on changes in modules. If the source code of a module has no changes then why the compiled/obfuscated module should change? This approach can considerably simplify the patch review process for software manufacturers.