Moveat documentation
Moveat is a nutrition and fitness product designed to help users log meals, body weight and workouts with the least possible friction. The product combines a web application, a business backend called Platform, and a conversational Agent that can operate through channels such as WhatsApp. This documentation is written for product, operations and engineering readers. It explains what Moveat is trying to achieve, how the core business flows work, and how the technical system supports those flows.What Moveat does
Moveat helps users:- Create an account and complete a fitness onboarding.
- Define goals such as fat loss, muscle gain or maintenance.
- Track meals and calories.
- Track body weight over time.
- Track workouts, exercises, sets, reps and loads.
- Use a conversational agent to reduce manual logging friction.
Main system components
| Component | Purpose |
|---|---|
| Web app | Human-facing client for signup, login, onboarding and dashboards. |
| Platform | Business backend and source of truth for user, nutrition, training and progress data. |
| Agent | Conversational orchestration service that receives messages, interprets intent and delegates business actions to Platform. |
| PostgreSQL | Durable source of truth for product data. |
| Redis | Short-lived session and conversational state cache. |
| Grafana and Loki | Operational observability for logs, errors and service behavior. |
Documentation map
- Overview explains the product logic and system shape.
- Product explains the user lifecycle and tracking modules.
- Technical explains Platform, Agent, APIs, auth and data ownership.
- Operations explains deployment, environments, observability and runbooks.