Skip to content
Decision Log
RFC / ADR system for engineering teams

Engineering decisions
shouldn't live in Slack.

A lightweight decision log for small engineering teams. Capture the problem, options, and trade-offs behind every technical decision — with full lifecycle tracking.

Free to start · No credit card required · Log in

decision-log · dashboard
All Decisions+ New
AcceptedAdopt Postgres for analyticsMar 15
ProposedMigrate auth to OAuth 2.0Apr 2
AcceptedUse feature flags for rolloutsFeb 18
ProposedSwitch to pnpm monorepoApr 10
SupersededUse Redis for sessionsNov 5

The problem

Engineering decisions get lost

💬

1.1

Slack discussions disappear.

Teams debate architecture in threads that vanish. No trace, no reasoning, six months later.

📄

1.2

Docs become outdated.

Decisions are buried in long pages nobody revisits. The "why" is always the first casualty.

👥

1.3

New engineers lack context.

People join and can't understand why systems were built a certain way. Repeat mistakes follow.

Example record

ADR-001 — Adopt Postgres instead of DynamoDB

ADR-0012024-03-15Review: 2024-09-15
Accepted
Problem

Analytics queries are becoming complex and DynamoDB makes aggregation difficult without expensive scan operations.

Options
  1. Continue using DynamoDB
  2. Introduce Postgres for analytics
  3. Move to a data warehouse
Decision

Introduce Postgres as the analytics database while keeping DynamoDB for transactional workloads.

Trade-offs

Operational overhead increases, but querying flexibility improves significantly. Team has existing Postgres expertise.

Decision lifecycle

Track every transition

Proposed

A decision is under discussion. The team weighs in here, not in Slack.

Accepted

The team agrees. Decision finalized with a review date. Permanently recorded.

Superseded

A newer decision replaces it. Full history preserved — the reasoning survives.

How it works

Three steps to a structured decision

I

Document

Capture the problem, options considered, decision, and trade-offs. Assign a reviewer and a review date.

II

Discuss

Comments thread directly on the record — no switching tools, no context lost to Slack.

III

Track the lifecycle

Proposed → Accepted or Superseded. Tags, review dates, full-text search.

FAQ

Common questions

What is an Architecture Decision Record (ADR)?

An ADR captures an important technical decision along with its context and consequences — the problem, options considered, the decision made, and the known trade-offs. Decision Log gives every ADR a permanent, structured home with a full lifecycle.

How is this different from Confluence or Notion?

Decision Log is purpose-built for engineering decisions. It enforces an ADR structure, tracks lifecycle states (Proposed → Accepted → Superseded), integrates with GitHub PRs, and surfaces analytics on review coverage. Confluence and Notion are general-purpose — decision context inevitably gets buried.

Does it integrate with GitHub?

Yes. Connect via a GitHub App and Decision Log posts a status check on PRs that touch architectural files (Dockerfile, schema.sql, terraform, etc.). The check blocks merge until a linked decision is Accepted. Patterns are fully configurable.

What do Proposed, Accepted, and Superseded mean?

Proposed means the decision is under discussion. Accepted means the team has agreed and it's final. Superseded means a newer decision replaced it — the original record is preserved so the reasoning survives even after the technology changes.

How many decisions can I log for free?

The free plan includes up to 25 decisions and 1 workspace — enough to get started and build the habit. Paid plans remove all limits.

Build a memory for your
engineering decisions.

Stop losing important technical decisions in Slack threads and outdated documents.

Start for free →No credit card required