Reduce repeated questions
Give teams one searchable home for procedures, onboarding guides, policies, incident notes, architecture decisions, and recurring support answers.
Vianordis--:--:-- UTCVianordis / ED. 02 / 2026
§ 07 — App support
Kognis
Sovereign knowledge base for procedures, decisions, and operational memory.
Kognis gives teams a controlled documentation workspace for runbooks, policies, technical guides, page history, search, comments, and AI-assisted knowledge work without scattering critical know-how across chat threads, drives, and unmanaged wikis.
01 — Problem
Operational knowledge usually exists, but it is rarely dependable.
Teams document processes in chat, shared drives, tickets, personal notes, old wikis, and exported PDFs. The information may exist somewhere, but it is hard to trust because ownership is unclear, duplicates drift, search is weak, and access rules do not match the sensitivity of the content.
- Runbooks, procedures, decisions, and technical guides are duplicated across disconnected tools.
- Teams cannot easily see which page is current, who changed it, or whether an older version must be restored.
- Search returns too much or too little because tags, hierarchy, links, and semantic meaning are not managed together.
- Access control is difficult when different departments, customers, or operating units need isolated knowledge spaces.
- Comments, review feedback, and follow-up discussion are separated from the page being improved.
- AI-assisted writing or summarization is risky when it is detached from tenant boundaries and page permissions.
02 — Solution
Kognis turns documentation into a governed knowledge system.
Kognis builds on a Wiki.js foundation and adapts it for Vianordis operations with tenant resolution, PostgreSQL-backed pages, GraphQL administration, configurable editors, page history, comments, tags, storage sync, search engines, and AI Hub features for semantic search and content assistance.
- Authors create structured pages with paths, locales, tags, publication state, privacy settings, and multiple editor modes.
- Readers find trusted knowledge through page search, trees, tags, links, search indexes, semantic search, and AI-assisted answers.
- Administrators keep tenants, groups, auth providers, API keys, storage targets, comments, history, and search settings under one controlled operating model.
03 — Benefits
Business outcomes before wiki mechanics.
Kognis is built for organizations that need living documentation with clear ownership, discoverability, tenant boundaries, and operational continuity.
Make knowledge auditable
Use page history, version restore, authorship metadata, publication state, and permission checks to understand how critical documentation changed.
Keep teams separated when needed
Tenant resolution, tenant users, roles, settings, and page-scoped access rules help isolate knowledge by organization, customer, or operating unit.
Improve discovery
Combine paths, page trees, tags, backlinks, configurable search engines, and semantic AI search so users can find the right answer faster.
Support different authoring styles
Let technical and non-technical users write with Markdown, WYSIWYG, AsciiDoc, code-oriented, redirect, source, or API-driven editing workflows.
Avoid knowledge lock-in
Use open-source Wiki.js foundations, Git and storage sync options, GraphQL APIs, and exportable page content rather than trapping operational memory in a closed note system.
04 — How it works
From scattered knowledge to dependable reference in three steps.
- 01
Structure the workspace
Create tenants, groups, roles, locales, navigation, search engines, storage targets, and page areas that match how the organization actually works.
- 02
Capture and review knowledge
Authors create pages with the right editor, path, tags, description, publication status, privacy posture, and ownership context, then use comments and history to improve them over time.
- 03
Search, reuse, and maintain
Readers search by keyword, tag, tree location, link context, or semantic meaning while administrators rebuild indexes, restore versions, sync storage, and monitor stale or duplicated content.
05 — Features
What teams can actually do in Kognis.
Page management
Create, update, move, delete, convert, render, publish, unpublish, and restore pages with path, locale, title, description, content, tags, privacy, and scheduling fields.
Multiple editors
Support Markdown, WYSIWYG, AsciiDoc, code, redirect, API, and source-oriented authoring so different teams can document in the format that fits the work.
Page tree and navigation
Organize documentation by hierarchy, locale, parent, ancestors, links, tags, navigation entries, and rebuildable page trees.
Version history and restore
Inspect page history, compare version metadata, check edit conflicts, restore older versions, and purge historical records under administrative control.
Search and discovery
Search pages, tags, links, and trees while managing search engines such as database, PostgreSQL, Elasticsearch, Algolia, Solr, Sphinx, Manticore, Azure, or AWS-backed options.
AI-assisted knowledge work
Use GSC AI Hub integration for content generation, rewriting, summaries, translation, semantic search, similar pages, duplicate detection, quality analysis, AI answers, and optional auto-tagging.
Comments and review context
Keep feedback attached to the page with comment listing, creation, update, deletion, and moderation permissions.
Tenant administration
Create and manage tenants, domains, tenant settings, tenant users, roles, feature flags, and OIDC tenant-access synchronization.
Storage sync
Configure storage targets and sync actions for disk, Git, S3-compatible storage, SFTP, Azure, Google Drive, OneDrive, Dropbox, Box, and DigitalOcean-style targets.
API and authentication controls
Manage GraphQL operations, API keys, enabled API state, active authentication strategies, self-registration, domain allowlists, and group auto-enrollment.
06 — Architecture
Architecture and security model.
Kognis separates page rendering, GraphQL administration, tenant resolution, authentication, storage sync, search, and AI services so documentation can be governed as operational infrastructure.
- The web application is based on Wiki.js with Node.js, Vue assets, GraphQL schemas, server-rendered views, configurable editors, and page-rendering jobs.
- PostgreSQL stores tenants, users, groups, pages, page trees, page history, tags, comments, assets, navigation, authentication strategies, search engines, settings, and storage state.
- Tenant middleware resolves the active tenant from custom domain, subdomain, authenticated X-Tenant-ID header, optional path prefix, or default tenant, then validates user access.
- GraphQL auth directives protect page, history, comment, tenant, authentication, API key, search, storage, site, navigation, and AI operations by permission.
- Authentication modules support Keycloak, OIDC, SAML, LDAP, OAuth2, local login, Microsoft, GitHub, GitLab, Google, Azure, Okta, Auth0, and other provider strategies.
- Search modules can use database or external search engines, while AI Hub services add embeddings, semantic search, content assistance, translation, quality analysis, and RAG-style answers.
- Storage modules synchronize pages and assets to Git, S3-compatible storage, SFTP, disk, Azure, Google Drive, OneDrive, Dropbox, Box, and related targets.
- Background jobs rebuild page trees, render pages, synchronize storage, sanitize uploads, and maintain localized or indexed content.
07 — Use cases
Where Kognis fits.
Runbooks and operations
Document incident response, maintenance procedures, deployment steps, escalation paths, and service ownership in a searchable operational manual.
Policy and compliance knowledge
Maintain information-security policies, data-handling rules, audit procedures, and controlled internal guidance with history and role-aware access.
Engineering documentation
Publish architecture notes, API usage, platform guides, database conventions, troubleshooting steps, and technical decisions with code-friendly editors.
Employee onboarding
Give new team members structured onboarding guides, department pages, account setup steps, and searchable answers to recurring internal questions.
Customer or partner knowledge spaces
Use tenant boundaries and access controls for separate customer portals, partner guides, project documentation, or managed-service knowledge bases.
AI-assisted documentation maintenance
Find duplicate or similar pages, summarize long content, improve drafts, translate documentation, and ask questions across selected page sets.
08 — Integrations
Connects to identity, storage, search, and AI systems.
Kognis uses standard wiki, authentication, database, storage, search, and API interfaces so knowledge management fits into existing infrastructure instead of becoming another isolated documentation island.
Wiki.js
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Keycloak
Keeps access tied to organization accounts, roles, and sign-in policy.
OIDC
Shows how this service fits into the wider Vianordis environment instead of standing alone.
SAML
Shows how this service fits into the wider Vianordis environment instead of standing alone.
LDAP
Shows how this service fits into the wider Vianordis environment instead of standing alone.
PostgreSQL
Stores structured service records in a controlled tenant-aware backend.
GraphQL API
Lets approved systems connect without ad hoc exports or manual copy-paste.
Markdown
Shows how this service fits into the wider Vianordis environment instead of standing alone.
AsciiDoc
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Git
Shows how this service fits into the wider Vianordis environment instead of standing alone.
S3-compatible storage
Provides the governed place where service data and files are stored.
SFTP
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Elasticsearch
Shows how this service fits into the wider Vianordis environment instead of standing alone.
PostgreSQL search
Stores structured service records in a controlled tenant-aware backend.
Algolia
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Solr
Shows how this service fits into the wider Vianordis environment instead of standing alone.
GSC AI Hub
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Kubernetes
Shows how this service fits into the wider Vianordis environment instead of standing alone.
09 — Trust
Compliance and trust signals.
Kognis is designed so documentation ownership, tenant access, authentication, page history, search behavior, storage synchronization, and AI assistance can be explained to IT, security, and compliance teams.
Tenant boundaries
Tenant resolution and user-tenant validation keep documentation scoped to the active organization or knowledge space.
Permission model
GraphQL operations require permissions such as read pages, write pages, manage pages, read history, delete pages, manage API, and manage system.
History
Page history, conflict checks, restore operations, authorship metadata, timestamps, and purge controls support accountable documentation changes.
Identity
Authentication strategies include Keycloak, OIDC, SAML, LDAP, OAuth2, local login, and major enterprise identity providers.
Portability
Open-source Wiki.js foundations, Git sync, storage targets, GraphQL APIs, Markdown, and external search options reduce documentation lock-in.
AI control
AI Hub features are permission-gated and tenant-aware, covering semantic search, content generation, summaries, translation, duplicate detection, and indexing.
European operation
Kognis runs as part of the Vianordis application suite and can use Vianordis-operated identity, database, storage, and AI infrastructure.
10 — Pricing
Use published pricing or map your knowledge estate in a demo.
Kognis is listed on the Vianordis rate card. For larger organizations, a demo is the fastest way to review tenant structure, identity providers, editor preferences, storage sync, search engines, AI features, migration scope, and access-control requirements.
11 — FAQ
Questions technical buyers usually ask.
Who is Kognis for?
Kognis is for teams that need a governed knowledge base for runbooks, policies, technical documentation, onboarding, project knowledge, customer spaces, and operational reference material.
Is Kognis based on Wiki.js?
Yes. Kognis builds on Wiki.js and adapts it for the Vianordis environment with tenant-aware operation, integrated identity, AI Hub features, and managed deployment patterns.
Which editors are supported?
The app includes editor modules for Markdown, WYSIWYG, AsciiDoc, code, redirect, API, and source-oriented workflows.
How does access control work?
Access is controlled through tenants, users, groups, roles, authentication strategies, and permission-gated GraphQL operations for reading, writing, managing pages, viewing history, comments, API keys, search, storage, and system settings.
Can documentation be synced outside the database?
Yes. Kognis includes storage targets for Git, S3-compatible storage, SFTP, disk, Azure, Google Drive, OneDrive, Dropbox, Box, and related providers, depending on configuration.
Does Kognis support AI?
Yes. GSC AI Hub integration supports content generation, rewriting, summaries, translation, semantic search, similar pages, duplicate detection, quality analysis, AI answers, and page indexing under the relevant permissions.
Can teams recover older content?
Yes. Page history and version restore workflows let authorized users inspect previous versions and restore a page when needed.
Can Kognis support separate customers or departments?
Yes. The tenant model supports separate domains, users, roles, settings, feature flags, and tenant-scoped pages, assets, comments, and storage operations.
12 — Next step
Move operational knowledge into the same sovereign operating model as the rest of your cloud.
See how Kognis can replace scattered notes and unmanaged wikis with tenant-aware documentation, page history, search, storage sync, comments, and controlled AI-assisted knowledge work.