Answer first: MHCLG says its shared AI Gateway has moved into departmental use, giving digital teams a governed route to approximately 20 approved AI models and reducing the need for separate AI integrations across services. The signal for suppliers is conditional rather than tender-led: firms supporting secure API management, AI governance, cloud integration and delivery controls may want to monitor future phases. For more UK public-sector technology signals, you can try PipeSignals for free.
Shared AI platform now in departmental use
The Ministry of Housing, Communities and Local Government announced on 15 September 2026 that its Technical Architecture team has developed the AI Gateway, described as a single shared departmental platform giving product and delivery teams a secure and consistent route to approved AI technologies source. The milestone is not an open tender. It is a documented internal deployment: MHCLG says the Gateway has already been adopted by multiple teams, provides access to approximately 20 AI models and has several initiatives using it, with further projects progressing through onboarding source.
Azure API Management underpins a provider-agnostic route
The platform is designed to avoid separate teams building their own AI integrations, governance approaches and support models. MHCLG says the Gateway uses Microsoft Azure API Management as the core platform, while remaining provider-agnostic so that models from multiple providers can be presented through one consistent approach source. It is intended to support developers, data scientists, applications and services running in Azure and AWS, enabling AI to be embedded directly into departmental services rather than used only through individual devices.
Secondary reporting by THINK Digital Partners on 17 September 2026 covered the same announcement and identified the project as a centralised AI platform intended to reduce duplication, strengthen governance and improve oversight of AI use across MHCLG source. That article is useful as sector reporting, but it relies on the department’s blog for the deployment claims. It should not be treated as an independent technical audit or performance assessment.
Deployment stage and what remains unknown
The appropriate stage is deployment: MHCLG says the Gateway is in use by several initiatives and being onboarded by others. The announcement does not provide a procurement value, a supplier award notice for the Gateway, quantified savings, usage volumes by service, model names, or a public launch date for citizen-facing services that depend on it. The department says the platform went through internal AI approval, technical and data-protection approvals, and a penetration testing assessment, but the public post does not identify an external reviewer.
Conditional supplier questions for BDR teams
For IT services firms, the opportunity is not a confirmed buying requirement. Qualification should start with questions: will future phases need additional cloud-provider connectors, model catalogue management, monitoring dashboards, cost-management support, security assurance, documentation, training or service integration? Cybersecurity providers may also want to qualify whether ongoing penetration testing, logging, auditability or RBAC configuration work will be handled internally or supported by framework suppliers.
MHCLG says its roadmap includes expanding access to AI services hosted by additional cloud providers while maintaining consistent governance, security and operational standards source. For teams tracking deployment signals rather than speculative tenders, this is the point to monitor future notices, technical blogs and framework activity. You can track comparable UK public-sector projects with PipeSignals.
.jpg){kind=link}