Final report suggested release
dsmurrell
PROOP

9 hours ago

Hi Guys

I'm getting this recommendation from Claude, and if I am, many others will be too:

"Suggestion: decide by 30 November.

  • If by then Railway has published a report that names a root cause, rules out source code access and covers how secrets are stored: stay, and do the Tailscale fix.
  • If not: move to AWS. A supplier that can't say how it was breached after six weeks is hard to defend if a client like XXX asks. The lean move is about two weeks of work and roughly $30–60/month more."

I've already had to email clients and tell them that you guys were breached.

Are you planning to release a final report?

Under Review

0 Threads mention this feature

0 Replies

Welcome!

Sign in to your Railway account to join the conversation.

Loading...