Your notes, become known. One place for you and your agents.
First time in the Hub? After you sign in, a short setup guide may open automatically. Reopen anytime from How to use → Getting started or Settings → Backup → Setup guide.
Run locally or get online access with our hosted service on decentralized Internet Computer canisters.
Proposals, Evaluations, and Scoped Access =
Security, Savings, and Ownership and Control
Legal, compliance, finance, and operations increasingly need proof of who approved a change and that the record was not silently altered. Knowtation pairs human-in-the-loop proposals with HMAC-signed attestation and optional Internet Computer blockchain anchoring — an audit trail you can point to, not just another row in a vendor database. Whitepaper: attestation and ICP
Your vault is searchable; memory keeps what agents and you did over time. Consolidation folds noisy events into compact facts so future context stays small. Optional Discover traces cross-topic insights — new paths between ideas — so yesterday’s notes actively inform tomorrow’s decisions instead of sitting in a forgotten folder. That is what “become known” means: interconnected, growing context, not a one-off chat dump.
Solutions for the worries we hear most: cost, lock-in, trust, and “can my agents actually use this?”
Narrow search - only notes you need. Memory consolidation continuously keeps future context smaller.
Markdown in your vault — Git, editors, backups. No “export my life’s work” crisis when you switch tools.
Attestation plus optional IC anchoring for provable intent. Pair with proposals - no unchecked agents
33 MCP tools, memory, consolidation, and the same CLI you use — not a thin search wrapper.
Imports, capture, digital wallet CSVs, Supabase bridge — one searchable corpus for humans and agents.
Same product: decentralized canisters when you want zero ops, or full control on your metal.
A Hosted Hub where you own the data: back up to GitHub anytime for portability.
Invite viewers, editors, and admins with scoped access in minutes.
No per-seat pricing
Knowtation is the brain — files, search, memory, and review. Together with your custom workflow, you get one direction: humans and agents propose, humans curate, and history stays inspectable across life, work, and research.
Use Knowtation any way you can imagine. Our vision was built around connecting open-source projects that share patterns: tiered retrieval, proposals before commit, and JSON-friendly automation. The use cases are infinite in business, research, legal, creative, personal life and more. We are curious to see how bridges may evolve.
Connect with our fellow community projects and partners to create an incredible future with supercharged tools. Adjust at will to fit your needs.
Stack roles (from ECOSYSTEM-VISION.md):
Knowtation integration: Agent integration — CLI, MCP, Hub API, proposals, optional external lineage, and hosted MCP in one guide. Multi-agent patterns: AGENT-ORCHESTRATION.md.
Full narrative, use cases, triple loop, and phasing: docs/ECOSYSTEM-VISION.md
Control, customize and own your data, agents, memory, and backup.
Discover new paths with cross-topic insights
Step 1
Sign in, invite teammates, pick who sees what.
Use Google or GitHub to open the hosted Hub. Add people with viewer, editor, or admin roles. Multi-vault setups let each team or project keep its own boundary while you stay in one account. Teams are included at no additional cost.
Hosted auth flows through the gateway; JWTs carry user id and role for API and Hub UI. Self-hosted Hub uses the same role model with data/hub_roles.json and optional invites.
Step 2
Stream messages to your inbox and pull exports into one vault.
Capture sends Slack, Discord, Telegram, or WhatsApp (via automation) straight to your inbox through the Hub. Import brings batch exports—chats, docs, tickets, audio, wallet CSVs—into the same Markdown vault. Webhooks and adapters write inbox notes automatically; you keep the files.
Capture (messages → inbox)
Hub endpoint: POST /api/v1/capture with JSON. Optional: set CAPTURE_WEBHOOK_SECRET in Hub env and send header X-Webhook-Secret.
SLACK_SIGNING_SECRET
🎮 DiscordRun a capture adapter (scripts/capture-slack-adapter.mjs, capture-discord-adapter.mjs, capture-telegram-adapter.mjs) or any automation that maps events to the capture format. Example body: {"body":"text","source":"slack"}. Full contract: Capture contract; platform wiring: Messaging integration.
Batch import (exports and files)
Importers normalize to vault notes with source, source_id, and date for idempotent re-runs. Supabase memory tables can be imported for users coming from database-centric stacks.
Step 3
Starter vault layouts and agent skill packs—before agents run wide.
Templates are example folders and notes you copy or seed into a vault. Skill packs are agent playbooks (Cursor and similar) that say how to search, which MCP prompts to use, and how outputs should look. Together they give you a sane default between importing data and letting agents work the vault.
Vault templates
Each template lives under vault/templates/<name>/ with a README and sample notes. Hosted: set KNOWTATION_HUB_URL, KNOWTATION_HUB_TOKEN, then npm run seed:template-research-lab (or business-ops, finance, engineering-team, personal-knowledge, smart-home, content-creation, education).
Skill packs
Domain skills: research-assistant, business-analyst, financial-ops. Marketing pipeline (seven): marketing-research, marketing-strategy, marketing-writer, marketing-editor, marketing-visual, marketing-distribution, marketing-analytics. Files live under .cursor/skills/packs/<name>/SKILL.md; they compose with MCP prompts and the base knowtation skill.
Step 4
Agents get the right context, not the whole vault.
Agents connect through a large MCP surface and the same CLI you use. They are guided to search narrowly, then open specific notes. Memory prompts remind them what already happened so they skip redundant work. That pattern saves tokens and improves answers.
Knowtation ships many MCP tools (search, get-note, memory store/query/consolidate, proposals, and more), resources (vault listings, media URIs, config snapshots), and prompts for workflows like briefs, meetings, and session resume. Hosted MCP adds OAuth-gated access aligned with Hub roles.
Token savings (operational layer). Beyond “search small, then open one note,” the product now wires savings into hosted and self-hosted operation: consolidation passes and quotas by plan, optional Discover inside the same consolidate run, advanced knobs (lookback, max events/topics, output token cap) persisted on billing records when hosted and in config/local.yaml when self-hosted, encrypt-aware consolidation prompts when memory encryption is on, and hosted MCP search over HTTP POST with parity fields so agents can keep payloads small in the browser path too.
search with --fields, --limit, filters → then get_note for bodiesmemory-context, memory-informed-search, resume-sessionStep 5
Re-index when content changes; compress memory; Discover cross-topic insights.
After imports or edits, indexing refreshes vectors so search stays accurate. A consolidation engine merges memory events into compact facts, verifies them against the vault, and can run an optional Discover pass that discovers cross-topic insights — patterns, tensions, and follow-ups across topics — on a schedule you control, with billing-aware limits when hosted. Discover is optional: when enabled, it enriches memory so agents load sharper, wider context in later sessions without pasting the whole vault into the prompt.
Indexer writes chunks to Qdrant or sqlite-vec. Consolidation runs consolidate, verify, and optional Discover — Discover discovers cross-topic insights by emitting insight events that connect themes a single-topic merge would miss. Cost guardrails apply throughout. Hosted mode persists advanced knobs through billing and gateway settings; Discover runs inside the same consolidate request (not a second pass count) when turned on.
npm run index; API routes under /api/v1/memory/consolidate (self-hosted Hub)Step 6
Tie the vault to GitHub for history and portability.
Connect a repository so your vault — notes and media — is backed up and versioned the way engineers already work. Your canonical story stays in plain files and commits under your control, not an opaque database export.
The Hub and bridge coordinate OAuth to GitHub, commits for backup, and (where configured) image upload paths. Proposals and review queues align with human-in-the-loop changes before writes land in the vault.
Step 7
Hosted data on ICP; or run everything yourself.
Hosted vaults can live on Internet Computer canisters with a gateway in front. Prefer your own machines? The same project runs locally with full control over config, keys, and network boundaries.
Motoko canisters store note payloads and proposal records; the gateway proxies with JWT verification and rate limits. Attestation records can be HMAC-signed and optionally anchored on-chain for audit.
hub/icp/ in the repoStep 8
Use it in the browser from anywhere; share at role granularity.
The web Hub is the friendly face: browse, search, edit, imports, settings, and billing when you use the hosted service. Team members see only what their role allows; you are not sharing a single password to a pile of notes.
Stripe-backed plans meter searches, index jobs, consolidation passes, and scale with your tier. The bridge handles vault IO, memory events in serverless deployments, and parity with self-hosted behavior where documented.
Step 9
Tags, entities, episodes, and causal chains — optional but powerful.
Optional frontmatter links notes across time and topic: projects, tags, entities, episode ids, causal chains, and follow-on relationships. Agents and filters use the same fields, so “what happened next?” stays searchable without dumping everything into the prompt.
Fields are opt-in in Markdown YAML frontmatter. CLI and MCP accept filters such as --entity, --episode, and --chain. See the spec and intention doc for the full schema and examples.
Read the full story in the whitepaper — thesis, token levers, imports, memory providers, attestation, and billing model.