---
title: "Duplicate Services, Improved Deployment Information, Template Service Eject"
date: 2024-07-05
number: 0193
url: https://railway.com/changelog/2024-07-05-duplicate-services
---

# Duplicate Services, Improved Deployment Information, Template Service Eject

Oh say can you see, it’s time for Changelog #0193. 

This week we’re bringing you a new handy way to duplicate services, we’re making generally available some improvements to the service deployment panel, and we’re officially shipping a way to eject a service from its upstream repo within a template. 

Let’s get started! 

## Duplicate Services

[Video: New: Duplicate a service directly from the dashboard]

We added a new and easy way to duplicate a service in the dashboard. 

To get started, all you need to do is right-click a service and select `Duplicate` from the drop-down menu. 

That’s all there is to it!

Let us know what you like or don’t like about this feature by dropping a comment in the feature thread [here](https://help.railway.app/feedback/duplicate-service-7d534363). 

## Improved Deployment Information

[Video: New deployment information panel is now generally available]

We’ve been busy making some improvements to the service deployment panel when deploying or redeploying a service. 

In particular, we’ve been working to communicate a more clear history of your deployments and to make it more transparent what stage your currently deployment is in.

We’re also aiming to make it easier to recognize the error or errors that might be interrupting your current deployment. 

So this week we made generally available the first new design for service deployments. 

We hope you find it a bit easier to understand what’s going on with your deployments. 

If you have feedback for us, we’d love to hear it [here](https://help.railway.app/feedback). 

## Template Service Eject

[Video: Ejecting a service from a template is now generally available]

Let’s say you’re using a [template](https://railway.app/templates) but you’d like to customize one or more services within the template — previously there hasn’t been an easy way to do this other than forking the repo via GitHub, making changes, deploying from the forked repo, and so forth. 

It was a lot of work.

Now we’ve introduced to general availability an `Eject` function. This creates a copy of the template service source inside your own GitHub account so you can do whatever you want with it — all within the Railway dashboard. 

It’s as easy as selecting the service within your project, navigating over to settings, and hitting the `Eject` button. 

We hope you like it. 

## Fixes and Improvements

- We fixed an issue that sometimes caused errant 404s to show up when using the Railway dashboard
- We made improvements to the way we display cost usage breakdown charts at the project level
- We added dates of the current billing cycle to usage limit notification emails