Tettra
Details
Knowledge structure
Tettra organises information into pages and categories, with support for nested categories and uncategorized content. The selected official interface shows a category overview containing pages, subcategories and page requests. A useful proof should recreate one real subject area with a shallow hierarchy, clear owners and naming that ordinary users understand without being taught the internal taxonomy.
Writing and collaboration
Teams can create and edit pages, add images and links, and collaborate around knowledge that changes over time. Test a short operating procedure with a subject-matter expert, an editor and a reader. Confirm how drafts, comments, permissions and revision history work, and verify that a restricted page remains unavailable through navigation, direct links and search for an unauthorised user.
Search and answers
Search indexes page titles, headings, body content and related metadata, while Kai provides AI-assisted knowledge experiences. Build a test set containing exact questions, synonyms, abbreviations and one deliberately outdated answer. Review whether results identify the source page, respect access rules and make uncertainty visible. Buyers should not treat a fluent generated response as accepted knowledge without a traceable source and owner.
Requests and maintenance
Page requests help teams identify missing knowledge and direct work to the right contributors. Categories can expose uncategorized pages that need attention, and knowledge workflows can support curation. Define a review rule for critical pages, then test an expired instruction, a duplicated answer and a request with no current owner. The operating team should be able to see what needs action rather than relying on informal reminders.
Who it may suit
Tettra may suit small and midsize teams that need a focused internal wiki and question-answer workflow without deploying a broad document-management suite. Fit depends on adoption, ownership and information quality as much as feature availability. Include readers, frequent contributors and administrators in the evaluation and use realistic permission boundaries and search language.
Implementation checkpoint
Start with one bounded knowledge domain and migrate only approved, current material. Record the category design, page owners, permissions, source systems, review dates, request workflow, search test set and export or rollback procedure. Expand only after users can find representative answers quickly, contributors can maintain them without hidden side processes, and administrators can identify stale or ownerless content from durable evidence.