Deploy your applications to Microsoft Azure with the same ease and consistency as AWS and Google Cloud. Ryvn now fully supports Azure Kubernetes Service (AKS) provisioning, giving you true multi-cloud flexibility for your customer deployments. You can now provision Azure environments directly from the Ryvn dashboard, with automatic setup of networking, security, and cluster configuration. This expansion means you can serve customers regardless of their preferred cloud provider.

​
Customer portal

Empower your customers with direct access to their deployment environments through the new customer portal. Customers can now view their installations, monitor deployment status, and access logs without requiring your team’s intervention. The portal includes a streamlined invite flow that lets you easily grant customers appropriate access to their specific environments while maintaining security boundaries.

​
AWS BYOC and BYOVPC

Enhanced AWS deployment options now include Bring Your Own Cloud (BYOC) and Bring Your Own VPC capabilities. You can deploy into customer-owned AWS accounts or existing VPC infrastructure while maintaining full Ryvn deployment automation. These options provide greater flexibility for enterprise customers with existing cloud investments or specific compliance requirements.

​
Improvements

  • Added the ability to specify allowed IP ranges (CIDRs) for EKS cluster endpoints for enhanced security
  • Enhanced environment provisioning to reference and template infrastructure outputs
  • Improved activity indicators to show more accurate deployment and task status
  • Added support for public container images in web server deployments
  • Enhanced template functionality with new text joining capabilities for better configuration management
  • Improved task management by automatically canceling pending tasks when new ones are created
  • Added organization user visibility to better track team access across environments

​
Fixes

  • Fixed an issue where pressing ‘C’ key on the logs tab was not working properly
  • Resolved Azure credential verification and token request issues during environment setup
  • Fixed secret management functionality to properly update installation secrets by ID
  • Corrected environment configuration key handling for better reliability
  • Fixed customer portal environment selection to show the correct deployment environment
  • Resolved frontend hook re-rendering issues that could cause interface delays