AllSource Core, Query Service, Prime, Hosted, and MCP Explained

AllSource has five product layers with different jobs:

• AllSource Core stores durable application events.
• AllSource Query Service serves HTTP, realtime, analytics, and projection reads.
• AllSource Prime derives durable agent memory.
• Hosted AllSource operates tenant-scoped infrastructure.
• AllSource MCP connectors expose event or memory operations as tools.

Calling every layer “AllSource memory” hides important boundaries. Calling every tool “the AllSource MCP server” merges two registries. This guide gives each layer one name and one job.

Product map

Applications ── HTTP / WebSocket / SDK ── Query Service ── AllSource Core
Hosted control plane ── auth / tenancy / billing ────────────────┘
AI agents ── MCP client ── Prime or event-store connector ───────┘

Core is durable record. Query Service supplies tenant-scoped read shapes from that record. Prime derives agent context. Hosted services supply public operating boundary. Connectors transport calls; none stores an independent copy of event database.

AllSource Core: store

Direct answer: AllSource Core is a Rust event-store database for ordered, immutable application events, replay, projections, and point-in-time inspection.

Core owns

• event ingestion and ordered streams;
• CRC32-checked WAL recovery;
• configurable fsync;
• Parquet persistence;
• indexed reads and projections;
• replay and historical reconstruction.

Core does not own

• hosted account, tenant, or billing workflows;
• agent-memory ranking;
• public multi-tenant authentication;
• MCP client configuration.

Use Core directly inside trusted infrastructure or embed it in Rust. External hosted clients should use the authenticated public gateway rather than exposing Core.

Read how AllSource Core works for storage-path detail.

AllSource Query Service: read

Direct answer: AllSource Query Service is a stateless Elixir/Phoenix read plane over Core. It separates four consumption paths:

• tenant-scoped HTTP queries and projection state;
• Phoenix Channel event and projection updates at /ws;
• Core-backed and locally computed analytics endpoints;
• rebuildable per-tenant projections and replay jobs.

Query Service keeps ETS caches and read models, not durable source data. Core remains source of truth, so Query Service state can be rebuilt after restart.

Read Query Service read paths for interfaces and boundaries.

AllSource Prime: remember

Direct answer: AllSource Prime is the agent-memory engine. It combines graph relationships, vector retrieval, temporal context, a compressed index, and source-event provenance.

Prime exists because an indexed event read and a useful memory recall are not the same operation. Hybrid recall can include embedding work, vector search, graph traversal, temporal scoring, and response assembly. Core's published 11.9μs p99 indexed-read result does not measure that complete path.

Prime owns

• prime_* memory tools;
• graph nodes and edges;
• vector indexes;
• temporal and hybrid retrieval;
• evidence linking recalled context to source events.

Prime does not own

• application event ingestion as a whole;
• billing plans;
• the 55-tool event-store MCP registry;
• a universal latency guarantee.

Read AllSource Prime for current installation and operating modes.

Hosted AllSource: operate

Direct answer: Hosted AllSource is the managed route to Core and related services. It supplies tenant provisioning, authentication, quotas, billing, and public API access.

Tenant events and operational metadata remain in Core system streams. Query Service keeps only rebuildable caches and read models.

Hosted use begins with a 14-day trial. Paid GBP prices come from the live billing catalog; hardcoded articles are not the charging source of truth. There is no permanent free hosted plan. Self-hosted community software is the free route.

Read hosted pricing for live offers.

AllSource MCP connectors: connect

Direct answer: AllSource MCP connectors are local tool interfaces for MCP-capable clients. Event-store MCP and Prime MCP are separate.

Tool count follows connector configuration. A plus-sign suffix is imprecise. “73 Prime tools” is wrong. Adding both registries together is also wrong because clients see separate servers with separate jobs.

Stable event-store connector 0.22.0 supports local or self-hosted Core but does not send the Authorization header needed by the hosted gateway. Hosted event-store MCP requires the 0.23.0 fix to be released. The hosted REST API remains the stable public route meanwhile.

Read the event-store MCP release guide and Prime MCP guide separately.

Where do Chronis and solution pages fit?

Chronis is an agent-native task tracker built on the AllSource event model. It is a reference application and CLI, not another database layer.

Audit, analytics, financial-services, IoT, SaaS, and quant pages describe workloads using Core durability and Query Service read paths. They are solution routes, not new storage engines.

Which layer should I start with?

For the short canonical definition and name disambiguation, use What is AllSource Event Store?.