Skip to content
Workers Native

Methodology

Most of the work is automated. The details on each page come from the app’s repository, or from the developer’s website for a commercial app, and AI drafts the descriptions from them.

What qualifies

Workers Native lists complete apps that you can deploy to your own Cloudflare account. Libraries, snippets, starters and demos do not qualify. The core app must run on Cloudflare services such as Workers, Pages Functions, D1, KV, R2, Durable Objects, Queues or Workflows. Each app needs accessible source code or a reproducible deployment path, an identifiable license and documented dependencies.

An open-source or source-available app also needs at least 20 GitHub stars or 20 forks and a commit on its default branch in the last year.

Using Cloudflare only as a CDN, DNS host or proxy is not enough. Neither is a static marketing site on Pages while the backend runs elsewhere, or a README claim without a reproducible deploy.

Commercial apps

Some apps are paid. You buy them from the developer, and they still run in your own Cloudflare account. Their listings say Commercial and show the price. The Commercial filter shows only these apps; the Open source filter leaves them out.

A commercial app has no public repository to count stars on, so it qualifies on other grounds. It has been released and is on sale. It runs in the buyer’s own Cloudflare account, not on the developer’s servers. Its price is published, and it has a live demo or a refund period. Like every app here, it installs with a Deploy to Cloudflare button or a short command; an installer that asks for an API token with broad rights over your Cloudflare account does not qualify. Neither does a hosted service that only connects to Cloudflare.

The price on the app page comes from the developer’s pricing page, with the date it was checked. Prices change, so check the developer’s site before you buy.

Runs on and also uses

Each listing separates the Cloudflare services the app runs on from the outside services it talks to. Runs on lists the Cloudflare services the app uses in your account, such as Workers, D1 or R2. Also uses lists services outside Cloudflare, such as a payment or AI provider, and says whether each one is required.

How a listing is prepared

  1. Apps are found through GitHub searches, community lists and the submit form, and some are added by hand, including every commercial app. Duplicates are merged by repository URL.
  2. An import job reads the repository metadata, README, license and wrangler configuration. A binding in the wrangler configuration confirms that the app uses a service. A service that only the documentation mentions gets a dashed outline on the app page. A commercial app’s details come from the developer’s website and documentation.
  3. AI drafts the description, the category and the technical details from those sources. Each field keeps a reference to where it came from.
  4. Repository data is refreshed every night. Fields edited by hand are locked, so the refresh does not overwrite them. If something is wrong, use Report incorrect information on the app page.

Cost on Cloudflare

Each listing says whether the app is likely to fit Cloudflare’s free plan, needs a paid plan or depends on how much you use it. The estimate links to the source it is based on. When the sources say too little, the answer is Unknown.

Ranking and independence

Lists are ordered by GitHub stars unless you search or pick another order. Commercial apps have no star count, so they come last in that order. Nobody can pay for a better position, and the developer of a commercial app does not pay to be listed. If I built an app myself, it follows the same rules, and its page says so. Corrections from app maintainers are applied once approved.