KalaBodha
Sovereign Encrypted Vault

A zero-knowledge encrypted vault on your hardware, under your control — with a sovereign AI assistant that searches, reads, and writes against the vault without ever breaking the seal.

KalaBodha — a monumental vault carved into bedrock, sealed in deep red light

What is KalaBodha?

Not another AI chatbot. A sovereign vault built around one structural guarantee: your data is encrypted with keys only you hold — and everything works against that vault without ever breaking the seal.

🔒

Zero-Knowledge Vault

Your notes are encrypted with AES-256-GCM and keys only you hold. The server stores ciphertext. We cannot read your data even if we wanted to. Auto-lock, trash with restore, encrypted backups, recovery key. This is architecture, not policy.

🤖

Local AI Assistant

Chat with your vault. The assistant searches, reads, and writes your notes, runs tools, and streams answers — powered by llama.cpp on your own machine. Built and in pre-release soak. Your words never leave your hardware.

🔌

Connected Services, Not Built-ins

Chat, storage, and plans connect as MCP services — open protocol, swappable, yours. End-to-end encrypted messaging. Client-side encrypted file storage. Plans that stay yours. More services can come; the assistant stays lean.

🔄

Model-Agnostic

Any OpenAI-compatible local model, swapped without losing a byte of your data. The model is the voice — your vault is the constant. Confidential-cloud inference arrives later through zero-trust connectors. Never plain cloud APIs.

🏠

Self-Hosted & Offline

A progressive web app and local services on your hardware. No cloud required. Full offline capability. Your vault, your machine, your rules.

📚

Proof You Can Check

Every object stored with the hosted Vault API receives a signed proof certificate, verifiable offline against a published public key. Don't trust the service — verify it. No opaque model weights making decisions about your life.

How KalaBodha Compares

A new approach to personal AI — trustworthy, user-owned, and built around the vault you already have.

Traditional Approach KalaBodha
Data sovereigntyCloud-hosted dataEncrypted vault — keys only you hold.
IntelligenceModel-centric intelligenceVault-centric — your notes, your context, your keys
MemorySession-based contextYour vault compounds — notes, chats, plans persist and stay yours
ModelFixed model choiceAny OpenAI-compatible local model. Swappable.
CloudRequiredOptional — local first; confidential cloud later, zero-trust only
OfflineCloud requiredFull offline capability with a local model
Your data trains their model?Varies by providerNever — by architecture. Nothing leaves your machine.
VerifiabilityTrust the providerPublished proof key + public audit chain. Check it yourself.
CostSubscription modelFree. Your hardware, your compute.

The Architecture

The vault is the product. The assistant works against it — on your hardware. Services connect over MCP. Models are interchangeable voices; your data is the constant.

YOUR VAULT (trust anchor) Encrypted notes · keys you hold · auto-lock · backups | ASSISTANT Chat UI · tool loop · MCP client | +-----+------+ | | | CHAT STORAGE PLANS (MCP services — more can come) (E2E) (encrypted) (yours) | MODELS (your choice) llama.cpp local · LM Studio · confidential cloud later

Shipping Now

No vapor — every claim below is true of the product as it stands today.

✅

Now

Encrypted vault, local assistant, and connected services — built, tested, and in release-candidate soak.

🔎

Next

Public release — then confidential-cloud inference through zero-trust connectors, without surrendering the vault.

🎯

Then

More connected services over MCP. The assistant stays lean; the ecosystem grows.

KalaBodha is in Pre-Launch

The vault, the local assistant, and the connected services are built and in release-candidate soak. The hosted Vault API is live — its proof key and audit chain are public, so you can verify storage proofs yourself, today, without trusting the server. Public release comes next, and collaborator onboarding opens with it.

When onboarding opens, these are the areas:

TypeScript / PWA Engineers

Assistant UI, vault hardening, chat experience, mobile web

MCP Service Builders

New connected services over the Model Context Protocol

Local Inference

Model evals, packaging, LM Studio flows, performance on consumer hardware

Security Engineers

Prompt-injection defense, zero-knowledge review, protocol scrutiny

Documentation

Architecture docs, setup guides, API docs, tutorials, onboarding content

UX / Design

Interface design for everyday people, onboarding flow, brand

Until then: request early access or read the whitepaper.

Our Values

Non-negotiable. Structural, not policy.

Tech Stack

CoreTypeScript
CryptoWebCrypto AES-256-GCM
StorageIndexedDB (encrypted)
Local LLMllama.cpp / LM Studio
ServicesNode.js + MCP
AppPWA, offline-capable
CI/CDGitHub Actions
ReleasePre-launch (private)

Get Early Access

KalaBodha is in pre-launch soak. Here is what you can do today:

1

Read the Whitepaper

The architecture, the values, and the design — in full.

2

Read the Founder's Letter

Why KalaBodha exists, in the founder's own words.

3

Verify a Proof

The Vault API publishes its signing key and its audit chain. Check them yourself — no account needed.

4

Request Early Access

Tell us what you would use KalaBodha for. Invitations go out as the release graduates.

Request Early Access