Common questions
Questions about self-hosted bastion hosts
Ezeelogin installs on any standard Linux server running RHEL, Ubuntu, or Debian. A 2-core, 2GB RAM VPS is sufficient for most teams. For larger deployments or high availability, we recommend dedicated hardware or a larger instance. Full requirements are in the installation guide.
Yes. Ezeelogin is cloud-agnostic. Any Linux server you can SSH into — whether on AWS, GCP, Azure, DigitalOcean, Hetzner, or bare metal — can be added to Ezeelogin. There is no cloud provider dependency.
A raw OpenSSH jump host gives you a network relay — nothing more. You still manage keys manually, have no session recording, no GUI, no RBAC, and no instant revocation. Ezeelogin builds the full access management layer on top: web-based management console, group-based RBAC, MFA enforcement, full session recording, audit logs, and single-action user revocation.
Ezeelogin supports a master-slave HA cluster configuration, allowing the secondary node to be promoted as the master during a primary node failure.
No. Ezeelogin is completely self-hosted. Session recordings, audit logs, access records, and all configuration data are stored entirely within your infrastructure. License validation is the only external communication, and it does not transmit session or user data.
Simple, server-based pricing. Your subscription is based on the number of servers added to the gateway, allowing you to scale your infrastructure without being limited by the number of users accessing the system.
Most teams complete installation in under 30 minutes. Adding servers and configuring your first user groups typically takes another 30–60 minutes. A free screen-share onboarding session is available if you want guided setup support.