Your data
SageOx stores your team's content in git repos — Ledgers and Team Context. You can inspect the customer content we store, clone it locally, and take it with you if you leave.
Data sovereignty
Your data belongs to you, in formats your tools can actually read. SageOx stores customer content in standard git repos — no proprietary export format and no lock-in.
- You own it. Clone the repo and you hold a complete copy, full history included.
- You can see it. Every customer-content file is readable and every change is in
git log. - It's versioned. Git tracks every change, so you can diff any two points in time and audit exactly what moved.
- Your AI coworkers can consume it. Git, Markdown, and standard media files work with tools beyond SageOx. Your data feeds your tools directly — not just ours.
This is a deliberate bet: the tools people keep are the ones whose data stays available to them and to the AI coworkers working on their behalf.
It's git repos all the way down
All customer content SageOx stores for your team lives in a git repository:
| Repo | What it contains | Scope |
|---|---|---|
| Team Context | Conventions, decisions, discussions, discussion recordings, transcripts, distilled memory | Team-wide |
| Ledger | Code work history, commits, session records, project-specific decisions | Per-repo |
These are real git repos. You can browse them, diff them, and git log them. A git checkout contains all customer content, including audio recordings. Only rebuildable caches and operational state such as permissions and settings live outside these repositories.
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) |
| Discussion recordings (audio/video) | Team Context git repository on the SageOx-hosted git server (us-west-2) |
| 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?
All customer content is in git repos. Your Team Context and Ledger checkouts give you a complete copy — recordings and full history included.
Repeat that for each Ledger you want to back up. No export wizard, no CSV downloads, no waiting for a support ticket. It's git. We will keep improving the checkout and portability experience over time.
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 don't proxy or inspect the live traffic between your AI coworker and your provider. Session records you capture live in your Ledger and have the same access controls as its other customer content.
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 customer content lives in git repos. 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, make a git checkout and walk away. Your data 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