Kubernetes Environment Management

Templated, Policy Compliant Environments In Minutes

Automatically provision fully featured environments in just one click for developers, data scientists, researchers, and more.

Start Now

Rafay Automates Cloud Kubernetes Environment Management Provisioning

Access to cloud infrastructure should be seamless, but rarely is. Instead, developers and other teams must often submit requests into a queue and wait for overloaded operations engineers to create the sandbox, test, and other environments they need in order to work. Rafay allows platform teams to automate these workflows, so cloud users can iterate and release more quickly.

Kubernetes Environment Management Built for Platform Teams

With Benefits Felt Across the Organization

Autonomy to cloud users

Move fast and innovate when dependable, self-service access to cloud resources is available to anyone who needs it for development or testing.

Control to platform engineers

Manage self-service workflows across a hybrid cloud environment, ensuring that all compliance, security, and financial requirements are met.

Efficiency to operations

Increase service availability by automating cloud management and standardizing configurations across all teams from a single console.

How Rafay Environment Management Works

Rafay’s single SaaS-based* controller provisions hundreds of cloud environments with ease. It accelerates these processes by providing developer self-service capabilities through one-click workflows, while delivering governance and control capabilities that platform teams need. In doing so, Environment Manager enhances the developer experience by reducing the complexity and time inherent in provisioning public and private cloud environments for their applications.

* A self-hosted version is also available.

All Your Kubernetes Environment Management Needs
In A Single Solution

For Autonomy

Rapidly provision new environments, with guaranteed safety
Estimate cost of requested infrastructure before provisioning
Free developers from cloud environment complexity

For Control

Deploy containers, AI/ML testbeds, and landing zones
Templatize using new or existing cloud resources
Enforce policies with audit logs and cost controls

For Efficiency

Limit changes allowed by users when deploying
Centrally manage updates to ensure ongoing stability
Eliminate wasted ‘zombie’ environments with explicit TTL

Key Features of Rafay’s Kubernetes Environment Management Solution

Multi-cloud Environment Provisioning

Environment Lifecycle Management

Flexible Template Framework

Centralized Upgrade & Deprecation

Centralized Dashboards & Monitoring

Policy Management & Enforcement

Use Case Example: Provisioning an App Landing Zone

When developers need to prototype, test, or deploy an application, they often need landing zones that come preconfigured with services that the app will need (like databases, object stores, or elastic caches). Requests for landing zone environments happen frequently, and can block developer progress.

Typical Process

Process With Rafay

Typical Process A developer identifies the requirements for a landing zone and opens a ticket (in ServiceNow, etc).

Process With Rafay A developer matches the requirements for their landing zone against a preset list of proven templates, and submits a request (in ServiceNow, Backstage, etc.)

Typical Process The platform / operations team queues the request, and prioritizes it based on other requests being worked.

Process With Rafay The request is routed to Rafay, which automatically evaluates it against policy controls and approves it.

Typical Process Platform / ops reviews the request, and modifies it to meet requirements for security, compliance, and cost.

Process With Rafay Rafay automatically reads the IaC configuration (from Terraform, etc.) and initiates provisioning of the environment instantly

Typical Process The developer must review and sign off on these changes.

Process With Rafay Rafay provides the environment back to the developer and closes the request within minutes.

Typical Process Platform / ops creates or updates IaC code (in Terraform, etc.) for the landing zone environment

Process With Rafay The platform / operations team maintains visibility of all created environments via centralized dashboards in Rafay.

Typical Process Platform / ops provides the environment back to the developer and closes the ticket. Sometimes, this happens weeks after the ticket was opened.

Process With Rafay Platform / ops can centrally manage updates to running environments in Rafay, to ensure currency and compliance.

Typical Process Platform / ops loses track of its ongoing compliance and cost, because visibility is not maintained.

Process With Rafay Platform / ops can automatically clean up environments that are no longer in use.

Typical Process Over time, developers may modify the environment configuration, or fail to make updates to maintain currency or compliance.

Typical Process Configurations start to proliferate and drift, causing inefficiency and instability.

Self-Service Cloud Automation

Platform teams at MassMutual, Guardant Health, and Verizon use the Rafay Cloud Automation Platform to enable anyone who depends on rapid access to cloud infrastructure to move faster safely.

Learn More