pipeshub-ai/pipeshub-ai

▲ 76 stars today★ 4,022⑂ 648

The open-source context layer for AI agents. PipesHub turns your company's knowledge (Slack, Drive, Jira, GitHub

About pipeshub-ai/pipeshub-ai

pipeshub-ai/pipeshub-ai is an open-source project on GitHub, mainly written in Python. The open-source context layer for AI agents. PipesHub turns your company's knowledge (Slack, Drive, Jira, GitHub It currently holds 4,022 stars and 648 forks with 225 open issues, and was last pushed on 2026-11-06 (repository created 2025-03-06).

Project Overview

AI Homed tracks it on the Today's Trending board, currently at rank #25 with 76 new stars today.

GitHub Repository Details

Repository pipeshub-ai/pipeshub-ai · default branch main · size 202363 KB · watchers 18 · source: GitHub REST API and repository README

README

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/PipesHub

An open-source context layer for AI agents and an enterprise search platform

Permission-aware search and cited answers across Slack, Google Drive, Jira, Confluence, GitHub and 50+ apps, for your people and for agents through MCP. Self-hosted or PipesHub Cloud.

#1 of 39 systems on EnterpriseRAG-Bench, ahead of OpenAI File Search, Amazon Q, Azure AI Search and Vertex AI Search. All benchmarks → · How it works →

Website · Docs · Discord · Roadmap

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/PipesHub on Trendshift

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/License https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Release https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Docker Pulls https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Discord https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Last commit https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Commits per month https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/GitHub issues https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/GitHub pull requests
https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Twitter https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/LinkedIn
https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/
https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Node.js SDK https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Python SDK https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Go SDK https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/MCP

Translations: Français · Deutsch · 简体中文 · 日本語 · Русский · עברית · 한국어 · Español · Português · Türkçe · Tiếng Việt · Italiano · Čeština

PipesHub - Explainable & Extensible

PipesHub is an open-source platform for connecting AI applications to the knowledge stored across your company's business systems.

Connect Slack, Google Drive, GitHub, Microsoft 365, Notion and 50+ other systems. Search across them and get answers with citations, filtered by what each person is allowed to see — or give that same context to your own agents, workflows and MCP clients.

[!TIP]
Deploy with a single command:
> curl -fsSL https://get.pipeshub.com/install | bash

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Watch the PipesHub demo on YouTube
▶ Watch the 2½-minute demo: Claude Code answering from Jira, Slack, GitHub and Drive, with each person's permissions

How PipesHub works

PipesHub builds a unified context layer across documents, conversations, structured data, wikis, tickets and code. Connectors sync each source along with its permissions. The indexing pipeline parses, chunks and embeds the content, and links records, people and entities in a knowledge graph.

Questions are answered by an agent loop, not a single retrieve-then-generate pass. The agent plans, calls tools, reads the results and keeps going until it has the evidence:

Every tool call is filtered by the asking user's permissions, and every answer cites the blocks it came from.

Benchmarks

How PipesHub performs, and how each test was run.

| Benchmark | What it measures | Result | Details | |---|---|---|---| | EnterpriseRAG-Bench (independent, run by Onyx) | 500 questions over 500,000+ company documents | #1 of 39 systems (93.24). OpenAI File Search 61.03, Amazon Q 48.96, Azure AI Search 48.42, Vertex AI Search 41.87 | Leaderboard | | Google FRAMES (824 questions) | Answers that need facts from several documents | 92.7%, against 78.9% for the best of 18 standard RAG pipelines | Write-up | | Company index vs. per-app MCP connectors | The same Claude agent on 100 work questions, searching each app through its own connector or through PipesHub | Facts found: Haiku 55% → 80%, Sonnet 65% → 89%, Opus 85% → 92%; 27–45% faster and 27–32% cheaper per answer | Write-up | | Code graph accuracy (vs. Graphify, codebase-memory-mcp, CodeGraphContext) | How accurately each tool maps relationships in code across 9 repositories | Highest accuracy (F1 score) on 8 of 9 repositories | Write-up |

Leaderboard standing as of 3 November 2026 (leaderboard data at that date). The FRAMES, connector and code-graph tests were run by the PipesHub team. The connector test used questions about our own internal work; we will publish a version on public data.

What can you build with PipesHub?

Don't just use PipesHub — build on it.

Give Claude Code, Cursor, or Codex secure access to your company's knowledge → About ten minutes once PipesHub is running with data indexed. Mint a Personal Access Token (no admin needed), connect your assistant (one command for Claude Code, one config file for Cursor or Codex), and ask "why was the retry logic in the billing worker changed?" — it answers from the incident postmortem, the pull request, the chat thread, and the design doc, each cited, and only if you're allowed to see them.

