For colleges
Your campus, administered by your own people.
Not a support ticket to a vendor. A console over exactly one college — with granular permissions, an audit log, and an export button you never have to ask us for.
18 min
to onboard
First login to live notice board
94%
notices read
Within 24 hours
9
permissions
Granted individually
1
college per admin
Enforced in the database
Campus console
Everything your campus runs, on one screen.
Overview, campus details, students, notices, moderation and your admin team. It opens on the queues that are waiting for someone, because that is what an administrator actually needs.
- Queues, not dashboardsVerifications, uploads and reports — with counts, oldest first, and one click to clear.
- Edit your campus yourselfName, branding, contacts, address, modules, attendance threshold, email domains.
- Publish your notice boardBy department, by audience, with deadlines pulled out and read receipts behind them.
- Verify your own studentsAutomatically from your email domain, or by hand from the queue.
The model
Four roles, and a hard line between each.
Most platforms give an administrator the keys and hope. This one hands out exactly one college — or exactly one subject — at a time, and writes down what was done with it.
Student
Scope · Their own rows
Uses the whole product. Sees their college's notices, papers and drives, and nothing belonging to any other student.
Professor
Scope · The subjects they teach
A teaching console over their own subjects: the register, the gradebook, assignments and their students' questions. Not a single row from a colleague's class.
Campus head
Scope · One college
Everything a student has, plus read and write over their own campus: its details, its students, its notice board, its moderation queues.
Super admin
Scope · The platform
Us, and whoever you nominate. Creates colleges, appoints campus heads, and cannot be quiet about it — every action is in the log.
The nine campus permissions
Granted individually, per person, per college
A T&P head who should publish placement notices but never edit the college gets exactly that: two permissions, one campus, and every notice they publish carries their name.
Placements
A placement cell that can see what happened.
Publishing a notice and hoping is not a process. Drives, eligibility, applications and outcomes live in the same place, so the cell can plan the next season against the last one.
- Campus drives alongside open rolesEligibility by branch, CGPA and backlog count, enforced at application.
- Read receipts on noticesWho has seen the deadline, and which students to chase before the form closes.
- Recruiter access you controlA switch per college, and a visibility switch per student on top of it.
- Outcomes, not just applicationsSelected, rejected, in interview — per company, per branch, per batch.
The four questions
What every principal asks in the first meeting.
All four have the same answer: it is enforced in the data model, and there is a log.
“Will another college see our data?”
It cannot. A campus administrator's access comes from a single database row naming exactly one college, and every query the console makes is filtered by that column. It is not a policy — it is the shape of the data.
“How do we know who changed what?”
An append-only audit log records every privileged write: the actor, their role, the campus, the entity and a before/after. Your campus head can read their college's log; nothing edits or deletes from it.
“What do students upload, and who checks it?”
Notes and papers land in a moderation queue and stay invisible until someone from your campus approves them. Every approval and rejection is recorded against the person who made it.
“What if we want to leave?”
Export your college's data as SQL or CSV from the console, without asking us. Self-hosting is available on the University plan. Leaving is a button, not a negotiation.
Onboarding
An afternoon, not a term.
No integration project, no data migration, no committee. The longest step is deciding which modules your college wants.
- 1
We create your college
Name, code, university, departments and branches. Ten minutes with someone from your office.
- 2
You appoint a campus head
From your own faculty. They get the console immediately and can delegate narrower permissions to their team.
- 3
Connect your email domain
Students signing up from @yourcollege.ac.in verify themselves, and your queue stays near zero.
- 4
Publish your first notice
That is the moment students start arriving. The papers library fills itself over the following fortnight.
The placement cell used to publish a notice and hope. Now we can see that 94% of the batch opened it, and which 6% we need to chase before the form closes.
Rajeev Nair
Training & Placement Head · PSIT Kanpur
What sold me was the scoping. My campus head can edit our campus and nothing else, and every change they make is in an audit log I can read.
Dr. Meera Joshi
Principal · PSIT Kanpur
Questions
What colleges ask us
Do we have to replace our ERP?
No, and we would advise against it. An ERP is a system of record for fees, admissions and results — built for your administration. Remote Campus is the layer students live in. Where you have an ERP worth reading from, we read from it; where you do not, your staff publish through the campus console.
Who from our college administers it?
Whoever you nominate. Usually the principal or a T&P head holds the primary appointment, and they delegate narrower permissions — publish notices, verify students, moderate uploads — to the people who actually do those jobs. Nine permissions, each granted separately.
What do our professors get?
A teaching console scoped to the subjects they are assigned: mark the register per class, keep the gradebook and decide when marks become visible, set and grade assignments, and answer questions their students ask them by name. Syllabus coverage and attendance percentages fall out of the register rather than being maintained by hand.
How much work is onboarding?
About an afternoon of your team's time. We create the college, you appoint a head, you connect your email domain so students verify themselves, and you decide which modules to switch on. The library fills itself once students start contributing.
Can we switch modules off?
Yes, per college, from the campus console. If your college does not want the mentors module or the AI layer, switch it off and your students never see it.
What about students who are not verified?
They can use the product, but they are invisible to recruiters, they cannot contribute to your library, and you are not billed for them. Verification is either automatic from your email domain or a queue your staff clear.
Pilot
Try it on one department for a semester.
Free, every module, a real campus head and real students. If it has not earned its place by the end of it, export everything and we will part on good terms.