Local AI Recipes3D / Gaussian Splatting

Local Gaussian Splatting on Windows

A commercial-friendly reference route with COLMAP + gsplat, plus sparse-view and AGPL alternatives that need different licensing decisions.

Commercial reference recipe · alternatives require reviewReviewed 2026-09-26
Commercial statusgsplat is Apache-2.0. OpenSplat allows commercial use under AGPLv3. FreeSplatter adds restrictions and includes dependencies with non-commercial licenses.
HardwareTraining cost depends heavily on scene size and Gaussian count. NVIDIA CUDA remains the simplest high-performance Windows path; CPU paths can be dramatically slower.
RuntimeReference path: camera reconstruction (for example COLMAP) → Gaussian training/rasterization (for example gsplat) → PLY/SPLAT export → viewer/editor.

Gaussian Splatting is a good example of why a recipe should include the whole dependency chain. A permissive renderer does not automatically make every reconstruction model or generated asset commercially safe.

For a conservative commercial reference, AILocalabs prefers a conventional camera-reconstruction + Apache-2.0 gsplat path. Faster pose-free models are still worth exploring, but should be labeled separately.

DIY recipe

Build it yourself

  1. Capture enough overlapping views with stable exposure and limited motion blur.
  2. Recover cameras/poses with a conventional reconstruction tool when you want the clearest licensing/provenance path.
  3. Train or optimize Gaussians with gsplat or another reviewed implementation, then export PLY/SPLAT.
  4. Try FreeSplatter for sparse-view/pose-free research, but audit its restrictions and dependencies before product use.
Risks

What can go wrong

  • FreeSplatter documents additional restrictions and non-commercial third-party components.
  • OpenSplat explicitly permits commercial use, but AGPL obligations matter if you integrate it into a closed product.
  • Viewer code license and the provenance/license of generated splat data are separate questions.
  • AILocalabs should audit the exact SplatKiln production dependency chain before publishing a blanket “commercial-safe stack” claim.
AILocalabs decision

What we ship — and what we do not

SplatKiln is the packaged product direction. This recipe is the public reference map; exact SplatKiln backend provenance remains a release/audit item rather than a marketing assumption.

Recipe discussion

Tried it? Leave results, questions and improvements.

Discussion stays with this recipe so future builders can learn from it. Never post passwords, API keys, license keys or private files.

Loading discussion…

Join the discussion