For solo developers, teams and whole companies

Explain it once. Every AI knows it.

cachly keeps what you explain to your AI in every session. Claude Code, Cursor, Copilot and Windsurf read your rules, decisions and solved bugs: for you alone, for your whole team and for every team in your company. Servers in Germany, with SSO and a DPA for companies.

npx @cachly-dev/mcp-server@latest autopilot

Servers in the EU · one command, restart your editor, done · 1 project free

Claude Code: two commands — see setup

#1 on LoCoMo in the OmniMemEval comparison, 90.71 points
Monday · You figure it outsolved by you
> deploy the api
✗ no space left on device
… you dig in, you find the cause
✓ Pull the finished image from the registry instead of building on the server
↳ cachly: saved as experience
Thursday · Your AI already knowsright first time
> deploy the api
⚠ Experience from Monday: building on the server stops when the disk is full
✓ I'll pull the finished image from the registry.
✓ deploy:api running

Sound familiar?

Six scenes from every week with an AI in your editor

  1. Every sessionThe first half hour of every session> Again: Postgres, no ORM, tests live in /spec

    You explain how the project is built. You explained it yesterday, and the day before.

    With cachly: Your AI starts with what matters, no lecture.

  2. PostgreSQLThe migration that hangs in productionERROR: CREATE INDEX CONCURRENTLY cannot run inside a transaction block

    Last month an index locked the orders table for four minutes. You learned: CONCURRENTLY, in its own migration, outside a transaction. Today your AI puts it back into the regular migration, and the deploy fails.

    With cachly: It knows your rule before it writes the migration.

  3. ArchitectureThe decision you already madeAI: I'll build a separate service with a queue for this.

    Three months ago you decided against microservices: too much ops work for four people. The reasoning sits in a Slack thread. On the next feature your AI proposes a separate service again.

    With cachly: The decision comes back with its reason, before anyone builds the service.

  4. StripeThe webhook that returns 400 againNo signatures found matching the expected signature for payload

    Stripe checks the signature against the raw body. Your framework had already parsed it as JSON: two days of digging. On the new endpoint your AI builds in the same bug.

    With cachly: It knows: pass the body through raw, before any JSON parser.

  5. /compactAfter /compact, it's goneAI: Let's catch the redirect in the middleware.

    That the middleware can't handle the login redirect was in the conversation. Then it got summarized. Now your AI suggests exactly that path again.

    With cachly: The fix lives outside the conversation and comes back with the next prompt.

  6. TeamYour colleague hit this last monthFATAL: sorry, too many clients already

    It took them a day: every serverless function opened its own pool, only PgBouncer in front fixed it. The fix is in their chat history. Your AI starts from scratch.

    With cachly: What one person solves, everyone's AI knows.

You're not alone. Developers write this in public:

Quotes from public posts, linked to the source. Not cachly customers.

Compared with Claude Code and ChatGPT

Claude and ChatGPT keep your preferences. cachly keeps your project's experience.

That works well for rules and preferences. cachly holds what your project has been through: decisions with their reason, solved bugs, the traps you already hit. For you, your team and every team in your company.

Claude CodeCLAUDE.md and auto memoryChatGPTMemorycachly
Where it worksOnly in Claude CodeOnly in ChatGPTClaude Code, Cursor, Copilot, Windsurf, Codex, Gemini CLI and JetBrains
On your second machineCLAUDE.md via git, auto memory stays on one machineIn your ChatGPT accountIn your project, on every machine
For your teamCLAUDE.md via git, if someone maintains itJust for youShared, with a name on every fix, and roles
What it keepsRules you write, notes Claude takesWhat ChatGPT knows about youFixes with the cause, the dead ends and the command that worked, plus your git history
When your AI sees itAt the start of every sessionWhen ChatGPT finds it relevantWith every prompt, only what matches (automatic in Claude Code)
After /compactFiles come back, the conversation only as a summary–Back with the next prompt
Where it livesOn your machineAt OpenAIOn servers in Germany

As of 5 November 2026, based on the Claude Code docs and OpenAI's Memory FAQ.

Your knowledge stays current

When you find something better, your AI relearns.

You replace an old solution with a better one. From now on your AI works with the new one and knows why it changed. The old one stays visible as history, pointing to the new one.

old solution
build on the server
Reasonbuilding on the server stops when the disk is full
✓ new solution
Pull the finished image from the registry

