Knowledge Sync (OIKB)
Keep your Knowledge Bases current, automatically.
Hrida OIKB connects Hrida.ai Knowledge Bases to the places your content actually lives: a docs folder, a GitHub repo, a Confluence space, an S3 bucket, a Jira project, a Slack channel and 38 more. Point it at a source and a Knowledge Base, and it uploads the files. Run it again and it uploads only what changed, and removes what was deleted.
Use it once from the command line, have it watch a folder, or run it as a daemon that syncs every source on a schedule and the moment someone pushes.
Hrida.ai (hrida-ai-studio) 1.0.0 or newer and Python 3.11+. Or use the Docker image.
How it works
- Scan the source and compute a checksum for every file (SHA-256, or the ETag for object storage).
- Diff: send that manifest to Hrida.ai, which compares it with what the Knowledge Base already holds.
- Clean up files that no longer exist at the source and create any missing folders.
- Upload only new and modified files. Unchanged files are skipped entirely.
Re-running a sync with nothing changed does nothing, so it's safe to schedule as often as you like.
Feature map
| Area | What's there |
|---|---|
| Use cases | Six end-to-end scenarios with diagrams: knowledge assistant, codebase copilot, support agent, live sync for writers, enterprise hub, CI/CD gate |
| Architecture | Components, and step-by-step sequence diagrams for one-time sync, daemon, webhooks, watch mode and the API |
| Installation & first sync | Private wheel or Docker, API key, finding a Knowledge Base ID, dry runs, watch mode |
| Configuration | .hrida-oikb.yaml, global defaults, environment variable interpolation, include/exclude filters, size limits, .hrida-oikbignore, splitting one source across Knowledge Bases |
| Connectors | All 44 sources: source syntax, required credentials, optional extras |
| Daemon & automation | Interval and cron scheduling, webhooks, HTTP API, status dashboard, Hrida.ai tool server, failure notifications, Prometheus metrics, JSON logs |
| Deployment | Docker, production Compose, GitHub Actions, Kubernetes, troubleshooting |
| CLI reference | Every command and flag |
Quick start
Knowledge Sync is distributed privately to licensed clients, not through public PyPI. Get the package from a release of the private Hrida-AI/hrida-oikb repository (see Installation):
gh release download v1.0.3 -R Hrida-AI/hrida-oikb -p "*.whl"
pip install ./hrida_oikb-1.0.3-py3-none-any.whl
export HRIDA_AI_URL=http://localhost:3000
export HRIDA_AI_API_KEY=sk-your-api-key
# preview, then sync a folder
hrida-oikb sync ./docs --kb-id your-kb-id --dry-run
hrida-oikb sync ./docs --kb-id your-kb-id
# or a GitHub repo
hrida-oikb sync github:owner/repo --kb-id your-kb-idFor several sources, scheduled syncs or webhooks, run hrida-oikb init to create a .hrida-oikb.yaml, then hrida-oikb daemon.
Connector coverage
| Category | Sources |
|---|---|
| Local | Filesystem |
| Code repos | GitHub, GitLab, Bitbucket |
| Cloud storage | S3, GCS, Azure Blob, Dropbox, Cloudflare R2, Google Drive, SharePoint, Egnyte, Oracle Cloud |
| Wikis & KBs | Confluence, Notion, BookStack, Discourse, GitBook, Guru, Outline, Slab, Document360, DokuWiki, Google Sites |
| Ticketing | Jira, Linear, Zendesk, Freshdesk, Asana, ClickUp, Airtable, ServiceNow, ProductBoard |
| Messaging | Slack, Discord, Microsoft Teams, Gmail, Zulip |
| Meetings | Gong, Fireflies |
| Forums | XenForo |
| Sales & CRM | Salesforce, HubSpot |
| Web | Website / sitemap crawler |