Skip to content
Juvina logo

Juvina

Stores codebase memories locally so AI coding assistants in your editor retain context across sessions.

Maintained

Developer toolsFor developersFree tier
juvina.ai ↗Launched on Product Hunt · Sep 7, 2026
Open juvina.aiAlternativesSet it up for my team
Juvina: data, price, alternatives
At a glancechecked Oct 30, 2026

20 linking domains

Emerging

For
developers using GitHub Copilot or Claude Code in VS Code who want memory across sessions
Activity
Maintainedsite updated 8 weeks ago
How it runs
Self-hosted
Used for
  • keep coding assistant memory across separate sessions
  • reuse past codebase context in new chats
  • reduce tokens spent re-sending repeated project context
Worth knowingcomputed from what we read · each with its source
  • Launched on Product Hunt on Sep 7, 2026Product Hunt ↗
Alternatives in Developer toolsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Juvina with

Pick up to two.

All 10 alternatives to Juvina →

All Developer tools tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Juvina for?

Sign in to leave a note
Questions this page answers
  • What is Juvina?

    Stores codebase memories locally so AI coding assistants in your editor retain context across sessions. It is listed in the Atlas under Developer tools.

  • Who is Juvina for?

    developers using GitHub Copilot or Claude Code in VS Code who want memory across sessions

  • Do people use Juvina?

    Emerging.

  • Is Juvina still maintained?

    Maintained: site updated 8 weeks ago.

  • What are alternatives to Juvina?

    In Developer tools, by use: Claude Pilot, ContextForge Memory, LinkLore, mnemo, WCP Cloud.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk