Single-page reference of the technical stack, integrations, AI capabilities, and operational KPIs that power the SERA Licensing Portal.
SERA Licensing Digital Transformation – Digital Requirements Document v2.0 (March 2026)
Hosting Model
Reference Architecture
High-level deployment from presentation to data — request flow per the Digital Requirements Document.
Request Flow. User requests are routed through the OCI Load Balancer to the Gravitee API Gateway, which securely directs traffic to containerized microservices running on OCI Kubernetes Engine (OKE). Core services interact with the database, object storage, and internal systems, while AI-related requests are securely processed through outbound integration with Azure AI.
Technology Stack
Environments
14 government & enterprise APIs feeding the licensing process — all routed through the Integration Layer / API Gateway and following secure, auditable patterns.
10 internal services — split between existing portal APIs and target system APIs, all secured with JWT and integrated through the same gateway pattern.
AI Governance
AI is used for decision-support only. All inputs and outputs are logged for auditability.
Manual approval is required for all regulatory decisions — AI outputs do not autonomously approve, reject, or amend any license-related action.
Per Digital Requirements Document v2.0, sections 9.2.e and 10.7.c.
Operational and Target Operating Model (TMO) KPIs from the digital licensing framework. Final list to be aligned with the Target Operating Model deliverable.
