Are your work manuals, internal policies, and past proposals scattered across shared folders and chat histories? An internal wiki tool collects this kind of internal information as pages and makes it searchable and easy to find. Also called knowledge sharing tools, they're used to keep know-how from being tied to individuals, to hand over work, and to train new hires.
This article is for people in IT, general affairs, and corporate planning who are considering introducing or switching internal wikis, and organizes 10 major products from the perspective of comparing internal wiki tools. For pricing and free-plan conditions, we list only the values written on each vendor's official website as of October 20, 2026.
Internal wiki tools differ greatly in how they count charges. Some charge per user per month, some charge a flat rate per headcount tier, and some let read-only users join free; for the same headcount, the cost can differ several times over. Along with the comparison table, we also explain these differences in how pricing is counted.
Bottom line: recommendations by goal
- If you want to start small for free: Confluence (Free is up to 10 users), Kibela (Community is up to 5 people), Qast (free plan for 10 people or fewer)
- If few people edit but many read: NotePM, Kibela. Both have allowances for adding read-only users for free
- If you have many engineers who want to write in Markdown: esa, Qiita Team, DocBase, GROWI.cloud
- If you want the wiki, tasks, and databases in one place: Notion
- If a development team will use it with Jira: Confluence
How to choose an internal wiki tool
Decide first who writes and who searches
Internal wikis are prone to "we introduced it but nobody writes" and "it's written down but nobody can find it." Before choosing, decide who writes (staff in each department, or the administrative departments) and who searches (all employees, or a specific team). The products and pricing models that suit you differ between a company where a few people write and many read, and a company where everyone writes.
Ease of writing and the editing style
Whether an internal wiki takes hold depends on how easy it is to write in. Products where you write in Markdown are easy for engineers, while a what-you-see-is-what-you-get editor suits people less familiar with IT. Some products, like DocBase, have multiple editing modes. Also check templates, editing from a smartphone, and importing existing Word files or PDFs.
Ease of search
The more pages you have, the more search quality matters. Check the accuracy of full-text search, filtering by tags and folders, searching the contents of attachments, and handling of spelling variations. More products now have a feature where you ask AI a question and it answers from the contents of the internal wiki.
Permissions and visibility
If you put HR and management information in the internal wiki too, it's important to be able to separate visibility by department or group. Check page-level permissions, sharing with guests and people outside the company, and support for SSO and IP address restrictions. In many products, SSO and audit logs are only available on higher-tier plans.
How pricing is counted
Internal wiki tools mainly count pricing in these three ways.
- Monthly fee per user: Notion, Confluence, esa, Kibela, and others
- Flat rate per headcount tier: NotePM, DocBase, Qiita Team, GROWI.cloud, and others
- Quote: Qast and others
Some products let you add read-only users for free, so estimate with separate counts of "people who edit" and "people who only read."
Migration from existing tools and export
If you already use another internal wiki, also compare how easy it is to migrate. DocBase has built-in import from esa, Qiita Team, and Kibela. To prepare for switching in the future, it's also reassuring to check whether you can export in formats such as Markdown.
Internal wiki tool comparison table
| Tool | Free plan | Paid plan (guide) | User limit | Highlights |
|---|---|---|---|---|
| Notion | Yes / up to 10 external guests; block limit for 2 or more people | Plus ¥1,650/member/month (billed annually), ¥2,000 (billed monthly) | Billed per member | Wiki, databases, and AI in one |
| Confluence | Yes / up to 10 users and 2GB | Standard from ¥850/user/month (billed monthly) | Free is 10 users | Integrates with Atlassian products such as Jira |
| NotePM | No (30-day free trial) | Plan 10 ¥5,400/month (excl. tax) | From 10 editors + 30 viewers | Read-only users free up to 3 times the number of editors |
| Kibela | Yes / up to 5 people and 4 groups | Lite ¥500/person/month (excl. tax) | Unlimited on paid plans | Discount next month for people who didn't use it |
| esa | No (free until the end of the month after next from creation) | ¥500/user/month (incl. tax) | No limit stated | Share drafts and grow them together |
| Qiita Team | No (free trial available) | Personal ¥500/month (incl. tax) to Large ¥15,300/month (incl. tax) | No headcount limit on Extra | Flat rate per headcount tier |
| DocBase | No (30-day free trial) | Starter ¥1,320/month (incl. tax, 3 people) | 1 to 30 people depending on plan; larger teams supported | Three editing modes, import from other wikis |
| GROWI.cloud | No (free trial available) | Small ¥8,000/month (excl. tax) | 30 people per app to unlimited | Fixed monthly fee, write in Markdown |
| Helpfeel Cosense | Free for personal and nonprofit use only | Business ¥1,100/person/month (incl. tax) | Unlimited members | Connects pages to each other with links |
| Qast | Yes / 10 people or fewer (no AI features) | Contact sales | Contract by number of IDs | AI search and answers, onboarding support |
Key features of each tool
Notion
A tool that brings documents, databases, and task management together in one workspace. Besides internal wikis, it's also used for project management and as a place for meeting notes. Pricing is per member: Plus is ¥1,650/month (billed annually) or ¥2,000 billed monthly. Business is ¥3,150/month (billed annually) or ¥3,800 billed monthly, and includes Notion Agent and AI Meeting Notes.
The Free plan is for individual use, and when two or more people use it, there's a limit on the number of blocks. Page history on Free is also 7 days. Because it's so flexible, note that information tends to scatter unless you decide rules for where pages go and how they're named at the start.
Confluence
Atlassian's internal wiki tool, widely used together with Jira for development teams' document management. The Free plan can be used free for up to 10 users and 2GB of storage. The paid Standard plan starts at ¥850 per user per month, and Premium starts at ¥1,640. On the official website, prices are shown as an estimate whose unit price changes with the number of users.
If the development team and other departments use the same wiki, it's easier to run if you decide how to divide spaces and design permissions first.
NotePM
A Japanese internal wiki tool with a flat monthly fee per headcount tier. The smallest, Plan 10, is ¥5,400/month (excl. tax) and covers a total of 40 people, 10 who can edit and 30 read-only users, plus 100GB of storage. Plan 25 is ¥13,500/month (excl. tax), and Plan 100 is ¥54,000/month (excl. tax). Read-only users can be added free up to 3 times the number of people who can edit.
Read-only users can search and view, but can't post or comment. It suits use where a few staff write manuals and all employees read them. There's a 30-day free trial, and you don't need to register a payment method.
Kibela
For small teams of up to 5 people, the "Community" plan lets you use some basic features free indefinitely. Paid plans are monthly per user (excl. tax): Lite ¥500, Standard ¥800, and Enterprise ¥1,500. Trials are 14 days for Lite, 1 month for Standard, and 2 months for Enterprise.
A distinctive feature is "active billing," which discounts the next month's charge for users who didn't use it, so you don't waste money on people who rarely use it. There's also an allowance for adding viewers for free. It also supports importing PDF, Word, and PowerPoint files.
esa
Pricing is a single rate of ¥500/user/month (incl. tax), which includes all features. You can try it free until the end of the month after next from the month you create your team. Upload capacity for articles and attachments is effectively unlimited. There's also a free plan for educational institutions.
You can share articles in progress as "WIP," and it assumes everyone grows articles together in a collaborative editor. It suits teams that want to build a culture of casually putting information out there rather than managing finished documents.
Qiita Team
An internal information sharing service run by Qiita, the engineering community. It's based on Qiita's editor, and you can also write in Markdown. It's a flat rate per headcount tier, with monthly fees (incl. tax) of Personal (1 person) ¥500, Micro (up to 3 people) ¥1,520, Small (up to 7 people) ¥4,900, Medium (up to 10 people) ¥7,050, and Large (up to 17 people) ¥15,300. Extra, for businesses, has no headcount limit: ¥15,300 plus ¥720 per person from the 18th person on.
All plans have unlimited posts and 30GB of file storage. IP address restrictions and invoice payment are Extra-only features. If you have more than 100 users, pricing is by quote.
DocBase
A Japanese internal wiki and knowledge sharing tool whose distinctive feature is that you can write in three editing modes. Pricing is a flat rate per headcount tier: Personal (1 person) ¥550/month, Starter (3 people) ¥1,320/month, Basic (10 people) ¥4,950/month, and Regular (30 people) ¥11,000/month (all incl. tax). Larger headcounts are also supported.
There's a 30-day free trial, and you can try all features without registering a credit card. It states clearly that data you enter is not used to train AI, and SSO and IP restrictions are available with the Security Pack. It has built-in import from esa, Qiita Team, and Kibela.
GROWI.cloud
A cloud-based internal wiki where you can write in Markdown. It uses a fixed monthly fee rather than usage-based billing, so the price doesn't change up to each plan's headcount limit. Small is ¥8,000/month (excl. tax) for up to 30 people per app, and Medium is ¥20,000/month (excl. tax) for up to 100 people per app with 3 apps as standard.
There are also plans that support building it in an on-premises environment, and an academic plan for educational institutions.
Helpfeel Cosense
An internal wiki designed to expand knowledge by connecting pages to each other with links. The free plan is limited to personal and nonprofit use. BUSINESS, for companies, is ¥1,100/person/month (incl. tax), with unlimited pages and members. You can try the first 100 pages free, and the free allowance grows by 100 pages for every 10 members you invite, up to 300 pages.
You need to get used to the idea of connecting information through keyword links rather than sorting it into folders. It suits teams that want to accumulate notes on ideas and discussions.
Qast
A knowledge platform with a strong focus on AI search and answers. There are three pricing plans, including Professional and Professional Plus; prices are not published and you need to contact sales. The initial setup fee includes support for initial design and for getting it adopted internally, and for deployments of 500 IDs or more, a dedicated consultant works alongside you.
Teams of 10 or fewer can use the free plan, but it doesn't include AI features. Payment is by bank transfer. It suits companies that have introduced an internal wiki before without it taking hold, and want support with operations as well.
Internal wiki pricing varies greatly depending on "how it's counted"
When comparing the cost of internal wiki tools, you need to estimate not just with the monthly unit price but with the counting methods aligned. For example, consider a company with "30 people who edit and 90 people who only read."
- Products priced per user per month: in principle, all 120 people are billed. Check whether there's a free allowance for viewers
- Products where viewers are free: 120 people may be able to use it with a tier for the 30 editors. NotePM lets you add read-only users free up to 3 times the number of editors
- Products with a flat rate per headcount tier: exceeding a tier's headcount limit moves you up to the next plan, so if you expect to grow, estimate with the plan one level up
Also, with products where AI features, SSO, and audit logs are limited to higher-tier plans, choosing a plan by working back from the features you need can make costs higher than expected. During the free trial, check which plan includes the features you'll actually use.
Tips for getting an internal wiki to take hold
A common failure when introducing an internal wiki tool is that just putting the tool in place doesn't increase the number of people who write. Deciding these four things at the start makes it easier to take hold.
- Decide what to publish first: start with information many people read, such as frequently asked internal questions, onboarding procedures, and work manuals
- Decide who writes and who updates: assign an owner to each page, and make clear who fixes it when the content goes out of date
- Decide rules for where things go: decide at the start how to divide spaces and folders and how to name pages
- When asked in chat, answer with a wiki link: building the habit of pointing to a wiki page for the same question gives people a reason to write
Samurai App as an option
Samurai App's "Docs" is an internal wiki your AI agents read and write. You place headings, bullet lists, tables, and code as lines, and you can nest pages. Agents read and write with the same permissions as people, and you can ask them to do work while looking at a page. It also connects with kanban boards and canvases in the same place.
Pricing is one base fee per company plus credits based on usage, and it doesn't grow with headcount. There's no limit on how many people you can invite, and you can group people by department to decide the visibility of internal knowledge. Amounts are summarized on the pricing page. You can start the free trial without a credit card. It's a candidate when many people read your internal wiki and the cost of per-user pricing is a concern.
FAQ
Are there internal wiki tools I can use for free?
Yes. Confluence's Free plan is free for up to 10 users, Kibela's Community plan for up to 5 people, and Qast's free plan for 10 people or fewer (as of October 20, 2026). However, they have limits on storage and features, so for company-wide use it's realistic to assume a paid plan.
What's the difference between an internal wiki and a knowledge sharing tool?
There's no clear line. "Internal wiki" often refers to accumulating pages organized by hierarchy and links, while "knowledge sharing tool" is used as a broader term that also includes Q&A and post formats like an internal social network. Which products fit depends on whether your company wants to "keep organized documents" or "casually share questions and answers."
Is Notion a good fit as an internal wiki?
It suits cases where you want to bring the wiki, task management, and databases together in one place. On the other hand, because it's so flexible, information tends to scatter unless you decide rules for where pages go. The Free plan has a block limit when two or more people use it, so for team use, estimate assuming Plus or higher.
Why doesn't an internal wiki take hold?
Common causes are that nobody has been assigned to write and update, that too little is published at first so there's no reason to read, and that how it's used versus chat and shared folders hasn't been decided. Along with choosing a tool, deciding the pages to publish in the first month and who owns them makes it easier to take hold.
Sources
- Notion pricing
- Confluence pricing
- NotePM pricing
- Kibela pricing plans
- esa pricing
- Qiita Team pricing plans
- DocBase pricing plans
- GROWI.cloud pricing and features
- Helpfeel Cosense pricing
- Qast pricing
Prices and specifications were checked on each vendor's official website as of October 20, 2026. Please check each vendor's site for the latest information.