Technology stack
Technologies chosen to fit the architecture.
Our stack covers backend services, frontend applications, databases, messaging, containers, cloud, quality engineering and AI. Technologies are chosen to fit the architecture and operating needs of each solution.
| Layer | Technologies | Used for |
|---|---|---|
| Backend | Python FastAPI, .NET Core MVC / Web API, ASP.NET Core, Node.js | APIs, business logic, microservices and integration layers |
| Frontend | ReactJS, TypeScript, Progressive Web Apps, Tailwind CSS, Shadcn UI | Responsive web apps, dashboards and role-based interfaces |
| Databases | PostgreSQL (Patroni HA, TDE encryption), SQL Server, MongoDB | Transactional storage, high availability and data protection |
| Messaging & caching | RabbitMQ (Quorum Queues), Redis | Asynchronous processing, inter-service communication and performance |
| Containers & DevOps | Docker, Kubernetes, Helm, HashiCorp Vault, CI/CD pipelines, Azure DevOps | Containerised deployment, secrets management and delivery automation |
| Cloud | Microsoft Azure, Amazon Web Services | Hosting, managed services and scalable infrastructure |
| Quality engineering | Selenium, Protractor, automated regression and performance testing | Functional validation, regression coverage and load assessment |
| Artificial intelligence | Custom domain language models, RAG pipelines, Ollama, open-weight LLMs, voice and chat AI | Institutional search, Q&A, conversational automation |
Architecture principles
How our platforms are designed.
Modular by design
microservices and clear service boundaries so platforms can evolve piece by piece
Built for scale
asynchronous messaging, caching and horizontal scaling for high-volume workloads
Highly available
replicated databases and container orchestration for resilience
Secure by default
encryption in transit and at rest, managed secrets and role-based access
Observable
logging, monitoring and alerting so issues surface before users notice
Security practices
Controls proven in regulated environments.
| Control area | Practices applied |
|---|---|
| Data protection | Transparent data encryption (TDE) at rest; TLS 1.3 for external endpoints |
| Service communication | Mutual TLS (mTLS) between internal services |
| Access control | Role-based access control and segregation of duties |
| Process controls | Maker-checker review workflows for sensitive operations |
| Traceability | Comprehensive audit logging of user and system actions |
| Secrets management | Centralised secrets handling with HashiCorp Vault |
| Environment isolation | Kubernetes namespace separation across environments and tenants |