Source: https://seerepo.com/compare/infiniflow/ragflow/vs/m1k1o/neko
Markdown source: https://seerepo.com/compare/infiniflow/ragflow/vs/m1k1o/neko.md
Description: ragflow and neko share 9 technologies: React, Tailwind CSS, class-variance-authority, tailwind-merge, Radix UI, sonner, react-markdown, remark-gfm, and remark-breaks. Both are written in Go.

# ragflow vs neko

ragflow and neko share 9 technologies: React, Tailwind CSS, class-variance-authority, tailwind-merge, Radix UI, sonner, react-markdown, remark-gfm, and remark-breaks. Both are written in Go.

- [infiniflow/ragflow](https://seerepo.com/r/infiniflow/ragflow): RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
- [m1k1o/neko](https://seerepo.com/r/m1k1o/neko): A self hosted virtual browser that runs in docker and uses WebRTC.

## What they share and what sets them apart

- In common: React, Tailwind CSS, class-variance-authority, tailwind-merge, Radix UI, sonner, react-markdown, remark-gfm, remark-breaks
- Only in ragflow: net/http, Gin, go-redis, mysql-connector-python, pgx, pq, s3, Postgres, MySQL, Redis, AWS S3, Google, MCP, AIOHTTP, werkzeug, React Router, OpenAI, github.com/aws/aws-sdk-go-v2/credentials, golang.org/x/oauth2, github.com/golang-jwt/jwt/v5, Model Context Protocol, github.com/yuin/goldmark, github.com/ledongthuc/pdf, github.com/gomarkdown/markdown, github.com/emersion/go-message, golang.org/x/image, reportlab, go.uber.org/zap, github.com/aws/aws-sdk-go-v2, github.com/aws/aws-sdk-go-v2/config, go.opentelemetry.io/otel/trace, OpenTelemetry, github.com/aws/aws-sdk-go-v2/service/sts, go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp, github.com/Azure/azure-sdk-for-go/sdk/azcore, qrcode, classnames, next-themes, React Hook Form, xyflow, lexical, tanstack, @monaco-editor/react, react-syntax-highlighter, react-force-graph-2d, react-day-picker, react-copy-to-clipboard, recharts, @floating-ui/react, cmdk, D3, embla-carousel-react, Mermaid, react-dropzone, react-resizable-panels, Lucide, Ant Design, @lexical/markdown, dompurify, react-pdf-highlighter, rehype-katex, rehype-raw, unist-util-visit-parents, xlsx, papaparse, rehype-sanitize, remark-math, Zod, @hookform/resolvers, Ajv, ajv-formats
- Only in neko: chi, Vite, github.com/rs/zerolog, Prometheus, @phosphor-icons/react

## Side by side

| | ragflow | neko |
|---|---|---|
| Size | 1,294,372 lines written, 2,843 code files | 37,408 lines written, 217 code files |
| Who writes it | 2.1% of its commits signed by AI. With Claude Code, Cursor, CodeRabbit, GitHub Copilot, Kilo Code, Codex, OpenHands, Gemini CLI, and Factory | 0.2% of its commits signed by AI. With Claude Code |
| Activity | Last push November 4, 2026, 10,792 commits, 93,494 stars | Last push October 28, 2026, 2,094 commits, 22,602 stars |
| Tests | 1,962 test files. 50.8% of its code files have a test that imports them | 39 test files. 30.4% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, ragflow or neko?

ragflow, with 1,294,372 lines written; neko has 37,408.

The proof: [infiniflow/ragflow's code at commit 8cab68a](https://github.com/infiniflow/ragflow/tree/8cab68a9a3b083da95abb2ea0789b0a5623defaf)

### Which has more GitHub stars, ragflow or neko?

ragflow, with 93,494 stars; neko has 22,602.

The proof: [infiniflow/ragflow on GitHub](https://github.com/infiniflow/ragflow)

### Which has more tests, ragflow or neko?

ragflow, with 1,962 test files; neko has 39.

The proof: [infiniflow/ragflow's code at commit 8cab68a](https://github.com/infiniflow/ragflow/tree/8cab68a9a3b083da95abb2ea0789b0a5623defaf)

### Which was updated more recently, ragflow or neko?

ragflow: its last push was on November 4, 2026, and neko's on October 28, 2026.

The proof: [infiniflow/ragflow's commits on GitHub](https://github.com/infiniflow/ragflow/commits)

### Which has more commits signed by AI, ragflow or neko?

ragflow: an AI signed 2.1% of its commits, with Claude Code, Cursor, CodeRabbit, GitHub Copilot, Kilo Code, Codex, OpenHands, Gemini CLI, and Factory; in neko, 0.2%.

The proof: [the commits each tool signed in infiniflow/ragflow](https://seerepo.com/r/infiniflow/ragflow/ai)

## Sources

- infiniflow/ragflow: Read on November 4, 2026, at commit 8cab68a (https://github.com/infiniflow/ragflow/tree/8cab68a9a3b083da95abb2ea0789b0a5623defaf)
- m1k1o/neko: Read on November 4, 2026, at commit 22e35dd (https://github.com/m1k1o/neko/tree/22e35dd52560acc4c17522b029c215c5cc6e14de)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.