Code, releases, wikis, and work tracking, wired into one map that stays current.
Diggy.chat is under construction. I install the crawlers for each organization on a schedule we agree, so your snapshot stays fresh. On top comes chat that can call the coding assistants you already use when you want that depth.
If this sounds interesting, you're already the right audience.
Diggy helps teams navigate and ask questions across how work really runs:
Answers draw from the systems you already run, for example:
Crawlers keep that map current. Chat sits on top so people stop living in twenty tabs.
I design and deliver production-grade crawler and connector rollouts, not experimental demos. I install and tune the crawlers for each client organization so data stays fresh on the cadence you choose.
Hands-on setup: authenticated pulls from the tools you already own, with schedules and guardrails matched to your risk profile.
One navigable map of code, releases, wikis, and tickets so teams stop rebuilding the same context in every meeting.
A conversational UI that can call coding assistants such as Cursor CLI or OpenCode. Bring your own models and policies.
A deployment your team can operate independently.
This is a one-off, fixed-scope project, with knowledge transfer at handover. Optional support can be agreed separately.
Most teams already pay for code, delivery, wiki, and work tracking tools. Diggy stitches those signals instead of inventing another island.
Crawlers run on a schedule you control so answers reflect what shipped, what broke, and what got documented last week, not a stale export.
The chat layer is built to cooperate with modern coding-agent CLIs; model choice and governance stay with you.
This is a practical integration: crawl, map, converse, without forcing one LLM story on everyone.
I'm an AI / DevOps engineer at Nokia, with a PhD in Computer Science and 15+ years of experience building and operating large-scale systems.
I've worked on telecom-grade cloud platforms, CI/CD and testing infrastructure, internal developer tooling, and AI systems applied to real production constraints.
I'm also the creator of Vivalerts, a news monitoring system that tracks and ranks emerging topics based on public discussion signals.
With Diggy.chat, I install the crawlers for each organization so internal data stays fresh on a schedule we agree, without heroic manual refreshes.
Diggy.chat is my way of bringing calm, practical automation to teams that want fewer tabs and faster answers across the tools they already run.
Pricing is project-based, not hourly. Projects typically range from €8,000 to €25,000 depending on scale and complexity. Details will be shared privately, based on scope.
The site will open soon. Stay tuned for updates.