Overview

rev.ng pairs decompilation with structure recovery and workflow controls. It emits syntactically valid, standards-compliant C and can identify structures across functions, giving analysts more to work with when tracing how a program handles data. The pipeline is Free Software, but the UI is intended as a commercial cloud or standalone product; this is a mixed-license offering, not an entirely open-source application.

The UI is described as available in a browser or standalone app, with the same experience in either mode. The closed beta is the main adoption hurdle: users should not plan around a broadly available interface until they can join and use it. For questions and problem reports, rev.ng points users to Discourse, Discord, and email.

Key features

Data-structure recovery: Automatic detection covers linked lists, structs, arrays, and arrays of structs, using information gathered across functions. This can help analysts form a clearer picture of a binary’s data model, though the detections are clues to interpret rather than a substitute for analysis.
C output: Syntactically valid, standard-compliant C provides a readable starting point for understanding program behavior. It does not, by itself, establish that the recovered code matches the original source.
Architecture and import coverage: Included architectures are x86, x86-64, ARM, AArch64, MIPS, and S390X. Imports include ELF, PE/COFF, Mach-O, DWARF, PDB, and IDB, making rev.ng relevant across several common binary and debugging formats.
Automation and workflow: A client-server design exposes an HTTP API, while YAML files let users define functions, edit prototypes, and rename items. These controls suit repeatable or scripted analysis better than a workflow limited to manual interaction.
Shared projects: Collaborators can work on a project through a shared URL. Public projects allow two collaborators per project; users needing private visibility or more collaborators must consider a different plan.

Pricing

rev.ng is presented as free, and its open-source core is the clearest no-cost route. The project plans distinguish public collaboration from private cloud or offline use, but prices for the paid options are not settled, so teams should confirm terms before making a procurement decision.

Plan	What it includes	Best fit
Open source	Open-source core, runs anywhere, private projects, all architectures; price not listed.	Users who want the core pipeline and private projects without relying on the commercial UI.
Public project	Two collaborators per project; price not listed.	Small teams willing to use public project visibility.
Private project	Cloud, all architectures, unlimited collaborators, and private visibility; custom pricing, billed TBD.	Teams that need private cloud projects and room for larger collaboration.
Standalone	Fully standalone and offline, all architectures, unlimited collaborators, and private visibility; custom pricing, billed TBD.	Teams that require offline deployment and private projects.

The public-project plan caps collaboration at two people and requires accepting public visibility. Private cloud and standalone plans remove that collaborator cap and add private visibility, but their TBD billing terms leave costs uncertain. The open-source plan provides private projects and all architectures, though the plan description does not promise the commercial UI experience.

Platforms

rev.ng lists API, Linux, macOS, web, and Windows support. Browser and standalone UI options cover different deployment preferences, while the standalone plan specifically offers offline use. The site invites users to join a closed beta for the UI, which may affect whether those options are accessible to a prospective user now.

Who it's for

rev.ng is a strong candidate for reverse engineers who need C output, structure recovery, and scripting across multiple architectures. The API and YAML-based controls will matter most to analysts building repeatable workflows, while shared URLs can suit small groups working on public projects. It is less suitable for teams that need a mature, generally accessible UI, fixed commercial terms, or private collaboration without confirming the relevant plan.

Pros and cons

Pros

Structure recovery spans linked lists, structs, and array forms, adding useful context to decompiled output.
Six listed architectures and imports spanning executable and debugging formats support varied analysis work.
An HTTP API and YAML workflow controls provide options for automation and repeatability.
The open-source core runs anywhere and includes private projects and all architectures.

Cons

The UI is in closed beta, making access a practical uncertainty for users who need a graphical workflow.
Public projects are limited to two collaborators and public visibility.
Private cloud and standalone plans have custom pricing with billing marked TBD, complicating budgeting.
The UI is commercial even though the decompilation pipeline is Free Software, so the product is not wholly open source.

Alternatives

Decompiler Software and Reverse Engineering Tools are useful starting points for comparing products across those categories.

Binary Ninja is worth considering for users who want a freemium alternative with a free evaluation and education plan, while its free tier limits decompilation to five architectures and excludes API or plugin access.
IDA Pro suits readers seeking a paid alternative with a free tier for x86-32 and x86-64 disassembly and two cloud-based decompilers; its listed platforms are Linux, macOS, and Windows.
JEB offers a free Community Edition for x86 and x86-64 decompilation, aimed at researchers, students, hobbyists, and nonprofit reverse engineers.
Bytecode Viewer is a free, open-source GPL v3 option for users who prioritize a fully free tool.
Ghidra is a free alternative for users seeking software with no stated price or usage limits.
ILSpy is a free, MIT-licensed alternative.
JADX is a free, Apache 2.0-licensed option for readers who can accept that decompilation may not recover all code.
Relyze is another Windows alternative.

Verdict

Choose rev.ng if you need multi-architecture decompilation with structure recovery and want an open-source pipeline that can support scripted workflows. Its strongest case is the combination of C output, interprocedural recovery, and API access. Look elsewhere if your project depends on immediate UI access, guaranteed private collaboration at a known cost, or an entirely open-source product.

	Reko	rev.ng
Free plan	Yes	Yes
Free trial	No	No
Paid from	Free	Free
Open source	No	No
Platforms	Linux, macOS, Windows	api, Linux, macOS, Web, Windows
Free plan	Yes	Yes
Native-code decompilation	Yes	Yes
Scripting API	Yes	Yes
Plugin support	Yes	—
License type	free	mixed
Debugger integration	—	Yes

Reko vs rev.ng

Reko

rev.ng