github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 06:03:26 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

Integrate with R2R for scaleable / feature rich local RAG #1455

New Issue
Closed
opened 2025-11-11 14:45:34 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 14:45:34 -06:00
Owner
Copy Link

Originally created by @emrgnt-cmplxty on GitHub (Jul 6, 2024).

Is your feature request related to a problem? Please describe.

open-webui offers an impressive suite of features, particularly its user-friendly interface. R2R has developed a powerful, flexible RAG (Retrieval-Augmented Generation) backend (R2R docs). Integrating R2R as a RAG provider option in open-webui would:

  1. Offer open-webui users more advanced RAG capabilities for complex use cases.
  2. Provide R2R users access to a polished chat UI without building from scratch.

Describe the solution you'd like

Integrate R2R as an optional RAG provider within open-webui:

  1. Add R2R as a selectable RAG backend option.
  2. Implement API connections between open-webui's frontend and R2R's backend.
  3. Expose R2R's advanced features through open-webui's interface.

As R2R core developers, we're eager to collaborate on this integration, providing expertise and implementation assistance.

Describe alternatives you've considered

  1. Developing separate UIs: Leads to duplication of effort.
  2. Building a plugin system: Requires extensive changes to open-webui's architecture.
  3. Forking open-webui: Creates maintenance challenges and fragments the community.

Direct integration offers the best balance of leveraging existing work and providing value to both projects' users.

Additional context

This integration aligns with both projects' goals:

  • For open-webui: Expands capabilities, offering users more choice in RAG implementations.
  • For R2R: Provides access to a polished chat UI, allowing focus on core RAG technology.

This collaboration can exemplify open-source projects working together to create more robust AI tools.

Disclaimer: As an R2R core developer, I'm seeking project growth opportunities. This proposal is made in good faith, believing it will benefit both projects and their users.

We're open to discussing any questions or concerns the open-webui community might have.

Originally created by @emrgnt-cmplxty on GitHub (Jul 6, 2024). **Is your feature request related to a problem? Please describe.** open-webui offers an impressive suite of features, particularly its user-friendly interface. R2R has developed a powerful, flexible RAG (Retrieval-Augmented Generation) backend ([R2R docs](https://r2r-docs.sciphi.ai/introduction)). Integrating R2R as a RAG provider option in open-webui would: 1. Offer open-webui users more advanced RAG capabilities for complex use cases. 2. Provide R2R users access to a polished chat UI without building from scratch. **Describe the solution you'd like** Integrate R2R as an optional RAG provider within open-webui: 1. Add R2R as a selectable RAG backend option. 2. Implement API connections between open-webui's frontend and R2R's backend. 3. Expose R2R's advanced features through open-webui's interface. As R2R core developers, we're eager to collaborate on this integration, providing expertise and implementation assistance. **Describe alternatives you've considered** 1. Developing separate UIs: Leads to duplication of effort. 2. Building a plugin system: Requires extensive changes to open-webui's architecture. 3. Forking open-webui: Creates maintenance challenges and fragments the community. Direct integration offers the best balance of leveraging existing work and providing value to both projects' users. **Additional context** This integration aligns with both projects' goals: - For open-webui: Expands capabilities, offering users more choice in RAG implementations. - For R2R: Provides access to a polished chat UI, allowing focus on core RAG technology. This collaboration can exemplify open-source projects working together to create more robust AI tools. Disclaimer: As an R2R core developer, I'm seeking project growth opportunities. This proposal is made in good faith, believing it will benefit both projects and their users. We're open to discussing any questions or concerns the open-webui community might have.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#1455
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?