8 hours ago
Hello Railway Community and Railway Support,
I have a general question about the availability of historical process-start evidence for Railway deployments.
For a previously deployed application, I would like to understand whether Railway retains provider-observed records of the actual executable and command-line arguments (argv) used when a container process started.
Specifically:
-
Does Railway retain historical process-start records that reflect the executable and arguments actually observed at runtime, rather than only the configured start command or Dockerfile CMD?
-
If such records exist, can Railway provide a provider-authenticated record that identifies the relevant deployment and replica?
-
Is there a secure method for an authorized customer or independent security reviewer to verify these records without publicly exposing credentials, sensitive process arguments, or application data?
-
If these records are unavailable through normal deployment metadata or logs, is there an official support channel to request a feasibility assessment of historical evidence availability?
This is a general documentation and feasibility question only.
I am not requesting an evidence export, production access, container execution, restart, deployment changes, or disclosure of sensitive information.
Thank you.
3 Replies
8 hours ago
The history we make available for deployments is what you can see yourself: your deployment details and logs, and your workspace audit logs. Beyond those, we don't provide historical process-start records, such as the executable and argv observed at runtime, or provider-authenticated attestations tied to a specific deployment or replica.
We also don't run a separate verification channel or feasibility assessment for that kind of evidence. Anything an authorized customer or reviewer needs to check has to come from the customer-visible records above.
Status changed to Awaiting User Response Railway • about 8 hours ago
Railway
The history we make available for deployments is what you can see yourself: your deployment details and logs, and your [workspace audit logs](https://railway.com/workspace/audit-logs). Beyond those, we don't provide historical process-start records, such as the executable and argv observed at runtime, or provider-authenticated attestations tied to a specific deployment or replica. We also don't run a separate verification channel or feasibility assessment for that kind of evidence. Anything an authorized customer or reviewer needs to check has to come from the customer-visible records above.
8 hours ago
Thank you for the automated response.
Could a Railway staff member please confirm whether historical, provider-observed process-start executable/argv records or deployment-specific attestations are available to customers?
I am only requesting clarification of Railway’s general evidence availability policy, not an export or access to any specific deployment.
If such records are unavailable, a brief confirmation from Railway staff would be sufficient.
Thank you.
Status changed to Awaiting Railway Response Railway • about 8 hours ago
7 hours ago
We can confirm that support doesn't provide historical process-start records, such as the executable and argv observed when a container started, or provider-authenticated attestations for a specific deployment or replica. We also don't offer a separate verification route or feasibility assessment for this kind of evidence.
The history available to customers and anyone they authorize to review it is what you can see yourself: your deployment details and logs, and your workspace audit logs.
Status changed to Awaiting User Response Railway • about 7 hours ago