Ally Backend Service

A multi-tenant, AI-powered backend platform for mental health counselor training built with NestJS. It connects counselors and learners through real-time voice communication, scenario-based simulations, AI-driven feedback, and comprehensive analytics.

Overview

Ally Backend is the core API and event-processing service that:

• Powers scenario-based learning with simulated client conversations and learning pathways
• Provides real-time communication via WebSocket gateways and LiveKit voice/video rooms
• Processes audio and transcriptions through an async pipeline using AWS SQS and S3
• Delivers AI-driven insights including call summaries, live nudges, and session reports via LLM integration
• Enforces conversational guardrails to detect boundary violations in real time
• Manages multi-tenant access with role-based permissions, groups, and tenant isolation
• Supports gamification through a badge and community leaderboard system
• Integrates with AWS (S3, SQS, SES, CloudWatch) for storage, messaging, email, and audit logging
• Exposes a versioned REST API with Swagger/OpenAPI documentation

Architecture

The system is organized as a modular NestJS monolith with the following key layers:

Key Components

• REST API (src/*/controllers) - Versioned endpoints (/api/v1/) with JWT and API key authentication
• WebSocket Gateways - Real-time communication for microphone chat (/microphone-chat), audio ingestion (/audio-ingest), and scenario reporting (/scenario-report)
• LiveKit Integration (src/livekit/) - Voice/video room lifecycle, participant tracking, agent dispatch, and webhook handling
• Audio Pipeline (src/audio/, src/audio-ingest/) - Multipart S3 upload, SQS-based transcription requests, and DLQ handling
• AI / LLM Service (src/ai/, src/ai-chat/) - Streaming LLM responses via OpenAI, session summarization, and event analysis
• Conversational Guardrails (src/conversational-guardrails/) - Real-time boundary detection with multi-language support
• Prompt Management (src/prompt/, src/prompts/) - Versioned system prompts with dashboard sync and external override resolution
• Scenario Engine (src/learn/, src/scenario-path/) - Scenarios, learning pathways, and session management
• Review Systems (src/scenario-session-review/, src/scribe-session-review/) - Threaded comments, reactions, and badge awards on sessions
• Message Broker (src/message-broker/) - Redis pub/sub for inter-service events
• Scheduler (src/scheduler/) - Periodic background jobs via @nestjs/schedule
• Analytics (src/analytics/) - Metabase integration for dashboards and tenant-specific reporting

Technology Stack

Component	Tech Used
Backend	NestJS (Node.js v24)
Database	PostgreSQL + TypeORM
Caching	Redis
Real-time Comm	WebSocket (Socket.io) + LiveKit
Authentication	JWT, OTP, Google OAuth, Magic Link
AI / LLM	OpenAI (streaming), Deepgram (STT)
TTS	ElevenLabs, Deepgram, Sarvam, Google, Hume
Cloud Storage	AWS S3 (multipart, presigned URLs)
Messaging	AWS SQS + Redis message broker
Email	AWS SES
Audit Logging	AWS CloudWatch (HIPAA-compliant)
Analytics	PostgreSQL + Metabase
Observability	Winston Logger + Slack alerts
Documentation	Swagger/OpenAPI

Codebase Directory Structure

ally-be/
├── src/
│   ├── ai/                              # LLM integration (OpenAI), session summarization, event analysis
│   ├── ai-chat/                         # AI chat interfaces and provider abstraction
│   ├── analytics/                       # Metabase integration and tenant analytics dashboards
│   ├── app-version/                     # App version management
│   ├── audio/                           # Audio file storage and processing utilities
│   ├── audio-ingest/                    # SQS-based async transcription pipeline and DLQ handling
│   ├── audit/                           # Audit logging (AWS CloudWatch, HIPAA-compliant)
│   ├── auth/                            # JWT, OTP, Google OAuth, Magic Link authentication
│   ├── authorization/                   # RBAC guards and permission decorators
│   ├── aws/                             # AWS S3, SQS, SES service wrappers
│   ├── badge/                           # Badge definitions, award logic, bulk and auto awarding
│   ├── case/                            # Case management and tenant-isolated case items
│   ├── chat/                            # Chat session tracking
│   ├── common/                          # Shared utilities, interceptors, and decorators
│   ├── community/                       # Leaderboard and user ranking
│   ├── config/                          # Application configuration
│   ├── conversational-guardrails/       # Real-time boundary detection with multi-language support
│   ├── database/                        # TypeORM data source, migrations, and seed scripts
│   ├── exception/                       # Global exception filters
│   ├── factory/                         # Factory classes for testing
│   ├── health/                          # Health check endpoint
│   ├── language/                        # Language settings and translation service
│   ├── learn/                           # Scenario engine, learning pathways, and session management
│   ├── livekit/                         # LiveKit room lifecycle, participant tracking, and webhooks
│   ├── logger/                          # Winston logger configuration
│   ├── message-broker/                  # Redis pub/sub for inter-service events
│   ├── notification/                    # Email and push notification delivery (AWS SES)
│   ├── place/                           # Location and place data
│   ├── prompt/                          # Prompt management and dashboard sync
│   ├── prompts/                         # Versioned system prompt definitions
│   ├── queue/                           # SQS queue setup and configuration
│   ├── rate-limit/                      # Request rate limiting
│   ├── redis/                           # Redis client configuration
│   ├── reference-document/              # Reference materials associated with scenarios or pathways
│   ├── review/                          # Shared review utilities
│   ├── scenario-character/              # Scenario NPC/character (client persona) definitions
│   ├── scenario-cover-image-library/    # Scenario cover image management
│   ├── scenario-path/                   # Learning pathway composition
│   ├── scenario-report/                 # Real-time scenario reporting WebSocket gateway
│   ├── scenario-session-review/         # Threaded comments, reactions, and badge awards on sessions
│   ├── scheduler/                       # Periodic background jobs (@nestjs/schedule)
│   ├── scribe-session-review/           # Transcript-based feedback with threaded comments
│   ├── session-event/                   # Session event tracking and storage
│   ├── settings/                        # Application settings management
│   ├── tenant/                          # Multi-tenant management and isolation
│   ├── user/                            # User profiles and management
│   └── voice-preview/                   # TTS voice preview (ElevenLabs, Sarvam, Google, Hume)
├── docs/                                # Additional documentation (prompts API, folder conventions)
├── test/                                # End-to-end tests
├── .env.example                         # Local development environment template
├── docker.env.example                   # Docker Compose environment template
├── docker-compose.yml                   # Infrastructure services (Postgres, Redis, LocalStack, SQS)
├── Makefile                             # Convenience make targets
├── nest-cli.json                        # NestJS CLI configuration
├── tsconfig.json                        # TypeScript configuration
└── package.json                         # Dependencies and npm scripts

Prerequisites

Before you begin, ensure you have the following installed:

Required Software

• Node.js (v24) - Download
• npm - Comes with Node.js
• Docker (v20.10 or higher) - Download
• Docker Compose (v2.0 or higher) - Usually included with Docker Desktop
• PostgreSQL (v14 or higher) - For local development (optional, Docker recommended)
• Redis - For local development (optional, Docker recommended)

Required Accounts & API Keys

• LiveKit Account - For WebRTC audio/video calls (Sign up)
• OpenAI Account - For LLM-powered summaries, guardrail detection, and translations
• Deepgram Account - For speech-to-text transcription
• AWS Account (optional) - For S3, SQS, SES, CloudWatch (LocalStack can be used for local dev)
• Metabase (optional) - For analytics dashboards
• Slack (optional) - For exception alerts

Installation

1. Clone the Repository

git clone <repository-url>
cd ally-be

2. Configure Environment

Copy the sample environment files:

cp docker.env.example docker.env
cp .env.example .env

Edit docker.env and .env with your credentials. See Environment Configuration for details.

3. Start Infrastructure Services

Start PostgreSQL, Redis, LocalStack, and SQS using Docker Compose:

docker-compose up

Make sure the SQS URLs in your .env file match the ones shown in the Docker output.

Note: The app service in Docker requires manual execution. Follow the steps below to run it.

4. Run Database Migrations

npm run migration:run

5. Start the Application

npm run start:dev

The application will be available at:

• Swagger Docs: http://localhost:8001/api-docs
• Health Check: http://localhost:8001/api/health

Production Mode

npm run build
npm run start:prod

📦 Environment Configuration

The application uses two environment files:

1. .env - For local development (running without Docker)
2. docker.env - For Docker Compose setup

Refer to .env.example and docker.env.example for all available configuration options.

Note: The docker.env file is used by Docker Compose services. The .env file is used when running the app directly with npm run start:dev.

🗄️ Database Management

Migrations

# Generate a new migration
npm run migration:generate --name=YourMigrationName

# Create an empty migration file
npm run migration:create --name=YourMigrationName

# Run pending migrations
npm run migration:run

# Revert last migration
npm run migration:revert

# Show migration status
npm run migration:show

Database Connection

• Host: localhost (or postgres in Docker)
• Port: 5477 (mapped from container's 5432)
• Database: Value from DB_DATABASE in docker.env
• Username: Value from DB_USERNAME in docker.env
• Password: Value from DB_PASSWORD in docker.env

Database Seeding

Seeds live in src/database/seeds/ and insert the minimum dataset needed for local development directly via TypeORM (no running server required). The fixture data is inline TypeScript in fixtures.ts — edit it there if you need to add/change seeded records.

What gets seeded:

• 1 tenant (ally)
• 4 test users: [email protected] (SUPER_ADMIN), [email protected] (ADMIN), [email protected] (LEARNER+COUNSELOR), [email protected] (MULTI_TENANT_ADMIN)
• One scenario voice per active language (13 by default), 3 session events, 2 scenarios, 1 pathway, 1 case, 4 badges
• 3 scenario sessions (2 completed with sample transcripts, 1 active) so scribe-reviewer and admin dashboards have data to read

Commands

# Seed the DB (idempotent — safe to re-run; existing rows are matched by unique key and skipped)
npm run seed

# Truncate all seeded tables, then re-seed from scratch
npm run seed:reset -- --confirm && npm run seed

seed:reset refuses to run without --confirm (or SEED_RESET_CONFIRM=1) and refuses entirely when NODE_ENV=production. It uses TRUNCATE ... CASCADE across the 14 seeded tables, so rows in other tables with foreign keys to these will also be deleted — run against a dev DB only.

Login credentials

All seeded users share the same password and OTP:

• Password: Password123! (override with SEED_DEFAULT_PASSWORD)
• OTP: 1234 (override with SEED_DEFAULT_OTP; also needs matching entry in TEST_ACCOUNTS in .env for OTP login to work)

Docker

Set AUTO_SEED=true in .env to run npm run seed once after migrations on container start (see docker-compose.yml). Or run manually:

docker compose exec app npm run seed

📚 API Documentation

Once the application is running, access the interactive API documentation:

• Swagger UI: http://localhost:8001/api-docs

The API is versioned and accessible at:

• v1: http://localhost:8001/api/v1/...

Authentication

Most endpoints require JWT authentication:

Authorization: Bearer <your-access-token>

The platform supports multiple authentication methods:

• JWT - Standard access/refresh token flow
• OTP - Email-based one-time password (v2)
• Google OAuth - Sign in with Google
• Magic Link - Email-based passwordless authentication
• API Key - X-API-Key header for service-to-service calls

Key API Endpoints

Endpoint	Description
POST /api/v1/auth/login	User login
POST /api/v1/auth/refresh	Refresh access token
POST /api/v1/auth/generate-otp	Generate OTP (v2)
POST /api/v1/auth/verify-otp	Verify OTP (v2)
POST /api/v1/auth/google	Google OAuth sign-in
POST /api/v1/auth/magic-link/verify	Magic link verification
GET /api/v1/users/me	Get current user profile
GET /api/v1/health	Health check endpoint
GET /api/v1/badges/me	Get current user's badges
GET /api/v1/community	Community leaderboard
GET /api/v1/community/my-rank	Current user's rank
GET /api/analytics/*	Analytics dashboards
GET /api/tenant-analytics/*	Tenant-specific analytics

Prompts API (dashboard and sync): See docs/prompts-api.md. Prompt folder (naming, meta JSON): docs/prompts-folder.md.

✨ Key Features

Scenario-Based Learning

• Learning Pathways - Compose ordered sets of scenarios into guided learning paths
• Scenario Characters - Define client personas (NPCs) for realistic simulations
• Session Management - Track learner progress through scenario sessions
• Trigger Warnings - Content warning system for sensitive scenario content
• Reference Documents - Associate supporting materials with scenarios or pathways
• Voice Preview - Text-to-speech preview for scenario voices (ElevenLabs, Deepgram, Sarvam, Google Cloud, Hume)

AI & Audio Pipeline

• LLM Integration - Streaming responses via OpenAI for session summaries and analysis
• Audio Processing - Multipart S3 upload with presigned URLs; SQS-based async transcription pipeline with DLQ support
• Conversational Guardrails - Real-time boundary detection using binary classification, with multi-language support and automatic agent redirect
• Session Reports - AI-generated post-session analysis and scoring

Real-Time Communication

• WebSocket Gateways
  • /microphone-chat - Live audio chat with message streaming
  • /audio-ingest - Cloud telephony integration
  • /scenario-report - Real-time scenario reporting
• LiveKit Integration - Voice/video room creation, participant lifecycle, agent dispatch, and webhook handling
• Redis Message Broker - Pub/sub for inter-service event delivery

Review & Feedback

• Scenario Session Review - Threaded comments, emoji reactions, read status tracking, and badge awards
• Scribe Session Review - Transcript-based feedback with comment threads and reactions
• Case Management - Case creation, session tracking, and tenant-isolated case items

Gamification & Community

• Badge System - Achievement badges with bulk and automatic awarding for milestones
• Leaderboards - Global and scenario-specific leaderboards with user ranking

Prompt Management

• Versioned Prompts - Store and version system prompts used across AI services
• Dashboard Sync - Sync prompts from external sources
• Per-Tenant Overrides - Resolve tenant-specific prompt variants at runtime

Multi-Tenant Platform

• Tenant Isolation - Cases, scenarios, dashboards, and analytics scoped per tenant
• Role-Based Access Control - Fine-grained permissions via groups and permission guards
• Tenant Analytics - Metabase integration with tenant-specific dashboard views

Multi-Language Support

• Translation Service - OpenAI-powered translations for session events and guardrail content
• Language Module - Configurable language settings per tenant or scenario
• Sarvam STT/TTS - Indian language support

🧪 Testing & Code Quality

Testing

# Run all tests
npm run test

# Run tests in watch mode
npm run test:watch

# Run tests with coverage
npm run test:cov

# Run end-to-end tests
npm run test:e2e

# Run tests inside Docker
npm run test:docker

Linting & Formatting

# Check for linting errors
npm run lint

# Auto-fix linting errors
npm run lint:fix

# Format code with Prettier
npm run format

🔍 Observability & Logging

Logging

• Winston - Structured logging with multiple transports
• CloudWatch - HIPAA-compliant audit logging (optional)
• Console Logging - Configurable log levels

Configure log level via LOG_LEVEL environment variable:

Level	Description
error	Only errors
warn	Warnings and errors (default)
info	Info, warnings, and errors
debug	All logs including debug messages

Monitoring

• Health Checks - Built-in health check endpoints (/api/health)
• Slack Alerts - Exception and error notifications
• CloudWatch Logs - Audit trail for HIPAA compliance

🐛 Troubleshooting

Database Connection Errors

# Check if PostgreSQL is running
docker-compose ps postgres

# Check PostgreSQL logs
docker-compose logs postgres

# Verify DB_HOST=postgres (for Docker) or localhost (for local) in docker.env

Redis Connection Errors

# Check if Redis is running
docker-compose ps redis

# Test Redis connection
docker-compose exec redis redis-cli ping

SQS Queue Errors

# Check LocalStack logs
docker-compose logs localstack

# Verify SQS queues are created
docker-compose logs sqs-setup

# Recreate queues if needed
docker-compose restart sqs-setup

Port Already in Use

# Find process using port 8001
lsof -i :8001

# Kill the process or change PORT in docker.env

Migration Errors

# Check migration status
npm run migration:show

# Ensure all required environment variables are set before retrying
npm run migration:run

Debug Mode

LOG_LEVEL=debug
NODE_ENV=development

👥 Contributing

For contributing guidelines, refer to CONTRIBUTING.md.

📞 Support

For issues, questions, or contributions:

• Open an issue on GitHub
• Contact the development team
• Check the API documentation at /api-docs

---