taisce.
What can remember — and prove it forgot?
Memory for your AI agents. Your agent tells Taisce what happened; later it asks a question and gets back facts, each with the exact words it came from and when it was true. When someone asks to be forgotten, you get a count of what is left, and it is zero.
The turn is stored and acknowledged at once. Nothing waits for a model.
Memory that shows its work.
Four things your agent gets that a pile of stored text can't give it. How it works →
Answers from things, not text search
It finds the people and things your question names and follows what is known about them, so answers stay fast as memory grows.
anchors → factsKnows when something was true
Every fact has a time. When something changes, the old fact is kept as history instead of being overwritten.
valid from · known fromShows its evidence
Every fact points at the exact words in the exact message it came from, so you can always check it.
evidence.quoteJust PostgreSQL
No vector database, graph engine or queue to run. One database to operate and back up, on your own infrastructure.
docker compose upOne memory, start to finish.
Saving is instant; learning happens in the background. A freshness check tells your agent how far behind its memory is.
docker compose upStarts PostgreSQL and the service, and prints your first API key.Your agent sends what happened
A turn is saved straight away and you get its position back. Saving never waits for a model, so memory never slows your agent down.
POST /v1/observationsTaisce turns it into facts
In the background, a model reads each message and pulls out facts. Every fact keeps the exact words it came from, or it is thrown away.
stored → formedAsk, and get facts with their words
A question starts at the people and things it names and follows the facts around them. You get each fact with the quote behind it.
POST /v1/recallsForget someone, and see the proof
Erase a person and Taisce removes everything derived from what they said, then counts what is left. The count you get back is zero.
POST /v1/erasuresPlug it into what you already use.
Adapters add memory to your agent framework in a few lines. Before each answer they fetch what's known; after, they save the turn. Every adapter passes the same test suite.
taisce-agent-framework · taisce-langgraphRead the guide →.NETMicrosoft Agent FrameworkTaisce.AgentFrameworkRead the guide →JavaSpring AI · LangChain4jtaisce-spring-ai · taisce-langchain4jRead the guide →MCPClaude Code and other coding agentsPOST /mcpRead the guide →HTTPAny language, plain JSON over HTTP/v1/…Read the guide →CLIProjects, keys, health and the audit logtaisceRead the guide →From a first example to the last index.
Examples
Short recipes: remember a preference, answer with evidence, forget a person.
architectureHow it is built
Saving, learning, recalling and forgetting, step by step, and how it is secured.
postgresqlThe database layer
Tables, roles, concurrency, indexes and query plans.
referenceEvery line, generated
Every package, function, test, table and migration, straight from the code.
The people building Taisce.
Built by Ensera and shaped by everyone who sends a fix, a test, a page of documentation or a good question. Your name belongs here too: add it with your first pull request.
