Use case · Product managers

DigUp for product managers

Specs, FigJam exports, and customer calls scatter. DigUp’s EmbeddingGemma 2 index finds the decision trail on your disk.

On-device flowSchematic: DigUp uses EmbeddingGemma 2 for Product managers 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
Where did we write the non-goal?PRD PDF/docx searchOpen at passage/page
User interview clip about onboardingAudio/video momentsJump near quote
Competitive screenshot setImage embeddingsDescribe the UI
Ship week laptop thrashSchedule indexing hoursBattery guide

Numbered checklist

  1. Install DigUp; index Product / Research / Demos locally.
  2. Allow ~865 MB EmbeddingGemma 2 first run.
  3. Search outcome language (“reduce time-to-value”), not only ticket IDs.
  4. Cross-link engineering code: search when needed.
  5. Read multimodal guide for modality matrix.

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