A full-stack expense tracking application built with Vue.js and .NET, featuring JWT authentication, charts, and mobile responsiveness.
Vue Expenses is a full-stack web application built with Vue.js and .NET for tracking personal or business expenses. It allows users to log expenses, view detailed statistics through interactive charts, and manage their profile and settings. The application solves the need for a simple, self-hosted expense tracker with a modern UI and secure authentication.
Developers or individuals looking for a self-hosted, open-source expense tracking solution with a modern tech stack. It's suitable for those familiar with .NET and Vue.js who want a customizable personal finance tool.
Developers choose Vue Expenses because it offers a complete, production-ready full-stack example with clean architecture (CQRS, JWT authentication), modern UI components via Vuetify, and detailed visual analytics. It's fully open-source and self-hostable, providing full control over data and deployment.
A simple expense tracking application
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Implements CQRS with MediatR and Entity Framework Core, promoting separation of concerns and easier maintenance, as outlined in the server-side tech stack.
Uses JWT tokens with refresh token support via ASP.NET Core JWT Bearer Authentication, ensuring robust security for user sessions.
Built with Vuetify, providing a fully responsive design that works seamlessly across desktop and mobile devices, as shown in the screenshots.
Integrates Vue-ECharts for interactive charts and statistics, enabling detailed spending pattern analysis on the stats page.
Includes seeded dummy data and clear step-by-step instructions for running both the .NET backend and Vue frontend locally, simplifying initial exploration.
Defaults to SQLite only, which may not handle high concurrency or large datasets in production environments, as indicated in the config section.
The README only covers local building with no instructions for deploying to servers or cloud platforms, making production setup challenging.
The future enhancements to-do list suggests missing features like recurring expenses or data export, limiting out-of-the-box functionality for advanced users.
The demo link is struck out, indicating the live instance may not be available or regularly updated, reducing trust for potential adopters.