Straight answers.

CombBase connects the places where your company's work lives (git hosts, issue trackers, chat, mail, drives, meeting transcripts and databases) and keeps one index of them on your own box. AI agents then ask it where something is and read the allowed items, each time for one person. It only reads; it never writes into your tools.

Companies whose work is spread across several tools and that want AI agents to work from the real record without opening everyone's data to every agent. It suits organisations that have someone who can create read-only access in their tools and that want the data kept on their own box. It is not a finished product to buy off the shelf today, and it is not for AI that must write into your systems, because it never does.

Code and issues: GitHub, GitLab, Bitbucket, Jira, Linear, Confluence and Notion. Chat: Slack and Microsoft Teams. Mail: Microsoft 365, Gmail for organisations and IMAP. Drives: Microsoft 365 and SharePoint, Google Drive for organisations and personal Google Drive. Meetings: Google Meet, Microsoft Teams and Zoom transcripts. Databases: PostgreSQL, MySQL or MariaDB, and SQL Server. All are built and in testing; none has run against a real company account yet.

No. Every connector is read-only. At setup CombBase checks that the token or login you give it cannot write, and it refuses one that can. Confidential issues, security-level items, code, private chats and direct messages, recordings and attachments are not read.

On your box, which runs in our cloud or at your office, with its own database and its own credential vault. Your keys are entered on the box and never pass through IT Labs India. IT Labs India manages accounts and seats from your IT Labs India account and sees counts and health, never names or content. Admins and organisation accounts manage connections and seats but never read content.

Only what the person it works for may see. Each read is checked against that person's seat and their own switches at the moment of the read, so removing access takes effect on the next request. Results come back as labelled data with their source, never as instructions, and mail is labelled with its DKIM and DMARC result.

CombBase is in development. The connectors, the index, the vault, the per-person checks and passkey sign-in are built and have been tested against simulated services. Nothing is in customer use yet. Next come first runs against a real company's accounts in a pilot, and security hardening for production use before any go-live.

A box, hosted by us or at your office; a person on your side who can create read-only access in the tools you want connected (for example a Microsoft 365 or Google admin); a short list of which repos, channels, mailboxes and drives to include; and the people who will get seats. Meeting transcripts also need each organiser's opt-in. The size of the box is agreed when we scope the pilot.

We do not give a number before we have scoped your tools. How long a pilot runs, and what counts as success, are agreed with you up front. Because no real company account has been connected yet, the first pilot is also the first real test, and we say so at the start.

Removing a connection stops access on the next request and destroys its credential. Its stored items are hidden at once and then purged. For personal Google Drive, removing the connection also revokes the grant at Google.

It is built for AI agents: BeeBox sessions, AI apps and bots, each acting for one person, and it is designed around open standards (MCP and REST). BeeBox and The AI Hive are the IT Labs India products it is meant to feed. Which outside AI apps connect is something we confirm in the pilot.

Cost is scoped per pilot, per organisation, so please talk to us and we will work it out with you.