How rajat-wyrm/salesforge works
SalesForge is a full-stack sales CRM and revenue operations workspace. Users authenticate, work in organization-scoped sales workflows—prospecting and managing leads, deals, and customer activity—and use reporting, automation, integrations, and billing capabilities. The frontend presents these workflows; its API client connects to an Express API that mounts feature routes, with PostgreSQL-backed account, subscription, and session operations evidenced in sampled controllers and services. The tree indicates additional product areas, but their internal call paths were not sampled, so those links are shown only at the mounted-route level.
Main entry points: app.js Express API · AppRouter.jsx App router · api.js API client · postgres.js PostgreSQL
Components 26
Web workspace
- SalesForge UI
frontend/src/App.jsx - App router
frontend/src/router/AppRouter.jsx - API client
frontend/src/lib/api.js - Lead workspace
frontend/src/pages/Dashboard/Leads.jsx - Deals workspace
frontend/src/pages/Dashboard/Deals.jsx - Analytics workspace
frontend/src/pages/Dashboard/Analytics.jsx - Prospect search
frontend/src/components/Tools/Database/DatabaseSearch.jsx
API surface
- Express API
backend/app.js - Authentication routes
backend/routes/authRoutes.js - Lead routes
backend/routes/leadRoutes.js - Deal routes
backend/routes/dealRoutes.js - Analytics routes
backend/routes/analyticsRoutes.js - Team routes
backend/routes/teamRoutes.js - Billing routes
backend/routes/billingRoutes.js - Workflow routes
backend/routes/workflowRoutes.js - Integration routes
backend/routes/integrationRoutes.js - Other feature routes
backend/routes
Workspace platform
- Account lifecycle
backend/controllers/authController.js - Organization and team
backend/controllers/teamController.js - Plans and payments
backend/controllers/billingController.js - Session service
backend/services/sessionService.js
Runtime services
- PostgreSQL
backend/config/postgres.js - Redis
backend/config/redis.js
Other components
- Sales user
- Razorpay
- Google OAuth
Connections 29
- Sales user → SalesForge UI: uses
- SalesForge UI → App router: renders
- App router → Lead workspace: routes to
- App router → Deals workspace: routes to
- App router → Analytics workspace: routes to
- App router → Prospect search: routes to
- Lead workspace → API client: requests data
- Deals workspace → API client: requests data
- Analytics workspace → API client: requests data
- Prospect search → API client: searches leads
- API client → Express API: HTTP requests
- Express API → Authentication routes: mounts
- Express API → Lead routes: mounts
- Express API → Deal routes: mounts
- Express API → Analytics routes: mounts
- Express API → Team routes: mounts
- Express API → Billing routes: mounts
- Express API → Workflow routes: mounts
- Express API → Integration routes: mounts
- Express API → Other feature routes: mounts
- Team routes → Organization and team: dispatches
- Account lifecycle → PostgreSQL: reads and writes
- Account lifecycle → Google OAuth: verifies credential
- Account lifecycle → Session service: session operations
- Session service → PostgreSQL: reads and writes
- Organization and team → PostgreSQL: organization data
- Plans and payments → PostgreSQL: subscription data
- Plans and payments → Razorpay: creates and verifies payments
- Express API → Redis: connects at startup