Timeline Knowledge Graph System

LLMs

A knowledge-base system that runs on your own computer: upload documents and it extracts entities such as people, organisations and events, together with facts about them. Every fact records two times, when it became true in the real world and when the system learned of it, so you can ask dated questions and get answers with the source passage. You bring it up with Docker Compose, the database and administrator passwords are generated at random by a script, and the first start creates the administrator and closes open registration. Derived from a frozen snapshot of an open-source project under the Apache-2.0 licence; the delivery adds an orchestration file that builds from source, a step that creates the administrator, a password generation script and a quick-start guide in Traditional Chinese.

Subscribe & download See how to start

SubscriptionUS$49 per month

Last run2026-11-02

In practice

Readiness3 / 5

What you need

Few changes needed4 / 5

Who it is for

Individuals and small teams who want to organise company or project documents on their own machine and trace facts by date.

How to start

$ sh scripts/quickstart/init-env.sh
$ docker compose up -d

Browse the files

Files in the product repository at the pinned commit. A few house files are left out of the zip.

File overview915 paths

▸assets1

banner.webp

▸crates430

utopia-cli/
utopia-core/
utopia-extract/
utopia-ingest/
utopia-llm/
utopia-reason/
utopia-search/
utopia-server/
utopia-store/

▸docker2

Dockerfile
init-app-role.sh

▸docs80

decisions/
design/
pipeline.md

▸migrations104

0001_core.sql
0002_ingest.sql
0003_graph.sql
0004_ontology.sql
0005_resolution.sql
0006_semantic_layer.sql
0007_audit.sql
0008_conversations.sql
0009_alerts.sql
0010_least_privilege_role.sql
…

▸scripts89

bench/
e2e_type_drift.mjs
e2e_type_drift.sh
quickstart/
smoke.sh
star-history.mjs

▸web176

DESIGN.md
components.json
index.html
package.json
pnpm-lock.yaml
public/
scripts/
src/
tests/
tsconfig.json
…

▫ATTRIBUTION.md

▫CODE_OF_CONDUCT.md

▫CODE_OF_CONDUCT.zh-CN.md

▫CONTRIBUTING.md

▫CONTRIBUTING.zh-CN.md

▫Cargo.lock

▫Cargo.toml

▫LICENSE

▫LICENSE-99LL.md

▫PRODUCT.md

▫QUICKSTART.md

▫README.md

▫README.zh-CN.md

▫SECURITY.md

▫SECURITY.upstream.md

▫SECURITY.zh-CN.md

▫delivery-manifest.txt

▫docker-compose.build.yml

▫docker-compose.yml

▫Config and hidden files 14

Latest passing run

Clone → Checkout → Toolchain → Build images → Admin login and registration closed

Pre-purchase Disclosure

What you are buying

A self-hosted timeline knowledge base: upload documents and it extracts people, organisations and events; every fact records when it became true and when the system learned of it, so you can ask dated questions and get answers with the source passage. You bring it up with Docker Compose, and the first start creates the administrator automatically.

Derived from an open-source project under the Apache-2.0 licence, and not the original project itself. Our work: an orchestration file, a step that creates the administrator, a password generation script and a quick-start guide in Traditional Chinese.

Delivery is a frozen snapshot: one zip, taken from the product repository at revision 5553cd5.

Known limitations

The service listens only on port 1516 of the local machine 127.0.0.1, over plain HTTP; TLS and opening it to others are yours to bring
The interface is in English and Simplified Chinese only, with no Traditional Chinese
Extracting documents and answering questions needs a chat model and an embedding model that you connect yourself, and none is included in the delivery
Until the model endpoints are set, the system cannot yet extract documents or answer questions
Registration is closed at start-up, and other users have to be opened up by the administrator
While the interface loads fonts, the browser connects to Google Fonts
The database password applies only when the database is first created, and a later change to .env is not synchronised
A backup has to take the database, the data directory and .env together, and without all three it cannot be fully restored
The data lives in Docker named volumes, and docker compose down -v deletes all documents and settings
The first start builds the image from source, fetching from registries, apt and package repositories during that time
Pinned to the delivered snapshot; it does not follow upstream.

The liability cap, the scope of what is promised and the statutory floor are governed by the Terms of Service.

Vetting record

Everything below was checked against the pinned commit 7ecf991. Every verdict carries its full reasoning, an evidence link and the checker; failures are published, not hidden — do not take our word for it, verify it yourself.

5 PASS0 WARN0 FAIL

Source ReviewPASS

Execution surface of the delivery reviewed item by item. Our own additions were read line by line: docker-compose.yml (the web port is bound to 127.0.0.1 only; the database port is not exposed; it refuses to start when any database or application password is missing; the data and the database use named volumes; the application connects with a restricted database role), scripts/quickstart/init-env.sh (openssl generates random values, .env is mode 600, an existing .env is not overwritten), scripts/quickstart/bootstrap-admin.sh (it creates the administrator first, then closes open registration and reads it back to confirm) and docker/Dockerfile (read line by line). The upstream Rust and front-end sources were not read file by file; the basis is the Apache-2.0 licence and container isolation.

Script SafetyPASS

The scripts on the buyer’s delivery path were each inspected: init-env.sh and bootstrap-admin.sh are ours (read line by line; quotes, backslashes and whitespace in the administrator credentials are refused before they go into JSON); the build goes through docker/Dockerfile (read line by line: front end and back end are built in separate stages, apt installs only ca-certificates, curl and poppler, with no download piped straight into a shell).

RecencyPASS

This product is a frozen snapshot and does not follow upstream: the upstream source is pinned to the main-line revision taken on the day the product repository was created (see the evidence link), and the product repository is that snapshot plus our own commits.

LicensePASS

SPDX:LicenseRef-99LL-Product

Upstream LICENSE was checked (the evidence link points at the file itself at the pinned version and matches the copy inside the product repository): the Apache License 2.0 text, with the copyright holder DeepLethe Contributors named in the closing part of the licence file. It allows commercial use, modification, derivative works, redistribution and sale; the duties are to keep the licence text and copyright notice and to mark modified files (LICENSE and ATTRIBUTION.md ship in the zip); upstream has no NOTICE file. The decision does not rest on GitHub’s licence field. For the product as a whole the 99LL product licence template is attached: upstream’s LICENSE is kept as it is and LICENSE-99LL.md is added as the sale and liability terms for the part we built, with spdx recorded as LicenseRef-99LL-Product.

Dependency LicensesPASS

This records the declared side, not a scan result: the Rust dependencies are declared in Cargo.toml and locked by Cargo.lock, the front end is declared in web/package.json and locked by web/pnpm-lock.yaml, and the packages themselves are fetched from their own repositories when the buyer builds; the base images and system packages come from a registry and apt. These dependency trees were not scanned package by package for licences. Upstream has no submodule and no third-party dataset was copied in (see ATTRIBUTION.md).