Allatori

Allatori is a Java obfuscator for protecting compiled code and making reverse engineering more difficult. It works on Java class files without requiring the original source code, and supports J2EE, J2SE, J2ME, and Android targets. Its tools include name, flow, and debug-information obfuscation, string encryption, watermarking, incremental obfuscation, and a module designed to interfere with decompilers. Build options include command-line scripts, Apache Ant, Maven, Android Studio, and an Eclipse plugin. Allatori is written in Java and can technically run where a Java 1.4-or-later virtual machine is supported; the maker says it has been tested on Windows, Mac OS X, and UNIX. The maker reports typical application size reductions of about 10–40%, sometimes up to 60% with many third-party libraries. String encryption can increase bytecode size by 1–2%, while flow obfuscation can slightly increase size and rarely affect performance. A single developer license is $$290 once; a free plan is also listed.

Allatori offers a broad set of obfuscation features for compiled Java applications and integrates with several build tools. Review its notes on bytecode size and native methods when deciding how to configure it.

Allatori suits Java developers who want to obfuscate compiled class files as part of a build process. Its Android, J2ME, J2SE, and J2EE support makes it relevant to projects targeting those environments.

Allatori is a desktop Java obfuscator for developers shipping J2EE, J2SE, J2ME or Android software. It suits teams that need layered protection in a compiled-class build pipeline, especially when source code is not present at the obfuscation stage. Its broad tooling and licensing options make it practical for many Java shops, provided they account for native-method exclusions and the cost of larger licenses.

Overview

Founded in 2006, Allatori is designed to make compiled Java code difficult to read and reverse engineer while also reducing application size. It works strictly on compiled class files, so an obfuscation job does not require the original Java source. The maker reports typical size reductions of about 10–40%, occasionally reaching 60% in applications containing many third-party libraries; actual results depend on the application.

Allatori is written entirely in Java and can technically run on systems with a Java 1.4-or-newer virtual machine. It has been tested on Windows, Mac OS X and UNIX, and its listed platforms are Android, Linux, macOS and Windows. Deployment is desktop-based.

Key features

The protection stack goes well beyond renaming identifiers. Name obfuscation changes symbols, while flow obfuscation makes control logic harder to trace. Debug-information obfuscation removes clues useful to someone examining a build. Watermarking can identify protected output, and incremental obfuscation supports repeat builds where preserving prior transformations matters.

String encryption stores encrypted literals in class constant pools and decrypts them at runtime. The maker says this usually increases bytecode size by 1–2% with insignificant performance impact. Flow transformations can add some size and rarely reduce performance, so applications with strict footprint budgets should measure the result before enabling every layer.

A dedicated decompiler-protection module transforms code intended to cause fatal errors when a decompiler attempts to process it. A stack-trace utility helps interpret obfuscated failures, an important operational counterweight to unreadable production names. J2ME and Android-specific obfuscation extend the feature set beyond conventional desktop Java.

Build integration is a strength. The command-line interface fits automated scripts, while Apache Ant and Maven integrations connect to common Java builds. Android obfuscation can be used with Android Studio and Ant projects, and an Eclipse plugin adds an Allatori Builder that runs obfuscation on clean rebuilds. Native methods require special care: native methods and their containing classes are not renamed automatically, and members reached from native code must be explicitly excluded.

Pricing

Allatori has a free plan and paid licensing from $75/yr. The $75 a year Single Developer License Update is an annual support renewal with email support, updates and upgrades for 12 months; it suits an existing single-developer license that needs continued maintenance rather than a new perpetual purchase.

A new Single Developer License costs $290, paid once for one developer and cannot be shared or used concurrently. Volume pricing lowers the one-time cost to $260, paid once for 2–5 licenses (10% discount), $230, paid once for 6–10 (20% discount), and $200, paid once for 11 or more (25% discount). Each includes email support, updates and upgrades for 12 months.

For organizations, Site License costs $3,750, paid once for any number of developers at one company office or location, normally within 30 miles. Business License costs $4,850, paid once for any number of developers across all company offices worldwide within the same juridical company. Site License Update is $500 a year, and Business License Update is $750 a year; both are annual support renewals with 12 months of support, updates and upgrades. These terms make the free edition useful for evaluation or limited use, while multi-developer and multi-office deployments should budget for the corresponding one-time license and yearly renewal.

Platforms

Supported targets are J2EE, J2SE, J2ME, Android and Java class files. Allatori's runtime environment covers Android, Linux, macOS and Windows, with command-line, Ant, Maven, Android Studio and Eclipse build paths.

Who it's for

Choose Allatori for Java or Android teams protecting proprietary class files, integrating obfuscation into repeatable builds, or working without source at the packaging stage. Its combination of control-flow changes, encrypted strings, decompiler protection and stack-trace support is well suited to commercial software distributed outside the organization.

It is less suitable when native interfaces dominate and exclusion management would be burdensome, or when a project cannot absorb even modest bytecode growth from encryption and flow transformations. Organizations should also match the license scope to developer count and office geography.

Pros and cons

• Pros: Layered protection covers names, control flow, debug data, strings, watermarking and decompiler resistance.
• Pros: CLI, Ant, Maven, Android Studio and Eclipse integrations fit automated and IDE-based release workflows.
• Pros: Compiled-class input avoids a source-code dependency, and reported size reductions can benefit library-heavy applications.
• Cons: Native methods and native-accessed members need explicit exclusions, adding compatibility work.
• Cons: Encryption and flow obfuscation can increase bytecode size, while licensing becomes expensive for broad organizational use.

Alternatives

For a free, open-source Java and Android shrinker, consider ProGuard. R8 is another free, open-source option when its API-focused Linux distribution fits your workflow. Choose ByteHide Shield if you want freemium protection spanning Android, iOS, desktop, web and self-hosted environments. Tigress suits readers seeking a paid obfuscator with a free plan and trial across major desktop platforms. For commercial Android-only protection without a free plan, compare DexGuard; DexProtector covers Android and iOS and offers a trial. DashO provides paid, trial-based team and enterprise options, while iXGuard targets iOS deployments.

See the broader Code Obfuscation Software list for additional choices.

Verdict

Allatori is a strong fit for Java and Android developers who want multiple obfuscation layers, mature build integration and class-file-only processing. Its main reason to choose it is the breadth of protection in a conventional Java workflow; its main reason to look elsewhere is the licensing cost and the extra diligence required around native code and output size.