Context + Wiki.js
Unlock institutional knowledge from your Wiki.js documentation and connect it across your entire tool stack
OVERVIEW
Wiki.js is a modern, open-source wiki platform that has become a popular choice for organizations seeking a self-hosted knowledge base with a clean editing experience, robust access controls, and support for multiple content formats including Markdown, HTML, and rich text. Its lightweight architecture, Git-backed storage options, and enterprise authentication integrations make it particularly attractive to engineering teams, research organizations, and regulated industries that need full control over their documentation infrastructure.
Over time, Wiki.js instances become critical repositories of institutional knowledge -- architecture decision records, runbooks, onboarding guides, API documentation, and operational procedures. But as the volume of documentation grows, finding the right page becomes increasingly difficult. Wiki.js's built-in search works well for keyword matching within the wiki itself, but it cannot connect documentation to the broader organizational context in your project management tools, communication platforms, and development workflows.
Context connects to your Wiki.js instance and incorporates every page, comment, and revision into your enterprise knowledge graph. When an engineer searches for information about a deployment procedure, Context does not just find the relevant Wiki.js page -- it also surfaces the Slack discussion where the procedure was last updated, the Jira ticket that triggered the change, and the GitLab merge request that modified the related infrastructure code. For organizations running Wiki.js on-premise in regulated or air-gapped environments, Context deploys alongside it with zero data exfiltration, ensuring that sensitive documentation never leaves your controlled infrastructure.
KEY CAPABILITIES
Key Capabilities
- 01Full page and content indexing -- extract and index all Wiki.js pages across namespaces with Markdown, HTML, and rich text content fully parsed and searchable
- 02Revision history knowledge mapping -- track page changes over time, connecting edits to the people who made them and the organizational events that triggered updates
- 03Comment and discussion extraction -- capture page-level comments and discussions, linking feedback to the documentation it references
- 04Namespace and tag taxonomy mapping -- understand your Wiki.js organizational structure including page hierarchies, tags, and cross-references
- 05Cross-tool documentation linking -- automatically connect Wiki.js pages to related Jira tickets, GitLab merge requests, Slack discussions, and other tool content
- 06Access control-aware indexing -- respect Wiki.js group and page-level permissions so that restricted documentation is only visible to authorized users in search results
USE CASES
Use Cases
Engineering Onboarding Acceleration
A defense technology company maintains hundreds of Wiki.js pages covering system architecture, deployment procedures, and operational runbooks. New engineers spend weeks navigating disconnected documentation. Context indexes the entire Wiki.js instance and links pages to related Jira tickets, GitLab repositories, and Slack channels. New hires ask natural language questions like "how do I deploy the sensor processing pipeline to staging?" and receive answers that combine the Wiki.js runbook with the latest Slack discussion about a deployment change and the GitLab CI configuration that automates it.
Documentation Freshness and Gap Analysis
An organization discovers that critical Wiki.js documentation has become stale -- procedures have changed but pages were never updated. Context's knowledge graph reveals which pages reference outdated tools, configurations, or processes by correlating wiki content with recent activity in connected tools. Teams can identify documentation gaps where important decisions were made in Slack or Jira but never captured in the wiki.
Research Knowledge Consolidation
A research team uses Wiki.js to document experimental methods, literature reviews, and technical specifications. Context connects these wiki pages to related discussions in Mattermost, data analysis notebooks referenced in GitLab, and project tracking in Redmine. Researchers can search across the full knowledge landscape to find prior work, avoid duplicating experiments, and trace the evolution of research approaches over time.
HOW IT WORKS
How It Works
DATA FLOW
SECURITY & COMPLIANCE
Security & Compliance
DEPLOYMENT
Deployment Options
DEPLOYMENT ARCHITECTURE
FREQUENTLY ASKED QUESTIONS
Frequently Asked Questions
Does Context work with self-hosted Wiki.js in air-gapped environments?
Yes. Context deploys entirely on your infrastructure with no outbound network dependencies. The Wiki.js connector communicates with your Wiki.js instance over your internal network and uses polling to detect changes. No data leaves your firewall at any point in the pipeline.
What Wiki.js content does Context index?
Context indexes all page content (Markdown, HTML, and rich text), page metadata including tags and descriptions, comments, revision history, and namespace structure. Context parses all content formats that Wiki.js supports to ensure full-text searchability. You can configure which namespaces and pages to include or exclude.
Does Context support Wiki.js page-level permissions?
Yes. Context respects Wiki.js's group-based and page-level permission rules. When users query Context, they only see results from pages their Wiki.js permissions allow them to access. Permission mappings are synced on a configurable schedule to stay current with your access control changes.
How does Context handle Wiki.js Git-backed storage?
Context indexes wiki content through the Wiki.js GraphQL API regardless of the underlying storage backend. Whether your Wiki.js instance uses Git, PostgreSQL, or another storage provider, Context accesses the same content through the API layer. Git-backed storage mode does not affect Context's indexing capabilities.
Can Context connect to multiple Wiki.js instances?
Yes. Context supports connecting to multiple Wiki.js instances simultaneously. Knowledge from all instances is unified in a single graph with permissions enforced per-user based on their access in each instance. This is useful for organizations that maintain separate wiki instances for different teams or classification levels.
SETUP OVERVIEW
Setup Overview
Install the Context Wiki.js connector using Helm or deploy it directly on bare metal. Generate a Wiki.js API key with read access in the Wiki.js administration panel. Configure the connector with your Wiki.js instance URL and API key. For air-gapped deployments, provide internal CA certificates if needed. Context will perform an initial sync of all wiki pages and then poll for updates on a configurable schedule. Most instances are fully indexed within an hour.
RELATED INTEGRATIONS
Related Integrations
Confluence
Connect Context to Confluence to link documentation, design decisions, and team knowledge to every tool in your stack. Permission-aware indexing with on-premise deployment.
Notion
Connect Notion workspaces to your on-premise knowledge graph. Context indexes pages, databases, and nested content structures to surface cross-tool relationships across your entire organization.
MediaWiki
Connect MediaWiki to Context and transform wiki articles, talk pages, and structured data into a searchable enterprise knowledge graph. Fully compatible with self-hosted MediaWiki deployments including Semantic MediaWiki extensions.
GitLab
Connect GitLab to Context and transform merge requests, issues, epics, and CI/CD pipeline knowledge into a searchable enterprise knowledge graph. Fully compatible with self-managed GitLab instances behind air-gapped networks.
Slack
Connect Context to Slack to surface organizational knowledge buried in conversations, threads, and channels. Permission-aware indexing with on-premise deployment.
Ready to connect Wiki.js?
See Context + Wiki.js in action with a 30-minute technical walkthrough tailored to your environment.
BOOK A DEMO