Deployment models

Lightup supports three deployment models: Cloud, Hybrid, and Self-hosted. The models vary in the placement of Lightup system components between the user environment and the Lightup environment. Those boundaries are shown ahead:

Cloud deployment (recommended)

The Cloud deployment model is the Lightup SaaS offering where the entire system runs in the Lightup cloud environment. Secure connectivity is established between the Lightup Cloud instance and user data sources. Each customer instance has dedicated resources (i.e., not shared with other customers).

Setup instructions are in the Lightup Cloud deployment guide.

Hybrid deployment

The Hybrid deployment model is an on-prem managed service offering. This is a split deployment where the Lightup data plane is deployed in the user environment (either a VM or a Kubernetes cluster) and the Lightup control plane is deployed in the Lightup cloud environment. Your data never leaves the user environment. Results are computed and stored by Lightup in the user environment. The control plane manages the data plane deployment for upgrades and troubleshooting.

Setup instructions are described in the Lightup Hybrid (dedicated VM) and Lightup Hybrid (existing Kubernetes cluster) deployment guides.

Self-hosted deployment

The Self-hosted deployment model is a fully on-prem offering that is operated by the user and supported by Lightup. All Lightup platform components are deployed in the user environment. Lightup has no access to the deployment. Upgrades are triggered by the user. The system is entirely contained within the security perimeter of the user. This is not an air-gapped deployment— outbound connections are required for authentication and installation of updates.

For setup instructions, see Lightup Self-hosted deployment, or (if you want to use an existing Kubernetes cluster) the Lightup Self-hosted (existing Kubernetes cluster).