On-Premise Setup
Install Warden and run a LaserData-managed deployment on your own servers
On-Premise runs Apache Iggy on servers that you control. The LaserData control plane manages monitoring, configuration, and tasks. It uses the same management services as Managed and BYOC deployments.
The LaserData team provisions On-Premise deployments. Contact us to discuss requirements and receive the deployment configuration and Warden installation instructions.
How It Works
Use physical servers, private cloud infrastructure, or virtual machines that you control. After LaserData provisions the deployment, each node runs Iggy and Warden. Warden is the agent that manages the node and communicates with the control plane.
Architecture
Warden starts management connections outbound. Management requires no inbound firewall rule, but application clients need access to the deployment's listeners. Iggy keeps running if the control plane becomes unavailable. Pending tasks run after the connection returns.
| Direction | What Flows | Protocol |
|---|---|---|
| Node → Control Plane | Heartbeats, metrics, task results | Outbound HTTPS |
| Node ← Control Plane | Config, tasks, certificates (pulled by Warden) | Outbound HTTPS |
| Control Plane → Node | Nothing - no inbound connections | N/A |
Setup Flow
1. Contact LaserData
Ask the LaserData team to create an On-Premise deployment. Provide these details:
- The tenant, division, and environment.
- Standalone for one node, or Cluster for multiple nodes with replication.
- Hostnames, public and private IPs, and ports for each node.
- Whether the deployment needs custom key encryption or deletion protection.
2. Deployment Provisioning
LaserData creates the deployment, registers its nodes, and prepares TLS certificates and Warden credentials. The team supplies these installation materials:
- A Warden installation script or manual instructions.
- An API key and authentication token for each node's Warden agent.
- TLS certificates signed by the deployment's CA, its certificate authority.
3. Install Warden
On each node, use the installation details and credentials from LaserData:
curl -fsSL https://artifacts.laserdata.com/scripts/install.sh | sudo bash -s -- \
--api <CONTROL_PLANE_URL> \
--secret <NODE_SECRET>The script installs dependencies, downloads binaries, and checks their signatures. It then configures services and starts Warden.
For manual installation, follow the supplied instructions on each node:
- Install the system dependencies.
- Create the required directories.
- Download binaries from the LaserData CDN and make sure that their signatures are valid.
- Configure Warden with the node secret and control plane URL.
- Start the Warden service.
Warden then manages the Iggy lifecycle.
4. Verify
After Warden starts, it registers with the control plane and retrieves configuration. Open the deployment in the Console to read its status. Nodes normally report healthy within a few minutes.
Ongoing Operations
Operational changes use the task system. Warden retrieves and runs each task on the node. Failed upgrades return to the previous version automatically.
| Operation | How It Works |
|---|---|
| Configuration changes | Update via Console or API - Warden pulls and applies automatically |
| Upgrades | Trigger via Console or API - Warden downloads, verifies, and swaps binaries atomically |
| Certificate rotation | Automatic - Warden pulls new certificates before expiry |
| Monitoring | Warden pushes heartbeats, metrics, and logs to the control plane |
Adding or Removing Nodes
Contact the LaserData team to change the nodes in a deployment. The team updates the deployment configuration and supplies credentials and TLS certificates for new nodes. A deployment supports up to 100 nodes.
System Requirements
Each node needs these:
- Ubuntu 22.04 or later.
- Outbound HTTPS on port 443 to the LaserData control plane.
- Root or sudo access for installation.