Juvina Light — memory for Copilot & Claude CodeFree forever. Your AI remembers.No card, no clock, no lock-out.
Nothing is ever deleted by the free tier; upgrade any time and everything the engine quietly kept comes back. Your AI bill went up. Your work didn't.Every session, your assistant is sent the same history it was sent yesterday. The same architecture notes. The same decisions. The same explanations you already paid to send once. You are not paying for new work. You are paying to say the same thing again. There is no line on the invoice that says so. And every morning it starts at zeroTwo hours explaining your codebase. Tomorrow you do it again. The code survives — git makes sure of that. The reasoning doesn't. Why you chose that approach. What you tried that failed. The constraint someone found three weeks ago that nobody wrote down. Your assistant can read every line you own. Ask it why and it has nothing. See it work before you install anythingjuvina.ai/demo — a working .NET codebase you can interrogate right now. No install, no signup, no card. Ask it:
It answers:
That sentence is in no file. Nobody wrote it down. It was constructed from decisions made in different conversations, on different days. Ask it what broke on the first smoke test. Ask it whether customers can be deleted. Then try to catch it out — that part is genuinely useful to us. Your key. Your machine. Your data.Your memories never leave your machine. There is no Juvina server for them to leave to. Model calls go straight to your own endpoint, on your own key — you pay your own token bill, under your own provider's terms. Point it at your company's Azure AI Foundry tenant and nothing crosses your own walls. We hold your email address and a licence record. That is all we could lose. What does reach your model provider: to build memory, the engine sends the content it memorises — your agent's conversation turns and your recall queries — to the endpoint you configure, for tagging, embedding and answer construction. That happens under your own account, exactly like any other call you make with that key. Setup — five clicks
Your assistant now has What you should know before you try itIt constructs — and it can construct wrong. Juvina doesn't look up stored sentences; it builds an answer from what it has. That is the whole point, and it is also the honest limit. If it gets something wrong in the demo, we'd rather you found it than didn't. Windows x64, VS Code 1.90+. Windows-first by design. Want another platform? Say so at juvina.ai — demand decides. You need an OpenAI-compatible endpoint — OpenAI, Azure OpenAI / AI Foundry, Groq, Mistral, OpenRouter, Gemini's OpenAI-compatible endpoint, or similar. It must serve both chat completions and embeddings. This powers the engine's own tagging and construction. An Anthropic key can't power the engine (different API, no embeddings) — but Claude Code itself works exactly as normal alongside it. Model notes: Free tier and ProFree forever, no card. Nothing to request from us — the only key involved is your own.
Running a team? hello@juvina.ai Built in the open, and we answerJuvina Light is young, and we are close to it. If something breaks or feels rough, tell us — hello@juvina.ai. A real person answers, and every note shapes what ships next. Technical detail — how the engine is installed and runThe extension downloads
The engine and its embedded PostgreSQL run on localhost as child processes of VS Code. An MCP endpoint at
Published by DATAVERSE CONSULTING LTD (juvina.ai). Extension: Apache 2.0. The Juvina engine is proprietary and licensed separately — see LICENSE.txt. |