--- title: "DB metrics, network flows, login with Railway, zero-downtime volume resizing" date: 2026-01-30 number: 0275 url: https://railway.com/changelog/2026-01-30-db-metrics --- # DB metrics, network flows, login with Railway, zero-downtime volume resizing In case you missed it, an [open-source personal AI assistant](http://openclaw.ai/) went viral this week. It runs on your own machine and you can connect it to WhatsApp, Telegram, Discord, or whatever chat app you already use. The project [crossed 100k+ stars](https://github.com/openclaw/openclaw) on GitHub,[ went through two name changes](https://openclaw.ai/blog/introducing-openclaw), and sparked a wave of community excitement. Of course, giving AI full access to your machine is not the greatest idea, so several folks have already created Railway templates to make it possible to run it remotely instead. We also put together [a quick video](https://x.com/Railway/status/2017349208114688377) showing how to deploy your own and configure it (we went with [this template](https://railway.com/deploy/openclaw-railway-template)). Give it a try. It's pretty fun. Now for the stuff we built. It's a big one this week. Priority Boarding gets Postgres metrics and network flow visualization (pretty orbs and purple pipes on your canvas). Login with Railway brings proper OAuth to the platform. Volumes can resize without restarts. And templates can now pull from private Docker registries. Let's get into it! 🚄 ## Postgres metrics to Priority Boarding [Video: View database metrics for your Postgres database] New in [Priority Boarding](https://railway.com/account/feature-flags): Postgres database metrics. You can now view detailed metrics for your Postgres databases directly in the Railway dashboard. See connection counts (active, idle, idle in transaction), cache hit ratios, query statistics with timing breakdowns, and table-level information including row counts, data sizes, and index usage. The Query Statistics panel surfaces your most expensive queries with call counts, rows returned, and timing percentiles. The Tables view shows you exactly where your data lives and how it's being accessed. If you're running Postgres on Railway, this gives you the observability you need without reaching for external monitoring tools. Let us know what you think on [Central Station](https://station.railway.com/new?type=feedback). ## Network flows to Priority Boarding [Video: View network flows and their logs] New in [Priority Boarding](https://railway.com/account/feature-flags): Network flow visualization. Your canvas now shows live network traffic between services. Animated flows visualize the actual packets moving through your infrastructure, with the thickness indicating throughput. Toggle between network flows and reference variables using the canvas controls in the top left. Under the hood, this is layer 4 network observability. Each flow is aggregated by source IP, source port, destination IP, and destination port every 5 seconds. You can inspect latency, see which peers are connected, and find out why packets were dropped. Head to a service's logs and you'll find a new Network Flow Logs tab where you can dig into the raw data: protocol, source and destination addresses, connected peers, traffic volume, latency, and status. Drop your feedback on [Central Station](https://station.railway.com/new?type=feedback). ## Login with Railway [Video: Platforms can now authenticate users with their Railway account] We want to make it easier to extend Railway, both for developers building tools and for platforms building integrations. Until now, platforms integrating with Railway had to ask users to manually provide an API key. That meant users had to navigate to their account settings, create a token with the right scope, copy it, paste it into the integrating platform, and hope they didn't mess up the permissions. If the token got invalidated? Back to step one. Login with Railway changes this. It's a proper OAuth 2.0 implementation with OpenID Connect. Users click a button, approve the permissions they want to grant, and they're done. The platform gets secure, scoped access without ever touching raw API keys. Here's what the flow looks like: 1. Create an OAuth app in your workspace settings under **Developer → New OAuth App** 2. Redirect users to the authorization endpoint 3. Exchange the authorization code for tokens 4. Use the access token to make API requests on behalf of the user The system supports both web apps (confidential clients with client secrets) and native apps (public clients using PKCE). Refresh tokens are available for long-lived access, and users can select exactly which workspaces or projects to share. For developers already building Railway integrations, this is the path forward. For users, it means fewer API keys floating around and more granular control over what third-party tools can access. Check out[ the OAuth quickstart](https://docs.railway.com/reference/oauth/quickstart), and share your feedback on [Central Station](https://station.railway.com/new?type=feedback). ## Resize volumes without restarting your service [Video: Resize volumes without restarting your service] *This feature is in beta* Previously, resizing a volume meant restarting your service. For most workloads that's fine, but for long-running processes or services where uptime matters, it was a pain point. Live Volume Resizing attempts to resize your volume without any restart. If the live resize fails (which can happen depending on the underlying filesystem state), a restart will be required as a fallback. Either way, you're in control. To try it out, head to your volume settings and look for the `Live resize` option. You'll be asked to type a confirmation phrase before proceeding. This is a one-way operation, after all. Let us know how it goes on [Central Station](https://station.railway.com/new?type=feedback). ## Templates can deploy from private Docker images [Image: Templates can now deploy services from private Docker images] Template authors, this one's for you. You can now include private Docker images in your Railway templates by securely sharing registry credentials. When someone deploys your template, the services built from private images will work seamlessly. The user never sees or accesses the underlying credentials. For added security, SSH access is blocked for these services, keeping your credentials and container internals protected. This opens up new possibilities for distributing proprietary software, internal tools, or commercial applications while benefiting from [Railway's template kickback](https://docs.railway.com/reference/templates#kickback-program) program. ## Fixes and improvements - We shipped an improvement for deployment messages with `railway up`. You can now pass `--message "text"` or `-m "text"` to set a deployment message that shows up in the UI the same way a commit message would - We improved the Service Settings page with a new "Scale" section that brings together regions, replicas, and replica limits all in one place