Home » Technologies
The Tools We Use - and
Why We Use Them
Every technology in our stack has been chosen because it solves a real problem in a production
environment. We do not add to this list for the sake of an impressive slide — we add when a client
platform needs it, it has been validated under real load, and our engineers know it well enough to debug
it at 2am.
Tech Stack
Frontend Engineering
Building interfaces from enterprise admin portals to consumer-grade streaming apps and crossplatform mobile
- Angular : Primary enterprise web framework — used across operator CRM portals, hospital management dashboards, gaming admin consoles, and data-heavy internal tools requiring complex state management
- React / Next.js : Consumer-facing web — marketing sites and SEO-priority applications
- Vue.js : Lightweight admin dashboards and rapid-prototype interfaces
- Flutter : Cross-platform iOS and Android mobile — patient apps (mHealth), gaming apps, and consumer mobile products. Single codebase delivering native performance across both platforms
- TypeScript : Type-safe codebases across all frontend projects above a certain complexity threshold
- Tailwind CSS / Material UI / Ant Design : UI frameworks selected per project design system requirements
Backend Engineering
The processing, business logic, and data layer that powers our platforms
- Node.js (NestJS) : Real-time services, API-heavy platforms, and event-driven systems — used across gaming, OTT, and AI Call Centre backends
- Java Spring Boot : Enterprise-grade, high-throughput backends — chosen for systems where JVM performance and mature ecosystem matter
- Python (FastAPI / Django) : AI/ML services, data pipelines, and LLM integration endpoints — FastAPI preferred for low-latency inference APIs
- PostgreSQL / MySQL : Primary relational stores for structured, transactional data across most platform builds
- MongoDB : Document store for content-heavy and schema-flexible use cases — OTT metadata, health records
- Redis : Caching, session management, and real-time leaderboard state — used in gaming and voice platforms
- Kafka / RabbitMQ : Event streaming and message queuing for decoupled, async processing at scale
Cloud & Infrastructure
AWS-first with a DevOps-embedded approach on every project
- AWS (Primary) : EC2, ECS, EKS, Lambda, RDS, ElastiCache, S3, CloudFront, SQS, SNS — used across all production deployments
- GCP : Secondary cloud — used for AI/ML workloads and MedGemma integration
- Private VPC : Telecom operator private virtual cloud — used where operator data residency or network security requirements mandate on-operator-premises hosting
- Docker : All applications containerised for environment consistency from dev to production
- Kubernetes / ECS : Container orchestration — Kubernetes for complex multi-service deployments, ECS for simpler workloads
- Terraform : Infrastructure as Code — all production infrastructure version-controlled and reproducible
- GitHub / Bitbucket : Source control — GitHub for most projects; Bitbucket where client environment or existing tooling requires it
- Jenkins : Primary CI/CD — automated test, build, and deployment pipelines; ArgoCD for Kubernetes-native GitOps deployments
- Prometheus / Grafana / ELK : Observability — metrics, dashboards, and log aggregation from day one of every production deployment
AI, ML & LLM Frameworks
Production AI — integrated into platforms we build, not separate experiments
- GPT-4o (OpenAI) : Primary LLM — used in AI Call Centre Agent (conversation), mHealth (clinical support), and general LLM integrations
- Anthropic Claude : Alternative LLM — used where reasoning depth or context window requirements favour Claude
- Google MedGemma : Medically specialised LLM — deployed in production for clinical consultation summaries and patient-facing prescription explanations in our mHealth platform
- Google Gemini : Multimodal AI and GCP-native integrations
- LangChain / LlamaIndex : RAG pipeline orchestration, agent frameworks, and multi-tool LLM workflows
- Pinecone / pgvector / Weaviate : Vector databases for semantic search and knowledge base retrieval
- OpenAI Whisper : Speech-to-text — real-time STT for AI Call Centre Agent voice pipeline
- ElevenLabs / Azure TTS : Text-to-speech — natural voice synthesis for AI voice applications
- Ollama : Local SLM deployment for on-premise or air-gapped AI requirements
- HuggingFace Transformers : Open-source model evaluation and domain fine-tuning experiments
Telecom & Voice Technologies
Our core differentiator — 14+ years of production telecom engineering
- Asterisk : Open-source SIP server — used in RBT platform, IVR systems, and AI Call Centre Agent voice ingestion
- FreeSWITCH : Production SIP server for high-throughput voice — AI Call Centre Agent primary telephony layer
- Kamailio : SIP proxy and load balancer — used in high-availability operator deployments
- SMPP v3.4 : SMSC integration protocol — transactional and promotional SMS, subscriber notification flows
- SS7 / MAP : Core telecom signalling — USSD session management and HLR interfaces
- USSD Gateway : Interactive subscriber menus at zero data cost — deployed in mHealth and RBT platforms
- IN / CAMEL : Intelligent Network — real-time charging and service control for operator VAS platforms
- WebRTC : Browser and mobile real-time audio/video — mHealth telemedicine, AI voice web channel
Platform-Specific Technologies
Specialist tools used within specific platform domains
- FFmpeg : Video transcoding — in-house proprietary transcoding pipeline for OTT streaming platforms
- Widevine / FairPlay / PlayReady : DRM — content protection across OTT streaming clients
- HLS / DASH : Adaptive bitrate streaming protocols — OTT video delivery
- DDEX : Digital Data Exchange standard — global industry standard for digital media supply chain content ingestion, used in our OTT editorial CMS for automated content delivery from labels and distributors
- LensKit : Open-source recommendation engine — collaborative filtering for OTT content personalisation
- Telecom Airtime & Wallet Billing : Operator airtime deduction and mobile wallet integration for in-platform charges — used in gaming and VAS platforms to enable carrier billing without payment cards
- Google Maps Platform / Mapbox : Real-time GPS mapping — ambulance tracking (mHealth), fleet management (student transportation)
- Stripe / Razorpay : Payment gateways — OTT subscription billing and regional payment coverage
- HL7 / FHIR : Healthcare data exchange standards — EHR interoperability in mHealth platform
- Wowza Streaming Engine : Live streaming media server — OTT live broadcast delivery
Our Partner for
Software Innovation




Ready to Build Your Streaming Platform?
Whether you are starting from scratch or rebuilding what is not working — let’s talk
architecture, content model, and launch timeline.