Source: https://seerepo.com/compare/hpcaitech/ColossalAI/vs/oumi-ai/oumi
Markdown source: https://seerepo.com/compare/hpcaitech/ColossalAI/vs/oumi-ai/oumi.md
Description: ColossalAI and oumi share 13 technologies: uvicorn, SQLAlchemy, tiktoken, torch, transformers, peft, datasets, safetensors, accelerate, torchvision, pillow, jsonlines, and Pydantic. Both are written in Python.

# ColossalAI vs oumi

ColossalAI and oumi share 13 technologies: uvicorn, SQLAlchemy, tiktoken, torch, transformers, peft, datasets, safetensors, accelerate, torchvision, pillow, jsonlines, and Pydantic. Both are written in Python.

- [hpcaitech/ColossalAI](https://seerepo.com/r/hpcaitech/ColossalAI): Making large AI models cheaper, faster and more accessible
- [oumi-ai/oumi](https://seerepo.com/r/oumi-ai/oumi): Easily fine-tune (SFT/RL), evaluate, and deploy Qwen, Gemma, or any open agentic LLM/VLM!

## What they share and what sets them apart

- In common: uvicorn, SQLAlchemy, tiktoken, torch, transformers, peft, datasets, safetensors, accelerate, torchvision, pillow, jsonlines, Pydantic
- Only in ColossalAI: FastAPI, chromadb, Hugging Face, anyio, Ray, Gradio, seaborn, matplotlib, Rich, ModelScope, OpenAI, rouge, scikit-learn, sentence-transformers, colossalai, LangChain, triton, diffusers, flash-attn, bitsandbytes, vLLM, einops, galore-torch, loralib, math-verify, sentencepiece, torchaudio, jinja2, markdown-it-py, markupsafe, mdurl, pypdf, unstructured, annotated-types, gpustat, psutil, fabric
- Only in oumi: pyarrow, PostHog, AIOHTTP, torchao, trl, lm-eval, MLflow, jsonschema

## Side by side

| | ColossalAI | oumi |
|---|---|---|
| Size | 319,283 lines written, 975 code files | 198,773 lines written, 430 code files |
| Who writes it | 0.3% of its commits signed by AI. With Codex and Claude Code | 2.2% of its commits signed by AI. With Claude Code, Cursor, and GitHub Copilot |
| Activity | Last push November 13, 2026, 3,904 commits, 41,424 stars | Last push November 12, 2026, 2,339 commits, 9,433 stars |
| Tests | 515 test files. 1.1% of its code files have a test that imports them | 287 test files. 66.3% 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, ColossalAI or oumi?

ColossalAI, with 319,283 lines written; oumi has 198,773.

The proof: [hpcaitech/ColossalAI's code at commit 297c8cf](https://github.com/hpcaitech/ColossalAI/tree/297c8cf6d91cb0bff795cba961d3aea1e66fa370)

### Which has more GitHub stars, ColossalAI or oumi?

ColossalAI, with 41,424 stars; oumi has 9,433.

The proof: [hpcaitech/ColossalAI on GitHub](https://github.com/hpcaitech/ColossalAI)

### Which has more tests, ColossalAI or oumi?

ColossalAI, with 515 test files; oumi has 287.

The proof: [hpcaitech/ColossalAI's code at commit 297c8cf](https://github.com/hpcaitech/ColossalAI/tree/297c8cf6d91cb0bff795cba961d3aea1e66fa370)

### Which was updated more recently, ColossalAI or oumi?

ColossalAI: its last push was on November 13, 2026, and oumi's on November 12, 2026.

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

### Which has more commits signed by AI, ColossalAI or oumi?

oumi: an AI signed 2.2% of its commits, with Claude Code, Cursor, and GitHub Copilot; in ColossalAI, 0.3%.

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

## Sources

- hpcaitech/ColossalAI: Read on November 13, 2026, at commit 297c8cf (https://github.com/hpcaitech/ColossalAI/tree/297c8cf6d91cb0bff795cba961d3aea1e66fa370)
- oumi-ai/oumi: Read on November 15, 2026, at commit 16517c8 (https://github.com/oumi-ai/oumi/tree/16517c8cd29921a044a4ea97ceac05b1e30e10a6)

## 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.
