ONE GATEWAY. ALL YOUR SERVERS.
Arcustech SSH Jump Servers are purpose-built bastion hosts designed for modern workflows: teams, contractors, dynamic IPs, and CI/CD deployment tools. Instead of leaving port 22 exposed to the internet, your Arcustech VPS servers can be restricted to accept SSH connections only from your jump server, while your team connects to the jump host using SSH keys.
Practical guide: If you want examples you can copy and adapt (CLI ProxyJump, Termius, SFTP key management, database tooling, and GitHub Actions), see our article: SSH Jump Servers: practical, secure access.
This add-on is not a customer-managed VPS with SSH enabled. Arcustech SSH Jump Servers are operated as a managed access control service. Accounts are provisioned, maintained, monitored, and secured by Arcustech to ensure consistent enforcement of security controls and fair-use limits.
By centralizing management, we can enforce key-only authentication, chrooted SFTP for safe key management, outbound connection controls, automated intrusion blocking, and hard session limits that prevent runaway automation from impacting platform stability.
One jump account, multiple servers.
A single SSH jump server account can be used to securely access all of your Arcustech VPS servers - it is not limited to a single VPS.
If your organization requires stricter access separation, you can maintain separate jump server accounts per developer. Alternatively, a single jump server account can be used with individual SSH keys per developer.
Developers with Arcustech VPS servers in multiple regions can operate separate jump accounts per region to align with latency, data residency, or compliance requirements.
Unlike per-server access models, Arcustech jump servers act as a central access gateway. Your developers and CI/CD tools connect to the jump server once, and from there can securely reach any Arcustech VPS servers your team manages - across regions, projects, and environments.
Regional availability.
Jump servers are available in North America and the EU, with additional regions planned as Arcustech expands its Gen5 platform (including future APAC availability).
For teams operating in multiple regions, you can run separate jump accounts per region to align with latency, data residency, or compliance requirements. Your workflow stays consistent, while access remains region-local and tightly controlled.
Best for: Solo developers, agencies, and studios that want secure SSH access without static IP requirements, while still supporting CI/CD deployments.
Plans and Limits
Each plan includes a single jump server account per customer, supports multiple SSH keys, and is compatible with SSH ProxyJump and standard tunneling workflows. Limits below are enforced to protect stability and ensure consistent performance for all customers.
| Plan | Recommended For | Concurrent Connections (Enforced) | Max Sessions per Connection | Idle Session Handling | Intrusion Protection | Price |
|---|---|---|---|---|---|---|
| Solo Developer | Individuals, freelancers, personal projects | Up to 3 | Up to 3 | Shorter idle tolerance | Automated IP blocking on repeated failures | $5/month |
| Small Dev Shop | Agencies & teams (approx. 5 developers) | Up to 8 | Up to 8 | Balanced for team workflows | Automated IP blocking on repeated failures | $15/month |
| Large Dev Shop | Larger agencies & studios (approx. 10 developers) | Up to 15 | Up to 15 | More tolerant for parallel deploys | Automated IP blocking on repeated failures | $30/month |
| Custom / Dedicated | Larger teams, high concurrency, or dedicated requirements | Custom | Custom | Custom | Automated IP blocking on repeated failures | Contact Us! |
Need extra capacity for a migration or major deployment? Short-term, time-limited plan increases can be applied and will automatically revert after the approved window. If you need additional capacity for longer than a couple of days, upgrading to the next plan level is usually the best option.
DIY Jump Server vs. Arcustech Jump Server
Many teams can build their own bastion host. The difference is in enforcement, operational maturity, and the safety controls that reduce risk and support load over time. Arcustech jump servers are configured specifically for secure tunneling access to Arcustech VPS infrastructure, with controls designed around real developer and CI/CD workflows.
| Feature | Typical DIY Bastion | Arcustech Jump Server |
|---|---|---|
| Access model across multiple servers | Often one per project with manual oversight | Single, centrally managed and monitored gateway |
| Operational ownership | Customer-managed and self-maintained | Managed and maintained by Arcustech |
| Authentication enforcement | Varies by configuration and discipline | Key-only authentication enforced by default |
| Interactive shell access | Often enabled unless explicitly disabled | Non-interactive access enforced |
| File access and key management | Often unrestricted or loosely controlled | Chrooted SFTP with restricted filesystem access |
| Connection and session limits | Rarely enforced or inconsistently applied | Hard enforced per-user and per-session limits |
| CI/CD and automation safety | Prone to runaway jobs or misconfiguration | Guardrails designed for CI/CD workflows |
| Outbound SSH destination control | Unrestricted unless manually configured | Restricted to Arcustech VPS infrastructure |
| Intrusion detection and blocking | Optional and inconsistently tuned | Automated intrusion detection with tuned thresholds |
| Idle session handling | Often unmanaged or overlooked | Automatically enforced based on plan limits |
| Access lifecycle management | Manual changes and ad-hoc procedures | Managed suspend, resume, and revoke controls |
| Temporary access scaling | Manual configuration changes | Time-limited increases with automatic reversion |
| Auditability and visibility | Depends on customer logging and review | Centrally monitored and auditable access model |
| Multi-region support | Requires separate builds per region | Available in multiple regions with consistent controls |
The goal is simple: you get a secure SSH gateway that supports real-world workflows without having to engineer and maintain a hardened bastion configuration yourself. Your team stays productive, your servers stay protected, and access remains controlled and auditable.
If your security policy requires restricting SSH access to known sources, a jump server is one of the most practical ways to do it without forcing every developer or CI runner to have a static IP, or long and complex allow/deny firewall rules per VPS server.
Additional Details:
Do I need a separate jump server account for each VPS?
No. A single Arcustech jump server account can be used to securely access all Arcustech VPS servers that your team operates within the selected region.
This makes it ideal for agencies, internal teams, and CI/CD pipelines that manage multiple servers or environments.
What regions are jump servers available in?
Arcustech jump servers are currently available in North America and the EU. As our Gen5 platform expands, additional regions, including APAC, will become available. Customers can choose the region that best aligns with their infrastructure and compliance needs.
How do SSH connection and session limits work?
Each plan enforces a maximum number of concurrent connections per user. This includes SFTP connections as well as SSH tunnel connections from developer machines or CI/CD tools.
In addition, each connection is limited to a maximum number of multiplexed sessions (also called channels). These guardrails help prevent runaway CI jobs or misconfigured tools from opening excessive tunnels and impacting stability.
Think of a connection as a single device or automation source connecting to the jump server - for example, your desktop, your laptop, or a CI/CD runner. Each session represents an individual tunnel or command stream opened within that connection.
Does this work with CI/CD tools?
Yes. Most CI/CD tools support SSH keys and standard SSH tunneling or ProxyJump workflows. Because access is key-based and non-interactive, it works well with automated deployments.
If a specific tool needs higher limits for a short period, we can apply a time-limited temporary bump.
Can I access servers other than Arcustech VPS servers?
No. Jump servers are configured with outbound SSH restrictions so they can only connect to Arcustech VPS IP ranges. This reduces the risk of a jump account being used as a general-purpose gateway to the wider internet.
Can I temporarily increase limits for a migration or major deployment?
Yes. We support time-limited temporary access increases for planned work. You may request a temporary increase of one to two days directly from our Support Team.
If longer-term additional capacity is required, we recommend upgrading to the next plan level instead. Temporary increases are tracked and automatically reverted back to normal plan limits after the approved window.