This page explains how to install the Looker application for customers who are hosting an [on-premises](https://docs.cloud.google.com/looker/docs/glossary.md.txt#customer-hosted) Looker deployment. Throughout our documentation, we refer to these as "customer-hosted" deployments.

We also offer the option for Looker to host your Looker deployment. Throughout our documentation we refer to these as "[Looker-hosted](https://docs.cloud.google.com/looker/docs/glossary.md.txt#looker-hosted)" deployments. Using a Looker-hosted instance greatly reduces the effort required to [install](https://docs.cloud.google.com/looker/docs/looker-hosted-installation-steps.md.txt), configure, and maintain the Looker application, because Looker handles all necessary IT functions that are related to the Looker application for you.

> [!NOTE]
> **Note:** Hosting the Looker application is independent of where your data resides; data always remains in-database and is not copied to the Looker instance. Some Looker features are not available for customer-hosted deployments, or they may require additional configuration or software. To learn more about feature differences between the two hosted options, see the [Choosing a hosting option for a Looker (original) instance](https://docs.cloud.google.com/looker/docs/choosing-hosting-option.md.txt) documentation page.

Complete the following steps:

1. Install Looker:

   - [Add Looker to your server](https://docs.cloud.google.com/looker/docs/installing-looker-application.md.txt).

   - [Configure Looker startup options](https://docs.cloud.google.com/looker/docs/startup-options.md.txt).

   - [Configure your SSL certificate for proper HTTPS](https://docs.cloud.google.com/looker/docs/ssl-certificate-for-proper-https.md.txt).

   - [Consider port forwarding for a cleaner URL](https://docs.cloud.google.com/looker/docs/port-forwarding.md.txt).

   - [Allow Looker support to access your instance](https://docs.cloud.google.com/looker/docs/support-access-customer-hosted-deployment.md.txt).

   - [Set up Looker monitoring](https://docs.cloud.google.com/looker/docs/monitoring-looker.md.txt).

   - [Set up a MySQL backend database](https://docs.cloud.google.com/looker/docs/migrating-looker-backend-db-to-mysql.md.txt).

   > [!NOTE]
   > **Note:** We recommend that all new customer-hosted instances set up a MySQL backend database rather than use the default HyperSQL database.

   - [Set up Looker backups](https://docs.cloud.google.com/looker/docs/creating-backups.md.txt).

   - [Ensure that Looker can access necessary services](https://docs.cloud.google.com/looker/docs/outbound-port-requirements.md.txt).

   - [Install rendering software](https://docs.cloud.google.com/looker/docs/installation-of-rendering-software.md.txt).

   - [Determine if your Looker instance can accommodate the Looker Action Hub](https://docs.cloud.google.com/looker/docs/action-hub.md.txt#considerations_for_customer-hosted_instances).

2. [Enable secure database access](https://docs.cloud.google.com/looker/docs/enabling-secure-db-access.md.txt).

3. [Configure your database for Looker](https://docs.cloud.google.com/looker/docs/dialects.md.txt).

4. [Connect Looker to your database](https://docs.cloud.google.com/looker/docs/connecting-to-your-db.md.txt).

5. [Test your database connectivity](https://docs.cloud.google.com/looker/docs/testing-db-connectivity.md.txt).

6. [Configure Looker sign-in options](https://docs.cloud.google.com/looker/docs/getting-started-with-users.md.txt).

Once your instance is set up, you're ready to [get started with development](https://docs.cloud.google.com/looker/docs/data-modeling.md.txt).

## Features that require additional configuration

The following Looker features require additional configuration or software to use:

| Feature | Additional configuration or alternative |
|---|---|
| [Paper Size](https://docs.cloud.google.com/looker/docs/scheduling-and-sending-dashboards.md.txt#paper_size) | [Install Chromium renderer](https://docs.cloud.google.com/looker/docs/installation-of-rendering-software.md.txt#chromium) |
| [Expand tables](https://docs.cloud.google.com/looker/docs/scheduling-and-sending-dashboards.md.txt#expand_tables_to_show_all_rows) | [Install Chromium renderer](https://docs.cloud.google.com/looker/docs/installation-of-rendering-software.md.txt#chromium) |
| [Sending, scheduling, downloading](https://docs.cloud.google.com/looker/docs/managing-business-user-features.md.txt): - Dashboards in PDF or Visualization format - Looks in Visualization or HTML format - Explores in PNG (Image of Visualization) or HTML format | [Install Chromium renderer](https://docs.cloud.google.com/looker/docs/installation-of-rendering-software.md.txt#chromium) |
| [Downloading custom visualizations](https://docs.cloud.google.com/looker/docs/admin-panel-platform-visualizations.md.txt) | [Install Chromium renderer](https://docs.cloud.google.com/looker/docs/installation-of-rendering-software.md.txt#chromium) |
| Maintenance tasks: - Updating an instance to a new Looker release - Auto-provisioning a new Looker instance - Moving to a new host - Clustering - Configuration management - Java memory settings - Archiving log files - Restoring backups - Migrating Looker backend database to MySQL - Migrating to AES-256 encryption - Changing Looker's encryption keys - Enabling Redis cache | [Self-manage](https://docs.cloud.google.com/looker/docs/managing-customer-hosted-deployment.md.txt) |
| [Elite System Activity](https://docs.cloud.google.com/looker/docs/elite-system-activity.md.txt) | [Set up a read replica of the Looker backend database](https://docs.cloud.google.com/looker/docs/system-activity-read-replica-db.md.txt) |
| [Looker Action Hub](https://docs.cloud.google.com/looker/docs/action-hub.md.txt) | To address the potential issue of the Looker Action Hub not being able to communicate with the Looker instance, Looker admins can implement one of the [following solutions](https://docs.cloud.google.com/looker/docs/action-hub.md.txt#considerations_for_customer-hosted_instances). The appropriate solution or combination of solutions will depend on the architecture of the Looker instance: 1. Enable the `public_host_url` license feature 2. Allowlist the egress IP address for the Looker Action Hub 3. Set up a customer-hosted action hub server |
| Unpackaged JDBC drivers | [Install JDBC driver](https://docs.cloud.google.com/looker/docs/unpackaged-jdbc-drivers.md.txt) |
| Load Assets from CDN | Enable the [**Load Assets from CDN** admin setting](https://docs.cloud.google.com/looker/docs/admin-panel-general-settings.md.txt#load_assets_from_cdn) to load assets from the CDN |
| Enabling secure database access | If your customer-hosted Looker instance is not on the same private network as its connected database, be sure to secure your data as well, perhaps using one of the following options: 1. [Configure an IP address allowlist.](https://docs.cloud.google.com/looker/docs/enabling-secure-db-access.md.txt#option_1_ip_address_allowlist) Add to the allowlist the IP address or addresses where your Looker instance is hosted 2. [Configure SSL encryption](https://docs.cloud.google.com/looker/docs/enabling-secure-db-access.md.txt#option_2_ssl_encryption) 3. Configure an [SSH tunnel](https://docs.cloud.google.com/looker/docs/enabling-secure-db-access.md.txt#option_3_ssh_tunnel) |
| Create a backup of a Looker instance | [Generate a keystore-independent backup](https://docs.cloud.google.com/looker/docs/creating-backups.md.txt#generating_a_keystore-independent_backup) |
| [Installing tools from the Looker Marketplace](https://docs.cloud.google.com/looker/docs/marketplace.md.txt#installing_a_tool_from_the_marketplace) | [Set up a shared (network) file system](https://docs.cloud.google.com/looker/docs/clustering-looker.md.txt#shared_file_system) |
| [Auto Install assets from the Looker Marketplace / API Explorer](https://docs.cloud.google.com/looker/docs/admin-panel-platform-marketplace.md.txt#auto_install) | If you are installing the API Explorer on a customer-hosted Looker instance, for users to view API examples, the server running the Looker instance must be configured to access the public internet server running at the URL `https://githubusercontent.com`. |
| Upgrading from OpenJDK 8 to OpenJDK 11 | [Manual upgrade](https://docs.cloud.google.com/looker/docs/upgrading-to-openjdk-11-customer-hosted-instance.md.txt) |
| Upgrading from OpenJDK 11 to OpenJDK 21 | [Manual upgrade](https://docs.cloud.google.com/looker/docs/upgrading-to-openjdk-21-customer-hosted-instance.md.txt) |
| Allowing Looker Support to access a customer-hosted deployment | [Allowlist the IP address for Looker Support](https://docs.cloud.google.com/looker/docs/support-access-customer-hosted-deployment.md.txt) |
| Git security sandboxing for SSH connections | To opt in to the Git CLI security sandboxing enhancement (planned to be available starting in release 26.10), install the [`proot` package](https://proot-me.github.io/) on the host machine running the Looker instance. Looker projects that use HTTPS connections are not affected. If `proot` is not installed, SSH-connected Git operations will still execute successfully but will not have sandboxing active. |