Use case · HR

DigUp for HR

Policy handbooks and training recordings pile up. DigUp + EmbeddingGemma 2 retrieves the page or minute — without uploading employee files to DigUp servers (there are none for search).

On-device flowSchematic: DigUp uses EmbeddingGemma 2 for HR local search
Original schematic — DigUp indexes local files with EmbeddingGemma 2 (llama.cpp).

Sourced snapshot (2026-10-15)

FactValueSource
ModelEmbeddingGemma 2 · ~740M params · ~865 MB Q8 via llama.cppGoogle AI · DigUp README
Vector space768-d shared multimodal spaceGoogle AI · DigUp README
Mac / Win·Linux0.6.1 · 0.7.0-beta.1GitHub Releases
Stars / forks~3,768 / ~254GitHub API

Pain → DigUp workflow → tip

PainDigUp + EmbeddingGemma 2 workflowTip
Remote-work clause locationPolicy PDF semantic searchOpen at page
Onboarding video chapterVideo + audio embeddingsJump near topic
Signed offer scan photoImage + OCR (Mac)Find by layout/text
ConfidentialityLocal folders onlyExclude personal drives; read privacy FAQ

Numbered checklist

  1. Coordinate with IT; DigUp indexes only selected folders after ~865 MB model install.
  2. Keep PII folders tightly scoped.
  3. Search policy language employees actually ask about.
  4. Schedule indexing off peak.
  5. Link employees to digup.run FAQ as community help — disclose not affiliated.

Why EmbeddingGemma 2 matters here

Google’s EmbeddingGemma 2 (~740M, unified 768-d multimodal space) is what DigUp runs via llama.cpp (~865 MB Q8 package). One query can rank images, PDF pages, audio windows, video frames, and optional code — see the local multimodal guide and model page. digup.run is not Google-official.

Downloads & installs

Related