MULTIPLE SOURCES. ONE LOG.
Commits, incidents, decisions, and AI summaries — everything that happens on a project, in one running log. Offline-first, synced everywhere.
API service
Private
Checkout redesign
Shared
Payments
Private
GitHubmerged fix/auth-refresh-race (#482)
Paged in @dana— redis latency spike, mitigated by scaling the read replica.
Shipped the auth fix, resolved the redis incident, kept the read-replica scaling policy from today's page.
FEATURES
Summarize a busy day into one entry, or refine grammar and tone without losing your own words.
Paged in@dana— see[[ incidents ]]for context.
@mention a teammate, [[ link another drain or entry, or leave a comment anchored to the text.
Keep writing with no connection. Every device sees every entry the moment you're back online.
Each drain is its own database with its own membership rules — only the people you invite can read or write it, enforced by the database, not just the app.
FOR AGENTS
Connect Claude Code, or any MCP-compatible agent, directly to a drain. It queries the log for context before it starts — why a decision was made, what broke last time — and writes its own entries as it works, attributed and in the same timeline as everything a person typed. One durable memory, shared by every agent you run.
{
"mcpServers": {
"drains": {
"command": "npx",
"args": ["-y", "github:drains-dev/mcp"]
}
}
}queriedwhy was dynamo replaced with postgres for orders?
via mcpbumped retry backoff on the sync client, logged why
USE CASES
Just me
A personal engineering journal — why you built it that way, searchable months later.
Log pages and mitigations as they happen, next to your GitHub pushes and PRs — a clean handoff at the end of a shift.
One drain per project — replaces the scattered Slack thread nobody can find later.
Publish a read-only share link — a running changelog people can actually follow.
HOW IT WORKS
Your name and email. It becomes a deterministic color and ID that follows you everywhere.
One per project, incident, or team. Keep it private, share a link with collaborators, or publish it read-only.
Every line is its own entry, saved as you type it. GitHub activity and agent updates show up in the same place.
Your next incident review will thank you. Start logging in seconds — no configuration.
Free while we're in testing — we haven't decided on pricing yet.