How vedikakute06/insurgenie works
InsurGenie is a wellness-oriented insurance platform: users sign in, log activity, and view scores and rewards, while a separate underwriting flow calculates risk from health, lifestyle, and driving inputs. The frontend routes to backend HTTP endpoints; backend handlers delegate to risk, authentication, and gamification logic backed by Supabase. The README also describes Google Fit tracking, but the sampled service is not shown wired into the activity endpoint. The graph includes documented capabilities while avoiding unverified connections.
Main entry points: main.py HTTP endpoints · App.jsx Route and session app · database.py Supabase client · auth.py Google identity logic
Components 16
User interface
- Route and session app
frontend/src/App.jsx - Google sign-in
frontend/src/pages/Login.jsx - Wellness dashboard
frontend/src/pages/Dashboard.jsx - Activity entry
frontend/src/pages/Gamification.jsx - Welcome page
frontend/src/pages/Home.jsx
Backend API
- HTTP endpoints
backend/app/main.py
Risk assessment
- Risk scoring engine
backend/app/controllers/risk_engine.py - Risk input schema
backend/app/schemas/schemas.py
Wellness and rewards
- Activity and rewards
backend/app/gamification.py - Fitness controller
backend/app/controllers/fitness.py - Google Fit client
backend/app/services/google_fit.py
Authentication and storage
- Google identity logic
backend/app/auth.py - Supabase client
backend/app/database.py - Supabase data store
Other components
- Policyholder
- Google identity provider
Connections 18
- Policyholder → Google sign-in: signs in
frontend/src/pages/Login.jsx - Google sign-in → HTTP endpoints: posts token
frontend/src/pages/Login.jsx - HTTP endpoints → Google identity logic: verifies and resolves
backend/app/main.py - Google identity logic → Google identity provider: verifies token
backend/app/auth.py - Google identity logic → Supabase client: queries and inserts
backend/app/auth.py - Supabase client → Supabase data store: connects
backend/app/database.py - Route and session app → Google sign-in: routes to
frontend/src/App.jsx - Route and session app → Wellness dashboard: routes to
frontend/src/App.jsx - Route and session app → Activity entry: routes to
frontend/src/App.jsx - Route and session app → Welcome page: routes to
frontend/src/App.jsx - Wellness dashboard → HTTP endpoints: gets dashboard
frontend/src/pages/Dashboard.jsx - Activity entry → HTTP endpoints: posts activity
frontend/src/pages/Gamification.jsx - HTTP endpoints → Risk scoring engine: calculates risk
backend/app/main.py - HTTP endpoints → Risk input schema: validates risk input
backend/app/main.py - HTTP endpoints → Activity and rewards: records and reads
backend/app/main.py - HTTP endpoints → Supabase client: updates score
backend/app/main.py - Activity and rewards → Supabase client: reads and writes
backend/app/gamification.py - Fitness controller → Google Fit client: calls service
backend/app/controllers/fitness.py