How danishyaseen-dev/zennou-version-nexqora works
Nexqora is an employee and business-operations platform with a web portal, a mobile app, HR workflows, and document management. Employees and managers use its clients to access capabilities such as attendance, leave, payroll, employee profiles, and documents; HR and administrators also manage analytics, recruitment, automations, and operations. The API is the backend entry point, with workflow execution and document services as distinct internal layers. The README is empty; unsampled feature links are limited to documented or indexed relationships.
Main entry points: backend/service.py Operations service · App.js Mobile app · engine.py Workflow engine · backend/service.py Document service
Components 21
User clients
- Web portal
core/frontend/src/App.jsx - Mobile app
nexqora-mobile/App.js - Mobile session
nexqora-mobile/src/context/AuthContext.js - Mobile API client
nexqora-mobile/src/api.js
API and HR
- API entry point
api/main.py - HR capabilities
modules/hr/backend/router.py - Operations API
modules/operations/backend/router.py - Operations service
modules/operations/backend/service.py
AI and workflows
- Operations workflows
modules/operations/backend/workflows.py - Workflow engine
workflows/engine.py - Workflow definitions
workflows/definitions.py - Workflow steps
workflows/steps.py - AI provider layer
workflows/llm.py
Document management
- Documents API
modules/documents/backend/router.py - Document service
modules/documents/backend/service.py - Document metadata
modules/documents/backend/repository.py
Shared platform
- PostgreSQL
- Database pool
core/db_pool.py - MinIO storage
- Storage adapter
core/storage.py
Other components
- Employees and managers
Connections 21
- Employees and managers → Web portal: uses
core/frontend/src/App.jsx - Employees and managers → Mobile app: uses
nexqora-mobile/App.js - Mobile app → Mobile session: provides session
nexqora-mobile/App.js - Mobile session → Mobile API client: loads profile
nexqora-mobile/src/context/AuthContext.js - Mobile app → Mobile API client: requests data
- API entry point → HR capabilities: mounts routes
api/main.py - API entry point → Operations API: mounts routes
api/main.py - Operations API → Operations service: calls
modules/operations/backend/router.py - Operations service → PostgreSQL: reads health
modules/operations/backend/service.py - Operations service → HR capabilities: delegates employee lookup
modules/operations/backend/service.py - Operations workflows → Operations service: reuses business logic
modules/operations/backend/service.py - HR capabilities → Workflow engine: invokes workflows
modules/hr/backend/router.py - Workflow engine → Workflow definitions: loads definitions
workflows/engine.py - Workflow engine → Workflow steps: dispatches steps
workflows/engine.py - Workflow steps → AI provider layer: uses AI
workflows/steps.py - Documents API → Document service: calls
modules/documents/backend/router.py - Document service → Document metadata: reads and writes metadata
modules/documents/backend/service.py - Document service → Storage adapter: stores file bytes
modules/documents/backend/service.py - Storage adapter → MinIO storage: uploads and retrieves
core/storage.py - Document metadata → Database pool: uses connections
modules/documents/backend/repository.py - Database pool → PostgreSQL: pools connections
core/db_pool.py