I presume this is me asking the community if it's something that I should spend my time considering I hacked on preliminary support in our internal hackathon.

Methinks yes, I'd love to have compose natively supported. One of the biggest friction point from "dev->prod" is "how do I match prod to my dev env"

Most dev stacks include a compose file for you to spin up dependencies locally. It's a natural standard starting point today for when you want to distribute dependencies of your app and ensure that "works on my local machine, not sure why not on yours" isn't a class of problem to contend with at all.

If we can marry the two notions and have "docker compose just work in production" I think it's a killer feature

Docker compose is definitely a must-have. There are so many projects out there, or like Ray said, dev stacks that are built with compose for speed of code to working product, that Compose is pretty essential to the dev cycle.

I also know that as a template maker, compose would help out, as the iteration process of converting compose to railway components/services is tedious and time consuming. Being able to drop that compose file and have it up and running would make life so much easier.

In almost all of our projects, there is a Docker Compose file for local development. It's essential for our team.

This feature would allow bigger companies, aka the interesting Customers, to get quickly started on Railway with an existing project. We have one project where we would love to move it to another provider, but the required time investment and associated risks don't justify the savings.

Trying out a service when you can just get started with your current setup can be tempting.

duplicate of https://community.railway.app/discuss/thread/support-docker-compose-30e9262f

It’s here as of yesterday!

Where? Can't find any reference to it in the docs

It's announced here: https://railway.com/changelog/2024-12-20-collapsed-groups