One workspace for projects, docs, code context, and task status — with an AI you can simply ask.

Live demo: https://cragai-tech.vercel.app/
Built by: Prathamesh Patil
Source: Private (startup codebase). Architecture walkthrough and temporary read access available on request.

Try it in 2 minutes


URL	https://cragai-tech.vercel.app/
Email	`[email protected]`
Username	`reviewer`
Password	`CragReviewer#2026`

Sign in with the account above.
Open Projects and pick a project.
On the board, open a task and try Docs (project pages).
Open Docs Hub to see generated documentation.
Open Chats and ask something like:
- "What tasks are still open and who owns them?"
- "Summarize the architecture from the project docs."
- "Which task is blocked, and why?"

Demo account is a regular member of a demo organization, not an admin. Data is sample data and may be reset.

The problem

Project context lives in too many places: requirements in docs, progress in a task board, truth in the code, decisions in chat. Teams lose time asking "where is this written?" and "who is doing what?". Status reports and documentation go stale the moment code is merged.

What CRag does

Problem	CRag's answer
Context split across docs, Git, and boards	One workspace per project: plan, docs, board, and chat
Starting a project means writing the backlog by hand	A short brief becomes a discovery interview, architecture, and a task backlog
Status updates are manual	Git webhooks update task progress as code lands
Docs go stale after merges	Docs Hub regenerates project docs and progress summaries from the codebase
"Where is this, and who owns it?"	Chat answers from project docs, code, and live task status, with sources
One company's data must never reach another	Multi-organization isolation with role-based access

One workspace for projects, docs, code context, and task status — with an AI you can simply ask.

Try it in 2 minutes

The problem

What CRag does

Major features

1. Multi-organization workspace and access control