Loading
About
What Grove is, who builds it, and why it exists.
Grove is a discovery platform for student-built projects — hackathon builds, research prototypes, coursework that outgrew its brief, side projects, and half-finished experiments looking for collaborators.
Students build remarkable things every semester, and almost all of it disappears into private repositories, expired demo links and forgotten slide decks. The work was real; the record of it was not. Grove exists so that it gets found, credited and continued.
It is not a portfolio host, a job board, or a social network that happens to contain code. It is a place where a project can be posted while it is still unfinished, and where the person who would have finished it with you can actually find it.
Grove is built and operated by VioniX, a student-led product studio. A studio rather than a club: we take products from the idea through design, engineering and release, and we keep running them afterwards. Grove is one of those products, and the one we use ourselves.
That shapes how the platform gets built. Everything here is shipped by people who are also students on a campus, posting their own projects into the same feed, which is a short and honest feedback loop.
Unfinished work is worth showing. A project that stalled at 60% is more useful to another student than a polished demo with the interesting parts removed, and it is far more likely to find a collaborator.
Credit should be specific. Teams are real, contributors are named, and the person who did the work is the person whose profile it appears on.
Discovery should not require self-promotion. The feed is chronological and the ranking is transparent, so being seen is not a reward for posting the most.
Projects on Grove are public and readable by anyone. Posting, liking, following, joining a team and browsing builder profiles require an account, which is issued against the campus email domain Grove is currently open to.
Builder profiles are deliberately behind sign-in. Students joined to share projects, not to be enumerated by anyone who fetches a page.
Feedback, bugs, feature requests, takedown requests, privacy questions, or an idea for something VioniX should build next — all of it reaches us at , and a person reads every one.
If something on Grove is broken, telling us what you were doing when it broke is worth more than an apology for the length of the message.
