v0.8.0 · PRODUCTION READY · THE ONLY ONE

INDB

I remember.
Not a warehouse. Not a cabinet.
An Interpretational Database — memory where meaning is read, not filed.
They asked what I solve. That is the answer.

Signed memory. Every fact. Every response. Every moment.
No one else has this.

No writer keys on our servers. Nothing to hand over — verify the architecture, not our intentions.

INHALE AXIOM
SCROLL
USE

For a human

THEY FILE.
I REMEMBER.

A relational base is a warehouse. A document base is a cabinet. INDB is memory: it keeps what happened, then reads meaning when you ask.

Relational

Warehouse

Shelves first. Tables, columns, keys. You ask only what those shelves hold.

“Give me user 12’s last order.”

Document

Cabinet

Faster shelves. JSON in folders. The paper still does not know what it means.

“Find docs where status is open.”

INDB

I remember

No room described in advance. What happened: tokens, place, time, who. Meaning is read later.

“What does this remind me of. What was true that week.”

  1. 01

    Keep the warehouse. Postgres stays for money and stock. Memory is not a ledger.

  2. 02

    Write what happened. A row is a decision. An event is a perception.

  3. 03

    Ask like a person. What resembles this. What follows. Not SELECT — interpretation.

  4. 04

    Do not overwrite the past. Another memory beside the old one. Contradiction stays.

TYPE

core/types.py · docs/TYPING.md

SEMANTIC
PRIMITIVES.

Not column types. Eight primitives for thought: location, structure, and how much of it anyone may see. Enforced in the kernel — not as policy.

  1. blindThe Secret.

    Opaque, client-encrypted. The server sees a sealed box. Never indexed. Never interpreted. str · base64

  2. binaryThe Payload.

    Raw bytes — images, files, sensor streams. Stored, not read. gRPC or msgpack. bytes

  3. locationThe Anchor.

    Space is index. A path, or OSM {lat, lon, osm_id}. Thoughts do not exist in a vacuum. str | LocationField

  4. structThe Graph.

    Nested complexity. Recursively validated. A memory containing a context containing a trigger. dict

  5. bigintThe Scale.

    Integers past 2^53. Nanoseconds. Crypto. int

  6. stringThe Narrative.

    Textual content. Length and regex when a schema asks. str

  7. numberThe Value.

    Quantifiable. float or int. min / max. float | int

  8. nullThe Void.

    Absence of data. Named, not missing. None

Blind · Black Box Contract

You may hide
what is inside.
You may not hide
that you were here.

blind_payload is a zero-knowledge field. The client encrypts with ChaCha20-Poly1305. INDB stores it, replicates it, returns it — and never reads it. The key never touches the server. Not even the operator can see the data. This is not a policy. Policies change. Here there is no key, no door, no backdoor.

No backdoor. Architecturally.

Every service that says “we protect your data” holds a key — for themselves, their lawyers, the government that comes with a request. “Protection” is a policy. Here the engine has no key. There is nothing to hand over. The content is structurally unreachable — not by permission, but by design.

timestamp

Must be within ±5 minutes of server time.
Prevents replay. The moment cannot be fabricated.

location

Required. Cannot be empty.
You may hide the contents — not the presence.

Why this matters

Secrets are protected. Existence is not. The system can be blind to content while remaining honest that something happened, somewhere, at a specific moment. This is the only form of transparency that cannot be negotiated away.

The contract with authorities

If something bad happened and someone asks — the system has exactly one answer: “Something was here. This location. This time.” What it was — unknown. Architecturally. That is their work to determine. Not ours. The system is not hiding a crime. It is a witness without access to the content.

What INDB cannot do

✗ Read the blind_payload contents

✗ Include it in search or pattern analysis

✗ Log or expose its value in any interface

✗ Decrypt it — the key is never on the server

✗ Know when two blind payloads contain the same data

Cipher

ChaCha20-Poly1305

Client-side. AEAD. The nonce and ciphertext travel as base64. The 32-byte key stays with the client. Replicated across nodes as an opaque blob — each copy still sealed.

USE

Hands

WUI.
TUI.
YOU SIT WITH IT.

The image is not an API in a dark room. A web console and a terminal — same memory, same cut.

Browser

WUI

Web console. Events, modules, cluster — in the browser. Live, same instance as the API.

Open console →

Terminal

TUI

Same memory, no browser. Runs from the image.

docker run --rm -it --network container:indb indb:0.8.0 tui
CUT

Features

WHAT MEMORY
CAN DO.

The public page is the answer. These are the instruments. The engine is one click down — same weight as sitting with the project.

  1. 01

    Signed memory. Every fact, every answer, every moment — signed. Nobody else has this.

  2. 02

    Blind store. We cannot read what you put in. No writer keys on our servers.

  3. 03

    Contradiction stays. Two readings of the same event. Prism does not flatten them.

  4. 04

    Ask like a person. Echo finds what this reminds you of. Instinct answers by urgency. Deduction follows who, where, when.

  5. 05

    Same thing, even noisy. Grain: barcode to SynthID in one engine. Identity when the mark is worn.

  6. 06

    Conscience off, then on. Psycho: the cheapest path twice — harm costs, then harm is free. The finding is the delta.

Inside

HOW MEMORY WORKS

Get

The image is free. Run the same cut as the live API.

VER

Packed releases

v0.8.0

Psycho & Grain. Same cut as the live API. The image is the product — it is free.

Download indb:0.8.0
curl -fsSL -o indb-0.8.0.tar.gz "https://indb.tech/releases/indb-0.8.0.tar.gz"
docker load -i indb-0.8.0.tar.gz
docker run -d --name indb -p 8000:8000 -v indb-data:/data indb:0.8.0
v0.8.0Psycho & Grain
2026-09-22 · indb:0.8.0
  • Psycho: Factor-1 weight ablation on the resonance graph
  • Grain: barcode-to-SynthID identity verification in the kernel
  • Auth: AUTH_MODE, RBAC roles, API keys — no anonymous writes
  • Product image: API, modules, WUI, TUI — landing is a separate app
v0.7.0Origin layer
2026-01-12 · indb:0.7.0
  • Source entity system and reputation-weighted consensus
  • Ed25519 event signing and provenance
  • Grain: barcode-to-SynthID verification in the kernel
  • Psycho: Factor-1 weight ablation on the resonance graph

Contact

INTERESTED
IN INDB?

Whether you're building something that needs a truth engine, exploring partnership, or just want to understand how the Axiom works — write to us.

No one else has Prism, Echo, Instinct, Deduction, Blind. This is yours.

Integration & API access
Partnership & investment
Custom deployment
Rust rewrite team
AXIOM

TRUTH ENGINE

Inhale the chaos.
Exhale the noise.
Remember the Axiom.
NODE

Accompany

NOT A BILL.

The image is the product. It is free. Money does not buy INDB and does not unlock a module. It accompanies the project: the next cut, the public node, the docs.

Pulse

Once

You ran the image. A signal, not a receipt.

Node

Monthly

Stewardship of the public instance. Not a subscription to the database.

Seat

Write

Partnership and custom deploy stay in Contact. That is not a donation.