State of Preview Environments Report 2023
Before we delve into the study's findings, let's first review what Preview Environments entail.
Preview Environments allow for code changes to be tested in isolation before merging to master, equipped with all necessary infrastructure and resources. They are created temporarily and automatically provisioned, making them easy to set up and remove. They provide a feature-specific version of staging or production environments, enabling effective testing and debugging. They are instrumental in increasing development team velocity by reducing the time it takes to test and release new features.
Now, let's turn our attention to the findings of the study.
Current Testing Process Within The Teams
The survey found that 80% of software engineering teams use some form of automated testing. Among these respondents, 18% fully automate their testing, while 38% use a mix of automated and manual testing, and 24% mostly rely on manual testing with some automation.
Importance of Preview Environments
Our survey found that 70% of software engineers believe Preview Environments are important (45%) or extremely important (25%). This response indicates a widespread acknowledgment of the importance of preview environments in the software development process.
Preview Environments Adoption With The Organizations
Of the survey respondents, 43% currently use some preview environment solution, while 18% prioritize adopting it this year.
Teams That Benefit Most from Preview Environments
A significant proportion of the respondents (45%) recognized the benefits of preview environments for cross-functional teams, which extend to Developers, QA teams, DevOps/Platform, and Product teams. Meanwhile, 38% of the participants identified Developers as the primary beneficiaries of these environments.
Biggest Benefit of Preview Environments
Respondents cited three primary benefits of preview environments, including shorter feedback cycles and faster delivery (36%), increased autonomy and development speed (28%), and reduce bugs and downtimes (18%). These benefits demonstrate the efficiency and productivity gains that preview environments can offer.
Obstacles to Adopting Preview Environments
The survey revealed three significant friction points to adopting preview environments: implementation time and effort (38%), technical challenges (27%), and absence of easy-to-use solutions (18%). Addressing these challenges is crucial for facilitating the more widespread adoption of preview environments.
Preferred Type of Preview Environments Solution
58% of respondents would seek to build an in-house solution for implementing Preview Environment capability for their team, while 35% indicated a preference to use an external solution instead.
Conclusion
Those results show clearly that Preview Environments have gained significant popularity among software engineering teams. The survey found that 70% of software engineers believe preview environments are valuable, and a significant proportion of respondents recognized the benefits of preview environments for cross-functional teams, extending to developers, QA teams, DevOps/Platform, and product teams. The primary benefits cited by respondents include:
- Shorter feedback cycles & faster delivery.
- Increased autonomy & development speed.
- Reduced bugs and downtimes.
The biggest obstacles to adoption were implementation time and effort, technical challenges, and a need for easy-to-use solutions.
With more accessible solutions, well-documented case studies, and high perceived value, we predict that preview environment adoption will significantly grow in 2023 (and beyond).
.svg)
.svg)
.svg)
Suggested articles
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
Effective Kubernetes management in 2026 demands a shift from manual cluster building to intent-based fleet orchestration. By implementing agentic automation on standard EKS, GKE, or AKS clusters, enterprises eliminate operational weight, prevent configuration drift, and proactively control cloud spend without vendor lock-in, enabling effective scaling across massive fleets.
A Kubernetes single pane of glass is a centralized management layer that unifies visibility, access control, cost allocation, and policy enforcement across § cluster in an enterprise fleet for all cloud providers. It replaces the fragmented practice of switching between AWS, GCP, and Azure consoles to govern infrastructure, giving platform teams a single source of truth for multi-cloud Kubernetes operations.
Deploying a Docker container on Kubernetes requires building an image, authenticating with a registry, writing YAML deployment manifests, configuring services, and executing kubectl commands. While necessary to understand, executing this manual workflow across thousands of clusters causes severe configuration drift. Enterprise platform teams use agentic platforms to automate the entire deployment lifecycle.
At enterprise scale, managing provider-specific Kubernetes YAML across multiple clouds creates crippling configuration drift and operational toil. By adopting an agentic Kubernetes management platform, infrastructure teams abstract cloud-specific configurations (like ingress controllers and storage classes) into a single, declarative intent that automatically reconciles across 1,000+ clusters.
To stop GPU costs from destroying SaaS margins, teams must transition from static to consumption-based infrastructure by utilizing Karpenter for dynamic provisioning, maximizing hardware density with NVIDIA MIG, and leveraging Qovery to tie scaling directly to business metrics.
AI is helping developers write more code, faster than ever. But writing code is only half the story. What happens after? Building, deploying, debugging, scaling. That's where teams still lose hours.We're building Qovery for this era. Not just to deploy your code, but to make everything that comes after writing it just as fast.
.webp)