Recommendation Engine

Find projects by fit, not only stars.

Explainable recommendations across use case, deployment, category, license, maintainability, readiness, and agent-readable project knowledge.

Browser Agents RAG
Use case: build Cloudflare-ready AI agentsCategory: Coding AgentDeployment: DockerLicense: MIT
1

Recommendation confidence: medium

anomalyco/opencode

anomalyco/opencode is a strong candidate for "build Cloudflare-ready AI agents": recommendation score 69/100 with matched deployment, category, license constraints.

Fit69
Use case50
Community84
Maintenance76
Readiness60
Coding Agent DockerLocalCloud Matched DeploymentMatched CategoryMatched License

Fit Profile

Primary fitPartial use-case overlap for "build Cloudflare-ready AI agents"; validate the target workflow.
DeploymentMatches requested docker deployment.
MaturityHigh maturity signal from community and maintenance scores.
Agent readinessAgent-readable summary and use cases are available.

Reasons

  • Use anomalyco/opencode when the user needs a coding agent project with docker, local, cloud deployment options.
  • Use-case match is 50/100 for "build Cloudflare-ready AI agents".
  • It matches the requested docker deployment target.
  • It is classified as coding_agent.

Tradeoffs

  • edge-only Cloudflare Workers deployment without adaptation

Adoption Plan

  • Open /projects/anomalyco/opencode to verify license, language, classification evidence, and quality signal confidence.
  • Inspect /graph/anomalyco/opencode for dependencies, related projects, deployment targets, and alternatives.
  • Use the matched constraints (deployment, category, license) as the initial acceptance checklist.
  • Prototype the docker deployment path before committing to a migration.

Risk Flags

  • No major risk flags generated from indexed signals.

ollama/ollama is a strong candidate for "build Cloudflare-ready AI agents": recommendation score 69/100 with matched deployment, category, license constraints.

Fit69
Use case50
Community84
Maintenance76
Readiness60
Coding Agent DockerKubernetesLibrary OnlyLocal Matched DeploymentMatched CategoryMatched License

Fit Profile

Primary fitPartial use-case overlap for "build Cloudflare-ready AI agents"; validate the target workflow.
DeploymentMatches requested docker deployment.
MaturityHigh maturity signal from community and maintenance scores.
Agent readinessAgent-readable summary and use cases are available.

Reasons

  • Use ollama/ollama when the user needs a coding agent project with docker, kubernetes, library-only deployment options.
  • Use-case match is 50/100 for "build Cloudflare-ready AI agents".
  • It matches the requested docker deployment target.
  • It is classified as coding_agent.

Tradeoffs

  • edge-only Cloudflare Workers deployment without adaptation
  • users expecting a complete hosted product

Adoption Plan

  • Open /projects/ollama/ollama to verify license, language, classification evidence, and quality signal confidence.
  • Inspect /graph/ollama/ollama for dependencies, related projects, deployment targets, and alternatives.
  • Use the matched constraints (deployment, category, license) as the initial acceptance checklist.
  • Prototype the docker deployment path before committing to a migration.

Risk Flags

  • No major risk flags generated from indexed signals.
3

Recommendation confidence: medium

earendil-works/pi

earendil-works/pi is a strong candidate for "build Cloudflare-ready AI agents": recommendation score 69/100 with matched deployment, category, license constraints.

Fit69
Use case50
Community84
Maintenance76
Readiness60
Coding Agent DockerLibrary OnlyLocalCloud Matched DeploymentMatched CategoryMatched License

Fit Profile

Primary fitPartial use-case overlap for "build Cloudflare-ready AI agents"; validate the target workflow.
DeploymentMatches requested docker deployment.
MaturityHigh maturity signal from community and maintenance scores.
Agent readinessAgent-readable summary and use cases are available.

Reasons

  • Use earendil-works/pi when the user needs a coding agent project with docker, library-only, local deployment options.
  • Use-case match is 50/100 for "build Cloudflare-ready AI agents".
  • It matches the requested docker deployment target.
  • It is classified as coding_agent.

Tradeoffs

  • edge-only Cloudflare Workers deployment without adaptation
  • users expecting a complete hosted product

Adoption Plan

  • Open /projects/earendil-works/pi to verify license, language, classification evidence, and quality signal confidence.
  • Inspect /graph/earendil-works/pi for dependencies, related projects, deployment targets, and alternatives.
  • Use the matched constraints (deployment, category, license) as the initial acceptance checklist.
  • Prototype the docker deployment path before committing to a migration.

Risk Flags

  • No major risk flags generated from indexed signals.
4

Recommendation confidence: medium

OpenHands/OpenHands

OpenHands/OpenHands is a strong candidate for "build Cloudflare-ready AI agents": recommendation score 69/100 with matched deployment, category, license constraints.

Fit69
Use case50
Community84
Maintenance76
Readiness60
Coding Agent DockerVercelServerlessLibrary Only Matched DeploymentMatched CategoryMatched License

Fit Profile

Primary fitPartial use-case overlap for "build Cloudflare-ready AI agents"; validate the target workflow.
DeploymentMatches requested docker deployment.
MaturityHigh maturity signal from community and maintenance scores.
Agent readinessAgent-readable summary and use cases are available.

Reasons

  • Use OpenHands/OpenHands when the user needs a coding agent project with docker, vercel, serverless deployment options.
  • Use-case match is 50/100 for "build Cloudflare-ready AI agents".
  • It matches the requested docker deployment target.
  • It is classified as coding_agent.

Tradeoffs

  • edge-only Cloudflare Workers deployment without adaptation
  • users expecting a complete hosted product

Adoption Plan

  • Open /projects/OpenHands/OpenHands to verify license, language, classification evidence, and quality signal confidence.
  • Inspect /graph/OpenHands/OpenHands for dependencies, related projects, deployment targets, and alternatives.
  • Use the matched constraints (deployment, category, license) as the initial acceptance checklist.
  • Prototype the docker deployment path before committing to a migration.

Risk Flags

  • No major risk flags generated from indexed signals.
5

Recommendation confidence: medium

kittors/CliRelay

kittors/CliRelay is an exploration candidate for "build Cloudflare-ready AI agents": recommendation score 60/100 with matched constraints, but quality and maturity signals need review.

Fit60
Use case50
Community48
Maintenance76
Readiness60
Coding Agent DockerLibrary OnlyLocalCloud Matched DeploymentMatched CategoryMatched License

Fit Profile

Primary fitPartial use-case overlap for "build Cloudflare-ready AI agents"; validate the target workflow.
DeploymentMatches requested docker deployment.
MaturityModerate maturity signal; maintenance is acceptable but compare community adoption.
Agent readinessAgent-readable summary and use cases are available.

Reasons

  • Use kittors/CliRelay when the user needs a coding agent project with docker, library-only, local deployment options.
  • Use-case match is 50/100 for "build Cloudflare-ready AI agents".
  • It matches the requested docker deployment target.
  • It is classified as coding_agent.

Tradeoffs

  • edge-only Cloudflare Workers deployment without adaptation
  • users expecting a complete hosted product

Adoption Plan

  • Open /projects/kittors/CliRelay to verify license, language, classification evidence, and quality signal confidence.
  • Inspect /graph/kittors/CliRelay for dependencies, related projects, deployment targets, and alternatives.
  • Use the matched constraints (deployment, category, license) as the initial acceptance checklist.
  • Prototype the docker deployment path before committing to a migration.

Risk Flags

  • No major risk flags generated from indexed signals.