Less hype.
More provenance.

What “checked” means

We reviewed the linked primary sources on the date shown. We checked whether the published source supports the stated REA relationship, project scope and license note. We did not independently build, execute, benchmark or security-audit the listed software.

Project progress and test results are author-reported unless explicitly stated otherwise. “Checked” is a source-review date, not a freshness guarantee. Pinned GitHub links preserve the reviewed snapshot where practical; project links go to current repositories.

Three different REA connections

Author documents REA use

A primary project source explicitly describes how REA contributed. That credit applies only to the documented work, not automatically to every feature or prior release.

REA maintainer case study

The official REA site documents a specific investigation or reconstruction. A linked full project may be much broader than the demonstrated REA work.

REA tooling present

A repository contains explicit REA scripts or workflow documentation. This is a useful ecosystem connection, but is not proof that its whole product was built with REA.

Four kinds of entries

Reconstructions

Code recovered or reimplemented from observed behavior or binary evidence. This may cover one feature; do not assume full application parity.

Interoperability

Tools that work with existing software, formats or hardware. They may complement rather than replace a commercial product.

Case studies

Published investigations. They are learning material, not necessarily new software you can install.

REA tooling

Projects with a documented REA investigation setup whose overall REA provenance is not established by our sources.

When would we call something a full alternative?

We would need public source under an appropriate open-source license, explicit evidence of REA's contribution, a documented usable build, and enough supported functionality to justify the particular replacement claim. Required original software, assets and hardware must be disclosed.

This edition confirms zero complete REA-built replacements for commercial applications. Our review covered public GitHub repositories, official REA showcases and selected public web results. It is not an exhaustive search of all communities or private work.

We exclude unrelated famous open-source alternatives, unexplained mirrors, direct binary-download promotions, and entries without enough evidence to describe them accurately. A source-available repository with restrictive terms is not automatically open source.

Rights, licenses and responsible use

Listing a project is not legal review or endorsement. Reverse-engineering, interoperability and redistribution rules vary by jurisdiction, license agreement and terms of service. A repository's license may cover only its authors' own code — not the original software, trademarks, assets or data.

REA's MIT license covers REA itself, not everything analyzed with it. Use only targets you are authorized to inspect. We do not host third-party binaries, game assets, proprietary code or instructions to bypass access controls. Descriptions of “clean-room” work remain the projects' claims, not a legal certification by this index.

License labels summarize the reviewed notices. Per-file and third-party terms may differ. Follow the source license link before reuse. This is not legal advice.

Suggestions, corrections & removal

This index is maintained by Jeff Xun ↗. Use the public contact address listed on the curator's GitHub profile: email a project suggestion or correction.

Include the entry URL, the specific claim to change, a primary source, and your relationship to the project if relevant. For new entries, add the repository, license, REA-use evidence and current limitations. Requests are reviewed manually; sending a request does not create a public listing.

Privacy & independence

The site is static. There are no accounts, advertising scripts, analytics tags, third-party fonts or embedded media. Search and filtering run in your browser and are not sent to us. We do not set application cookies or store search queries.

Cloudflare serves the site and may process request information for delivery and security. Outbound links and email use the destination service's privacy rules. We do not control those services.

Awesome REA is not affiliated with or endorsed by morluto, REA, or any listed project. No paid placements are included in this edition.