Docker is the shortest path to a running XPLG node: one container on a laptop or a server, a volume for data, and your license key as an environment variable. This is the narrative version of the Docker deploy page. Values in angle brackets are placeholders; the signed-in version renders them with your key.
Minute 0: the workspace
Create a workspace and name your company. Two things happen on their own: an evaluation license is issued to the organization, and an allocation of XMC AI tokens, the unit the AI features consume, is granted to it. Both show on your first page. Open Deployments and choose New; pick Docker. The page shows the command below with your key filled in.
Minute 2: the container
Pull the image at the version you want to run:
docker pull <xplg-image>:<version>
Run it with the console port published, a named volume for data and the key in the environment:
docker run -d --name xplg-node \ -p <console-port>:<console-port> \ -v xplg-data:<data-path> \ -e XPLG_LICENSE_KEY=<your-key> \ <xplg-image>:<version>
Two habits worth keeping from the first run: never keep data inside the container's writable layer (the volume is what survives an upgrade), and never paste the key into a shell history you share. The signed-in page gives you a copy button for a reason.
Minute 4: ready
Follow the logs until the node reports that it is listening:
docker logs -f xplg-node
Open the console on the published port:
http://localhost:<console-port>
Complete the first-run screen.
Minute 6: register
Back in dock, the deployment you created under Deployments is pending. The product calls home with the registration token that was part of the command, and the row turns active with the version and the last-seen time. If the node cannot reach dock (an air-gapped host, a strict egress policy), the same dialog offers a registration file to upload in the console instead. See Register a deployment.
Minute 8: license and usage
The evaluation license is attached to the deployment and the product accepts it; you see the license, its expiry and its units under Licenses. As data flows, Usage shows the volume per day and the AI token balance moving. That is the loop dock exists for: deploy, license, see it report in.
What next
- Move to a real environment: Kubernetes with Helm, a virtual machine, or a cloud marketplace.
- Bring in data: the product pages in the docs list sources, destinations and formats.
- Add your team under Team, and connect SSO if you have it.
Everything in angle brackets on this page is a placeholder until XPLG engineering publishes the image names, ports and variable names. The page will be updated when they are.