Skip to content
Soc2 Evidence
csawai
OP

a month ago

Goal

We're migrating a production Rails application off AWS (EKS/RDS/S3) to Railway and need to maintain our existing SOC 2 Type II program. On AWS, most of our controls were service-inherited (WAF, GuardDuty, CloudTrail, Config, KMS, RDS Multi-AZ) and auto-collected into Drata. Before we commit to the migration, we need to understand exactly what Railway provides natively for compliance and what we'll have to cover ourselves. Please point us to options/docs for each item below.

  1. Compliance artifacts (sub-processor evidence)
  • How do we obtain Railway's SOC 2 Type II report, latest penetration test report, DPA, and subprocessor list? Is the Trust Center the only route, or is NDA/request-gating involved?
  • Which underlying infrastructure provider(s) and regions host production workloads, and what data-residency guarantees can we get (US-only)?
  1. Committed Spend tiers
  • Please confirm the feature unlocks per tier: does the $2,000/mo tier give us SSO (SAML), RBAC, and 18-month audit log retention, and the $1,000/mo tier give HIPAA BAA + 90-day logs? We want to confirm $2,000/mo is sufficient for SOC 2 access controls (we don't need the $5,000 SLO tier unless required).
  1. Audit logs & evidence export (for Drata)
  • There's no native Drata integration. Can you confirm the GraphQL API (backboard.railway.com/graphql/v2) exposes auditLogs (actor/event/timestamp) and service/variable config in a way suitable for an automated read-only evidence poller? Any rate limits, token scoping (read-only), or recommended patterns?
  • Do you have customers successfully feeding Railway evidence into Drata or similar — any reference approach?
  1. Database (replacing RDS Multi-AZ)
  • For managed Postgres: please confirm encryption at rest (and whether it's customer-managed-key or platform-managed), PITR and its exact retention window, and the HA/failover model (Patroni, in-region). Is there any cross-region DR option, or is multi-region customer-architected?
  1. Encryption in transit
  • Confirm automatic TLS on public domains. For service-to-service private networking and DB/Redis connections over the private network, is traffic encrypted, or should we treat the private mesh as the isolation control and additionally enable TLS on DB connections?
  1. Networking / WAF / egress
  • We plan to front Railway with Cloudflare for WAF (ruleset + geo-block) since Railway's WAF is Under-Attack-Mode only. Any recommended origin-lockdown mechanism so traffic can only reach our services via Cloudflare? Are static egress IPs dedicated or shared, and do they change on region moves (we may need stable IPs for allowlisting)?
  1. Logging
  • Railway has no native log drain. What's the recommended way to forward container stdout logs to an external store (New Relic in our case) — Fluent Bit output plugin, OTel, or an agent run as a service? Max retention on Railway-native logs per tier?
  1. Access control
  • With RBAC on the $2,000 tier, can we restrict production environment access to a subset of members while others retain deploy-via-git-push? Is 2FA enforcement workspace-wide available at that tier?

We're planning the control-mapping and evidence pipeline now, so concrete answers (or doc links) on the above will let us finalize the migration plan and the Railway tier commitment.

$20 Bounty

1 Reply

Railway
BOT

a month ago

We checked our documentation and it does not cover this yet, so the Railway community is the best place to get a real answer: people who have already worked this out on their own projects and can tell you what actually worked.

So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

  • Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
  • Keep it private and close the thread - Nothing becomes public and the thread closes.

Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.

Status changed to Open Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...