Pipeline CRM
Deal stages, forecasting and activity history for a sales team that has outgrown a spreadsheet.
5.0 out of 511 sold
OverviewReader1 / 6
Knowledge Management
DocsLive
Knowledge Hub
5.0 out of 58 sold
Most internal wikis fail the same way: nobody owns the page and nobody knows it went stale. This build makes ownership and freshness structural.
From$479
- Function
- 25
- Roles
- 6
- Users
- Unlimited
- Next.js
- TypeScript
- PostgreSQL
- MDX
Inside the app
What it does out of the box
25 connected functions on one schema, spanning six permission levels. Everything below is in the template before a line of customisation.
Dashboard for Elena
Nine articles are overdue for review and two of them are the most-read pages here.
Browse
Spaces and what is in them, with freshness shown up front.
Recently updated
What changed, who changed it, and when it is next due for review.
My articles
What you own, and what you owe a review on.
Reviews due
Overdue and upcoming, ordered by how much the article is actually read.
Search gaps
What people looked for and did not find. The list of what to write next.
Spaces and access
Who can read and who can edit, per space.
Audit log
Every edit, permission change and archive. Retained for seven years.
Permissions
Three roles, one build
A reader searches and reads. An editor owns articles and works the review queue. An administrator sets spaces and permissions. Ownership and freshness are structural rather than aspirational.
- Search weighted by title, tag and recency
- See freshness before trusting an article
- Browse only spaces they may read
- Suggest an edit or flag something stale
- Cannot see restricted spaces at all
- Everything a reader can do
- Own articles with a named review interval
- Work the review queue by readership
- See what people searched for and did not find
- Version history with restore
- Everything an editor can do
- Create spaces and set visibility
- Assign and reassign article owners
- Set review intervals and escalation
- Read and export the audit log
The build
Every function in the box
9 screens, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
Access
- Sign in
Knowledge
- Overview
- Browse
- Recently updated
Editing
- My articles
- Reviews due
- Search gaps
Administration
- Spaces and access
- Audit log
What you get
Delivered as a repository, not a login.
Operations, support and engineering teams whose knowledge currently lives in chat history.
- 9 production functions spanning six permission levels
- Full source code and PostgreSQL schema in your repository
- Role-based access control, enforced server-side
- Immutable audit log written on every change
- Responsive layouts, usable on a phone, not just resized
- CSV import and export on every core record
- Deployment configuration for your cloud account
- Twelve months of updates, and no per-seat charge ever
Access and evidence
Why wikis go stale
Internal wikis fail the same way everywhere: nobody owns the page and nobody knows it went stale. Making ownership and freshness structural is the only thing that reliably prevents it.
- Every article has a named owner, not a team
- Review intervals are set per article, because a policy and a runbook age differently
- Overdue articles are flagged in place, where readers actually see them
- Unowned articles escalate rather than sitting quietly
- Space visibility is enforced server-side, not by hiding navigation
- Superseded material moves to Archive rather than being deleted
- Role-based access control, enforced server-side
- Immutable audit log written on every change
Related
Apps that pair with this one
From$549View details
Partner Portal
A whole partner programme in one app: deal registration, a gated resource library, training, funding requests and tier performance.
4.0 out of 53 sold
Customer Success Hub
Health scores, renewal calendars and QBR prep for the team that keeps revenue from leaking.
4.5 out of 56 sold
Questions
Knowledge Hub, in practical terms
Not covered here?
Ask a consultant directly. No form to fill in first, and no follow-up sequence.
Book a consultantAll questionsDo I get the source code for Knowledge Hub?
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery.
How many people can read and edit?
As many as you like. Per-seat pricing on a knowledge base is self-defeating, the whole point is that everyone can find the answer without asking a person.
What stops it going stale like every other wiki?
Two things made structural rather than optional. Every article has a named owner, not a team, and every article has its own review interval. Overdue articles are flagged where readers see them, and unowned ones escalate.
What are search gaps?
Searches that returned nothing. It is the most useful content plan available, because it is a list of what people actually wanted and could not find, far better than guessing what to document next.
Can Knowledge Hub be changed to match our teams?
That is the usual route. A fitted build sets up your spaces and permissions, review intervals, article templates, search synonyms for your internal vocabulary, branding and up to two integrations.
What does it cost to run?
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month.
Start here
Want Knowledge Hub shaped around your process?
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
- No sign-up to open one
- One-time price, no seats
- Source code transferred on delivery
