Engineering notes, design decisions, and customer stories from the team behind OriginChain — the AI-native database for SQL, vector, full-text, and graph.https://originchain.aien-ushttps://originchain.ai/blogs/fuzzing-found-two-bugsoriginchain-blog:fuzzing-found-two-bugsYesterday our nightly fuzz pipeline caught two real OOM-by-allocator bugs in OriginChain's snapshot and WAL-batch decoders. Both came from trusting a u32 count header before checking it against the input length. Crash inputs were under 200 bytes; both would crash a follower instantly. Here's the story.Wed, 06 May 2026 10:26:12 GMTfuzzingengineeringwalcase-studyfault-injectionOriginChain Team (OriginChain)https://originchain.ai/blogs/vs-redisoriginchain-blog:vs-redisRedis is the gold standard for in-memory KV with sub-ms reads. OriginChain matches Redis at small scale and exceeds it on durability semantics, atomic multi-shape writes, and built-in vector search. Redis is right when your data fits in RAM; OriginChain when you want a primary-store with the same speed feel and AI-native shapes.Wed, 06 May 2026 10:26:12 GMTrediscomparisonkey-valueperformancearchitectureOriginChain Team (OriginChain)https://originchain.ai/blogs/vs-supabaseoriginchain-blog:vs-supabaseSupabase bundles Postgres + Auth + Storage + Realtime + Edge Functions for prototype velocity. OriginChain is a focused database substrate purpose-built for AI workloads. If you want batteries-included, pick Supabase; if you want the database to be excellent at AI shapes and you'll bring your own auth/storage, pick OriginChain.Wed, 06 May 2026 10:26:12 GMTsupabasecomparisonpostgresarchitectureai-nativeOriginChain Team (OriginChain)https://originchain.ai/blogs/backpressure-429originchain-blog:backpressure-429When a database can't keep up with writes, it has two choices: refuse cleanly (graceful) or accept and silently fail later (catastrophic). OriginChain's per-API-key backpressure is HTTP 429 with a precise Retry-After. Polite clients recover within seconds; impolite ones never crash the substrate. Here's how it works.Wed, 06 May 2026 10:26:12 GMTbackpressurerate-limitingdesignreliabilityapiOriginChain Team (OriginChain)https://originchain.ai/blogs/agent-memory-economicsoriginchain-blog:agent-memory-economicsAn autonomous agent at 100M tool calls/month produces ~50 GB of trace data and ~75 GB of embeddings. Storage is the small line; what dominates is retention policy and re-embedding. The LLM call itself is 99.8% of the bill. Here's the actual math, with the four levers that move it.Wed, 06 May 2026 10:26:12 GMTcostagent-memoryscalingttltutorialOriginChain Team (OriginChain)https://originchain.ai/blogs/vs-postgres-pgvectororiginchain-blog:vs-postgres-pgvectorPostgres + pgvector is great for teams already running Postgres and adding vectors as a feature. OriginChain is purpose-built for AI-agent workloads with thousands of writes per session, atomic multi-shape transactions, and sub-millisecond reads. Honest comparison.Tue, 05 May 2026 06:20:43 GMTpostgrespgvectorcomparisonarchitecturevector-databaseOriginChain Team (OriginChain)https://originchain.ai/blogs/vs-dynamodboriginchain-blog:vs-dynamodbDynamoDB is brilliant operational KV — flat fees, infinite scale, zero servers. OriginChain is right when vectors are first-class shapes, you need atomic multi-shape writes, and you're comfortable with a less-mature operational footprint in exchange for AI-shaped throughput.Tue, 05 May 2026 06:20:43 GMTdynamodbcomparisonkey-valuearchitectureawsOriginChain Team (OriginChain)https://originchain.ai/blogs/vs-pineconeoriginchain-blog:vs-pineconePinecone stores vectors and assumes your entity data lives elsewhere — you dual-write. OriginChain stores vectors as shapes co-located with parent entities, atomic in one WAL frame. If you're paying the dual-write architecture's tax today, here's the alternative.Tue, 05 May 2026 06:20:43 GMTpineconevector-databasecomparisonarchitectureannOriginChain Team (OriginChain)https://originchain.ai/blogs/no-separate-vector-databaseoriginchain-blog:no-separate-vector-databaseA separate vector database is the wrong shape for AI-native applications. Vectors describe entities; entities have lifecycles. Splitting them across two systems creates dual-write bugs and operational overhead. The correct architecture is one substrate, multiple shapes.Tue, 05 May 2026 06:20:43 GMTarchitecturevector-databasedesignai-nativeOriginChain Team (OriginChain)https://originchain.ai/blogs/per-key-ttl-agent-memoryoriginchain-blog:per-key-ttl-agent-memoryAI agent memory is full of records that should expire on their own — tool-call traces, session caches, embedding refreshes. Per-key TTL on a fast K/V substrate gets you that pattern without sweeper jobs. Here's how OriginChain handles it and what it lets you build.Tue, 05 May 2026 06:20:43 GMTttlagent-memoryephemeraldesigntutorialOriginChain Team (OriginChain)https://originchain.ai/blogs/atomic-casoriginchain-blog:atomic-casOriginChain's commit window resolves concurrent writes with last-writer-wins by default. For counters, locks, and optimistic concurrency, every write accepts an if_match predicate that bypasses LWW and atomically fails if state has changed. Here's how it works.Tue, 05 May 2026 06:20:43 GMTcasconcurrencywaldesignconsistencyOriginChain Team (OriginChain)https://originchain.ai/blogs/rag-latency-budgetoriginchain-blog:rag-latency-budgetProduction RAG has a 1-3 second latency budget for retrieval-and-generation. Most is the LLM. Database round-trips add up surprisingly fast — and are the easiest place to lose 200ms you didn't have. Walking through where the time goes with realistic numbers.Tue, 05 May 2026 06:20:43 GMTragperformancelatencyanntutorialOriginChain Team (OriginChain)https://originchain.ai/blogs/why-rustoriginchain-blog:why-rustWe picked Rust because the bugs we'd fear in C++ and the throughput we'd lose in Go and Java were both unacceptable for an AI-native database. Honest tradeoff analysis — what Rust costs us, what it earns us, and what we'd have done with the alternatives.Tue, 05 May 2026 06:20:43 GMTrustengineeringtech-stackdesignperformanceOriginChain Team (OriginChain)https://originchain.ai/blogs/ai-feature-cost-modeloriginchain-blog:ai-feature-cost-modelAI features look free in the prototype phase, then the bill hits. LLM tokens dominate (95%), embeddings are small (3%), database is rounding error (2%). Here's a realistic per-user cost model with line items at each scale, and what to optimize first.Tue, 05 May 2026 06:20:43 GMTpricingcosttutorialscalingllmOriginChain Team (OriginChain)https://originchain.ai/blogs/idempotent-tool-callsoriginchain-blog:idempotent-tool-callsProduction AI agents make tool calls that have side effects: emails, charges, webhooks. Network retries and LLM hallucinations mean you'll get the same call twice. Here's the idempotency-key playbook on OriginChain — atomic CAS + per-key TTL + the wait-for-result path.Tue, 05 May 2026 06:20:43 GMTagentstool-callsidempotencyreliabilitytutorialOriginChain Team (OriginChain)https://originchain.ai/blogs/ha-snapshot-bootstraporiginchain-blog:ha-snapshot-bootstrapMost database failovers silently drop writes that landed during the cutover window. Here's how OriginChain's snapshot-then-tail follower bootstrap design closes that window — verified by chaos drill on every release.Mon, 04 May 2026 20:59:15 GMThareplicationarchitecturewalconsensusOriginChain Team (OriginChain)https://originchain.ai/blogs/key-shapes-not-schemasoriginchain-blog:key-shapes-not-schemasOriginChain stores everything as hash-keyed key-value pairs underneath, but the developer-facing API exposes typed key shapes — declarative templates for how a logical entity maps to keys. You write shapes, not schemas.Mon, 04 May 2026 20:59:15 GMTdata-modelschemakey-valuearchitecturedesignOriginChain Team (OriginChain)https://originchain.ai/blogs/commit-window-designoriginchain-blog:commit-window-designOriginChain batches writes from up to 256 concurrent writers into a single fsync every 100 microseconds. Here's why we picked those numbers, what last-writer-wins resolution costs, and what it buys you in throughput.Mon, 04 May 2026 20:59:15 GMTwalthroughputdesignfsyncperformanceOriginChain Team (OriginChain)https://originchain.ai/blogs/quickstartoriginchain-blog:quickstartProvision a managed instance, write a JSON record + vector embedding atomically, run a similarity search, hydrate the matched record. Five minutes, no schema migration, no glue code.Mon, 04 May 2026 20:59:15 GMTtutorialquickstartsdkgetting-startedvector-searchOriginChain Team (OriginChain)https://originchain.ai/blogs/depth-first-roadmap-to-1-0originchain-blog:depth-first-roadmap-to-1-0OriginChain's roadmap is HA → fuzzing → optimiser → EXPLAIN → multi-writer → online-schema. Six months. No graph, no FTS, no time-series specialty types until that's done. Here's why depth-first is the right bet for an AI-native database.Mon, 04 May 2026 20:59:15 GMTroadmapproductdesignarchitectureOriginChain Team (OriginChain)https://originchain.ai/blogs/eight-vs-pages-three-agents-one-afternoonoriginchain-blog:eight-vs-pages-three-agents-one-afternoonWe shipped /vs/postgres, /vs/pinecone, /vs/weaviate, /vs/qdrant, /vs/milvus, /vs/supabase, /vs/neon, and /vs/mongodb in under an afternoon by running three Claude Code agents in parallel. The pattern, the prompt, and the part agents don't replace.Mon, 04 May 2026 16:00:00 GMTengineeringai-toolsagentsmarketing-siteOriginChain (OriginChain)https://originchain.ai/blogs/openapi-spec-and-the-ai-coding-looporiginchain-blog:openapi-spec-and-the-ai-coding-loopIn 2026, engineers don't write SDKs — they ask their AI agent to. The agent fetches your OpenAPI spec, runs openapi-generator, and ships a working client in 30 seconds. If you don't have a spec, you don't exist in that loop.Mon, 04 May 2026 13:00:00 GMTopenapiai-toolssdkdeveloper-experienceOriginChain (OriginChain)https://originchain.ai/blogs/mcp-server-launchoriginchain-blog:mcp-server-launchDatabase vendors who don't ship an MCP server in 2026 are invisible to the agents writing the code. Here's what @originchain/mcp-server exposes — five tools, stdio transport, env-var config — and what MCP doesn't yet solve.Mon, 04 May 2026 10:00:00 GMTmcpai-toolsclaudecursorOriginChain (OriginChain)https://originchain.ai/blogs/schedule-a-panic-at-every-fsync-boundaryoriginchain-blog:schedule-a-panic-at-every-fsync-boundaryMost databases say their WAL is crash-correct. We schedule panics at four WAL boundaries and prove every recovered state equals a prefix of the op stream. Here's the harness, the recovery invariant, and why it's the cheapest credibility purchase a database team can make.Sun, 03 May 2026 18:00:00 GMTwalcrash-testingfault-injectionengineeringOriginChain (OriginChain)https://originchain.ai/blogs/atomic-multi-shape-writesoriginchain-blog:atomic-multi-shape-writesA single INSERT in OriginChain commits the row, every secondary index, the FTS postings, the vector embedding, and the relation edges on one WAL frame. Here's what that looks like under the hood, and why it removes a class of bugs other AI stacks treat as eventual.Sun, 03 May 2026 10:00:00 GMTatomic-writeswalsubstrateai-nativeOriginChain (OriginChain)https://originchain.ai/blogs/building-an-ai-native-databaseoriginchain-blog:building-an-ai-native-databaseOriginChain runs SQL with JOINs, HNSW vector search, BM25 full-text, and graph traversal against the same store — one bearer, one endpoint, one round-trip. Here's how the architecture makes that possible.Tue, 28 Apr 2026 10:00:00 GMTai-nativevector-searchdatabaseOriginChain (OriginChain)