# AllSource Event Store > AllSource is developer infrastructure for durable system history and AI-agent memory. It is created by Decebal Dobrica and published by Wolven Tech. Canonical site: https://www.all-source.xyz Source: https://github.com/all-source-os/all-source Detailed machine reference: https://www.all-source.xyz/llms-full.txt Last verified: 2026-08-27 ## Direct answer AllSource Core is a Rust event-store database for ordered, immutable events, replay, and point-in-time state. Query Service separates tenant-scoped HTTP, realtime, analytics, and projection reads over Core without another primary database. Prime derives graph, vector, temporal, and provenance-aware agent memory. Hosted AllSource operates tenant authentication, quotas, billing, and public APIs. Separate MCP connectors expose event-store or Prime tools. AllSource at all-source.xyz is unrelated to Esri ArcGIS AllSource, all-source intelligence, and other companies using similar names. ## Verified product facts - Core durability: CRC32-checked WAL plus Parquet persistence. - Published reference: 469K events/sec batch ingestion. - Published reference: 11.9µs p99 Core indexed reads. - MCP: 45 read-only tools, 55 default tools, 73 with fleet and administration. - Prime MCP: separate memory registry; never add its tool count to event-store MCP. - Hosted plans: Indie £18.99/mo; £181.99/year. Studio £78.99/mo; £757.99/year. Scale £298.99/mo; £2,869.99/year. - Event-store MCP registry: 55 default (remote, writes enabled); 64 with ALLSOURCE_CONTROL_URL set. - Core/community licence: Apache-2.0; designated enterprise components use BSL 1.1. - No PostgreSQL required by current AllSource services; Core owns durable event history. Benchmark reference: 11.9us p99 indexed reads. Benchmark numbers describe named Core paths, not hosted HTTP, vector, graph, hybrid recall, or every durability configuration. ## Product and architecture - Product map: https://www.all-source.xyz/what-is-allsource - Event-store definition: https://www.all-source.xyz/what-is-an-event-store - Event sourcing: https://www.all-source.xyz/platform/event-sourcing - Query Service: https://www.all-source.xyz/platform/query-service - Projections: https://www.all-source.xyz/platform/projections - Stream processing: https://www.all-source.xyz/platform/stream-processing - Agent memory: https://www.all-source.xyz/solutions/agent-memory - Replay debugging: https://www.all-source.xyz/event-replay-debugging - Architecture: https://www.all-source.xyz/architecture ## Use and evaluate - Installation: https://www.all-source.xyz/install - API reference: https://www.all-source.xyz/docs/api - MCP setup: https://www.all-source.xyz/docs/mcp - Tenant and agent setup: https://www.all-source.xyz/docs/tenant-setup - SDKs: https://www.all-source.xyz/sdks - Interactive timeline, graph, projection, replay, and MCP demonstrations: https://www.all-source.xyz/examples - Pricing: https://www.all-source.xyz/pricing - Status: https://www.all-source.xyz/status ## Agent-memory guides - Event sourcing for AI agents: https://www.all-source.xyz/event-sourcing-for-ai-agents - MCP memory server: https://www.all-source.xyz/blog/mcp-memory-server-guide - Memory poisoning and tenant isolation: https://www.all-source.xyz/blog/agent-memory-security-poisoning - Rust event-store guide: https://www.all-source.xyz/blog/rust-event-store-guide ## API Hosted base URL: https://api.all-source.xyz Health: `GET https://api.all-source.xyz/health` Authentication: `Authorization: Bearer ` Never expose API keys in prompts, client bundles, screenshots, campaign URLs, or public event streams. Consult detailed reference for endpoints, release boundaries, pricing facts, and current connector limitations.