Almost Fit is a gym management platform I'd describe as three jobs in one system: front-desk admin, trainer coaching, and member engagement, all running on one shared data model. It's built with Django 4.2, and each of the three roles gets its own portal. Admins handle membership plans, pricing, trainer accounts, announcements, the public gallery, and revenue. Trainers publish their availability, write day-by-day diet and workout plans (with reusable templates they can assign to many clients at once), and review each client's progress and leave feedback. Members work through a daily checklist, book sessions on a calendar, log body measurements, check progress charts, and pay for memberships online. Access is controlled on two levels. Each membership plan unlocks specific portal tabs for members, admins choose which modules each trainer can use, and the server enforces the same rules on every protected endpoint. Payments go through eSewa, Nepal's digital wallet, using HMAC-SHA256 signed requests. A membership only activates after the transaction is verified server-to-server against eSewa's status API, and every attempt is logged for auditing. One shared analytics engine calculates 30-day diet and workout consistency, workout streaks, BMI, weight and measurement changes, and plateau alerts, so members and trainers see the same numbers. Cloudinary handles media uploads, the CalorieNinjas API powers plain-language nutrition lookup, and SMTP covers email-verified registration. The code is split into six Django apps (accounts, gym, nutrition, scheduling, payments, and staff_control). It uses SQLite locally and PostgreSQL in production, renders server-side templates with vanilla JavaScript, FullCalendar, and Chart.js, and is deployed on Vercel. The source is public on GitHub under the CodeTrioo account.
