Ross ROSS = Recommend OSS · open-source software intelligence for agents

cocoindex-io/cocoindex

Incremental engine for long horizon agents 🌟 Star if you like it! observed · 2026-08-28

github.com/cocoindex-io/cocoindex · homepage · Rust · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

82/100

  • Activity 99
  • Release rhythm 85
  • Longevity 39
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 2.0
  • age_days: 548
  • days_rel: 21
  • days_push: 7
  • n_releases_24m: 165

Full methodology

Adoption not part of the score

11409 stars · 888 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

CocoIndex is an open-source incremental data framework for AI, with a Rust engine and a declarative Python API that keeps sources (files, S3, Postgres, Kafka, etc.) in sync with targets like pgvector, Qdrant, Neo4j, and LanceDB by reprocessing only the delta. It is aimed at building continuously fresh context for AI agents, including RAG pipelines, semantic search, knowledge graphs, and real-time codebase indexing.

Use cases

  • build a rag pipeline over my documents
  • keep a vector index of my codebase in sync with every commit
  • incrementally embed files into postgres pgvector
  • build a knowledge graph from meeting notes or docs
  • semantic search over pdfs and markdown
  • feed fresh context to coding and code-review agents
  • stream csv or kafka data into a vector database
  • index code call graphs and symbols for an ai agent

When to choose

  • you need continuously updated indexes where reprocessing everything on each change is too slow or expensive
  • you want a declarative python flow from sources like s3, postgres, or local files to vector stores or graph databases
  • you are building ai agents that need fresh retrieval context, including codebase intelligence
  • you want incremental etl with built-in connectors and only-delta processing

When to avoid

  • you need a one-off batch etl job with no ongoing sync
  • your pipeline is simple enough that a plain script or existing etl tool suffices
  • you need a target store or source not covered by its connectors and don't want to write a custom connector
  • you require a mature v1 ecosystem — the v0 docs are already in maintenance mode

Facets

framework · maturity active

etl rag vector-database search-engine data-science llm-inference agent-framework streaming workflow-automation large-language-models databases developer-tools python rust cross-platform self-hosted incremental-processing change-data-capture semantic-search knowledge-graph vector-embeddings codebase-indexing declarative-pipelines context-engineering live-indexing pgvector data-engineering retrieval-augmented-generation ai-agents search docker

6 sources

Member repositories

RepositoryRoleHealth v2
cocoindex-io/cocoindexmain82

For agents

markdown · JSON · MCP: product_card(name="cocoindex-io/cocoindex")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem