Your team made that decision. Can anyone find out why?
Cascadras will be one place for your team's architecture decisions. Write them, review them, approve them, and find them again, across every repo. Your risk matrix and your service tiers live right beside them.
$19 per architect a month. Everyone else reads for free.
Cascadras isn't built yet. Founding seats get first access if it launches. We don't take any money now.
The problem
Decisions get made in meetings, Slack threads and pull requests. Then they get lost.
Six months later, someone asks why the system works this way. Nobody knows. The person who decided has moved on, and the reasons went with them.
Some teams keep decision records. Most keep them as markdown files spread across a dozen repos, or as wiki pages nobody can find. Free tools help you write a record. Few help your team review it, approve it, and find it again.
What Cascadras will do
Decision records. Write, review, approve and search. Every repo, one place. Start from Lee Atchison's templates, or bring your own.
Risk matrices, linked to the decisions. A risk spreadsheet gets filed away and goes stale. In Cascadras, each risk links to the decisions that create it or reduce it, and to the service it lives in.
Service tiers. Tag each service Tier 1 to Tier 4, or name your own tiers. The tier shows on every decision, every risk, and the map.
A map of who owns what. Which team owns which service, who's on call, and where the runbook is. It comes free with the records.
Your records stay yours. Git is the backend. Clone, pull and push. Export everything, any time. Already keep records in Nygard or MADR format? Cascadras will import them on day one.
Your AI tools can read them. A built-in MCP server lets Claude Code, Cursor and the rest read your decisions while they work.
Who it's for
Engineering teams of about 10 to 50 engineers. Big enough to lose track of why things were built the way they were. Too small for a heavyweight developer portal.
The price
$19 per architect a month. You pay for the people who write the records, usually one to three per team. Everyone else reads and comments for free.
From Lee Atchison
I've spent years writing and teaching about architecture decisions and risk. Cascadras would put that thinking into a tool your team uses every day. Its risk matrix is the one from Architecting for Scale.
Reserve a founding seat
Cascadras isn't built yet. Reserve a seat and you'll get first access if it launches. No payment, no card.