Hello,

I would like to clarify the following general Railway platform capabilities.

This is not a request to investigate or change a specific project.

1. Enforced outbound network restrictions

For a workload that fetches URLs using Node.js and Chromium, is there a

platform-enforced way to allow connections only to a specified forward proxy

and deny all other direct connections?

Can this be enforced per process within a service, or per service if the

workload is moved to a dedicated service?

Please clarify the scope and any exceptions for IPv4, IPv6, TCP, UDP, and

private-network connections to other services.

The requirement is not just to configure a proxy environment variable.

Direct connections must remain blocked even if the workload does not use the

proxy or the proxy becomes unavailable.

Please provide the supported plans and relevant official documentation.

If this is not supported, is there a recommended deployment approach?

1. Safely pausing Cron jobs

Is there an official way to stop future scheduled runs without deleting the

service or its configuration?

In particular, what happens when “No schedule” is selected and the change is

applied? Can this trigger a redeployment, an immediate run, a normal

non-scheduled service startup, or interruption of an already running process?

Please clarify the safe pause/resume procedure and whether missed runs are

executed when scheduling is resumed.

1. Inspecting non-sensitive startup settings

If a Custom Start Command may contain secrets, is there an official UI feature

or read-only method to inspect only the non-sensitive target path,

authentication method, and timeout/retry settings without exposing the full

command or secret values to an AI assistant or support?

The goal is to understand the available platform capabilities and limitations

before deciding on a deployment configuration and operating procedure.

If the answers depend on the plan or configuration, please specify those

conditions.

Thank you.