What gets listed
- Self-hosted apps come from the community-maintained awesome-selfhosted list, plus apps we add by hand and reader submissions. The source code must be public on GitHub and the repository must not be archived.
- MCP servers, agent skills, templates, mobile apps and desktop apps are discovered from the official MCP Registry, skills.sh, the F-Droid index, public awesome lists and GitHub topics. Each collection has its own rules, such as a recognised licence, a commit in the recent past and a minimum number of stars.
- Software under a restrictive licence (BSL, SSPL, Elastic and similar) is labelled source-available, never open source.
- We do not list a project because someone paid for it, and we only remove one for the reasons on our takedown page.
How lists are ranked
- Organic lists are sorted by public GitHub data: total stars by default, commits in the last 12 months for Trending and Most active views, plus release recency, licence and Docker support as filters.
- Best picks pages score apps with a published formula (stars and recent commits on a log scale, with extra weight for the audience in question). Each page states which signals it used. Features that the data cannot show, such as SSO or ease of use, are not scored or claimed.
- Nobody can pay to move up a ranked list.
Sponsors and affiliate links
- Sponsored placements (Featured listings, the homepage spotlight and newsletter sponsorships) are always labelled "Sponsored" and sit apart from organic lists.
- Hosting providers in our partner blocks are affiliate links: we earn a commission if you sign up through them, at no cost to you. These links use rel="sponsored" and carry a disclosure next to them.
- Sponsors and affiliate partners do not review or approve anything we publish.
What is automated and what is written by hand
- Generated from data: listing and category pages, item pages, statistics, trending lists and most short descriptions. Descriptions come from the upstream sources named on our data sources page, and stay under their own licences.
- Written by appsgit: deploy guides, comparisons, best-pick introductions, articles, the alternatives mappings and category definitions.
How we use AI
appsgit is built and run with the help of AI tools. We use them to write and maintain code, to draft guides, comparisons and articles, and to help write the rules that sort projects into categories. A person reviews AI-drafted articles before they are published and checks facts such as prices, versions and licences against their sources. Data-generated pages are checked by automated rules rather than read one by one, so mistakes can slip through; please tell us when you find one.
Hardware and product advice
Unless an article says otherwise, hardware and hosting advice is based on published specifications, official prices, cited reporting and community reports, not on our own lab tests.
Corrections
Email info@appsgit.com with the page URL and what is wrong. We aim to reply within 3 business days and to fix confirmed errors within 7 days. When a correction changes the substance of an article, we update its "updated" date. Project owners can ask for a listing to be changed or removed using the steps on our corrections and takedown page.