---
title: "Plans and Pricing Changes, Replica Support in Deploy Logs"
date: 2023-06-02T15:00:00.000+00:00
number: 0136
url: https://railway.com/changelog/2023-06-02-plans-and-pricing-changes
---

# Plans and Pricing Changes, Replica Support in Deploy Logs

It’s getting legitimately crazy around here with hype for some of the new features that are dropping in the next 1-2 months. 

We’re talking persistent volumes, regions, private networking — and way more. 

In preparation for all this stuff, we’re announcing some updates to pricing and plans today.

Read on to see what we’re doing!

## Incoming Plans and Pricing Changes by August 1st

[Image: A summary of the new plans expected to come by August 1st]

A few changelogs ago, [we announced](https://railway.app/changelog/2023-04-28-docs-search) that we wanted to revisit pricing. After many months of internal and community discussion, we are ready to reveal these changes. 

We published a pair of blogposts today to let you know about some of the changes coming to plans and pricing. 

Here’s the TL;DR:

- New Trial Plan (One time $5 credit grant, execution hours are going away)
- New Hobby Plan ($5 base cost that includes usage. Waiving the fee for qualified users.)
- Team becomes Pro (No changes, still $20 per seat + usage)
- Ability to pay using prepaid credits
- Charging for network egress ($0.10 / GB)
- Usage-based billing remains the same

That’s a lot — but we REALLY encourage you to read these blog-posts to see what we’re thinking.  The top one explains the Why, and bottom explains the What. 

Give them a read here: 

- [Introducing the $5 Plan](https://blog.railway.app/p/introducing-trial-hobby-pro-plans)
- [Migration Guide for Upcoming Pricing and Plan Changes](https://blog.railway.app/p/pricing-and-plans-migration-guide-2023)

Before we go into the next changelog item, we want to thank all of you. You’ve stuck with us as we’ve scaled to where we are today and we’re looking forward to seeing what you build next. 

## Replica Support in Deploy Logs

We are super impressed with reception we have gotten for replicas so far and team is now hard at work making these replicas … auto-scale! But that doesn’t mean we can’t improve the experience in the short term. This time, we are making it obvious to see which replica a log comes from.

Deploy logs now show the ID of the replica for every log item. To filter logs by replica, simply click on the ID and away you go!

[Image: You can now get logs (and filter them) for each of your replicas in the Deploy Logs pane]

## Improvements and Fixes

- We made some improvements to the log filtering interface
- We made some improvements to the metrics rendering when only a small amount of data is available
- We fixed an issue where some project pages were showing 404 randomly, this was due to a bad redirect on error
- We fixed an erroneous … um … error when unfocusing the replicas input
- We fixed a visual bug where new services might report a huge amount of resource usage