Design reviews your whole team can take part in.
Writing RFCs as Markdown in a repository and reviewing them in pull requests gives you real approvals and history. It also means most of the people who should weigh in never do, and the discussion is buried once the PR is merged. Sekkei keeps the rigour and opens the door.
Where GitHub falls short for design reviews
Only engineers show up
Product, design and support rarely open a pull request. Their input arrives late, in another channel, or not at all.
Discussion ends with the merge
Once a PR is merged or closed, its comments are hard to find from the document they shaped.
Diagrams are text only
Mermaid renders in GitHub, but nobody outside engineering can edit it, and you cannot comment on a shape.
Line comments, not decisions
Pull request reviews approve a diff. They do not record what was decided, what was rejected and why.
Sekkei vs GitHub
GitHub is where code is reviewed. Required reviews, branch protection and history are excellent, and agents already open pull requests there. For the code that implements a design, keep using it.
What Sekkei does differently
Everyone can review
Product, design and engineering review the same document in the same place, with comments, suggestions and mentions.
Approvals with a decision record
Review rules and approvals like a pull request, plus decisions, reasons and rejected alternatives that stay with the document.
Visual diagrams that stay text
Draw diagrams visually; they are saved as Mermaid inside the document, so they still diff and export cleanly.
Agents with full context
Agents read the document, the review and past decisions before they propose a change, and act under their own identity.
Back to the repository
Export Markdown into your repo, and paste pull request or issue links into a document as references.
Independent of a code host
Sekkei runs on the Internet Computer, not on a cloud vendor's servers, and Enterprise teams run their own instance on canisters they control.
Move from GitHub in a few minutes
- Import the Markdown RFCs from your repository; up to 20 at once.
- Bring the open feedback from the pull request into document comments.
- Link the settled design from the pull request that implements it.
Design and decide in Sekkei, implement and review code on GitHub. Link each from the other.
GitHub alternative FAQ
Does Sekkei sync with GitHub?
Not yet. Paste a pull request or issue link and Sekkei shows it as a reference. Export documents as Markdown to commit them to a repository.
Can I keep my RFCs in Markdown?
Yes. Sekkei imports and exports Markdown, and diagrams are stored as Mermaid text.
Is it free?
Free during the beta. Beta members get their first year of Pro and Team free when paid plans start.