all.sourceAllSourceEvent Store
Menu
Introducing AllSource Event Store

Introducing AllSource Event Store

This article introduced AllSource Event Store, a Rust event store for event sourcing, CQRS, and AI workflows. The product has expanded since publication. For current definitions and exact boundaries between Core, Prime, hosted services, and MCP connectors, start with What is AllSource Event Store?.

The history gap in current-state systems

In today's data-driven world, developers face critical challenges:

  • History becomes optional infrastructure: Current-state databases can preserve history, but teams usually add audit tables, change-data capture, or logs to do it.
  • Point-in-time reconstruction takes design work: Answering what data looked like last Tuesday requires reliable history and deterministic projections.
  • AI Integration Gap: Your data is trapped behind rigid APIs that weren't designed for autonomous workflows.

all.source tackles these challenges head-on with an event store that thinks.

What Makes all.source Different

1. Blazing Fast Performance

  • 469K events/second in the published Core batch-ingest reference
  • 11.9μs p99 in the published Core indexed-read reference
  • ~129MB binary footprint

Built in Rust with lock-free data structures and Parquet-based storage for both high-throughput ingestion and fast analytical queries.

2. Time-Travel Queries

Reconstruct any entity's state at any point in time:

# Get user state as of last Tuesday
GET /api/v1/entities/user-123/state?as_of=2026-02-04T15:00:00Z

Debug issues, audit changes, or replay historical states instantly.

3. AI-Native by Design

The default tenant MCP registry exposes 55 tools for Claude Desktop and other MCP clients. Fleet and administrative controls raise the registry to 73:

  • Query events with natural language
  • Create projections autonomously
  • Manage schemas and pipelines
  • Run analytics and correlations

Let AI agents manage your event streams.

Core Capabilities

Feature Description
Event Sourcing Immutable event logs with full audit trail
Projections 5 types including snapshots, counters, and funnels
Schema Registry Versioned schemas with evolution and compatibility
Stream Processing Filter, map, reduce, window operators
Multi-tenancy Full isolation with RBAC and quotas

Getting Started

AllSource uses an open-core model. Core and community components are Apache-2.0; designated enterprise features use BSL 1.1. Run Core locally:

# Docker
docker run -p 3900:3900 ghcr.io/all-source-os/all-source:latest
 
# Or create a hosted trial tenant
curl -X POST https://api.all-source.xyz/api/v1/onboard/start \
  -H "Content-Type: application/json" \
  -d '{"email":"you@example.com","name":"My project"}'

What's Next

This was the original roadmap at publication:

  • Vector embeddings for semantic event search
  • Real-time anomaly detection
  • Cross-tenant analytics
  • Edge deployment support

Join us in building the future of data infrastructure.

Read the current AllSource product map

Write → inspect → query

Store one real event, then query it back.

Start with hosted AllSource, or run the Apache-2.0 core on your own infrastructure. Both use the same event model and APIs.