Want the same retrieval inside your own code, or behind a search box for your team? The SDK starter and search example cover both. Built something? Show us.

PipesHub in Action

Connectors

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Connectors

Citations

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Citations

All Records

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/All Records

Knowledge Search

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/Knowledge Search

Features

Answers you can trust

Connected to your systems What you can build

PipesHub Cloud

Prefer a fully managed PipesHub without running your own infrastructure? Sign up for PipesHub Cloud: the same connectors, permission-aware search, and APIs, with nothing to install.

Coding agents connect to https://app.pipeshub.com/mcp with a personal access token. See For coding agents.

Connectors

https://github.com/pipeshub-ai/pipeshub-ai/blob/HEAD/PipesHub Connectors

🚀 Deployment Guide

PipesHub can be run locally or deployed on any server using Docker Compose. The interactive installer handles all configuration — including secrets, graph DB, broker, and image tag selection — and generates a .env for you.

HTTPS on cloud servers: If you deploy PipesHub on a cloud server, use an HTTPS endpoint. Browsers block certain requests over plain HTTP. Use Cloudflare, Nginx, or Traefik to terminate TLS. A white screen after HTTP-only deployment is typically caused by this restriction.

---

⚡ Quickstart (Recommended)

Requires Docker with Compose v2. One command:

curl -fsSL https://get.pipeshub.com/install | bash

This downloads the deployment files for the latest release into ./pipeshub and launches the interactive installer. Open http://localhost:3000 once it finishes.

Prefer to read before running? Download and inspect the script first:
>
> curl -fsSL https://get.pipeshub.com/install -o pipeshub-install.sh
less pipeshub-install.sh # review it
bash pipeshub-install.sh

The installer will:

🛠️ From a cloned repository (developers)

To build from source, contribute, or pin the installer to your checkout:

git clone https://github.com/pipeshub-ai/pipeshub-ai.git
cd pipeshub-ai

Same installer, run from the repo root

./install.sh

Building local images from source requires this cloned-repo path (./install.sh --build); the one-command installer above always uses prebuilt images.

Installer options

| Flag | Description | |------|-------------| | -y / --yes | Accept all defaults; skip interactive prompts (CI-friendly) | | --version TAG | Pin a specific image tag, e.g. --version 0.7.0 | | --reconfigure | Re-run the wizard and overwrite an existing .env | | --print-env-only | Write .env and print the compose command without starting containers |

Advanced options: CI environment variables, slim vs. full deployment types, manual Compose profile usage, and local source builds are covered in Advanced Deployment Options.

Build with PipesHub

The built-in search experience is one way to use PipesHub. The same connected, permission-filtered context is available to your own agents and applications — over MCP for any compatible client, or through the SDKs when you are calling it from your own code.

An agent connects as a specific person rather than as the application, so it retrieves exactly what that person is allowed to see. Access is resolved when the query runs, against the source system's own permissions, instead of being approximated at build time.

Step-by-step tutorials for the most common builds — an MCP for your coding assistant, private enterprise search, and SDK starters — live in pipeshub-ai/examples. The reference material for each building block is below.

MCP Server

Use PipesHub with any MCP-compatible client to bring your enterprise context into AI workflows. Check the README for setup and usage.

Repository: pipeshub-ai/mcp-server

Connecting an Omnigent agent

First, mint a long-lived credential: workspace → Developer settings → Personal Access Tokens → New token. Pick an expiry (30/90/365 days, or never) — this runs as you, so results respect your own per-user permissions, unlike an OAuth app's client-credentials flow.

Three ways to connect, from least to most setup:

1. Attach in the Omnigent web UI (fastest, no clone). Open a session's info panel → Manage MCP Servers → add PipesHub's URL and an Authorization: Bearer header → restart the session. 2. Run the packaged example agent. A ready-made agent bundle (tuned prompt + instructions) ships with Omnigent: PIPESHUB_MCP_URL=... PIPESHUB_MCP_TOKEN=... omnigent run examples/pipeshub/. 3. Use the connect kit in integrations/omnigent/ (setup.sh / run.sh) for CI, service accounts, or password/OAuth client-credentials auth instead of a personal token.

SDKs

PipesHub provides developer SDKs for Python, TypeScript, and Go to help you integrate quickly. Check the respective SDK repository README for setup and usage details.

| Name | Description | Link | |------|-------------|------| | Python SDK | Python SDK for PipesHub | pipeshub-ai/pipeshub-sdk-python | | TypeScript SDK | TypeScript SDK for PipesHub | pipeshub-ai/pipeshub-sdk-typescript | | Go SDK | Go SDK for PipesHub | pipeshub-ai/pipeshub-sdk-go |

