The InventDB blogTechnical articles on how the InventDB database engine, its security model and its business engine work.https://www.inventdb.com/blog.html2026-10-01T09:00:00ZInventDB Engineeringhttps://www.inventdb.com/https://www.inventdb.com/assets/brand/inventdb-icon-256.pnghttps://www.inventdb.com/blog/inside-inventdb.htmlInside InventDB: one engine from the disk to the AI2026-10-01T09:00:00Z2026-10-01T09:00:00ZThe layers of one InventDB instance, from the encrypted storage engine to the business engine, and the path one request takes through them.https://www.inventdb.com/blog/segmented-storage.htmlHow a single instance holds 250 million records2026-10-01T09:00:00Z2026-10-01T09:00:00ZEvery InventDB table is a list of 100,000-record segments. One segment takes the writes, the others are sealed, and reads skip the segments that cannot match.https://www.inventdb.com/blog/blink-trees-and-page-cache.htmlConcurrent B-link trees and one shared page cache2026-10-01T09:00:00Z2026-10-01T09:00:00ZReaders walk InventDB's B-link trees without latches, a writer latches only the leaf it changes, and one page cache shared by every tree holds the live pages.https://www.inventdb.com/blog/how-a-query-runs.htmlHow a SQL query runs in InventDB2026-10-01T09:00:00Z2026-10-01T09:00:00ZOne SELECT followed through InventDB's parser, rule-based planner and four execution paths, and how much each path reads.https://www.inventdb.com/blog/columnar-aggregates.htmlColumnar aggregates inside a JSON document database2026-10-01T09:00:00Z2026-10-01T09:00:00ZInventDB keeps records as JSON but answers aggregates from totals in its indexes and from dense, encrypted column files built for every sealed segment.https://www.inventdb.com/blog/reading-less.htmlReading less: zone maps, Bloom filters and the ORDER BY LIMIT walk2026-10-01T09:00:00Z2026-10-01T09:00:00ZBloom filters, zone maps and a k-way merge over sorted indexes let InventDB skip segments that cannot match and stop a top-N query after N rows.https://www.inventdb.com/blog/transactions-and-durability.htmlTransactions and commits that survive a crash2026-10-01T09:00:00Z2026-10-01T09:00:00ZHow an InventDB commit becomes all-or-nothing, conflict-checked and durable, and exactly which anomalies it prevents.https://www.inventdb.com/blog/crash-recovery.htmlWhat happens to your data when the power goes out2026-10-01T09:00:00Z2026-10-01T09:00:00ZThe first start after a crash, step by step: how InventDB detects it, replays committed writes and repairs only what a crash can damage.https://www.inventdb.com/blog/backups.htmlHot backups and recovery while writes continue2026-10-01T09:00:00Z2026-10-01T09:00:00ZInventDB backs up a live instance file by file to object storage in the same region, proves each backup complete, and checks it again before a restore.https://www.inventdb.com/blog/encryption-at-rest.htmlEncryption at rest that cannot be switched off2026-10-01T09:00:00Z2026-10-01T09:00:00ZEvery InventDB instance encrypts records, indexes, files and its log with AES-256-GCM, and the engine has no mode that stores data in plaintext.https://www.inventdb.com/blog/sign-in-roles-and-grants.htmlSign-in, roles and grants for people, apps and agents2026-10-01T09:00:00Z2026-10-01T09:00:00ZAn InventDB instance is its own authorization server: password sign-in for people, OAuth 2.1 with PKCE for AI agents, and one grant check for every caller.https://www.inventdb.com/blog/row-level-security.htmlRow-level security inside the database engine2026-10-01T09:00:00Z2026-10-01T09:00:00ZThe InventDB engine applies each person's row rules to every SQL query and every write, whichever interface the request came through.https://www.inventdb.com/blog/four-kinds-of-search.htmlFour kinds of search, from exact match to meaning2026-10-01T09:00:00Z2026-10-01T09:00:00ZExact, fuzzy, full-text and semantic search run inside the InventDB engine, over the same records and under the same permissions.https://www.inventdb.com/blog/embeddings-in-the-database.htmlEmbeddings computed inside the database, in pure Rust2026-10-01T09:00:00Z2026-10-01T09:00:00ZA MiniLM sentence model written out by hand in Rust runs inside the InventDB engine, with caches and HNSW graphs that make its vectors searchable.https://www.inventdb.com/blog/files-and-ocr.htmlFiles on every record, read by OCR and searchable by meaning2026-10-01T09:00:00Z2026-10-01T09:00:00ZInventDB stores files with the records they belong to, reads them with local OCR, and searches inside them by words and by meaning under each person's access rules.https://www.inventdb.com/blog/http-api.htmlOne HTTP API: REST, SQL and a live OpenAPI spec2026-10-01T09:00:00Z2026-10-01T09:00:00ZEvery InventDB instance answers HTTP itself: records over REST, reads as SQL, bulk writes, transactions, and an OpenAPI 3.1 spec it serves about itself.https://www.inventdb.com/blog/importing-data.htmlImporting CSV, JSON and spreadsheets into a live database2026-10-01T09:00:00Z2026-10-01T09:00:00ZOne parser infers column types, a preview shows what will be stored, and permissions, row rules and foreign keys are checked as records go in.https://www.inventdb.com/blog/eventing-webhooks.htmlWebhooks and a change feed from the database itself2026-10-01T09:00:00Z2026-10-01T09:00:00ZInventDB records every committed write where all writes pass, then serves the changes as a cursor feed and as signed webhooks that carry no record data.https://www.inventdb.com/blog/mcp-server.htmlAn MCP server inside the database, signed in with OAuth2026-10-01T09:00:00Z2026-10-01T09:00:00ZAn AI client signs in to InventDB as a person, works through 51 typed tools under that person's grants, and stages record changes until a commit.https://www.inventdb.com/blog/ai-agent.htmlHow the InventDB SOAR AI answers with SQL you can check2026-10-01T09:00:00Z2026-10-01T09:00:00ZThe InventDB SOAR agent answers questions by writing SQL, running it as you under your row rules, and showing the query beside the answer.https://www.inventdb.com/blog/safe-ai-changes.htmlSafe AI changes: change sets, approval and an audit log2026-10-01T09:00:00Z2026-10-01T09:00:00ZA multi-step AI change in InventDB applies as one transaction after a person approves it; MCP proposals wait for a commit that the audit log records.https://www.inventdb.com/blog/ai-gateway.htmlThe AI gateway between your instance and the model2026-10-01T09:00:00Z2026-10-01T09:00:00ZEvery AI call from InventDB SOAR passes one gateway that checks the account, enforces the monthly AI allowance, routes to Claude on Amazon Bedrock and meters tokens.https://www.inventdb.com/blog/workflows.htmlEvent-driven workflows with a person in the loop2026-10-01T09:00:00Z2026-10-01T09:00:00ZA workflow in InventDB SOAR is a fixed plan of typed steps that a trigger starts, that acts on your records, and that parks until a person decides.https://www.inventdb.com/blog/reports-and-views.htmlReports and views with SQL behind every figure2026-10-01T09:00:00Z2026-10-01T09:00:00ZAn InventDB SOAR report stores no numbers: its HTML template runs SQL under the reader's row rules every time it renders, on screen, on paper or in an email.https://www.inventdb.com/blog/sleep-and-wake.htmlIdle instances that sleep, and the energy we measure2026-10-01T09:00:00Z2026-10-01T09:00:00ZAn idle InventDB instance stops, keeps every byte of its storage and wakes on the next request. Here is the order of events and how we measure the energy.