Config-driven partner portal with microservice architecture

Manual onboarding that couldn’t scale with demand

A rapidly growing investment platform faced a critical bottleneck: their partner onboarding process was manual, error-prone, and couldn’t scale with demand. Partners — ranging from individual investors to institutional families managing complex financial arrangements — needed a unified way to onboard, manage accounts, and access engagement tools, but the legacy monolithic backend couldn’t support the complexity.

Different partner types (NRI clients, individual investors, HUF entities) required custom onboarding paths, but no single system could handle them all. Client-facing documents were created manually, there was no visibility into partner engagement, and adding new features meant coordinating changes across multiple teams.

A config-driven partner portal built on microservices

Trinay built a modular microservice-based partner portal consisting of three core services: an Admin Service for centralized configuration management and dynamic multi-step onboarding forms, a Partner Service for self-service portal access with real-time notifications and media kit sharing, and an Auth Service for secure token-based authentication with role-based access control.

The config-driven onboarding system was the key innovation. Rather than hard-coding workflows, a configuration layer defines field validation rules, conditional branching logic, and document generation templates. New partner types can be onboarded without touching code — just updating configuration. This meant new partner types shipped in hours, not weeks.

A sophisticated notification system handles bulk email campaigns using Redis-based queuing, in-app notifications via AWS SQS FIFO for guaranteed delivery ordering, deduplication strategies, and engagement analytics tracking open rates, click-through rates, and partner interaction patterns.

Measurable impact at scale

Document generation time dropped from manual 30-minute tasks to automated 2-minute processes. The self-service portal reduced support tickets by 35%, and bulk communication campaigns reached partners 4× faster than the previous email-only approach. Engagement analytics revealed which communications actually drove partner action.

The system now supports 5,000+ monthly onboardings across 12+ partner types with zero-downtime deployments through containerization. Per-service scaling allows the notification service to scale independently during campaign seasons without affecting other services.

Why microservices and config-driven architecture

Each service has a single responsibility, making updates and scaling independent. Teams can deploy without coordinating with others, and clear API contracts reduce coupling and integration friction. The config-driven approach enabled the product team to iterate without engineering bottlenecks, reducing integration bugs by 60%.

Redis-based task queuing handles background jobs with retry logic, AWS SQS FIFO ensures message ordering and deduplication, and structured error handling manages batch operations gracefully. The platform is now positioned for advanced segmentation, AI-powered recommendations, and expansion to new geographies.