Need an SDK in another language? Reach out to us at developer@pipeshub.com

Roadmap

We ship in the open. Here's what's done and what's next:

👉 View the full product roadmap on Notion


👥 Contributing

Want to join our community of developers? Please check out our Contributing Guide for more details on how to set up the development environment, our coding standards, and the contribution workflow.

Contributing with a coding agent (Claude Code, Cursor, Codex, Copilot, Gemini CLI)? AGENTS.md gives it the repo layout, test commands and the conventions reviewers check.

Where to go for what

Ask a question or get helpDiscord
Report a bug or request a featureGitHub Issues
Report a security issueReport Security Issue
Read the docsPipeshub Docs
See what changed in each releaseChangelog

FAQ

What is PipesHub?

PipesHub is an open-source platform for connecting AI applications to the knowledge stored across your company's business systems.

It connects systems such as Slack, Google Drive, GitHub, Microsoft 365 and Notion, then makes what they hold available in two ways: permission-aware search with citations for your team, and trusted context for your AI agents through APIs, SDKs and MCP. Agents get the same governed view of your company's knowledge that a person would, with the same access controls applied, so they can answer from real company data instead of guessing across tools. You can use the built-in search experience, or build your own agents, workflows and applications on top of it.

How is PipesHub different from other workplace AI tools?

PipesHub is fully open-source (Apache 2.0) and self-hostable — your data never leaves your infrastructure. It features permission-aware search that enforces source-level access controls, and delivers explainable answers with precise block citations to original documents.

Answers come from an agent loop that combines hybrid search, grep, knowledge-graph navigation and full-document reading, instead of a single retrieve-then-generate pass. See How PipesHub works.

What connectors does PipesHub support?

PipesHub has 50+ enterprise connectors with real-time and scheduled indexing. See the connectors overview.

What file formats can PipesHub index?

PDF (including scans), Microsoft Office (Word, Excel, PowerPoint), Google Docs/Sheets/Slides, Markdown, HTML, CSV, plain text, and images. Audio and video can be stored but are not indexed yet. Storage accepts a wider set of MIME types — see Supported MIME Types.

How do I deploy PipesHub?

curl -fsSL https://get.pipeshub.com/install | bash

This writes Compose files into ./pipeshub and starts the interactive installer. Open http://localhost:3000 when it finishes. Use HTTPS for cloud deployments — HTTP may cause frontend security blocks.

Developers building from source should clone the repository and run ./install.sh (or ./install.sh --build) from the repo root. See the Deployment Guide.

What LLM providers does PipesHub support?

PipesHub is "Bring Your Own Model" — you can use any LLM provider. Deploy in your VPC with your preferred models.

What is the tech stack?

PipesHub has three parts:

Those services call AI models you bring. An embedding model turns parsed text into vectors for search. An LLM writes the cited answer. Use any provider or a local model (Ollama); a local embedding server is the default.

Data sits in a knowledge graph (Neo4j by default, or ArangoDB), a vector store (Qdrant), and MongoDB. Redis is the cache. Files live on disk or object storage. Services hand work to each other over Redis on a local machine, or Kafka in a larger deployment. See the system overview.

What is the Knowledge Graph Retrieval feature?

PipesHub uses graph-backed retrieval that captures relationships across enterprise data. It uses Neo4j or ArangoDB as the graph database, combined with a vector store (Qdrant by default) for semantic search. The agent can follow graph links between documents, people, tickets and code during a question, not only at indexing time.

Does PipesHub have an MCP server?

Yes. PipesHub provides an MCP server for integration with any MCP-compatible client. Repository: pipeshub-ai/mcp-server.

What SDKs are available?

PipesHub provides SDKs for:

Can I build AI agents without coding?

Yes. PipesHub has a no-code agent builder. You can build agents visually and execute actions across enterprise tools without writing code.

What is the multimodal support?

PipesHub supports image, diagram, and scanned-file understanding, plus voice-based interaction. It uses Docling and pdfplumber for document parsing, or a multimodal LLM (VLM) for scanned PDF OCR.

How do I troubleshoot deployment issues?

1. Ensure HTTPS is configured for cloud deployments 2. Check Docker compose logs: docker compose logs 3. Verify environment variables in env.template 4. Consult docs.pipeshub.com for detailed guides

Where can I get help?


⭐ Star us on GitHub!

It h

GitHub Stars & Activity

4,022Stars
648Forks
225Open issues
PythonLanguage

GitHub Popularity

GitHub stars4,022
Forks648
Open issues225
Primary languagePython
LicenseApache-2.0
Stars gained today76
Created2025-03-06
Last pushed2026-11-06

Trending History

Daily boardrank #25 · ▲ 76 stars

Related AI Projects

More AI Rankings