I'd like to reserve a minimum vcpu/memory allocation for a service. Scaling to zero is great, but some apps perform poorly on a single vcpu, id like to just pay to have 2 or 4 vcpus always reserved for some workload. Thanks

Take a look atsomeofthesestandalonenits

Also another one: There should be a comment preview feature here.
Edit: Also another one: Fix rendering of adjacent links

Deploying a template from the marketplace didn't ask which project to deploy to. It just blindly created a new random project against my intention.

Template search results on the dashboard canvas should have links to the actual marketplace page of that template. I don't want to blindly deploy whatever based on 5 words of description. Why can't I open the template page from the search bar?

In the project canvas, would be cool to be able to:

• duplicate whole groups of services,

• select multiple elements (either by Ctrl+click or rectangle select tool) and then perform bulk actions on them (like duplicate or delete),

• use Ctrl+C, Ctrl+V for the duplicate action,

• copy/paste elements between projects without the need of creating templates,

• create private templates.

Since you are on the Pro plan, every service has 32 vCPU and 32 GB of memory available at all times.

If you are maxing out at ~1 vCPU is likely because your workload is single threaded, and thus, it could benefit from horizontally scaling with our replicas.

I'd love if builds were more heavily cached. My service takes 5min to build without the cache, but 10sec if all dependency installation layers are cached. But despite only changing a few files, it often has to do a full build, including downloading mise packages. I'd love if each account got an allocation of cold cache space, so even if it's been a week since the last build it is still available rather than being purged instantly.

Mise packages also take a surprisingly long time to install, so I suspect they're being fetched from the source every time. It'd be great if Railway ran an internal mirror/cache to speed them up too.

Finally, as a stretch goal, it'd be awesome to get feedback in the build logs of why the cache isn't being used. Something like "Cache skipped because environment variable ABC_XYZ changed" or "Cache skipped because file package-lock.json changed" would be immensely helpful in knowing if the cache busting is intended or not.

Also shared volumes and ability to expose more than one port publicly would be great.

I have the following items on my wishlist.

Technical:

1. Roll out a basic WAF for which I can create basic rules by clicking on a http request in the logs.

2. Improve the GitHub integration when deploying a web app or website. It would be great if there was a way to automatically generate a preview URL and mention that URL in the PR comment on GitHub.

3. Making database deployments with backup as one-click as possible. Bonus if I can deploy a cluster this way.

Communication:

4. Add an RSS feed to https://railway.com/changelog or make it part of your blog.

5. Post to Bluesky.

I'm very much looking forward to the "Copy Volume Data" feature returning for when preview environments get spun up. This was a very handy feature.

Maybe this is a bug, but I cannot seem to get the "Base Environment" setting when set to "No Base Environment" to work properly. How I'd like it to work: I have two git branches, "main" and "develop", with each branch connected to services in a Railway environment ("production" and "develop", respectively). When PRs targeting "develop" branch are opened, I want the preview env to be based off the "develop" env. When PRs targeting "main" are opened, I want the preview env to be based off the "production" env. That isn't happening and all PR environments are getting based off "production".

• Sticky sessions for replicas. This would be helpful for websocket servers

• Read replicas across regions for databases

Many bounty questions are related to basic content, like if the private network isn't working or how to set up custom domains. Perhaps you guys (and girls) could add an FAQ section with a link to a YouTube channel where you explain these concepts... and the next time someone asks a question with an existing solution, we'll simply redirect them to that specific FAQ. (i know you have the docs, but apparently it is not enough, maybe a FAQ approach solves the problem)

Don't get me wrong, I love the idea of bounties rewards, but maybe this will help someone solve their problems faster.

When adding a custom domain to a service a window pops up with the value for the CNAME record, if you dismiss this window there is no way of checking what the record value was, if this is intended add a note to say "we'll show you this only once" or something like that.

You cannot view the value if your DNS record is correctly set. Unable to view the instructions = you set the value correctly. If you didn't set the record yet, or if it is incorrect, there should be a button that opens the modal again.

Though I agree there is no reason to hide this information from the UI. It is indeed confusing since there is no explanation as to WHY it refuses to let you view the instructions while also not showing any "success state" either.

I invited another member to my workspace, when they navigate to that workspace it takes 6 to 10 seconds to load that screen with the list of projects, it's really slow for some reason.

Command based health checks would be amazing! simply a bash command that can exit depending on the containers status.

It would be great to be able to set a default resource limit for all new services, something similar to the preferred deployment region, but for resource limits.

In my team, we almost always set the same vCPU and RAM limits (close to the minimum) for all projects, to prevent resource leaks and unexpected charges.

While it's great to have access to 32 vCPUs and 32 GB of RAM on the Pro plan, most of our simple projects — like APIs or microservices — don’t need that much power. Having a default limit would save us time and reduce the risk of overprovisioning.

These deploys are ordered incorrectly. The newest build should be first.

Also would be great to be able to set $ Usage limit per project.

I've deployed quite a few templates and have had to make many hacky workarounds to limitations. For example, we can't do the following:

1. Multiple volumes to a service

2. Sharing a volume with another service

3. IPv4 internal addresses (lots of issues with Redis over IPv6)

4. Specify multiple public addresses in the template. Some services require multiple ports (maybe 8000 for API, and 9000 for app). We could specify this after the template has been deployed with custom domains.

5. We can do pre-deploy commands. What about post-deploy commands? For example Apache Superset has this dumb requirement that you use their CLI to create the superuser after deploy. Would love to automate that in a non-hacky way in the template itself

6. Supplying configuration files in the template. Some images require you to pass a config file in a volume.

Also, US Central metal region pls

It would be great if state were preserved when navigating between Architecture, Observability, Logs. Essentially, proper tabs.

I would love to be able to set a "primary domain" for a service. That, or change the domain link within the service pane to a dropdown if there are multiple.

When changing a service variable it seems pointless having to rebuild the project all over again and having to wait 4+ minutes while it should have simply be a service restart to pickup the new variables

@kallikakis Railway cannot know if the variables are used at build time. They are available there and your application may use them at build time.

But your request is sound in principle. I would amend it to: Allow users to choose whether service should be fully rebuilt or just restarted when applying variable changes.