We’re excited to announce the latest updates to our DevZero platform, designed to enhance flexibility, control, and insights for your development workflows. Here’s what’s new:

1. Self-hosted Development Environments

Full Control Over Infrastructure. Introducing Self-hosted Developer Environments—the ultimate solution for engineering teams that need to rapidly develop applications that are deployed on-premise or in private cloud environments. Manage your development infrastructure entirely within your network, ensuring compliance and enhanced security.

• Problem We’re Solving:
  Using public cloud-hosted environments can be a significant compliance risk in regulated industries or companies with strict data privacy policies. Teams need secure, isolated environments that align with their internal policies.
  
  
• Use Case for Developers:
  Software engineers at a healthcare company can use a self-hosted development environment to securely build applications that access patient data for testing purposes, ensuring that sensitive information never leaves the organization's private cloud.
  

Here, you will learn how to use self-hosted development environments that can consist of: 

• Workspaces, hosted either directly on the base Kubernetes cluster or inside a virtualized Kubernetes cluster,
• Control Plane software that administers the entire deployment and supports multiple globally distributed Data Planes, and
• Data Plane software that controls the deployment and end-user-facing environments, whose placement can be in geographies nearer to the applications' end-users. 

Get started with self-hosted environments →

‍

‍

2. Custom Base Images

Flexibility in Development Environment Setup. Now, you can tailor development environments with Custom Base Images. A base image is a foundational image used in containerized development to build and customize other container images. By specifying a custom base-image in your Recipe configuration file, you can ensure that all necessary dependencies and configurations unique to your organization are included upfront when you create a Workspace, which is a containerized development environment.

• Problem We’re Solving:
  Due to differing configurations, development teams often face inconsistency across local, testing, and production environments. Teams usually have base images that serve as the starting point for defining the environment and include the operating system, libraries, and core utilities needed to run applications. Developers can layer additional software, configurations, and dependencies on top of a base image to create an environment tailored to their specific needs. This leads to less wasted time debugging environment-related issues, time that can instead be spent on core development tasks.
  
  
• Use Case for Developers:
  Developers working on a machine learning project can use a custom base image pre-configured with the correct version of Python, TensorFlow, and GPU drivers. This ensures they can onboard quickly and start coding without worrying about setting up dependencies.
  

Learn more about custom base Images →

‍

3. Open Developer Analytics (ODA)

Data-Driven Insights for Engineering Teams. Track and analyze developer activity like never before with Open Developer Analytics. This new feature enables engineering leaders to monitor key metrics and improve workflows, ensuring peak productivity and optimized performance.

• Problem We’re Solving:
  Engineering leaders lack visibility into how development processes impact productivity, making it difficult to identify bottlenecks or inefficiencies in workflows.
  
  
• Use Case for Developers:
  A team lead can use ODA to analyze build times, identify frequent build failures, and pinpoint inefficiencies in the CI/CD pipeline. This helps the entire team improve their workflows and spend more time delivering features.
  

Here, you will learn how to identify resource-heavy commands that consume significant resources, enabling optimization for better performance and cost reduction. ODA monitors the following metrics: execution times, resource utilization, command success/failure rates, developer idle time, and processes spawned.

Explore Open Developer Analytics →

‍

4. Hibernating Workspaces and Clusters

Optimize Resource Usage Without Losing Progress. Introducing Hibernating Workspaces, allowing developers to pause their active workspaces and resume precisely where they left off, conserving resources while maintaining productivity.

• Problem We’re Solving:
  Active workspaces that host development environments often consume unnecessary resources when developers step away for hours or switch tasks, leading to wasted compute and storage costs. Teams need a way to preserve the workspace state without constantly running resources.
  
  
• Use Case for Developers:
  A developer working on a long-running backend service can hibernate their workspace at the end of the day, preserving their work-in-progress setup. This immediately stops the clock on compute resources so that they are not charged for the time the workspaces are not in use. The next day, they can resume the workspace instantly without rebuilding or reconfiguring the environment.
  

Here, you can learn about Time-based hibernation for automatically hibernating workspaces/clusters at a specified time, and Activity-based hibernation, which hibernates them after a defined period of inactivity. In addition, you can set email alerts on spending, and when resource usage reaches certain thresholds.

Learn more about Hibernating Workspaces →

‍

‍

We’re committed to empowering developers with tools that simplify workflows and accelerate innovation. Try these new features today, and let us know your thoughts! 🚀

‍