Your head start from day one

Your first day with cachly starts with your whole project history.

One command reads your Git history and turns every fix, every revert and every decision into experience. From then on it grows with every commit and every CI run. You just work — the notes write themselves.

  • From your Git historyfixes, reverts, decisions.
  • From every new commitautomatically, through a Git hook.
  • From your CIwhich step was red and what turned it green.

Your team

Your team's experience. In every AI you use.

Tomorrow your solution is in your teammates' briefing, with your name on it. New people start with everything you've learned together. When several AIs work on the same project, you see where they disagree at a glance.

Your name on your solution.Roles: read, write, manage.A log of who changed what.

You stay in control

You decide. Your AI sticks to it.

Saved means saved.

When your AI says “got it”, cachly checks the proof. If it's missing, your AI fixes that before you read the answer.

AI“got it”
cachlychecks the proof · missing → fixes it
AI✓ saved
  • Your keys stay yours.

    API keys and passwords in known formats are redacted before anything is stored.

  • Experience stays information.

    Injected knowledge reaches your AI clearly marked as data.

  • More room for your work.

    Your AI loads 27 core tools instead of 124. That leaves more context for your code.

  • Your data is stored in Germany.

    Servers and all stored data are in Germany (Hetzner). Web and API traffic passes through Cloudflare's network, where the encrypted connection terminates.

Start with one project. Grow with your team.

Free
€0
500 recalls a month included (a recall = your AI asks its Brain)
Projects
1
Storage
25 MB
one project, everything included
Solo
€19 / month
€15 / month billed yearly
Projects
3
Storage
200 MB
for one person with several projects
Try 7 days free →
Teamrecommended
€49 / month
€39 / month billed yearly
Projects
10
Storage
900 MB
teams of up to 5, everything included
Try 7 days free →
Business
€199 / month
€159 / month billed yearly
Projects
25
Storage
7 GB
companies of up to 20 people, SSO included
Try 7 days free →

7 days free with your card, then €19 a month for Solo (Team €49, Business €199). Cancel before day 7 and you pay nothing.

For teams shipping AI code: “done” means exit 0.

The verification process we use to build cachly itself is available as a package.

→ Ask about the Proof package

Questions

Which tools does cachly work with?

One command sets up Claude Code, Cursor, Windsurf, GitHub Copilot and Continue. There are also extensions for VS Code and IntelliJ. Automatic context on every question runs in Claude Code today.

What does cachly keep?

Decisions with the reasoning behind them, fixes for recurring problems with the context that made them work, and the instructions your team keeps giving. cachly also learns from your Git history and your CI.

I work alone. What does cachly do for me?

Your project stops forgetting between sessions. A fix you found months ago comes back as soon as the question fits: in a new session, after /compact, on another machine or in another editor. You don't write the notes yourself. cachly learns from your Git history and from what your AI records. 1 project is free.

Does cachly replace my AI coding assistant?

It works alongside it. Claude Code, Cursor, Copilot or Windsurf stay your tools; cachly gives them the experience of your project.

What happens when my storage is full?

First, cachly clears older versions that have already been replaced. Your current lessons stay. Before space runs low, you get an email.

What do I need to do for my AI to use cachly?

Run one command. It sets up the connection and writes the instructions for your AI along with it.

Does cachly replace CLAUDE.md?

No. Rules like "we use pnpm" stay in CLAUDE.md, which Claude Code reads at every start. cachly holds experience: what went wrong, why, and what worked then. Your AI gets only the part that matches the question at hand.

What can cachly do that Claude's or ChatGPT's memory can't?

Claude Code's auto memory stays on one machine and works only in Claude Code. ChatGPT remembers what it knows about you, in ChatGPT. cachly keeps the fixes from your project, in every editor with MCP, on every machine and for your whole team, on servers in Germany.

What happens after /compact?

Claude Code summarizes the conversation, and details that only lived there get lost. cachly keeps lessons outside the conversation. The first prompt after /compact gets the matching ones back.

What does it cost, and do I need a card?

Free costs €0: 1 project and 500 recalls a month (a recall = your AI asks its Brain), no card needed. Every paid plan starts with 7 days free, and for that you need a card. After that you pay automatically: Solo €19, Team €49, Business €199 a month. Cancel before day 7 and you pay nothing.

Your project remembers what your AI forgets.

npx @cachly-dev/mcp-server@latest autopilot
Start free