--- title: "Trust Center, New Slack Bridge, Edge Proxy Cutover Progress" date: 2024-08-02 number: 0197 url: https://railway.com/changelog/2024-08-02-trust-center --- # Trust Center, New Slack Bridge, Edge Proxy Cutover Progress Have a friend that’s new to Railway? Send ‘em over to the new [*Basics*](https://docs.railway.app/overview/the-basics)*** ***tutorial.** ** Have a security-minded coworker that’s new to Railway? Send ‘em over to the new [*Trust Center*](https://trust.railway.app/). Want to talk to us directly? Well you’re in luck as this week we’re introducing a new Slack Bridge for that. That’s right, folks, this week we’re coming in hot with resources to make your experience on Railway as great as possible. Without further ado, let’s all please mind the gap and find our seats. Wonderful. Let’s begin. ## Trust Center [Image: The new Railway Trust Center is available at trust.railway.app] The all-new [Railway Trust Center](https://trust.railway.app/) is now live! This web property allows you to review Railway’s compliance posture on such topics as GDPR, SOC 2, and HIPAA. It also makes it easy to download documents that you might need such as the Acceptable Use Policy, Data Security Policy, and so forth. Need even more documents? If you’re a Pro team with substantial compliance needs and you’d like to talk to us about SOC 2 or HIPAA, we invite you to schedule a session [here](https://cal.com/team/railway/demonew). Otherwise be sure to check out the [Trust Center](https://trust.railway.app/). ## New Slack Bridge [Image: There’s a new easy way to file a help ticket directly from Slack] If you’re a [Pro tier](https://railway.app/pricing) user with a direct Slack channel with the Railway team, we’ve enabled a new way to get your questions resolved faster. ~~With a simple ~~~~`/support`~~~~ command in Slack, you’ll first be asked to make sure your Slack is connected to your Railway account via ~~[~~Account Integrations~~](https://railway.app/account)~~. ~~ *Record scratch* [Freeze frame] Angelo: “You might be wondering how I got here.” So I was in progress of rolling this feature out until I realized I didn’t test the flows on different Workspaces. See, I worked in a Shared Channel in a Dev workspace, I had two different workspaces connected but since the command was the same I couldn’t tell them apart. Imagine my surprise when I saw no Slash Command. As such: I didn’t realize I wasn’t able to invoke a command in a shared channel from another workspace. Massive egg on my face. So I am doing you one better. I did some research. Out of 100+ channels, none of you stop by to say hello. (Stay with me here.) You want to talk to us direct because something’s gone horribly wrong. Now immediately when you post a message as a member, we immediately spin up a thread and apply a SLO timer to the support on-call. It only applies to channels with the Railway Support app installed which I am rolling out in stages. No more dropped Slack threads. Okay- cool… phew. [Changelog resumes] We are so confident in our ability to be responsive to user requests on Slack now that we have also lowered the requirements needed to get a Slack Channel. Want a Shared Slack Channel? [Just ask.](https://help.railway.app/) ## Edge Proxy Cutover Progress [Image: The new edge proxy is now the default for most services] As we mentioned [two weeks ago](https://railway.app/changelog/2024-07-19-database-private-networking#new-edge-proxy-migration) (and [four weeks ago](https://railway.app/changelog/2024-06-14-nyoooom#edge-proxy-rollout-update) and [eight weeks ago](https://railway.app/changelog/2024-05-17-new-edge-proxy-beta#introducing-the-new-edge-proxy-(beta))), we’re rolling out a new edge proxy to speed up deploy cutovers, provide richer error pages, and a whole host of other benefits that are coming down the line. As of this week, all new domains are using the new proxy. If there’s a reason you need the legacy proxy (unlikely), you can now toggle the legacy proxy in your network service settings. Over the next month we’ll be transitioning all existing service domains off the legacy proxy and onto the more performant new edge proxy. Custom domains will remain configurable for a bit longer than that. Now you know! Have a great weekend. ✌️ ## Features and Improvements - We introduced a new “[Basics](https://docs.railway.app/overview/the-basics)” page in the docs - We added a tutorial called [Setting up Proximity Steering Using Cloudflare](https://docs.railway.app/tutorials/proximity-steering) useful for those who want control over routing their app - We made it so that service domain ports are now part of the staged config. This means that if you have multiple ports configured, they'll be respected in PR environments - We finished migrating all templates to the new [template composer](https://railway.app/compose) v2 infrastructure. That means we’re now able to push features and flows around templates faster as we don’t have to manage both systems - We fixed a bug where services would sometimes fail to delete in some cases - We fixed a bug where deployments in PR environments would sometimes be stuck on "Waiting for CI" - We fixed a bug with the template creator not showing up on the template details page