SSH Gateway routes your session through ssh.webscale.com to any internal machine in your environment. Bring whatever SSH client you already use.
No public IPs. No Port 22 open to the internet.
SSH Gateway sits between your SSH client and your private cloud. Connect to ssh.webscale .com and the gateway handles last-mile authentication to any internal machine from there.
OpenSSH, PuTTY, FileZilla, SCP, SFTP, local port forwarding. Your existing client setup works as-is.
Access is key-pair only, tied to User Roles. Remove someone from the "Editor" role and their SSH access is gone across every server, right then.
Connect to your servers the way you already work. Standard SSH clients only. Your existing setup, nothing new to install.
SSH Connect registers your host with the Webscale Control Plane through the Webscale Monitoring Agent. Once registered and approved, any authorized user can reach it through a standard SSH session.
The UI generates a config snippet you paste straight into ~/.ssh/config. After that, getting in is one command: ssh webscale-prod.
Keys live in your user profile: up to 5 public keys, a custom login name, and the SSH config snippet. Manage all of it from the SSH tab.
Shopware ships often. Magento ships less often. Both deserve a standing calendar hold.
Bookmark the release pages. A missed patch is cheaper to prevent than to explain after an incident.
Both maintain public release pages. If you’re not checking them on a schedule, you’re reacting instead of catching issues first.
Add SSH Gateway’s audit logs to that cadence and you have a clear record of who accessed what, and when.
Quick reference
Your monthly patch checklist
✓
Check Shopware changelog
✓
Check Magento release notes
✓
Review SSH Gateway audit logs
✓
Verify access roles are current
✓
Test deployments post-patch
Do this before the next sprint, not after an incident.
From the Blog
Infrastructure
~6 min read
What Breaks First When Ecommerce Traffic Doubles in 90 Seconds
When traffic spikes hit, architecture stops being theoretical. This breaks down which layers buckle first, what the logs tell you, and why peak traffic is the wrong time to discover your AI layer cannot keep up. Required reading if you’re on the hook for uptime.
