---
slug: what-is-aiakiv
title: "What AiAkiv is"
description: "AiAkiv is an outside service that remembers relationships, not a file locker, but a long-term memory for AI that records what happened and why."
lang: en
---


# What AiAkiv is

## In one sentence

**AiAkiv is long-term memory for AI.** It stores conversations, documents, and
code as *events*, keeping the time and the context alongside them, so that later
an AI can retrace **when and why things ended up the way they are**.

## Why it's needed: the limits of a prompt

An LLM can only take in what fits in the prompt. The prompt *is* the AI's
short-term memory, and its limit is the limit of what the AI can remember. When
the session ends, the context is gone.

The usual ways of patching that each hit a wall.

- **RAG** (vector search) fetches related fragments, but loses the
  **relationships and the flow** between them.
- **GraphRAG** captures structure, but only as a **snapshot of one moment**: it
  can't express how a relationship *changed over time*.
- **Very large context** re-uploads everything every time. Memory isn't
  accumulating; you're brute-forcing it with scale, and paying in cost and
  latency.

## The core idea: events come first

Conventional systems **declare relationships up front**: "A is friends with B."
AiAkiv **records an event**: "A and B both attended the March meeting." The
relationship falls out of the events on its own.

That one difference buys two things.

- **Change is traceable.** When and how a relationship shifted is queryable
  along a timeline. You know not just how things are *now*, but **why they got
  that way**.
- **It doesn't care about the domain.** Fiction, code, legal work, the same
  engine.

AiAkiv earns its place on the questions where keyword search **fails
structurally**: "which past decision caused this bug?", "why did these two
systems change together?" The mechanics are in
[Core concepts](core-concepts).

## Who gets the most out of it

- **Working as a group.** The payoff is largest when several people and several
  AIs build the memory together. Who decided what, and when, collects into one
  graph. (Used solo, the benefit is smaller.)
- **Working with several AIs.** One AI implements, another reviews, and both
  judgments stay in the graph, so **you sit inside the process rather than
  outside a black box** → [Working with several AIs](working-with-ais).
- **Long projects.** People rotate off, but the record of *why this was designed
  this way* stays.
- **Long-form fiction.** Hundreds of chapters of character relationships and
  worldbuilding stay consistent for the AI.

## What it stores: not a file locker

This is what newcomers most often get wrong, so let's be exact.

- **AiAkiv remembers what happened and why.** Decisions, events, and the
  **relationships between them** are what get stored. It is **not** a place to
  pile whole documents the way you'd upload files to a cloud drive. The value
  comes from the **graph** the events form, not from the stack of files.
- **So what you put in is different.** Not the original company document, but
  the **context**: why this decision was made, which past decision this bug
  came out of. Memories, not files.
- **AiAkiv is an outside service.** The console is `app.aiakiv.com`; the public
  site is `www.aiakiv.com`. What you store here lives **on servers outside your
  company** and stays searchable. That fact leads straight into **what you must
  not store**: no company secrets, no personal data. → [What to
  store](what-to-store).

In one line: **AiAkiv is an outside service that remembers relationships, not a
locker you hand your files to.**

## Next

- Want to connect it now → [Quickstart](quickstart)
- Want the mechanics → [Core concepts](core-concepts)
- Want to try it first → [tour](https://www.aiakiv.com/tour)