The release of VELOX 3.1 introduces several important changes to strengthen performance, security, and reliability. While not feature-heavy, this update represents a foundational step forward for enterprises running VELOX in cloud environments.

‍

Key Changes in 3.1

• Buildpacks for Containers
  VELOX now uses buildpacks to create container images. This eliminates the need for manual Docker files, improving the stability, security, and quality of deployments. Buildpacks ensure containers handle errors more predictably and are maintained with industry best practices.
  
  
• Java Native Images
  VELOX services now run as compiled native executables instead of relying on the JVM. This reduces startup times from around 15 seconds to under 1 second, which is critical for scaling up or down in Kubernetes and cloud environments. The result: faster responsiveness and better resource efficiency.
  
  
• Breaking Change in Health Checks
  Because of the move to Java native images, health checks must be updated. This is a breaking change that requires attention during deployment, but it ensures smoother startup behavior and aligns with the new execution model.
  
  
• Security Patching Q2 2025
  VELOX 3.1 includes the latest 25-Q2 security patches, ensuring all clients benefit from up-to-date protection and compliance.
  
  

What It Means for Your Business

VELOX 3.1 is a technical but strategic release:

• Faster scaling = better customer experience during peak demand.
  
  
• Buildpacks = reduced risk and improved operational stability.
  
  
• Updated health checks = safer deployments in production.
  
  

Security patches = continuous protection by default.