About AllSource
Durable event history for applications. Evidence-backed memory for agents.
AllSource exists because the data layer underneath modern applications — and especially agentic ones — often treats history as secondary. Current-state systems can preserve history, but teams commonly add audit tables, change-data capture, or logs after the primary model is designed. Time-travel debugging then spans several systems. Agents have to recover context on every invocation.
AllSource Core is the focused answer: append-only events as source of truth, projections for derived state, and point-in-time inspection from one ordered history. It is written in Rust and persists accepted event data through a CRC32-checked WAL and Parquet files. Published performance numbers describe specific Core benchmark paths, not every hosted request or memory-recall operation.
Around Core sit three named layers. Prime derives graph, vector, and temporal agent memory. Hosted AllSource handles tenant provisioning, authentication, quotas, billing, and public API access. Separate MCP connectors expose event-store or Prime operations to compatible agents. Chronis is a reference task-tracking application, not another database. Community components are Apache-2.0; designated enterprise features use BSL 1.1.
What we believe
Events, not rows
Mutable rows lose history. AllSource records every state change as an immutable event, derives current state by projection, and lets you reconstruct any past moment with a single `as_of` query.
Core IS the database
No second database to keep in sync. Core owns event and operational-metadata durability through its WAL and Parquet storage, with DashMap-backed reads. Current services require no PostgreSQL instance.
Built for agents
AI agents need persistent memory beyond a context window. A default tenant connector exposes 55 MCP tools for durable history; fleet operators can enable 73 with administrative controls.