Features
not a feature list — a working library.
Six capabilities. Each one built around a single fact: a wiki is only worth the trust readers put in it.
Plans from $99 a year.
Editor
write together. comment on the line.
Several people in one page, each with a live cursor. Comments pin to the exact sentence, so the question sits next to the thing it questions. Type / and a block appears: table, checklist, callout.
- Threads that resolve, so the page ends clean
- @mentions notify the page owner at once
- Markdown shortcuts and a slash menu, no toolbar hunt
Freshness and owners
pages that expire on purpose.
Every page carries an owner and a review cycle of 30, 60 or 90 days. When the clock runs out, the owner is nudged and every reader sees the flag: Fresh, Due soon or Overdue. One click marks it reviewed.
Owners and review reminders start on Edition.
Spaces and permissions
spaces nest. access cascades.
Put spaces inside spaces. Set access once at the top and it flows down; override on a single page when one document needs a smaller circle. People and groups sit side by side with four roles: Admin, Editor, Commenter, Viewer.
- Inherited access is always labeled as inherited
- Contractors get a group, not a pile of invites
Granular permissions by space start on Edition.
Search
one box. every source.
Pages, attached PDFs, Slack threads and Datadog monitors answer from the same field. Press ⌘K from anywhere. Results land as you type, grouped by where they live, with each page's freshness beside it.
- Freshness shown in the result, before you click
- Filter by space, owner or source
- Fully keyboard driven: ↑ ↓ ↵
Page history and usage
every edit kept. every page measured.
Compare any two versions line by line and restore one in a click. On Archive, usage analytics show which pages get read and which sit untouched, so review time goes where readers actually are.
Draft keeps 30 days of history. Edition and Archive keep every version. Analytics start on Archive.
Import and templates
arrive with the tree intact.
Bring Notion, Confluence or Google Docs across in one pass. Page trees, attachments and comments land where they were. Starting clean instead? Templates for runbooks, policies and handbooks come with owners and cycles pre-set.
- Structure first, then files, then comments
- Imported pages start with a review date, not a blank history
Security and reliability
locked down. kept current.
Access, audit and retention controls that match how your library is actually used.
single sign-on
SAML sign-in so access follows your identity provider. Offboarding someone closes the library at the same moment.
Archive planaudit logs and retention
See who viewed, edited and changed access, and set how long old versions are kept.
Archive planrole-based access
Four roles, enforced per space and per page. A Viewer cannot edit, whatever the link says.
Edition and uphistory as a safety net
Every edit is recoverable. A bad paste is a one-click restore, not a lost afternoon.
All plans
Integrations
answers where the work happens.
Reminders go to the channel owners already read. Runbooks open from the monitor that fired. Review dates land on real calendars.
Compare plans- SlackReview reminders delivered to the owner, threads searchable from Vellum.
- Google CalendarEach review date appears as an event for the page owner.
- DatadogLink a monitor to a runbook; the alert opens the page.
- DiscordPage updates posted to community channels.
- SalesforceAccount playbooks surface inside search.
- IntercomSupport answers pulled straight from the source page.
- SegmentContent usage events flow downstream.
you've seen the shelf. choose yours.
Draft $99, Edition $299, Archive $599. Billed once a year.