Billion random sources,
one lens.
LensHub is the data plumbing for AI agents — one place where every doc, ticket, thread, repo, and spreadsheet is classified, scored, and handed to any AI agent over MCP.
Your company's knowledge lives everywhere.
Slack threads. Jira tickets. Confluence pages. GitHub READMEs. Notion docs. Sales playbooks. Finance spreadsheets. None of it reaches your agents.
Same question.
Two very different agents.
Watch the same prompt run against an agent without LensHub, and one with it. The work isn't in the model — it's in what the model can see.
The product.
Boring on purpose.
No futuristic mockups — this is the actual UI. A dashboard for context health, a chat for agent-cited answers, and a connector panel that does the boring sync work.
Questions that used to take a week,
answered now.
LensHub pulls your security policy, audit evidence, incident runbooks, and pen-test results. Your agent fills in 94% of sections automatically.
The agent reads GitHub release notes, Jira tickets, Figma specs, and existing docs — producing a structured draft ready for review.
Connect Salesforce, Slack CS channels, Jira, and the renewal playbook. Get a root-cause analysis with evidence, not opinions.
One context layer.
Four ways to reach it.
Add LensHub as an MCP server with one command. Works with any agent that supports the Model Context Protocol.
Drop the OpenAPI schema into your Custom GPT action config. Works with any OpenAI-compatible tool-calling setup.
Use the LensHub chat UI directly — no agent setup required. Ask questions, get cited answers from all your connected sources.
Connect LensHub to n8n, Zapier, or your own agent runner. Schedule daily briefings, alerts, and digests.
Not a search box.
An operating system for context.
Every other “AI knowledge” tool just indexes your docs. LensHub is the layer your whole org runs its context through — with the rules, structure, and observability a production system needs.
Built for production.
Not just demos.
18 connectors.
One sync.
Self-host today.
Managed when you're ready.
The self-hosted version has been running in production since January 2026. Move to managed when you want someone else to handle the infra.
- 1k contexts
- 100 memories
- 5k queries / mo
- 50k contexts
- 10k memories
- 100k queries / mo
- All connectors
- 10 human users
- 500k contexts
- 100k memories
- 1M queries / mo
- SSO
- Unlimited users
- Unlimited everything
- Audit logs
- DPA
- Dedicated CSM
Questions, answered.
How is this different from just using RAG or a vector database?
A vector database stores embeddings — it doesn't know which sources are stale, contradictory, or out of scope for the requesting user. LensHub adds health scoring, access control, deduplication, feedback loops, and versioning on top of the retrieval layer. You get production-grade context, not just search.
Does LensHub see our data?
Self-hosted: never. Everything runs in your VPC — your data never leaves. Managed: data is processed in your dedicated tenant. We will never train on your data.
How do you guarantee an agent doesn't leak data a user shouldn't see?
Permissions are enforced at four layers. (1) ACL mirroring: when we sync a source we ingest its permission metadata alongside the content — page restrictions, channel membership, repo collaborators, sharing scopes — and store it as a separate source-of-truth ACL graph. (2) Query-time enforcement: every search and agent query carries the requesting user's identity; we resolve their effective permissions across all connected sources and filter results before they leave the database. If a user can't see a Confluence page directly, neither can their agent. (3) Audit-ready logging: every retrieval is logged with user, agent, query, returned context IDs, and timestamp — exportable to your SIEM (Splunk, Datadog, S3). (4) Continuous reconciliation: ACL changes propagate within minutes, not on the next full sync — revoke someone's Notion access and their agent loses it before their next query.
Where does my data live, who can access it, and what happens when we leave?
Where it lives: self-hosted means your data never leaves your VPC. Managed runs in your chosen region (US or EU), encrypted at rest with AES-256 and in transit with TLS 1.3, with separate encryption keys per tenant. Who can access it: self-hosted, only your team. Managed: no LensHub employee has standing access — production access requires a JIT approval flow with two-person sign-off, fully audited. What happens when you leave: full data export at any time — every context, version, memory, and audit log in a documented JSON/SQL format. After cancellation, all customer data is purged within 30 days with a cryptographic deletion certificate signed by our SRE team. No exit fees, no proprietary formats, no lock-in.
Which agents does it work with?
Any agent that supports the Model Context Protocol (MCP) — Claude, Claude Code, Cursor, Windsurf — or the OpenAI Actions schema (ChatGPT, Custom GPTs). The REST API works with anything else.
How long does setup take?
The self-hosted version deploys in about 20 minutes with Docker Compose. Managed onboarding takes a short call to configure your connectors and access scopes. Most teams have their first agent query working within an hour.
Billion random sources,
one lens.
LensHub has been running in self-hosted setups since January 2026. We're now opening up a public managed service — sign up to be among the first to try it.