Production Release: 4/16/26

This release delivers a set of infrastructure improvements to the AXN and our Admin platform, focused on runtime performance, service architecture, and platform maintainability. These are internal changes with no impact to your APIs or integrations.

What's Changing

Area

Summary

Service Consolidation

AXN: The Policy Manager service is being merged into the AXN core runtime, rather than operating as a separate service. Consolidating services into a single runtime eliminates redundant pods, reduces inter-service network latency, and removes serialization overhead between the two services, resulting in increased performance and resilience.
Admin: The Admin platform is being consolidated from seven microservices down to two, reducing operational complexity and improving code maintainability.

Hardware Migration

AXN infrastructure is migrating from x86 (AMD) to ARM64 (Graviton) processors. This move delivers equivalent throughput and latency characteristics on a more efficient compute architecture.

Memory Optimization

JVM runtime settings and container resource allocations are being right-sized to better match actual workload demands, reducing memory overhead while maintaining current performance and headroom targets.

Code Quality

We're resolving several security and reliability recommendations from SonarQube static analysis, maintaining security and reliability standards of our platform.

Why It Matters

These changes strengthen the platform's operational foundation without affecting your day-to-day experience. Service consolidation reduces moving parts and potential failure points; the hardware migration positions the platform on a more modern compute tier; and memory tuning improves resource efficiency across the environment.

What You Need to Know

No API or Integration Changes

All changes are internal to the platform infrastructure. Your existing API integrations, authentication flows, and service endpoints remain unchanged.

No Downtime Expected

Changes will be deployed incrementally, one workstream at a time, through our standard release process. Each change is independently testable and reversible, with releases pushed to our Disaster Recovery trailing Production releases by one day to maintain a rollback window between Production and DR.

Improved Platform Reliability

Tighter resource allocation and improved observability support faster detection and resolution of infrastructure issues, contributing to overall platform stability.