Blog
Product
4
minutes

New Feature: Instantly Clone Your Service

We're excited to announce the general availability of the new "Clone Service" feature on Qovery, which is built to augment the capabilities of our platform and to cater to our user needs more effectively. Qovery has always prided itself on being a user-centric platform, and this new feature continues to uphold that tradition.
September 26, 2025
Romaric Philogène
CEO & Co-founder
Summary
Twitter icon
linkedin icon

What is the Clone Service Feature?

Up until now, Qovery users were able to clone a complete environment. This feature, one of the most popular, was leveraged by teams who needed to duplicate an environment for testing, benchmarking, demos, sales purposes, and more, without impacting the original environment. It's the Clone Environment feature that is used behind the powerful Preview Environment feature from Qovery.

Today, we've taken it a step further with the ability to clone an individual service from one environment to another, within the same environment, or even within another environment inside another project. That's right, we've lit the 🔥 and amplified the capacity of our platform!

For a detailed understanding of the difference between Clone Service and Clone Environment, we recommend this comprehensive video: Clone Service vs Clone Environment.

How Does the Clone Service Feature Work?

With the Clone Service feature, users can now duplicate a service effortlessly. It smartly clones all the necessary properties, such as environment variables, secrets, resources settings, and advanced settings, ensuring that your duplicated service retains the core of the original. However, it wisely leaves out the settings that cannot be duplicated across services, like the custom domain.

Watch this video to get a quick overview of the Clone Service feature.

Why Clone a Service?

With the Clone Service feature, our users can create replicas of their services instantly, streamlining their workflow and accelerating their development process.

This feature is particularly beneficial when teams need to duplicate a particular service multiple times for various purposes without needing to clone the entire environment. It saves time, improves efficiency, and mitigates risks by allowing users to perform actions on the cloned service without affecting the original one. But here a non-exhaustive list of appropriate use cases for the Clone Service feature:

  1. Individual Service Testing: While Clone Environment is perfect for comprehensive testing, Clone Service allows you to focus solely on a specific service. This approach is not only more efficient but also significantly more cost-effective.
  2. Bug Reproduction and Debugging: Isolating a faulty service by cloning it helps to focus the debugging efforts and reduces the resources needed compared to cloning the entire environment.
  3. Performance Benchmarking: Cloning individual services allows you to tweak and optimize their performance without the overhead costs of duplicating the whole environment.
  4. Demo Purposes: In sales or client demos, you might only need to showcase a specific service. Cloning just this service saves unnecessary expenditure on environment duplication.
  5. Education and Training: Trainees can learn and experiment on a cloned service rather than a full environment, reducing training costs and resource usage.
  6. Microservice Architecture: For applications using a microservice architecture, cloning individual services is significantly more cost-effective than cloning the entire environment.
  7. Environment Cleanliness: Cloning only the necessary services helps keep your environments clean and organized, and is also a more economical use of resources.
  8. Cost-Efficiency: One of the major advantages of the Clone Service feature is its cost-effectiveness. Cloning a whole environment can rack up costs, especially for larger, more complex environments. By allowing users to clone individual services, you can significantly reduce costs while still achieving your objectives.

By bringing the cost-effectiveness of service cloning to the forefront, we've highlighted another significant advantage of the Clone Service feature. Balancing cost with development requirements is crucial, and this feature offers an efficient way to maintain this balance.

The Takeaway

The Clone Service feature is yet another step in Qovery's commitment to facilitating a smooth and efficient development process for our users. It not only broadens the capabilities of our platform but also empowers users to manage their environments and services more flexibly.

We are thrilled to see this feature in action and look forward to hearing your experiences. So, go ahead and start cloning your services, and remember, we're here to assist you every step of the way!

Share on :
Twitter icon
linkedin icon
Tired of fighting your Kubernetes platform?
Qovery provides a unified Kubernetes control plane for cluster provisioning, security, and deployments - giving you an enterprise-grade platform without the DIY overhead.
See it in action

Suggested articles

Kubernetes
6
 minutes
Kubernetes observability at scale: cutting the noise in multi-cloud environments

Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.

Morgan Perry
Co-founder
Kubernetes
 minutes
Understanding CrashLoopBackOff: Fixing AI workloads on Kubernetes

Stop fighting CrashLoopBackOff on your AI deployments. Learn why traditional Kubernetes primitives fail large models and GPU workloads, and how to orchestrate AI infrastructure without shadow IT.

Morgan Perry
Co-founder
Kubernetes
Platform Engineering
 minutes
Mastering multi-cluster Kubernetes management: Strategies for scale

Stop fighting cluster sprawl. Learn why traditional scripting and GitOps fail at scale, and discover how to achieve fleet-wide consistency without the complexity of Kubernetes Federation.

Mélanie Dallé
Senior Marketing Manager
Developer Experience
Kubernetes
8
 minutes
Top 5 Kubernetes automation tools for streamlined management and efficiency

Looking to automate your Kubernetes environment in 2026? Discover the top automation tools, their weaknesses, and why scaling your infrastructure requires a unified management platform.

Mélanie Dallé
Senior Marketing Manager
AI
 minutes
Beyond Compute Constraints: Why AI Success is an Orchestration Problem

As the AI race shifts from hardware acquisition to GPU utilization, success is now an orchestration problem. Learn how to bridge the 84% capacity gap, eliminate "ghost" expenses, and leverage AI infrastructure copilots to maximize ROI in 2026.

Romaric Philogène
CEO & Co-founder
Kubernetes
DevOps
Platform Engineering
6
 minutes
Kubernetes vs. Docker: Escaping the complexity trap

Is Kubernetes complexity killing your team’s velocity? Compare Docker vs. Kubernetes in 2026 and discover how to get production-grade orchestration with the "Git Push" simplicity of Docker.

Morgan Perry
Co-founder
Kubernetes
Cloud
DevOps
8
 minutes
9 key reasons to use or not Kubernetes for your dev environments

Morgan Perry
Co-founder
Kubernetes
DevOps
Platform Engineering
7
 minutes
Kubernetes vs. OpenShift (and how Qovery simplifies it all)

Stuck between Kubernetes and OpenShift? Discover their pros, cons, differences, and how Qovery delivers automated scaling, simplified deployments, and the best of both worlds.

Morgan Perry
Co-founder

It’s time to change
the way you manage K8s

Turn Kubernetes into your strategic advantage with Qovery, automating the heavy lifting while you stay in control.