Overview
Choose the environment for your XPLG deployment: Docker, Kubernetes, VM, AWS, Azure, Google Cloud or XPLG SaaS.
What you will do: pick one deployment environment and open its guide.
All environments run the same products and accept the same licenses. The choice is about where the data lives, who operates the nodes and how you want to pay.
Choose by situation
- A first try on a laptop or test server — Docker.
- A cluster managed like the rest of your platform — Kubernetes (Helm).
- A classic install on Linux hosts you manage — Virtual machine and bare metal.
- Deploy in your AWS account and pay on the AWS bill — AWS Marketplace.
- Deploy in your Azure subscription and pay on the Azure bill — Azure Marketplace.
- Deploy in your Google Cloud project and pay on the Google Cloud bill — Google Cloud Marketplace.
- Nothing to install or operate — XPLG SaaS.
What is common to every environment
- Topology. A deployment is one or more nodes. Nodes can form a cluster. Agents and proxies/gateways forward data from the places where it is produced.
- Storage. Nodes keep hot data for direct querying, a persistent queue for data in flight and an archive/cold tier for full-fidelity copies in low-cost storage.
- Registration. Every deployment is registered in dock once, then licensed and tracked from the Deployments page.
- Sizing. Read Sizing and capacity planning before you commit to node sizes.
Mixing environments
You can run production on Kubernetes, non-production on Docker and keep an evaluation in SaaS. Each is a separate deployment with its own license; the workspace shows them side by side.
Next: Docker
