Evidence-backed capability, for students and their colleges
Let the work speak.
You've been building. Orizenn reads your repositories and shows what that work actually proves: which capabilities you've demonstrated, where the evidence is thin, and what changed since last time. Your record, owned by you. When your college runs Orizenn, they see the same evidence, never a score.
I'm a student
See what your work proves.
Connect GitHub, pick your repos, get your record in minutes.
Connect your GitHubI run a department
See the work behind the outcomes.
A paid six-week pilot with one batch. No integration.
See how a pilot works160+ real analyses run, Free for students, No sign-up forms, just GitHub
01, The problem
The work is there. We just don't see enough of it.
Students build real work across code, notebooks, docs, data and projects. Most of it gets reduced to a CGPA, a resume, a certificate or a placement record.
Example: a fictional student and record.
01: CGPA
Grade card · B.Tech CSE · Semester 5
8.4/ 10
A snapshot, not the work.
Survives One number
Loses: 47 commits, 23 tests, the schema, the README, the auth middleware
02: Resume
Resume · Skills
Node.js · Express · Prisma · JWT
Skills listed. Context missing.
Survives Four tool names
Loses: Where each tool was used, how well, and what it proves
03: Certificate
Certificate of completion
Full-stack web development
Completed · 12 Aug 2026
Completion, not capability.
Survives A date
Loses: Everything that was built before it
04: Placement record
Placement record · Batch of 2027
Placed
Service company
What happened, not what they can do.
Survives An outcome
Loses: The work behind it, and the time to act on it
The evidence exists. It just gets lost.
02.1, A different approach
Start with the work.
Orizenn begins with the work itself, not the claim made about it. It finds the artifacts inside a project, pulls out specific cited evidence, and puts it in view.
Example: a fictional student and record.
- src/middleware/auth.ts:42
Token verified before the route handler runs.
- prisma/schema.prisma:12-58
Six models related with foreign keys and cascades.
- tests/expense.test.ts:1-90
Routes and validation covered by automated tests.
Evidence
not Assumption
Technical work should be understood through the evidence inside it.
02.2
A real project. A clearer picture.
01 of 5: Project
A real repo, as the student built it.
02 of 5: Artifacts
Code4
- middleware/auth.ts
- routes/expenses.ts
- routes/admin.ts
- schemas/expense.ts
Tests2
- expense.test.ts
- auth.test.ts
Schema1
- schema.prisma
Docs1
- README.md
Config1
- package.json
Every file sorted by what it is.
03 of 5: Evidence
- src/middleware/auth.ts:42
Token verified before the route handler runs.
- prisma/schema.prisma:12-58
Six models related with foreign keys and cascades.
- tests/expense.test.ts:1-90
Routes and validation covered by automated tests.
- src/schemas/expense.ts:1-40
Request bodies validated at the boundary.
- README.md:14
Claims rate limiting on every route. No code found.
Specific lines, each with a one-sentence reading.
04 of 5: Evaluation
Observed · kept
- src/middleware/auth.ts:42
Token verified before the route handler runs.
- prisma/schema.prisma:12-58
Six models related with foreign keys and cascades.
- tests/expense.test.ts:1-90
Routes and validation covered by automated tests.
- src/schemas/expense.ts:1-40
Request bodies validated at the boundary.
Unconfirmed · set aside
- README.md:14
Claims rate limiting on every route. No code found.
Only confirmed evidence counts. Uncertain findings are held back.
05 of 5: Findings
Not Uses Node.js, Express, Prisma, JWT
- Backend Engineering
- API Design
- Authentication & Authorization
- Database & Data Modeling
- Validation & Error Handling
Technology is the evidence. Capability is the finding.
Example: a fictional student and record.
03.1, For students
Nobody reads your GitHub. Orizenn does.
Connect your account, choose the repositories that are yours, and every meaningful push updates your record. No forms. No self-rated skills. No score to game.
Student 047 / cohably
3 pushes
Capabilities
- Backend EngineeringDEMONSTRATED
- API Designwas EmergingDEMONSTRATED
- Database & Data ModelingDEMONSTRATED
- Authentication & Authorizationwas EmergingDEMONSTRATED
- Testing & Quality Automationwas InsufficientEMERGING
- Infrastructure & DeploymentINSUFFICIENT
What changed
- RESOLVEDFirst test suite added (23 tests)tests/expense.test.ts:1-90
- NEWInput validation at every boundarysrc/schemas/expense.ts:1-40
- PERSISTENTNo deployment evidence
Example: a fictional student and record.
What you've demonstrated
Capabilities with the file and line that prove them.
Where evidence is thin
Not "you're bad at testing". "No test suite found in 3 of 4 repos."
What changed
Every push: what's new, what got fixed, what's still there.
Who sees it
You. Your college only if you're in a pilot with them, and only the same evidence you see.
Your record is yours. It goes with you when you graduate.
Free, Takes about 5 minutes, Reads only the repos you choose
03.2, Ask it why
Ask it why.
Every capability opens up into the evidence behind it. If Orizenn can't point to the work, it doesn't make the claim.
API Design
Confidence: HighEvidence: 6 items across 3 projects
State: demonstrated
18router.post("/expenses", validate(ExpenseIn), create);31res.status(201).json(expense);47if (!expense) return res.sendStatus(404);
Related: Validation & Error Handling · Authentication & Authorization
Example: a fictional student and record.
- No claim without evidence
- Strength and confidence tracked separately
- Documentation alone proves nothing
04.1, For departments
Pilot programMore visibility into the work that matters.
See the work behind the outcomes.
Backend Engineering
API Design
Authentication & Authorization
Testing & Quality Automation
Infrastructure & Deployment
Student 047Backend Engineering demonstratedAPI Design demonstratedAuthentication & Authorization demonstratedTesting & Quality Automation emergingInfrastructure & Deployment insufficient
Hover a dot, or use the arrow keys, to follow another student.Tap a dot to follow another student.
Student 047: Backend Engineering demonstrated, API Design demonstrated, Authentication & Authorization demonstrated, Testing & Quality Automation emerging, Infrastructure & Deployment insufficient
Example: a fictional student and record.
- Which capabilities are weak across the batch?
- Who is improving?
- Who has stalled?
- Who is strong but invisible?
- Who needs attention, and what is the evidence?
The department view is in pilot. The student analysis underneath it is live today.
04.2, What it isn't
You already have systems. None of them answers this question.
| System | What it tells you |
|---|---|
| LMS | Who logged in and what they submitted. |
| Resume | What the student chose to claim. |
| GitHub | Files. Thousands of them. |
| Assessment | How one hour went. |
| Placement data | What happened, after it's too late to change it. |
| OrizennFor you: a record you own. For your college: the same evidence, in aggregate. | What each student can demonstrably do, how it's changing, and the evidence for it. |
Orizenn sits above the tools your students already use. Nothing to migrate. Nothing to replace.
Questions
Two things students ask first.
- Is it free for students?
- Yes. Connecting your GitHub, choosing your repositories and getting your record is free for students.
- Can my college see my repos without me knowing?
- No. A college only sees evidence for students enrolled in a pilot with them, and only from the repositories you chose to connect. You see exactly what they see: the same capabilities, the same cited lines.
A clearer way to understand technical work
Let the work speak.
Colleges know who submitted the work. Very few know what their students are becoming capable of.
No student should graduate invisible.
Students: see what your work proves.
Departments: see the work behind the outcomes.