AllSource Event Store is developer infrastructure for durable event history and AI-agent memory. Core stores ordered events; Query Service separates HTTP, realtime, analytics, and projection reads; Prime derives agent memory; hosted services operate the stack; MCP connectors expose tools.
It is the developer product at all-source.xyz and github.com/all-source-os/all-source. It is not Esri ArcGIS AllSource, the all-source intelligence discipline, or unrelated audience-data and logistics companies using a similar name.
Product map
“AllSource” names the platform. Use the component name when describing a specific job. Core stores. Query Service reads. Prime remembers. Hosted services operate. MCP connectors expose tools.
Applications
HTTP · WebSocket · SDK
Query Service
HTTP · realtime · analytics · views
Control + agent layers
Auth · billing · Prime · MCP
AllSource Core
Immutable events · replay · state
Product boundaries
Store
Rust event-store database for ordered, immutable application events, replay, and point-in-time inspection.
Read
Stateless Elixir/Phoenix read plane that separates tenant-scoped HTTP queries, realtime channels, analytics endpoints, and rebuildable read models over Core events.
Remember
Agent-memory engine that combines graph relationships, vector retrieval, temporal context, and source-event provenance.
Operate
Managed AllSource deployment with tenant provisioning, authentication, quotas, billing, and public API access.
Connect
Tool interfaces that let MCP-capable agents use either the event store or Prime from a local stdio process.
Name disambiguation
Developer infrastructure at all-source.xyz: Core, Query Service, Prime, hosted services, and MCP connectors.
Esri desktop intelligence-analysis and geospatial software. Unrelated product.
Intelligence discipline combining multiple collection sources. Not this software.
Audience data, logistics, procurement, and contracting businesses using similar names. Unrelated.
Direct answers
AllSource Event Store is developer infrastructure for durable event history and AI-agent memory. Core stores ordered events; Query Service separates HTTP, realtime, analytics, and projection reads; Prime derives agent memory; hosted services operate the stack; MCP connectors expose tools.
Query Service is the stateless read plane over Core. It serves tenant-scoped HTTP queries, Phoenix Channel realtime streams, analytics endpoints, and rebuildable per-tenant projections without becoming another database.
No. AllSource Event Store is developer infrastructure published at all-source.xyz and github.com/all-source-os/all-source. ArcGIS AllSource is Esri intelligence-analysis software. The products are unrelated.
Core is the durable event-store database. Prime is the agent-memory engine that builds graph, vector, and temporal retrieval over event-backed memory. Prime can use Core for persistence; Core does not require Prime.
No. AllSource Core is an event store. Prime includes vector retrieval as one part of agent memory, alongside graph relationships, temporal context, and source-event provenance.
No. Core stores events and event-sourced operational metadata. Query Service derives tenant-scoped reads from Core, so current AllSource services require no PostgreSQL instance.
No. The event-store connector exposes 45 read-only tools, 55 by default, 64 with control-plane access, and 73 with system administration. Prime has a separate memory-oriented registry with 19 prime_* tools and 27 when optional inbox and hound modules are enabled.
Choose a route
