JEB

JEB is a reverse-engineering platform for disassembly, decompilation, debugging, and analysis of code and document files. Its Android tools cover static and dynamic application analysis, including multi-dex decompilation, resource reconstruction, and Dalvik and native-code debugging. Other modules address Intel x86 and x86-64, ARM, MIPS, RISC-V, WebAssembly, Ethereum contracts, Siemens S7 PLC programs, and PDF documents. Python or Java scripts and plugins can automate analysis, including through headless front ends. The GUI runs on Windows, Linux, and macOS for x64 and arm64 systems and requires JDK 21 or above. JEB Community Edition is free and listed for x86 and x86-64 decompilation. Paid choices include Android modules at $140 per user per month, Pro at $2,000 per user per year, Pro Floating at $4,000 per seat per year, and Pro OEM at $8,000 per server per year. The demo limits decompilation, project saving and loading, clipboard use, session length, and offline use. JEB was founded in 2013 and is based in Silicon Valley, California.

JEB offers a free edition alongside paid options for Android, Pro, floating-seat, and OEM use. Check the demo limits and required desktop setup against the intended analysis workflow.

JEB is suited to reverse engineers, researchers, students, and hobbyists, with its Community Edition specifically described for those groups and nonprofit reverse engineers. The range of modules may fit users analyzing Android applications, native code, or other listed targets.

JEB is a reverse-engineering platform for analyzing applications, binaries, and documents. It suits practitioners who need Android analysis alongside broader architecture coverage or scripted workflows. Its range is a clear strength, but full access is costly and the free edition is tightly constrained.

Overview

JEB brings disassembly, decompilation, debugging, and analysis into one platform. Its modules span x86 and x86-64, ARM, MIPS, RISC-V, WebAssembly, Ethereum contracts, Siemens S7 PLC programs, and PDF documents. That breadth can reduce the need to switch tools when a workflow crosses target types, though module access depends on the plan.

PNF Software, founded by Nicolas Falliere in 2013, is based in Silicon Valley, California. JEB uses a mixed licensing model, ranging from a free community edition to monthly, annual, floating-seat, and OEM plans.

Key features

Android and architecture coverage

JEB supports static and dynamic Android application analysis, including multi-dex decompilation, resource reconstruction, and Dalvik and native code debugging. The Android plan is therefore a focused option for app analysis without buying the full module set. For broader work, the platform also supports native-code and bytecode decompilation and debugger integration across its covered targets.

Automation and integrations

Python and Java scripts and plugins let users tailor analysis, while headless front ends support automated workflows. JEB's VIBRE assistant and MCP server connect to OpenAI-, Anthropic-, Google Gemini-, and AWS Bedrock-compatible endpoints, as well as MCP clients including Codex CLI, Claude CLI, OpenCode, and LM Studio. These connections suit teams incorporating those services into existing processes; they do not replace the need to choose appropriate modules and licenses.

RISC-V support

RISC-V coverage excludes RV128, RVE, and several less common extensions, and floating-point decompilation is planned rather than included as a current capability. That makes JEB less suitable when a workflow depends on those excluded or planned capabilities.

Pricing

The JEB Community Edition is free and includes x86 and x86-64 decompilation. It is aimed at researchers, students, hobbyists, and nonprofit reverse engineers, but its architecture scope makes it a poor fit for users who need Android modules or the platform's wider target coverage. The separate demo is not an unrestricted substitute: it decompiles only a subset of code, disables project saving and loading and clipboard use, limits session time, and requires an internet connection.

JEB Android costs $140 a month, billed monthly at $140 per user. It includes Android modules, the official UI client, extensions, and offline work, making it the focused paid choice for Android-centered analysis. JEB Pro costs $2,000 a year, billed yearly at $2,000 per user, and includes all modules, the official UI client, extensions, and offline work. It fits individual users who need the full target range.

JEB Pro Floating costs $4,000 a year, billed yearly at $4,000 per seat. It includes all modules, floating seats, the official UI client, and extensions; up to the licensed seat count can connect concurrently, and a seat is freed when a client leaves. This is useful when access needs to move among users rather than remain attached to one person. JEB Pro OEM costs $8,000 a year, billed yearly at $8,000 per server, and includes all modules, SaaS and back-end integrations, and third-party front-end clients. It is the plan for product or service integrations, not a lower-cost individual license.

Eligible JEB Pro license holders can add priority support for 30% of the license cost. It provides replies within one business day and prioritized bug reports, which may matter for workflows where support response time is important.

Platforms

The GUI client runs on Windows, Linux, and macOS on x64 and arm64 systems and requires JDK 21 or above. That requirement is a practical setup consideration, particularly for users who do not already maintain a compatible Java environment. The platform also supports API-based workflows.

Who it's for

JEB is strongest for reverse engineers who need several analysis modes in one product, especially Android specialists who need static and dynamic inspection or teams whose targets extend across native code, bytecode, and documents. Its scripting and headless options suit automation, while the floating and OEM plans address shared access and product integration. It is less compelling for learners or occasional users who only need basic decompilation, or for anyone whose budget cannot accommodate paid module access.

Pros and cons

• Pros: Android analysis combines multi-dex decompilation, resource reconstruction, and Dalvik and native debugging.
• Pros: Broad module coverage and Python or Java automation support varied targets and repeatable analysis workflows.
• Pros: Floating seats can be shared up to the purchased concurrent-seat count, and the OEM plan supports third-party front ends.
• Cons: The free edition is limited to x86 and x86-64 decompilation, while broader access starts at $140 a month.
• Cons: The demo's restricted decompilation, disabled project and clipboard functions, time-limited sessions, and internet requirement limit sustained evaluation.
• Cons: RISC-V support omits some extensions and floating-point decompilation remains planned.

Alternatives

IDA Pro is worth considering if its free edition's x86-32 and x86-64 disassembly and two cloud-based decompilers meet the need, or if a named license is preferred; its IDA Pro Essential plan is $1,099. For an open-source, free option on Windows, macOS, or Linux, Boomerang is a simpler fit.

Binary Ninja may suit evaluation or education users who can work within five decompilation architectures and do not need API or plugin access on its free plan; its Personal plan is $199, paid once. rev.ng is an alternative when a Free Software decompilation pipeline is the priority, with its UI offered commercially in cloud and standalone versions.

For a free, open-source bytecode tool, Bytecode Viewer is an option; dotPeek is a free Windows choice. Ghidra is another free alternative across Linux, macOS, and Windows. Windows users comparing a freemium option can also consider Relyze.

Browse more options in Decompiler Software and Reverse Engineering Tools.

Verdict

Choose JEB if your work benefits from combining Android analysis, broad target coverage, and automation in one platform, and the appropriate license fits your budget. The focused Android plan helps contain cost for app-centric work, while full-module and integration needs point to Pro, Floating, or OEM. Look elsewhere if a free basic decompiler is enough, if the demo restrictions block meaningful evaluation, or if your RISC-V workflow depends on excluded capabilities.