Regelwerk or Confluence?
Confluence is a workspace for knowledge and collaboration. Regelwerk is built entirely around your manual. How the two differ, and when Regelwerk fits best.
Regelwerk does less than Confluence. On purpose.
Some businesses try a wiki such as Confluence for their manual. When the same wiki also serves meetings and projects, notes soon sit next to work instructions, and your team no longer knows which page is a rule and which is just an idea.
A workspace for everything, or just your manual
- Confluence Atlassian describes Confluence (opens in a new tab) as a workspace for knowledge and collaboration: pages, whiteboards, databases, videos and slides, AI features, and connections to many other tools.
- Regelwerk Chapters and pages, a reading view, and search. Nothing more, on purpose: it only holds what someone has approved.
How your team finds an instruction in it is on the one page per topic page.
Who gets into the manual
- Confluence Everyone signs in with an Atlassian account (opens in a new tab). Whoever creates one themselves confirms an email address (opens in a new tab) for it. If your business manages the accounts, an admin creates them, and the person gets an email once their account is ready.
- Regelwerk You create accounts with a username and password. Whoever works on site or in the workshop without a company email still gets into the manual.
How that works is on the sign-in without email page.
Who may read what
- Confluence The free plan (opens in a new tab) is for up to 10 people and has no permission settings (opens in a new tab): anyone who can sign in may view, add, and edit all spaces and pages. Space and content permissions start with the Standard plan.
- Regelwerk One plan with every feature and 20 users. You assign permissions per group and chapter: read, write, publish. What someone may not read shows up neither in the table of contents nor in search.
More on the permissions per group and chapter page.
Only approved content reaches your team
In Regelwerk, every change starts as a draft. Your team keeps reading the current version until someone with the right to do so publishes the draft. Writing and publishing are two separate permissions, so responsibility for the content stays with you or the person you choose. Every publication lands in the version history, with name and date. More on the drafts and approval and version history pages.
What Regelwerk costs is on the pricing page: pricing will be announced at launch.
What the current version looks like in Regelwerk
When Regelwerk fits best
- One place for what appliesYou want a manual that holds only the rules that apply, kept apart from notes, meetings, and projects.
- A team without company emailYour people on the job site or in the workshop should get into the manual with a username and password.
- Approval before readingSomeone should check and approve every change before your team reads it.
Frequently asked questions
Can I bring over my Confluence pages?
Yes. You create chapters and pages and bring over your texts. If you like, we import your Word files, PDFs, or wiki pages for you as a paid service.
Is Regelwerk a wiki?
No. In Regelwerk, every change starts as a draft, and your team only reads the approved version.
How many users are included?
20. If your team needs more, you add further users. Every feature is included in the plan.
End the documentation nobody reads.
Join the waitlist and be the first to know when Regelwerk launches.