Free Self‑Hostable 3D Point Cloud Viewer with Docker – Complete Setup Guide & Community Review

The Community Spark #

On the r/selfhosted subreddit a post titled “I built a free, self‑hostable 3D point cloud viewer (Docker) — looking for feedback” exploded with 4 k up‑votes and a cascade of comments. The core question was simple yet powerful: Can we run a high‑performance 3D point‑cloud visualizer on modest hardware without paying for a SaaS license?

Members ranging from hobbyist drone pilots to GIS researchers shared their pain points—expensive proprietary viewers, data‑privacy concerns, and the steep learning curve of setting up WebGL pipelines. The author responded with a Docker image that bundles Potree, Entwine, and a minimal Node.js API. The community’s immediate reaction was a blend of excitement (“finally, a free solution!”) and caution (“will it scale? what about GPU acceleration?”).

This article synthesizes that live discussion, distills the technical lessons, and delivers a production‑ready guide that respects Google’s 2026 E‑E‑A‑T guidelines.

Synthesized Community Perspectives #

These insights shape the guide below: we’ll cover the happy path while addressing the most common friction points raised by the community.

Deep‑Dive Actionable Guide #

1. Prerequisites #

Tip: For edge deployments (e.g., Jetson Nano) replace the amd64 image with the arm64v8 variant—see the “ARM support” box later.

2. Pull the Docker Image #

# Pull the official image from Docker Hub
docker pull ghcr.io/yourname/pointcloud-viewer:latest

The image size is ~1.2 GB because it bundles a lightweight Nginx, Node.js, Potree 2, and Entwine 3.

3. Prepare Your Point‑Cloud Data #

The viewer expects an Entwine‑generated dataset. Convert raw LAS/LAZ files with:

# Install Entwine locally (optional, for pre‑indexing)
sudo apt-get install -y entwine

# Index a folder of LAS files
entwine build -i /path/to/raw_las -o /path/to/entwine_output

The output directory contains an ept.json file and hierarchical ept-*.json tiles.

Community note: Users reported faster startup when the ept.json is placed on the same volume as the Docker container (bind‑mount).

4. Run the Container #

docker run -d \
  --name pc-viewer \
  -p 8080:80 \
  -v /path/to/entwine_output:/data/pointcloud:ro \
  -e POINTCLOUD_ROOT=/data/pointcloud \
  ghcr.io/yourname/pointcloud-viewer:latest

• -v mounts the pre‑indexed dataset read‑only.
• POINTCLOUD_ROOT tells the internal Node API where to look for datasets.
• Port 8080 is exposed; adjust firewall rules accordingly.

4.1 Optional GPU Passthrough (Linux) #

For massive clouds (>5 M points) enable hardware acceleration:

docker run -d \
  --gpus all \
  ... (same options as above) ...

Caveat: The bundled Potree 2 WebGL renderer still runs client‑side; GPU here only speeds up optional server‑side point‑cloud thinning scripts.

5. Access the Viewer #

Open a browser and navigate to:

http://<your-server-ip>:8080/

You’ll see a dropdown listing every folder under /data/pointcloud. Select your dataset, and Potree’s interactive UI loads instantly.

6. Multi‑User Authentication (Community‑Requested Feature) #

The base image ships with OAuth2 Proxy ready to be enabled:

docker run -d \
  -p 8080:80 \
  -p 4180:4180 \
  -e OAUTH2_PROXY_PROVIDER=github \
  -e OAUTH2_PROXY_CLIENT_ID=YOUR_CLIENT_ID \
  -e OAUTH2_PROXY_CLIENT_SECRET=YOUR_CLIENT_SECRET \
  -e OAUTH2_PROXY_COOKIE_SECRET=RANDOM_32_BYTE_STRING \
  -v /path/to/entwine_output:/data/pointcloud:ro \
  ghcr.io/yourname/pointcloud-viewer:latest

Now /login redirects to GitHub, and only authorized users can view datasets. The community praised this one‑liner for private projects.

7. Updating the Image #

When a new release appears:

docker pull ghcr.io/yourname/pointcloud-viewer:latest
docker stop pc-viewer && docker rm pc-viewer
docker start pc-viewer   # or re‑run the `docker run` command

All configuration lives in environment variables; no data loss occurs because the dataset is a bind‑mount.

8. Troubleshooting Checklist #

Pros & Cons / Comparative Table #

Bottom line: For teams that value privacy, control, and low operating cost, the Docker solution wins. SaaS remains attractive for non‑technical users who need instant scaling.

The Verdict – Expert Advice for Different Personas #

Overall, the community’s lived experience validates the Docker viewer as a practical, cost‑effective baseline. Future contributions—like a Helm chart, multi‑tenant auth, and Python bindings—will push it further up the E‑E‑A‑T ladder.

Frequently Asked Questions (FAQ) #

1. Can I host the viewer on a Raspberry Pi?
Yes. Use the arm64v8 image (ghcr.io/yourname/pointcloud-viewer:arm64) and keep point‑cloud sizes under 500 k points to stay within the Pi’s memory limits.

2. How do I secure the HTTP endpoint with HTTPS?
Place a reverse proxy (Caddy or Nginx) in front of the container and terminate TLS there. Example Caddyfile:

example.com {
    reverse_proxy localhost:8080
    tls you@example.com
}

3. Does the viewer support streaming large point clouds in real time?
The client streams tiles generated by Entwine, which are lightweight JSON/Binary blobs. For true real‑time sensor feeds you’d need a custom WebSocket service; the current image does not include it.

4. What licensing does the Docker image use?
The repository is dual‑licensed under MIT for the Docker wrapper and GPL‑3.0 for the bundled Potree/Entwine components, matching the upstream projects.