The Confluence alternative built for design reviews.
Confluence is where many teams keep their pages. It is also where design docs go to die: a page gets forty comments, someone resolves them, and six months later nobody can say what was decided or why. Sekkei keeps the review, the decision and the reasoning inside the document.
Where Confluence falls short for design reviews
Decisions are not on record
In Confluence a decision exists only if someone writes it up. The discussion that led to it sits in resolved inline comments that few people ever reopen.
Sign-off lives somewhere else
Approving a page usually means a workflow app from the Marketplace, a higher plan, or a comment that says "LGTM". None of it says which version was approved.
Heavy for the work that matters
Spaces, page trees, macros and permissions make Confluence a good wiki, and slow for a five-person design review that needs to finish this week.
Agents cannot join the review
The built-in assistant can summarise and draft. Your own coding agents cannot read the discussion, propose edits under their own name or check what was already rejected.
Sekkei vs Confluence
Confluence is a mature company wiki. It handles large page trees, granular space permissions, Jira integration and a big Marketplace of apps. If your problem is finding last year's onboarding page, it does that well.
What Sekkei does differently
Decisions with reasons
Record a decision on the passage it is about, with the reason and who agreed. It stays visible after the thread is resolved and shows in the document's decision log.
Rejected ideas are remembered
Keep the alternatives you considered and why you turned them down. When someone, or an agent, proposes one again, the earlier answer is right there.
Review rules and a finish line
Request reviewers, set the rules a document must meet, and settle it when they are met. Edit it afterwards and everyone sees what changed since approval.
Diagrams you can discuss
Flowcharts, sequence and state diagrams have visual editors, and every diagram is text inside the document, so a shape can be commented on and changed through a suggestion like any sentence.
Agents as reviewers and editors
Connect Claude, Codex or Gemini through the Internet Computer MCP connector. Each agent has its own identity and role, reads the full history, and can be kept to suggestions only.
Light enough for one review
Create a document, invite the people who need to weigh in, and finish. No space to configure and no macros to learn.
Documents you can keep sovereign
Sekkei runs on the Internet Computer, not on a cloud vendor's servers, and Enterprise teams run their own instance on canisters they control. You get the independence of self-hosting without running servers.
Move from Confluence in a few minutes
- Export the Confluence pages you want to move as Word or HTML.
- Convert them to Markdown, for example with Pandoc (pandoc page.docx -o page.md).
- Import up to 20 Markdown files at a time into a Sekkei folder, then invite your team.
Many teams keep Confluence as the wiki and move design docs, RFCs and decision records to Sekkei, linking to them from the relevant Confluence space. Others move everything; folders, teams, sharing and search are all there.
Confluence alternative FAQ
Is Sekkei a free Confluence alternative?
Free during the beta. Beta members get their first year of Pro and Team free when paid plans start. AI agents never count as paid seats.
Can I import my Confluence pages?
Yes, through Markdown. Export pages from Confluence as Word or HTML, convert them to Markdown with a tool such as Pandoc, and import up to 20 files at a time. Sekkei exports back to Markdown, HTML, PDF and Word.
Does Sekkei integrate with Jira?
Not directly. Paste a Jira or GitHub link into a document and it stays a live link. Many teams record the decision in Sekkei and link it from the ticket that implements it.
Can Sekkei replace Confluence as our wiki?
It can. Spaces for each person and team, nested folders, roles, invite links and public read-only pages are built in. Where Sekkei does the most is the documents a team has to review and decide.
Is my data safe?
Sekkei runs entirely on the Internet Computer, a decentralised network, rather than on a cloud vendor's servers. Every change is recorded with who made it, and Enterprise teams run their own instance on canisters they control.