HostCritiq
Search ⌘K
Menu

Application hosting

Hosting Apache Guacamole

Apache Guacamole provides remote desktop and terminal access through a web browser. It connects to existing machines over RDP, VNC or SSH, so users do not need a separate remote-access client on each device. It suits a team that wants one controlled entry point to workstations or servers. The computers being accessed still need their own operating systems and resources.

Requirements last checked against the project's documentation.

Compare server plans Size a server

Understand the setup

Find the software and services needed to run the application.

See requirements

Budget your resources

Plan memory, storage and CPU for the way you will use it.

Open resource planner

Build your shortlist

Compare plans for the starting size, then review the provider and billing terms.

See plans

Must have

Installation requirements

  • A host capable of running the Guacamole web application and guacd service.
  • A configured authentication method.
  • Network access from guacd to the intended RDP, VNC or SSH destinations.

Recommended

Planning guidance

Use the resource planner to size a server for your workload.

Choosing a server for Apache Guacamole

Simultaneous sessions, screen changes and recording settings affect gateway load and traffic. Resources on the remote desktop are separate from the gateway, so increasing gateway memory does not enlarge the computer a user connects to.

Deploy with

Supported paths

  • Docker containers
  • Native installation

The host must provide

Runtime

Connection proxy
guacd paired with the selected Guacamole release.
Authentication storage
MySQL or PostgreSQL for the documented database-authentication deployment.

Storage

Persistent data

Persist the authentication database and protect configuration and connection secrets. If session recording is enabled, include recordings in storage and retention planning; the gateway database is not a backup of the remote machines.

Step by step

Plan your Apache Guacamole deployment

  1. Separate the components

    Deploy the web application, guacd and chosen authentication backend on restricted networks.

    Official instructions
  2. Initialise authentication

    For database authentication, create the schema using the supplied SQL before starting the web service.

    Official instructions
  3. Configure authorised destinations

    Add connections and user permissions, then check access through HTTPS with a non-administrator account.

    Official instructions

Security

Before you go public

  • Do not expose guacd directly to the public internet: it does not authenticate users.
  • Restrict gateway access and use an appropriate authentication and multi-factor setup.

Cost

Beyond the server price

  • The Apache-licensed software and the machines it connects to are separate budget items.
  • Include gateway traffic, authentication storage and any session recordings in the deployment cost.

Want the full monthly bill? Use the hosting cost calculator. Add storage, backups and other costs to your estimate.