Hoop on Ubuntu 24.04 LTS by cloudimg
by cloudimg
Open source access gateway that brokers and audits privileged access, by cloudimg.
Hoop access gateway on Ubuntu 24.04 LTS
Hoop is an open source layer 7 access gateway that sits between your people and your infrastructure. Instead of handing out standing credentials to databases, servers and internal tools, users connect through Hoop, which enforces access at the wire protocol level, records every session, and can route sensitive actions through review and approval.
It brokers audited access to PostgreSQL, MySQL, SQL Server and MongoDB databases, SSH and RDP servers, Kubernetes and internal web apps, so a single audited entry point replaces scattered direct connections. Every command and query is captured to an immutable session log for audit and incident review, optional reviewers can approve or reject risky operations before they run, and data masking can redact sensitive fields in flight.
What cloudimg delivers
This image runs the pinned upstream Hoop gateway as a systemd managed service, backed by a local PostgreSQL 16 database on the same VM. The web console and REST API are served on port 8009 and access agents connect over gRPC on port 8010.
- Secure by default — local password authentication with no administrator baked into the image; the first user you register becomes your organization admin
- A unique PostgreSQL password and a unique administrative API key generated on first boot and written to a root only file, so no two instances share a secret
- The gateway learns its own public address on every boot, so the console works without hand editing
- PostgreSQL bound to loopback; the base fully patched with unattended security upgrades enabled
- A paired step by step deployment guide and 24/7 cloudimg support
Licensing — MIT, free. The cloudimg charge of $0.04 per vCPU hour covers packaging, security patching, image maintenance and 24/7 support. Recommended size: Standard_B2s to start, scaling up for heavier use. Prerequisites: an Azure subscription, a VNet and an SSH key; the network security group should permit ports 22, 8009 and 8010.