AllSource records ordered events so teams can prove what happened, replay how state changed, give agents source-backed memory, and reconstruct financial history.
Choose by problem
01 · Prove
Record each accepted change with its actor, timestamp, entity, and metadata. Query the ordered history instead of reconstructing it from overwritten rows and scattered logs.
Use when: When someone asks what changed, who changed it, and what the system knew then.
customer.created
risk.reviewed
policy.approved
Derived result
Export the source events and reconstruct state at the review timestamp.
02 · Reproduce
Replay the exact production sequence against a fresh projection. The first divergent state gives engineers a smaller, testable explanation for a failure.
Use when: When current state shows the failure, but not the sequence that caused it.
checkout.started
payment.authorized
inventory.rejected
Derived result
Rebuild the checkout projection and compare state before and after rejection.
03 · Remember
Let an agent recall decisions across sessions while retaining the source events behind each memory. Prime derives graph, vector, and temporal context; Core can persist the record.
Use when: When an agent must remember more than the current prompt and explain where recall came from.
decision.recorded
constraint.changed
memory.recalled
Derived result
Return the relevant decision with its relationships, timestamp, and source-event trail.
04 · Reconcile
Store debits, credits, reversals, and corrections as ordered events, then derive balances in a projection. Corrections remain visible instead of replacing prior facts.
Use when: When a balance or transaction must be explainable at any point in its history.
debit.posted
fee.assessed
credit.reversed
Derived result
Replay the ledger to show when the balance moved and which event caused it.
Architecture fit
Core owns durable source history and event-sourced operational metadata. Tenant boundaries let one deployment serve multiple projects without adding a database per application.
Events and system metadata share one WAL-durable source of truth.
Separate products with tenant-scoped streams, keys, metadata, and projections.
Query Service builds tenant-scoped read models from retained Core events and rebuilds them through replay.
Connect external transport or specialist systems only when a workload explicitly needs them.
Product walkthrough
Direct answers
Core remains the durable source of truth. Query Service provides tenant-scoped HTTP queries, realtime event and projection channels, analytics endpoints, and rebuildable read models tailored to each consuming application.
AllSource is designed for audit trails, event replay and debugging, AI-agent memory with provenance, and financial transaction history. These workloads benefit from ordered, immutable events and point-in-time reconstruction.
No. AllSource Core is the database for event history and event-sourced operational metadata, including tenants, users, API keys, configuration, subscriptions, quotas, and billing state. Current AllSource services run without PostgreSQL.
AllSource Prime is the agent-memory engine. It combines graph relationships, vector retrieval, temporal context, and source-event provenance. Core is the event-store database; MCP connectors expose explicit tools to compatible agents.
Yes. Tenant-scoped streams, API keys, system metadata, and projections let one AllSource deployment isolate and serve multiple products. External databases and streaming systems are optional integrations, not prerequisites.
Next event
Use hosted services for managed operation, or run Apache-2.0 Core in your own stack.
