Slab
Team knowledge base with topic-based structure and search that spans Slack, Drive and GitHub as well as its own posts.
Quick facts
| Pricing | Freemium |
|---|---|
| Free tier | Yes — free plan for a small team with limited posts |
| Platforms | Web, desktop, Slack |
| Developer | Slab |
| Website | https://slab.com |
What Slab is
Slab is a knowledge base for teams. Content is organised into topics rather than a folder tree, posts are edited in a clean editor, and search covers both Slab and connected tools such as Slack, Google Drive and GitHub, so an answer can come from anywhere the team stores it. It adds verification reminders so posts do not go stale, and a unified search bar that is the main entry point for most users. The appeal is simplicity: less configuration than a wiki platform, with search that actually spans systems. The limits are depth and scale: it is a documentation tool rather than a workspace, there is no database or project functionality, and very large organisations may need more granular permissions than it offers. A post can be embedded elsewhere and kept in sync, so the same answer does not fork into two versions. Topic subscriptions notify people when something they own changes.
Best for
- Teams whose answers are split across several tools
- Onboarding documentation that must stay current
- Finding an old decision without knowing where it lives
Not ideal for
- Project management and database use cases
- Organisations needing fine-grained per-page permissions
Pros
- Search reaches connected tools, not just its own posts
- Verification reminders keep content current
- Editor is simple enough that people actually write
Cons
- No database or project features
- Permissions are coarser than large organisations need
- Limited customisation of layout
Pricing in detail
The free plan covers a small team with a limited number of posts. Paid plans are billed per user per month and raise post limits, add verification workflows, integrations, analytics and advanced permissions; annual billing lowers the monthly rate. Because the cost is per seat and the benefit depends on participation, rolling it out to people who never write inflates the bill without improving the knowledge base.