5 min read
Two ways to run keyes.ai services
The same engine — Vector, Memory, GitDB — runs as a managed service or inside your own cloud account. A short note on what each shape is for, and what's actually built.
Tag
#gitdb
7 posts tagged gitdb.
- 5 min read
Engineers leave. Source code shouldn't.
A look at real, documented cases where departing engineers walked out with the codebase — and what GitDB does to make that materially harder.
- 6 min read
GitDB vs GitHub Enterprise — what each is for
GitHub has been built for human developers for over 15 years. GitDB has been built for AI agents from day one. Both are correct designs — for different actors. A look at what each one fits.
- 5 min read
How GitDB cut our AI coding bill by 95%
A walk-through of the actual token math — where the savings come from, what they don't help with, and how I'd reproduce them in your codebase.
- 5 min read
A real day with an agent swarm on GitDB
A walk-through of four coding agents shipping a feature in parallel — what each one did, where they handed off, and what the bill looked like.
- 6 min read
Agent-to-Agent workflows in GitDB
How GitDB coordinates multi-agent code workflows without ever putting source on a developer machine — and why a database, not a filesystem, is the right substrate for it.
- 6 min read
What GitDB is, and why I built it
AI coding agents spend 60–80% of their tokens just finding things in the codebase. That's grep hell. Here's what we built underneath instead.