What runs at your college
It runs on your servers. Your data stays yours.
ReadyHo installs on a server your college already has. Student work, marks and teacher comments stay there. Only a finished record a student chose to publish ever leaves.
What it does
One app, at an address on your own domain
You install ReadyHo on a server or cloud account your college already controls. It sits at
an address like ready.yourcollege.edu. That is a placeholder, not a real
college.
Everyone works in that one place. Teachers set the project and the scorecard. Students hand in work. An outside professional sees only the work they were asked to check.
You hold the keys. There is no ReadyHo admin account, and nobody here can sign in to your system.
The data boundary
What stays with you, and what goes out
The line is fixed. It is the same for every college and it is not something you configure.
Stays on your infrastructure
- Submitted work and drafts
- Drafted evaluations and their reasoning
- Faculty comments and marks
- Internal deliberation and revisions
- Every student who did not consent
Goes to the registry
Only a completed, approved record, and only for a consenting student
- The rubric and the scores
- The practitioner’s name and credentials
- The institution’s attestation
A first draft score your teacher overruled stays with you. The student never sees it. Students who publish nothing still get marked and still get feedback.
Your system reaches out to two places and no others. The AI provider you chose, on your own account. And the public record page, only when a student publishes.
Requirements
What you need to run it
Three things on the technical side.
-
A server
A modest server or cloud instance. Enough for your first few hundred students.
-
Half a day of IT time
One IT staff member, about half a day.
-
An AI account
An account with an AI provider, billed straight to you. Or your own hardware, if you would rather run the models in house.
The rest is people. Teachers willing to set projects. Professionals willing to check work. And a decision on student consent, taken with whoever handles data protection at your college.
The shape of a setup
docker compose up -d 100 to 300 rupees per student per year
There is no ReadyHo licence fee, and the public record pages are free for colleges, students and employers.
Why it is built this way
Why it is free, and why it runs on your kit
Because it holds exam material. Your system holds work in progress, draft marks nobody was meant to see, and comments a teacher later changed. Hand that to a vendor and you are renting access to your own records.
Because consent has to be real. India's data protection rules expect consent to be specific, informed, and something a student can take back. That is far simpler when the data never leaves you.
Because you should be able to keep it. The software is free to use under a licence called AGPL v3. Install it, change it, run it, with no fee. If this project stops tomorrow, your setup keeps running. You can fork it or hire anyone you like to support it.
One exception. The public record pages are run by us, in one place. They cannot be copied to each college, because checking a record only works if every record sits somewhere a reader can trust. That is a real dependency, and we would rather you heard it from us.
Boundaries
What this does not do
- It does not replace your other systems. ReadyHo is one app doing the assessment loop. No timetabling, no attendance, no course delivery, and no link into your student records system. It does not replace Moodle.
- It does not remove the AI provider. Unless you run models on your own hardware, student work goes to the provider you chose, under their terms.
- It does not give you your own copy of the public record pages. You can publish nothing at all, but there is no second registry to run.
Support is public
The issue tracker and the written documentation, with no private support line and no promised response time. If you need a guaranteed response, bring in an implementation partner. We encourage that.
Get started
ReadyHo is free and open source, and you keep everything it produces. Start with one course, or run it across your departments.
The rest of what runs at your college
- Set the work Your teacher writes the project and a simple scorecard once, then reuses both every year.
- Collect the work Send a project to one student, a group, or a whole year. The actual work comes back in one place.
- First draft scores Every submission comes back scored against your scorecard, with comments. No student ever sees this part.
- Your teacher decides Your teacher sees the work and the draft side by side, changes anything they disagree with, and sets the mark.
- An industry signature A working professional checks the same work and puts their name and credentials to it.
- The proof The work, the scorecard, all three opinions, and who gave each one. One page an employer can open.
- Student control Nothing is published unless the student says so, and they can change their mind at any time.
- Cost control You hold the account, pick what it uses, and set a spending limit. Nothing is billed through us.