{"repo":"kalamdb/KalamDB","free":true,"listed":false,"github":"https://github.com/kalamdb/KalamDB","clone":"git clone https://github.com/kalamdb/KalamDB.git","description":"KalamDB — a lightweight, real-time, storage-efficient SQL database. Designed for per-user data isolation and scalable performance — ideal for the AI era.","language":"Rust","stars":49,"topics":["ai-agents","database","realtime-database","streaming","agent-memory","chat-database","multi-tenant-database","backend-as-a-service","agents","realtime"],"license":null,"category":"ai-agents","readme_excerpt":"Give AI agents one SQL tool to your app data. KalamDB is a SQL-first realtime backend for agent-native apps. Agents and frontends use the same backend directly: SQL over HTTP for reads and writes, live query rows over WebSocket for subscriptions. USER tables, auth, and EXECUTE AS USER keep access policy-scoped instead of exposing broad backend access. Official SDKs SDK Package Release Tests Downloads TypeScript / JavaScript @kalamdb/client Dart / Flutter kalam link Rust kalam-client PostgreSQL extension Docker image: jamals86/pg-kalam with pg kalam preinstalled. Frontend clients can execute SQL directly against KalamDB. You keep one SQL API plus live subscriptions instead of maintaining a custom REST or GraphQL CRUD layer for every agent workflow. One SQL Tool, Live Rows KalamDB is designed for both frontend and backend SQL execution. - Agents and workers use one SQL tool plus the current schema instead of dozens of narrow CRUD tools. - Frontends run the same backend directly for user-scoped reads, writes, and live row updates. - Queries and writes go through the HTTP SQL API; realtime subscriptions reuse the shared WebSocket connection. - Ordinary USER-table reads stay subject-scoped; privileged service, DBA, and system accounts may use explicit EXECUTE AS USER only through the role hierarchy. This is what lets chat UIs, support agents, approval flows, and other product workflows share one data plane without separate polling, sync, or fanout infrastructure. Why KalamDB - One","default_branch":null,"files":null,"tree":[],"storefront":"/r/kalamdb","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/kalamdb/KalamDB/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}