Halo has announced a significant upgrade to its underlying infrastructure, with its application servers moving to AWS Elastic Kubernetes Service (EKS).
The first Beta release is planned for version 2.252 in September 2026, with the first Stable release using the new architecture expected in Q1 2027.
The move should bring faster scaling, improved resilience, more consistent deployments and better global performance. However, there are also several practical changes that Halo customers, administrators and integration teams should start considering:
- New outbound IP ranges may need to be added to customer allowlists.
- Custom domains will require new DNS records for certificate validation.
- All API requests will need to include a
User-Agentheader. - Halo Automations will move into a dedicated microservice, with its data ultimately moving towards DynamoDB.
- Reports or integrations that directly query the
Automation,AutomationIteration,AutomationVariableorWebhookEventtables may need to be reviewed. - IP-based access restrictions will move into Halo’s application configuration.
- Halo is also introducing greater visibility and control around platform upgrades.
There is no immediate action required for Stable-channel customers, but this is worth reviewing now—particularly if your environment uses custom domains, IP allowlisting, bespoke integrations or direct database reporting.
You can read Halo’s full announcement here:
https://www.usehalo.com/news/upgrading-halos-infrastructure-faster-more-scalable-and-built-for-the-…
We’re reviewing the potential impact across our customer environments at Mozaic and will share more as the rollout details develop.
What stands out most to you? Are there any areas where you would like further technical clarification from Halo?
Source: r/TalkingHalo · by /u/PaulAtMozaic