Alpha Looms Overview
Alpha Looms is AND Global's lending platform for running borrower-facing journeys, internal operations, and domain services across a managed cloud environment.
This portal combines platform context with the API Catalog used to explore integration contracts exposed through Alpha Looms.
At A Glance
The platform architecture shown in the current deployment diagram centers on an Azure private network with an AKS cluster as the main runtime boundary.
- Public user traffic enters through DNS, a public load balancer, and the NGINX ingress controller
- Service-to-service communication inside the cluster uses Kubernetes DNS and service discovery
- Authentication and token validation are handled through Keycloak and API gateway layers
- Business capabilities are delivered through multiple downstream services with clear data-store boundaries
- Delivery into the cluster follows a GitHub to ArgoCD deployment path
For the full topology view, including runtime boundaries and data dependencies, see the Architecture page and the embedded deployment diagram.
Core Runtime Areas
Edge And Access
The platform supports multiple user and system entry points.
Admin Webserves internal or operational usersBorrower Webserves borrower-facing flowsSales Webserves browser-based sales flowsSales Appserves sales users in an app-based channelAdmin API Gateway,Borrower API Gateway, andOpenAPI API Gatewaysit behind the ingress layerKeycloakvalidates tokens used by the gateway and downstream service flows
Platform Services
Several platform-level services support workflow execution, orchestration, and analytics.
Formiosupports form-driven flowsN8Nsupports workflow automation and integration tasksSupabasesupports shared platform capabilitiesSupersetsupports reporting and analytical consumption
Downstream Services
The AKS-hosted service layer includes multiple domain and operational downstreams behind the gateway layer.
Examples called out in the architecture include services such as Auth and Log management, alongside other lending, workflow, document, and beta-related capabilities.
Data And Messaging
The architecture connects runtime services to several managed data and infrastructure dependencies.
MySQL Flexible ServerPostgreSQL Flexible ServerRedisMongoDB- storage accounts such as
betateststorageandauthalphatest01 Service Bus
Typical Request Flow
- A user starts from
Admin Web,Borrower Web,Sales Web, orSales App. - Traffic resolves through DNS and enters the platform through the public load balancer.
- The
NGINX Ingress Controllerroutes traffic to the appropriate API gateway or platform service. - The gateway coordinates authentication with
Keycloakand forwards authorized traffic. - Downstream domain services interact with their assigned data stores, messaging infrastructure, or supporting platform components.
Deployment Model
The diagram also shows the operational delivery path used to move changes into the cluster.
- Developers publish a new version through GitHub.
ArgoCDsynchronizes the target state into AKS.- Updated services become available behind the existing ingress and load-balancing layers.
Documentation Map
- Architecture: platform boundaries, runtime zones, data dependencies, and deployment topology
- Access And Authentication: public entry, internal exposure, gateways, and token validation
- OpenAPI Gateway Annotations: shared route annotations, generated
x-*extensions, and gateway exposure metadata - Services And Data: service groups, backing stores, and integration-relevant dependencies
API Catalog
For contract-level API details, use the API Catalog.
Who This Portal Is For
- Product and platform engineers integrating Alpha Looms services
- Solution architects mapping service boundaries and traffic flows
- Delivery teams validating deployment and runtime topology
- Operations teams reviewing supporting infrastructure and data dependencies
External References
For product and company context, visit AND Global and Looms.