Rafay Systems Unveils Developer Self-Service Capabilities for Enterprise Platform Teams

Rafay Systems has announced new capabilities that enable enterprise platform teams to provide developer self-service for faster application deployments with the necessary guardrails businesses need.

With these new features, Rafay’s Kubernetes Operations Platform (KOP) offers platform teams the most efficient way to establish Kubernetes standards and practices while enabling developers to innovate.

Today’s enterprise developers want the autonomy to innovate and rapidly deploy their modern applications. Platform teams want standardization and control for repeatability and governance. Finding the right balance between these requirements has been difficult for today’s businesses, until now.

With Rafay, Platform Teams enables development teams to provision clusters using Terraform or GitOps workflows, as well as create and manage namespaces for their teams on dedicated or shared clusters. At the same time, platform teams stay in control with pre-approved and curated cluster plans, centrally defining and enforcing Kubernetes policies, and more. Platform teams also get central visibility, health, and policy violation notifications across the entire Kubernetes fleet.

Developer self-service capabilities replace slow, ticket-based processes to request new infrastructure or access existing infrastructure. As a result, development teams can eliminate the main obstacle to developer productivity: waiting for central IT to provision or provide access to Kubernetes clusters and infrastructure.

According to Lydia Leong, Distinguished Vice President and Analyst at Gartner for Technical Professionals, “self-service — and more broadly, developer control over infrastructure — is not an all-or-nothing proposition. Liability can be distributed throughout the application lifecycle, so you can take advantage of “You build it, you run it” without necessarily parachuting your developers into the wild and uncharted wilderness and wishing them luck surviving because it’s not an infrastructure and operations (I&O) team issue anymore.

“Platform teams can leverage Rafay’s KOP to create standardized, repeatable automation that developers can use as a service,” said Mohan Atreya, senior vice president of products and services at Rafay. “This allows developers to focus on building transformational products and deploying them to customers faster instead of spending valuable time trying to master the complexities of Kubernetes management and operations.”

Rafay offers companies the following advantages:

• Speed ​​without sacrificing stability: Platform teams that enable application development teams to self-service enable container-based application development. Since all Kubernetes cluster namespaces are created according to predefined standards, Rafay reduces human error, which improves the stability of the underlying Kubernetes cluster.
• Create autonomy while reducing risks: The self-service aspect allows developers to work asynchronously with the appropriate infrastructure configurations and quotas in place. This avoids excessive CPU and memory usage to control costs and avoid a monopoly of Kubernetes cluster resources.
• Accelerate deployments and innovation: By shifting the creation and management of the Kubernetes cluster namespace to the development team, central IT and platform teams are no longer seen as a bottleneck for engineering workflows using Kubernetes . The independence gained by developers allows more time to be spent innovating instead of worrying about infrastructure.
• Flexible multi-location with railing: Establishing quotas and allowing development teams to have self-contained workspaces allows platform teams to reduce overhead and operational costs by leveraging shared clusters between teams with isolation of the ‘workspace. This eliminates the need for platform teams to provision a cluster for each development team, reducing cloud compute costs.
• Hard Multitenancy: Rafay enables platform teams to enable development teams to create and operate multiple clusters to comply with isolation requirements. This enforces tighter ownership lines, reduces infrastructure dependencies, and avoids any negative consequences from other applications or application teams.