About this software
Third-party protection tool for Android applications that encrypts classes.dex to impede static decompilation. Distributed by BIS Guard and offered via the JetBrains Marketplace, it is available as an IntelliJ-compatible plugin and as standalone/console tools for build integration. Vendor documentation describes a trial mode and lists Java runtime and Android API requirements.
Licenses & prices
Standard
Provides core anti-decompilation features and team-oriented integration for organizational development and build workflows.
Personal
Licensed for individual developers, includes the same anti-decompilation protections with single-user activation and personal support.
Purchase
JetBrains 3rd Party Antidecompiler
In Stock
Delivery: 1 working day
Loading...
€413.28
Free and without obligation
Do you need more information or looking for another license?
Benefits
- Bytecode encryption: Encrypts classes.dex to hinder static decompilation.
- IDE integration: Installs as a JetBrains Marketplace plugin for IntelliJ-based IDEs.
- Build integration: Also available as standalone and console tools for build integration.
- License options: Offered with per-user subscriptions sold via JetBrains Marketplace.
- Resource protection: Protects app resources and classes against casual reverse engineering.
Available languages
- English
Support information
- Vendor documentation: User guide, installation steps, and trial details are available on the BIS Guard website.
- Marketplace licensing: Purchases, subscriptions, and license management are processed through JetBrains Marketplace and JetBrains Account.
- Plugin updates: Plugin updates and new releases are published on JetBrains Marketplace when provided by the vendor.
- Integration guidance: Console and standalone modes include instructions for integrating into build systems and CI pipelines.
- Trial mode details: Vendor notes a trial mode that adds a toast message and log output in protected apps.
Frequently asked questions
What does JetBrains 3rd Party Antidecompiler do?
Provides anti-decompilation capabilities to make compiled code harder to reverse-engineer by applying obfuscation or runtime protections to artifacts.
How is it integrated into build pipelines or CI/CD?
Integration typically occurs by incorporating the tool into build steps or post-compilation tasks so protections are applied to build artifacts before deployment; exact integration method depends on build system.
Will using this tool affect runtime performance or debuggability?
Anti-decompilation techniques can increase binary size or incur runtime overhead and may complicate debugging; impact varies by selected protections and runtime environment.
What licensing and compliance considerations apply?
Licensing terms and export, open-source, or regulatory compliance obligations depend on the product license and target markets; review the product's license and legal guidance before deployment.