Muni | Devpost

Muni's dashboard; view base document information.
Muni's financial insights page; dig deep into your finances.
Upload your financial documents; you can preview, archive, or delete them.
Muni assistant: chat with a chatbot to discuss your finances and future in more detail.

Why Muni?:

University students often have to manage several types of financial documents, such as scholarships, FAFSA, tuition, and other important amounts. The thing is, financial information can be scattered across many different documents. In turn, hidden costs, deadlines, and funding conflicts are easy to overlook.

Students struggle to determine whether an opportunity is financially realistic or not, and they lack a clear picture. To solve this, Muni manages financial documents (scholarships, etc.) for students, finds inconsistencies, and helps them make smarter financial decisions.

What it does:

Muni allows you to put your academic financial documents into a secure system where you can process them intuitively. It analyzes, cross-checks, and simplifies your finances so you can make informed, accurate decisions about your academic finances.

How we built it:

For Muni's frontend, we used React, Vite, and Tailwind, and deployed it on Vercel. For the backend, we used FastAPI and deployed it on Render. We implemented the Gemini API for the chatbot.

Challenges we ran into:

There were several instances where we had trouble integrating what each team member worked on into the whole. Connecting the frontend to the backend, then implementing the Auth0 system took some time and effort, but we eventually brought everything together to create Muni.

Accomplishments that we're proud of:

We're proud of creating a functional platform that brings together several aspects of student finances in one place. We designed an intuitive dashboard that makes complicated financial information easier to understand. We're especially proud of implementing document comparisons to help students identify inconsistencies that might otherwise go unnoticed. Despite challenges with integration, we were able to combine our individual contributions into a cohesive application.

What we learned:

Throughout this hackathon, we learned how to collaborate effectively while developing different parts of the same project. We gained experience integrating frontend and backend systems, implementing authentication with Auth0, and working with APIs. We also learned the importance of communication, version control, and adapting quickly when things didn't work as expected.

What's next for Vibe Coder FNB:

In the future, we hope to expand Muni's capabilities by supporting more types of financial documents and improving the accuracy of our document analysis. We also want to introduce personalized financial recommendations, smarter deadline tracking, and additional tools to help students plan their academic expenses. Ultimately, our goal is to make Muni a reliable and intuitive platform that students can use throughout their college experience.