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.
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

Product
4
 minutes
Scale What Matters, Not Just CPU - Welcome Keda autoscaling

Not every workload should scale on CPU. Qovery brings event-driven autoscaling into the application lifecycle, letting applications scale on real signals like queue depth or request latency.

Alessandro Carrano
Head of Product
DevOps
Kubernetes
Platform Engineering
15
 minutes
10 Red-Hat OpenShift Alternatives to Reduce Cost and Complexity in 2026

Fed up with OpenShift? Compare the top 10 enterprise alternatives. Discover how modern Kubernetes management platforms like Qovery reduce TCO, simplify Day 2 Ops, and scale AI workloads.

Morgan Perry
Co-founder
Kubernetes
DevOps
9
 minutes
Top 10 Rancher alternatives in 2026: Beyond cluster management

Looking for Rancher alternatives? Compare the top 10 Kubernetes Management Platforms for 2026. From Qovery to OpenShift, find the best tool to scale multi-cluster operations and reduce TCO.

Morgan Perry
Co-founder
Internal Developer Platform
DevOps
 minutes
PaaS vs. DIY IDP: The Fastest Path to a Self-Service Cloud

Building an Internal Developer Platform (IDP) from scratch seems cheaper, but the maintenance costs add up. Discover why a modern PaaS on your own infrastructure is the faster, smarter path to a self-service cloud.

Mélanie Dallé
Senior Marketing Manager
Heroku
15
 minutes
Top 10 Heroku Alternatives in 2026: When Simplicity Hits the Scaling Wall

Escape rising Heroku costs & outages. Compare top alternatives that deliver PaaS simplicity on your own cloud and scale without limits.

Mélanie Dallé
Senior Marketing Manager
DevOps
Developer Experience
9
 minutes
Top 10 DevOps Automation Tools in 2026 to Streamline Mid-Market Infrastructure

Scale your engineering organization without the headcount hit. Compare the top 10 DevOps automation tools for mid-market teams, from IaC leaders like Terraform to unified platforms like Qovery.

Mélanie Dallé
Senior Marketing Manager
Kubernetes
DevOps
 minutes
Best CI/CD tools for Kubernetes: Streamlining the cluster

Static delivery pipelines are becoming a bottleneck. The best CI/CD tools for Kubernetes are those that move beyond simple code builds to provide total environment orchestration and developer self-service.

Mélanie Dallé
Senior Marketing Manager
DevOps
Cloud
 minutes
Top 10 vSphere alternatives for modern hybrid cloud orchestration

The Broadcom acquisition of VMware has sent shockwaves through the enterprise world, with many organizations facing license cost increases of 2x to 5x. If you are looking to escape rising TCO and rigid subscription bundles, these are the top vSphere alternatives for a modern hybrid cloud.

Mélanie Dallé
Senior Marketing Manager

It’s time to rethink
the way you manage K8s

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