Launch catalog / Playbook

Awesome REA

awesomerea.com ↗

Free route directory

Researched from public pages — no submission was run · sources read 2026-10-25. Rules change — recheck the platform's own pages before submitting.

Requirements

  • The directory's stated scope is open-source reverse-engineering work, independent reimplementations, compatibility projects, and related tools/resources; this is a narrow technical fit, not a general SaaS listing.
  • REA usage is optional. Any claim of REA involvement must be supported and limited to the evidence.
  • Contributions should include a canonical project/resource URL, a concise scope description, primary evidence, license and rights information where software is involved, current status and limitations, and the submitter's relationship.
  • The official guide says listing is free and there is no paid ranking. Maintainers review submissions and may decline them.

Prepare before opening the form

  • Search the current directory and existing Issues for duplicates.
  • For a proposed software project, gather its public repository, direct primary evidence, applicable license and any separate asset or dependency terms.
  • Summarize what is analyzed, reimplemented, or made compatible; state unfinished work and any required original software, assets, hardware, credentials, or paid services.
  • Disclose the submitter's relationship and keep any REA claim within what the cited source proves.

Workflow

  1. Open the official new project, integration, or resource issue template.
  2. Provide the canonical URL and concise scope, primary evidence, license/rights, status/limitations, and relationship requested by the form.
  3. Complete the duplicate, evidence, and authorized-content confirmations; do not include secrets, private binaries, or proprietary investigation data.
  4. Treat the issue as a proposal only. A maintainer-reviewed contribution must be merged before it counts as listed; the repository says the website updates after its release workflow succeeds.

Watch for

  • A link to another directory may help discovery but is not enough evidence for inclusion; use direct primary sources for each software claim.
  • A public repository is not by itself proof of an open-source license. Preserve original asset, third-party, commercial-service, and platform limits.
  • Do not call a listed project a full replacement unless the supported scope and usable build justify that claim.
  • The maintainers do not promise acceptance or a review time. A submitted issue, pull request, or open-source license does not mean a listing is live.
  • The directory's own MIT license applies to its repository material; linked projects retain their own licenses.

What counts as live

The proposed item is present in the maintained public directory after the contribution is merged, and the resulting website release succeeds. An open issue or unmerged pull request does not count.

Not verified

  • No review-time or acceptance commitment is stated.
  • Outbound link attributes and domain-rating metrics were not researched; neither should be inferred.
  • No submission or placement was attempted for this LaunchDesk research.

Sources

← Back to the launch catalog