
Knowledge Hub
Internal documentation with real search, ownership, review dates and version history.
Next.js · TypeScript · PostgreSQL · MDX
OverviewRequester1 / 6
A support queue and a knowledge base are the same system viewed twice. Answer a ticket once, publish the answer, and watch that category of ticket stop arriving.
Next.js · TypeScript · PostgreSQL · Recharts
Inside the app
22 connected functions on one schema, spanning three permission levels. Everything below is in the template before a line of customisation.
Three of your tickets are open and one is waiting on your reply.
Everything you have raised, and what it is waiting on.
Search before you raise. Most questions have already been answered.
Everything open, ordered by what breaches first.
Response and resolution targets by priority, with pauses recorded.
How many questions the knowledge base answered before a ticket existed.
Where a ticket goes, and what it promises when it gets there.
Every reassignment, SLA pause and rule change. Retained for seven years.
Permissions
A requester raises and tracks, after searching first. An agent works a queue ordered by what breaches next. An administrator sets routing and targets. Deflection is measured rather than assumed.
The build
22 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
What you get
Internal IT, operations and support teams fielding requests from tens to thousands of people a month.
Access and evidence
A support queue and a knowledge base are the same system viewed twice. Answering a ticket and publishing that answer should be one action, and the deflection it earns should be measured rather than assumed.
Related

Internal documentation with real search, ownership, review dates and version history.
Next.js · TypeScript · PostgreSQL · MDX

Deal stages, forecasting and activity history for a sales team that has outgrown a spreadsheet.
Next.js · TypeScript · PostgreSQL · Tailwind

A whole partner programme in one app: deal registration, a gated resource library, training, funding requests and tier performance.
Next.js · TypeScript · PostgreSQL · Auth.js
Questions
Yes. The repository, application code, database schema, migrations, seed data and deployment configuration, is transferred to your organisation on delivery.
As many as you like. Per-agent licensing is the standard model in service desk software and the reason small teams end up running support from a shared inbox.
A resolved ticket becomes an article in one action, keeping the link between them. The portal then shows how many people found that article and did not go on to raise a ticket, so deflection is a measured number rather than a claim.
Yes. Clocks pause while a ticket is with the requester and the pause is recorded, so agents are not penalised for someone else's delay and the reported figures stay honest.
That is the usual route. A fitted build sets up your categories and routing, priorities and targets, approval requirements, portal branding, email ingestion and up to two integrations.
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month, rising with attachment storage.
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.
