Your workspace is on the Hobby plan, which has a per-project service limit of 50, and you are at that cap. We don't offer limit increases on Hobby.

For staged changes: the public API exposes an environmentStagedChanges query (documented at docs.railway.com/integrations/api/manage-environments) that returns the pending changeset for a given environment. In the dashboard, uncommitted edits appear as a numbered banner on the canvas. The start command shown in a service's settings is the committed value; any edit to it is staged and not applied to the running deployment until the changeset is committed, so comparing the two surfaces tells you whether the running deployment matches the saved configuration.

Thank you. Two quick confirmations before I close this:

1. If I move from Hobby to another paid plan, does the per-project service limit increase above 50? If so, what is the service limit on each applicable plan?
2. If environmentStagedChanges returns an empty changeset, and the start command in the service settings is the committed value, can I treat that combination as authoritative evidence that there are no unapplied configuration changes affecting the currently running deployment?

I am still only requesting information and do not want any changes made.

Yes, Pro has a per-project service limit of 100 (Hobby is 50). To your second question: that combination is reliable evidence that no unapplied edits exist for that environment. The settings page shows the committed values that the most recent deployment was launched with, so when nothing is pending, they match.