The snapshot
November 10, 2026. One team, one deployment.
- 267 active operational skills, up from 45 in August. Nearly six times the library in three months, without a single documentation sprint.
- 33 internal documents ingested, up from 12. Runbooks, design docs, vendor guides and outage reviews, all searchable by section.
- 2.4 memory reads per session. Most of them happen automatically, before the agent asks.
The incident that proved it
Mid-deployment, an AI assistant went silent, with no useful error to go on.
The cause was the kind that costs an afternoon: Python was resolving through a symlinked release directory while the pipeline copied only part of the required configuration. Once found, the fix was captured as a skill.
Weeks later, a different session touched an adjacent area. The skill was already in its pre-flight briefing.
Nobody searched for it or remembered it, and the problem never got a second afternoon.
A library nobody sat down to write
The skills cover deployment recovery, Kubernetes access, certificates, Jira and agent-tool configuration, DNS and LDAP, Kafka, and CI/CD. Every one was captured at the moment a problem was solved, by the agent that solved it. That is why the library kept growing while the team was busy doing other work.
One memory, two teams, no handover
Development and operations share a single memory. Operations inherited development’s design decisions without a handover meeting. Incidents worked in operations became skills that development saw later, without anyone forwarding a thing.
Documents that find you
Ingested runbooks and guides are split into searchable sections. The relevant part surfaces during recall, so nobody has to remember which file it lives in, or that the file exists at all.
Entirely on the team’s own infrastructure
Firekeep runs on a Rancher-managed Kubernetes cluster with Redis, Neo4j, Qdrant and local Ollama inference. There are no per-token API charges, and no data leaves the building.
What ten months taught us
- The knowledge layer should outlive the tool that created it. Agents will change. What your team learned should not go with them.
- Firekeep does not replace your agent. It gives the agents you already use a shared memory and context across sessions.
- Persistent agent memory can stay inside your own infrastructure. This deployment has done exactly that since day one.