LixRay — Shared repository for you and every AI agent you use.

Shared repository for you and every AI agent you use.

Files and SQL tables under version control, in one open-source repo. Claude, ChatGPT, Codex, and your scripts read and write the same data.

lixray.com
homeAllDocumentsTablesHistorySOURCESSOONGoogle DriveNotion+Connect sourceAGENTSClaudeChatGPT
AllNew ▾
NameChanged by
customersYou
ordersYou
researchYou
roadmap.mdYou
budget.xlsxYou
pitch-deck.pdfYou
You changed 1 row in customers
nameplan
Acmetrial paid
KeepUndo
ClaudeChatGPTCodexand moreEvery agentClaude, ChatGPT, Codex, and any MCP client connect. Your scripts use the same SQL.
FilesMarkdown, CSV, PDFs, and spreadsheets stay files. Any agent can read them.
Database tablesCustomers, orders, runs. Agents query them with SQL.
Version controlBranch, diff, and roll back files and rows. Markdown and CSV diff row by row.
Open sourceSelf-host the Lix server, or embed Lix in your product.
Granolaand moreMount your sourcesSoonMount Drive, Notion, and Granola. Agents work from one place.

Why not Notion or GitHub?

Each covers part of it. LixRay is the only one that is open source and keeps files, database tables, and version control in one repo every agent can use.

LixRayNotionChatGPT / Claude ProjectsGitHubObsidian
Open source, self-hostable
Works with ChatGPT, Claude, and Codex
Plain files: Markdown, CSV, PDF
Database tables
Version control

Your agents can build on it

Ask an agent to build a dashboard, an app, or a workflow on your files and tables. It works on a branch, so it can try anything. Merge what works and throw away the rest. LixRay is built on , an open-source engine with one SQL API for agents and your own code.

$ npm install @lix-js/sdk
import { openLix } from "@lix-js/sdk";const lix = await openLix({  server: { url, headers },});const rows = await lix.execute(`  SELECT name, city, plan  FROM customers  ORDER BY name`);
lixray.com/acme/home
customers
namecityplan
AcmeHamburgpaid
Bluebird CaféLisbontrial
NorthwindBerlinpaid

Set url and headers using your repository connection settings.

EXAMPLES
orders→refund panel
refund-panel
Order 4821 · €39Approve
Order 4817 · €120Approve
Refund approvalsAsk an agent to build a refund panel on your orders table. It works on a branch until you merge.
support/*.md→requests
CSV export4
Dark mode2
SSO1
Feature requestsAn agent reads support emails and keeps a table of who asked for what.
cvs/*.pdf→candidates
Screen
JWATKO
Call
ML
Offer
Hiring pipelineCVs stay PDFs. An agent screens each new one into a candidates table, and your team reviews it from any AI tool.
clips/*.md→reading
Local-first softwaresync
SQLite in productiondb
Designing data appsdb
Read-later archiveClip articles as Markdown files. An agent tags them and keeps your reading list.
CHANGELOG.md→wiki/
wiki/exports.md
- Runs every night.
+ Runs every hour.
Auto-updating wikiAfter each release, an agent updates your wiki. Every edit shows up in a diff.
skills/→
refund-policy.md
release-notes.md
hiring-rubric.md
Sharing skillsWrite down how your team does a task, once. Every agent can read it.