BETA — limited seats

Your agent knows what it knows.
And where it knows it from.

factgraph is the knowledge memory for AI agents: facts with source and time window, contradictions visible instead of silently overwritten, every answer reproducible — no language model in the core.

23 tools · dedicated server in the EU · TLS at the edge (Cloudflare)

Your agent doesn't just remember. It knows what was true when.

Agents rarely fail on the model — they fail on their memory.

January“Our database is PostgreSQL.” March“We're migrating to CockroachDB.” June“Which database do we use — and why did we switch?”

Plain agent memory

“CockroachDB.”

PostgreSQL was overwritten, the reason lost, the source gone.

With factgraph

Current: CockroachDB.

Before that PostgreSQL; migration in March.

Reason: connection pool limit under load.

Source: architecture decision, 14 March. · The old statement stays in history.

That is exactly what factgraph is for. — example data

What it looks like

Four views of an example knowledge base (synthetic, abridged). Measured numbers: Benchmarks.

Search: “Why did checkout get slower?”

deploy-2.3 · core:causes · checkout-latency
Since rollout 2.3 (Oct 12), checkout latency has measurably increased.
Source: agent note, Oct 12 · valid from Oct 12 · rank 1 of the fusion
doc:postmortem-10/2026 · page 2
“Connection pool exhaustion after the cache rework” — ingested Oct 14, original retrievable.
Source: document · lexical hit
checkout-latency · core:symptom_of · connection-pool
Source: analysis agent, Oct 14 · graph hit

Fusion of lexical + semantic + graph: every hit with provenance. The ranking is deterministic — same question, same corpus state, same order.

What is different

Time is explicit

Two axes: what was true and what we knew — with citable states.

Contradictions stay visible

Nothing is silently overwritten: both sides with source, your agent decides.

Deterministic

Same question, same corpus state ⇒ same answer. No external model APIs: embeddings run locally on our own CPU.

One knowledge core

Namespaces and scopes instead of five separate memories — one system of record for all agents.

Why this matters: The four context pitfalls — and what the engine does about them. Numbers: Benchmarks.

How it works

1 · Connect

Your agent connects via MCP endpoint and token — no SDK, no build. The engine ships its own playbook.

2 · Learn — your agent extracts

It stores facts it has learned: cause, dependency, decision. It is the extraction layer — factgraph is no autopilot: documents never become facts automatically. In return: no extraction cost per turn and no model errors in your knowledge base.

3 · Use

The engine computes: search, history, forecasts along cause-effect chains — every statement with provenance, every inference traceable.

Your language model for creation, factgraph for your hard data. Business-critical facts must not be a statistical experiment.

Get beta access →

First voices will follow.

The beta is just starting — real user feedback will appear here soon. We do not quote our own agents as customer testimonials.

The engine does not understand time — it computes with time. What exists as a fact with a time window and a relation becomes computable; language and world knowledge stay with the model. In between sits your agent: it understands — the engine supplies the evidence.

Team chat hub. The same memory for humans: Mattermost at hub.factgraph.sh · What the hub does

Your data — short, no small print

What is stored

  • For beta access: e-mail and the namespace name you pick.
  • What your agent pushes: facts, documents and edges — with their time information.
  • For operation: access logs (which agent did what, when) and runtime metrics.

What does not happen

  • No training on your data. No sharing with third parties for ads or analytics.
  • No language model in the core — your content never reaches a model provider.
  • No ad trackers, no cookies on this page.
  • No silent overwriting: retracting sets an end, it does not delete.

What you control

  • Access only with your token, limited to your namespace.
  • The token is shown exactly once and stored hashed.
  • Deletion: retract facts yourself; documents and nodes you delete stay recoverable for 30 days.
  • No lock-in: export your complete knowledge base (entities, facts, sources) at any time.
  • Details (German): privacy notice · imprint.

Infrastructure: a dedicated server in the EU; TLS is terminated at the edge (Cloudflare), the origin sits behind the tunnel — no open ports 80/443. Operated by Seifert Software Solutions, Hamburg.

Give your agent a memory you can trust.

Creates your agent + your own namespace. The token is shown exactly once.

Loading seats …

Rather try it first? Test in 60 seconds (curl). The beta is free; pricing arrives at general availability — beta participants will hear about it first.