Using AllSource as a CMS from Claude Desktop
A walk-through of treating AllSource Prime as the memory layer for your content — drafting, editing, and querying posts entirely from a Claude Desktop conversation. The wedge isn't 'better CMS' — it's 'your CMS already lives where your agents work.'
Prime 0.21.4: text-only embeds, sync, and a Memory tab
Three shipping changes for AllSource Prime — prime_embed and prime_recall take plain text, prime-mcp can push events to your tenant Core, and the panel grew a Memory tab to show them. Install in 30 seconds.
An Agent That Provisions Its Own Persistence in One API Call
Your agent doesn't need a human to set up storage. One POST to AllSource and it has a tenant, an API key, and 100K events waiting to be written.
Write Before You Execute: Building Crash-Safe AI Agents
An agent that crashes mid-task and then re-runs can send the same email twice, create duplicate orders, or push the same commit twice. Here's a single pattern that prevents all of it.
How Agent Teams Stay in Sync with a Shared Event Stream
When multiple AI agents work on the same problem, they need a shared world model — not direct calls to each other. Here's how to build it with AllSource and chronis.
AllSource for Startups: From Local Dev to Production in 15 Minutes
The fastest path from zero to event sourcing for startups and side projects. Self-service onboard, free tier, no infrastructure to manage. Move to production when you're ready — not before.
How AllSource Core Works: WAL, Parquet, and DashMap
A deep-dive into AllSource Core's storage architecture. Write-Ahead Log with CRC32 checksums, Parquet columnar persistence, and DashMap concurrent reads. How we get 469K events/sec with zero data loss.
How to Build Audit Trails That Pass SOC2 with Event Sourcing
A practical guide to building SOC2-compliant audit trails using AllSource event sourcing. Immutable event logs, time-travel queries, and cryptographic integrity — without the compliance tax.
Event Sourcing for AI Agent Memory: A Practical Guide
How to use AllSource as durable, time-travelling memory for LLM agents. Store conversations, decisions, and context as events. Query any past state. Give agents memory that survives restarts.
Real-Time Dashboards Without ETL: Event Sourcing + Projections
How projections replace traditional ETL pipelines for real-time dashboards. AllSource event sourcing keeps materialized views in sync as events arrive — no Kafka, no Airflow, no batch jobs.
Why Your SaaS Needs Event Sourcing (Not Just a Database)
The business case for event sourcing in multi-tenant SaaS. Audit trails, tenant isolation, usage billing, and feature flags — all as a natural consequence of storing events instead of state.
Connecting to AllSource without an SDK
How to ingest, query, stream, and build projections against AllSource using only HTTP and WebSockets — no SDK required. For teams on unsupported languages or anyone who wants to understand the wire protocol.
Direct to Core, or through the gateway? Choosing your connection path
AllSource has one public front door (api.all-source.xyz) and one internal fast path (Core, reachable only inside your network). Picking the right one cuts your p99 in half — picking the wrong one either reimplements rate limits or exposes your event store to the internet.
Tiered Context Loading: Cut Agent Memory Costs by 60% Without Losing Recall
Most agent turns don't need full recall. L0/L1/L2 tiers let agent loops fetch exactly the context depth they need — from 100-token stats to full hybrid retrieval — reducing token costs while keeping accuracy where it matters.
12μs Agent Memory: How We Got There
From event store to agent memory engine in microseconds. DashMap projections, HNSW vector index, and why the storage layer matters more than the query layer.
Building Agent Memory in Rust: From Event Store to Knowledge Graph
How we built a unified agent memory engine — vectors + graph + compressed index — on top of an event store. Architecture decisions, SOLID refactoring, and why Rust was the right choice.
How a Compressed Index Doubles Cross-Domain Recall
Vector similarity finds X or Y — rarely both. A 500-token markdown index bridges the gap. Here's why, with benchmark data.
From zer0dex to AllSource: What We Learned
We analyzed zer0dex's dual-layer memory system, found the insight that matters, and built on it. Here's what we kept, what we changed, and why.
zer0dex vs AllSource: What Agent Memory Actually Needs
zer0dex proved that a compressed index doubles cross-domain recall. We took that idea, made it automatic, and added temporal reasoning. Here's the honest comparison.
Your AI Agents Need Memory, Not Just Storage
AI agents are getting smarter, but they still can't remember yesterday. Here's why temporal context is the missing piece in agentic AI.
Event Store vs Database: Choosing the Right Foundation
Databases store state. Event stores store history. Here's how to decide which foundation your application actually needs.
Temporal AI: Why Your RAG Pipeline Needs a Timeline
Vector search finds similar content. Event sourcing tracks history. Combined, they create AI that truly understands context.
Why Event Sourcing in 2026: Beyond Simple Storage
Your application needs more than a database—it needs perfect memory. Here's why event sourcing matters more than ever.
AI Agents with MCP Tools
How to let Claude and other AI agents manage your event streams autonomously.
Time-Travel Queries Explained
How to reconstruct any entity's state at any point in time with all.source.
Introducing all.source
Time-travel your data with the AI-native event store built for the future.