What usually goes wrong
- Course projects live in chat threads and personal repositories, and vanish at the end of term.
- Lecturers have no way to see who contributed what without reading every commit.
- Students learn Git but never see a requirement traced to a test to a release.
How Oprex handles it
🎓
A workspace per class
Groups and projects mirror faculties, courses, and teams — with per-project access so cohorts do not read each other's work.
🔌
Connects to the repo you already use
Link a GitLab or GitHub repository to a project so commits, pipelines, and releases line up with the requirements they implement.
✨
AI as a teaching aid
Students connect Claude Code or Cursor to their project over MCP and watch an agent work against real specifications.
What the flow looks like
| Step | What happens |
|---|---|
| Create a group per course | One namespace, one place for every team's project. |
| Students form project teams | Invite by email; membership decides what each student can see. |
| Work the full cycle | Requirement, specification, test case, bug, release — the same objects a company uses. |
| Assess from evidence | Activity, coverage, and release history replace "who did the work?" guesswork. |
Verified schools and campuses get an expanded free tier — more projects, more storage, and unlimited members. Talk to us and we will set it up.
Other use cases
Start free, today
A personal workspace is created the moment you sign in. Three projects, the full lifecycle, AI, and MCP included — no card, no sales call.
Get started free See pricing