This page explains how to install the Looker application for customers who are hosting anon-premisesLooker 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" deployments. Using a Looker-hosted instance greatly reduces the effort required toinstall, configure, and maintain the Looker application, because Looker handles all necessary IT functions that are related to the Looker application for you.
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 thefollowing solutions. The appropriate solution or combination of solutions will depend on the architecture of the Looker instance:
Enable thepublic_host_urllicense feature
Allowlist the egress IP address for the Looker Action Hub
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:
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 URLhttps://githubusercontent.com.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-10-24 UTC."],[],[]]
