pathwaycom/llm-app
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
pathwaycom/llm-app
Pathway/llm-app is an MIT-licensed Python repo of ready-to-run LLM application templates for RAG, AI pipelines, and enterprise search over live data. It is actively maintained, has a large fork/star footprint, and is aimed at quick local testing plus deployment to cloud or on-premises.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Prefer upstream unless you specifically need this frozen snapshot. This fork adds no visible capabilities and mainly represents an older copy of an actively maintained template repo.
Choose this fork only if you want a mostly unmodified upstream snapshot; otherwise the upstream repo is the better default because it is newer and has the same core capabilities.
Prefer upstream unless you specifically want an unchanged, older snapshot; this fork adds no visible capability and is materially behind current upstream work.
Choose upstream unless you specifically need this fork as a frozen snapshot. It adds no visible capability and is already behind on recent upstream improvements, so it is only attractive for users who want a low-change starting point.
Prefer upstream unless you specifically want an old snapshot. This fork offers no extra functionality and is already behind upstream on recent template, dependency, and documentation updates.
Prefer upstream unless you specifically need this older snapshot; this fork adds nothing and mainly carries the risk of drift and missing upstream improvements.
Prefer this fork only if its custom example workflow matches your exact use case. For most adopters, upstream is the safer choice because this fork is stale and appears to have traded breadth and maintenance for a narrow bespoke demo.
Choose upstream unless you specifically need this exact fork snapshot. This fork adds no visible capability and is slightly behind, so it is best suited to users who want a near-vanilla mirror rather than a differentiated distribution.
Choose this fork only if you want a near-identical copy of upstream in your own account. If you want the newest upstream state or any added capability, upstream is the better default.