Your data
SageOx stores your team's knowledge in git repos — Ledgers and Team Context. You can inspect everything we have, clone it locally, and take it with you if you leave.
It's git repos all the way down
Every piece of data SageOx stores for your team lives in a git repository:
| Repo | What it contains | Scope |
|---|---|---|
| Team Context | Conventions, decisions, discussion transcripts, distilled memory | Team-wide |
| Ledger | Code work history, commits, project-specific decisions | Per-repo |
These are real git repos. You can browse them, diff them, and git log them. There's no proprietary database behind the scenes — what you see in the repo is what we have.
Common questions
Does SageOx work with private repos?
Yes. SageOx connects to your existing git hosting (GitHub, GitLab, etc.) using the access you grant during ox init. Your source code stays where it is — SageOx reads metadata and commit history, not your codebase.
CodeDB indexes your code locally on your machine. The index lives in your local filesystem, not on SageOx servers.
Does SageOx send my code to Anthropic or OpenAI?
SageOx does not send your source code to any LLM provider.
When you use AI coworkers (like Claude Code), those sessions run through your AI provider account — the same way they would without SageOx. SageOx adds context to those sessions (Team Context, CodeDB results) but doesn't proxy or intercept the AI traffic.
SageOx uses LLMs for processing recordings (transcription, summarization, keyframe analysis) via AWS Bedrock in our own AWS account. Your code is not involved — the inputs are audio and video from discussions you record, not your source code.
Where does the data live?
| Data type | Where it lives |
|---|---|
| Your source code | Your existing git host (GitHub, GitLab, etc.) — unchanged |
| Team Context | SageOx-hosted git server (US-West-2) |
| Ledger | SageOx-hosted git server (US-West-2) |
| Recordings (audio/video) | SageOx-hosted object storage (US-West-2, AES-256 encrypted at rest) |
| CodeDB index | Your local machine only |
Team Context and Ledger repos are synced to your local filesystem via ox init. You always have a local copy.
Can I export my data?
Everything is a git repo. Clone it and you have a complete copy — full history included.
No export wizard, no CSV downloads, no waiting for a support ticket. It's git.
Can SageOx employees see my data?
SageOx infrastructure operators have access to the git servers that host your Team Context and Ledger repos, the same way any hosted git provider's operators have access to the servers hosting your repos. We don't access customer data without explicit permission, and all access is audit-logged.
We can't see your source code — it stays on your existing git host. We can't see your CodeDB index — it's local to your machine. We can't see your AI coworker sessions — those run through your AI provider.
The transparency principle
Most tools that offer "AI-powered team knowledge" are black boxes. You put data in, magic happens, and you hope the output is right.
SageOx is a git repo. You can cat every file, git log every change, and diff any two points in time. If something looks wrong, you can see exactly what changed and when.
If you decide SageOx isn't for you, git clone and walk away. Your knowledge is yours.
What's next
- Team Context — what's inside your Team Context repo and how to edit it
- Connect a repository — how SageOx connects to your code
- Security — encryption, access control, and compliance details