Private product showcase / Verified native database slice
DynaCapDB
A next-generation, hyper-fast, lightweight database engine. Build teeny-tiny mobile databases, hit one button, and bam: Earth-scale enterprise power with more than six familiar ways to use it, ready for the biggest data centers. Better than every other database in the world, yet still familiar.
The durable governed memory layer for the owned stack
Why this changes the game
Three reasons to care.
Fix warehouse sprawl at the root: one canonical truth with eight familiar doors instead of drifting copies.
AI-ready out of the box, with next-generation AutoIngest: explainable mappings, approvals, exact lineage, drift control, vectors, context packs, and Yodi memory.
Crash it, restart it, rebuild every view, and keep the truth intact.
Proof today
The current machine, without mythology.
The Yeho-native executable proves ordered storage, WAL recovery, checksums, atomic promotion, backup, catalog rebuild, graph and hybrid retrieval, authorized read-only SQL, governed ingestion, and tenant transfer. Yodi independently proves identical authorized memory after a full restart while other-owner and expired records never enter ranking.
Data warehouses and AI stacks copy the same truth into tables, search indexes, vector stores, graphs, memory, and training pipelines, multiplying cost, drift, access risk, and repair work.
DynaCapDB fixes warehouse sprawl at the root: store one governed record, then expose it as records, relationships, search, SQL, graphs, mindmaps, Yodi memory, or governed training without multiplying truth. AutoIngest maps new sources into that same truth with sensitive-data approvals, exact lineage, and controlled schema drift. AI capabilities are native, not bolted on after the data already drifted.
Every way in
Twelve doors. One truth underneath.
Use the shape that fits the question without copying the data into another system. Every door returns to the same records, permissions, provenance, and recovery path.
Ordered key + value
Read and write deterministic keys through the small durable core.
Canonical records
Use records, properties, provenance, lifecycle, expiration, and content references.
SQL views
Ask familiar read-only SQL questions with filters, LIKE, projection, order, count, and limits.
Text search
Find exact language across only the records the caller is allowed to see.
Vector search
Retrieve by semantic similarity after permission checks, never before them.
Time
Filter and rank memory through creation, expiration, and temporal eligibility.
Graph
Walk typed relationships without moving graph truth into a second database.
Mindmaps
Turn authorized relationships into explorable nodes, branches, and ideas.
Hybrid search
Blend text, vector, time, graph, and metadata signals into one ranked result.
Yodi memory
Build attributed context packs, traces, feedback, evaluations, and governed training manifests.
AutoIngest
Map incoming rows with approval, exact lineage, and controlled schema drift.
Backup + transfer
Back up locally or export and import a tenant as verified canonical truth.
The database landscape
Nine proven systems. One cleaner idea.
DynaCapDB studies what the strongest databases do beautifully, then carries those lessons into one small, governed engine. The goal is not to imitate nine products. It is to stop needing nine disconnected copies of the same truth.
The usual AI and data stack
A relational database, document store, cache, search engine, vector store, graph database, ingestion pipeline, and model-memory layer. Each copy adds synchronization, access, lineage, and recovery work.
The DynaCapDB shape
One canonical record can become an authorized SQL row, relationship, search result, vector match, mindmap node, Yodi memory, or governed training source. The doors multiply. The truth does not.
SQLite
Known forTiny, dependable, serverless local SQL with almost no operational weight.
The DynaCapDB answerKeep the embedded simplicity. Add durable records, edges, hybrid retrieval, AI memory, lineage, and policy around the same local truth.
FoundationDB
Known forA disciplined ordered transactional core designed to support higher-level layers.
The DynaCapDB answerKeep the small ordered foundation and layered architecture. Make records, graphs, SQL, search, memory, and governance ready-made parts instead of work every app repeats.
PostgreSQL
Known forMature relational SQL, transactions, indexes, extensibility, and a vast familiar ecosystem.
The DynaCapDB answerKeep SQL as a familiar authorized view. Let canonical records and edges remain the master copy so SQL, graph, search, and AI never become competing truths.
CockroachDB
Known forPostgreSQL-style distributed SQL, strong consistency, replication, and horizontal scale.
The DynaCapDB answerKeep the cell, shard, residency, and strong-consistency thinking, but begin as a small local engine. Physical multi-machine replication is the next execution layer, not a current claim.
MongoDB
Known forFlexible document-shaped data, friendly schema evolution, indexing, and application ergonomics.
The DynaCapDB answerKeep flexible properties. Make relationships, provenance, lifecycle, expiration, and authorization first-class so useful data never disappears inside isolated blobs.
Redis
Known forExtremely fast in-memory data structures, caching, sessions, queues, streams, and hot-path access.
The DynaCapDB answerKeep simple, fast access patterns while making durable truth the default. WAL recovery, checksums, snapshots, and rebuildable views survive beyond the cache.
Elasticsearch
Known forPowerful full-text search, filtering, relevance ranking, analytics, and retrieval ergonomics.
The DynaCapDB answerKeep the search experience. Make text, vector, time, graph, and hybrid results rebuildable views whose candidates are authorized before ranking.
Microsoft SQL Server
Known forEnterprise relational data, security, administration, auditing, backup, and operational tooling.
The DynaCapDB answerKeep governance, evidence, backup, and predictable operations explicit while owning a smaller engine whose layers can be inspected and changed together.
Azure Cosmos DB
Known forManaged global distribution, elastic partitioning, flexible records, multiple APIs, and multi-region operation.
The DynaCapDB answerKeep multi-model access, partition, cell, and residency ideas without making local use depend on a cloud service. Global transport grows from the same contracts later.
The connected stack
Nothing powerful lives alone.
Public Academy
Learn DynaCapDB from the inside.
Every public guide, field lesson, and architecture map for this system is gathered here. No membership is required to study these rooms.
DynaCapDB: records, search, SQL, and AI memory
Explore DynaCapDB's canonical records, graph and vector retrieval, read-only SQL, governed ingestion, and restart recovery. Plan a practical database source evaluation.
Open in the Academy ↗02 / Field lessonSource-code licensing for companies and government teams
A practical guide to evaluating Demon Hunter Labs source memberships: commercial and public-sector rights, team seats, release scope, and the evidence to request before adoption.
Open in the Academy ↗03 / Field lessonTesting access-controlled memory for private AI
A practical evaluation of owner filtering, expiry, restart, and source attribution in AI memory, using the bounded Yodi and DynaCapDB evidence as a starting point.
Open in the Academy ↗04 / Field lessonDynaCapDB: One Truth, Many Doors
Meet the compact data capsule that keeps durable records, graph relationships, search, AI context, and ingestion history attached to one canonical truth.
Open in the Academy ↗The door is open