Search IT Labs India

Didn't find it? Ask in plain words. Ask us a question
CombBaseby IT Labs India
In developmentCombBase by IT Labs India

Your work places, in one index on your own box.

CombBase reads your git, Slack, Drive, mail and more, read-only, and keeps one index that your AI agents can use for one person at a time.

Book a pilot All features →
SOURCES · READ-ONLY git Slack Drive mail ONE INDEX on your own box AI agent one person

Who it is for

Not for you if you need a finished product today, if AI must write into your tools (CombBase never does), or if only one or two tools matter.

  1. 01Your work is spread over git, issue trackers, chat, mail, drives and meetings, and your AI agents cannot see it, or you cannot control what they see.
  2. 02You want AI agents to work from the real record, but you will not give them write access to your tools or open everyone's data to every agent.
  3. 03You want the connections and their keys on your own box, with someone you trust able to see what is connected and how fresh it is.

How it works

FIG. 2 · FROM YOUR TOOLS TO ONE INDEXREAD-ONLY
Your tools On your box Who reads it Code and issues git hosts, Jira, Linear, wikis Chat Slack, Microsoft Teams Mail Microsoft 365, Gmail, IMAP Drives SharePoint, Google Drive Meetings Meet, Teams, Zoom transcripts Databases PostgreSQL, MySQL, SQL Server Read-only connectors The token is proved unable to write, at setup. Only the repos, channels, folders and views you pick. Credential vault Encrypted on your box. Shown once, never in logs. Credentials stay on your box. keys One index Systems and spaces Which connection holds it Who may read each one How fresh each one is Permission-aware Checked per person, at every read. Switches can narrow it, never widen it. Text comes back as labelled data with its source, never as instructions. BeeBox AI agents, each working for one person The AI Hive gets its sources from your index Other AI apps and bots, over MCP and REST Your tools Code and issuesChatMailDrivesMeetingsDatabases On your box Read-only connectors Proved unable to write Credential vault Encrypted. Shown once, never in logs. Credentials stay on your box. One index Permission-aware: checked per person, at every read. Who reads it BeeBox, The AI Hive, other AI apps and bots

Dashed boxes are your own tools. Credentials are entered on the box and never pass through IT Labs India.

CombBase connects to each tool with a read-only credential kept in a vault on your box. It records where your work lives and keeps the index fresh. When an AI agent asks, CombBase answers only for the person that agent works for, and only with what that person may see.

Main features

All features →
One index of where the work livesIn testing

Your systems, and the repos, channels, mailboxes, drives, meetings and databases in them, with who may read each and how fresh it is.

Reads for one person, never moreIn testing

An AI agent sees only what the person it works for may see, checked at every read.

Code and issuesIn testing

GitHub, GitLab, Bitbucket, Jira, Linear, Confluence and Notion, read-only. Code itself is never read.

Meeting transcriptsIn testing

Google Meet, Teams and Zoom, only for organisers who opted in, with consent built in.

Credentials in a vaultIn testing

Encrypted on your box, shown once, never in logs.

Isolation between clients and peopleIn testing

One client's data never reaches another, and admins manage connections without reading content.

Built and in testing. Anything that does not pass testing will be removed.

Security and where your data lives

  • Your box runs in our cloud or at your office, on its own, with its own database and credential vault.
  • Keys are entered on the box, straight into the vault. They never pass through IT Labs India and never appear in logs.
  • IT Labs India manages accounts and seats from your IT Labs India account and sees counts and health, never names or content.
  • Connectors only read. Confidential issues, code, private chats, recordings and attachments are not read.
  • Admins and organisation accounts manage connections but never read content. Support reads only with a person's time-boxed yes.
  • Not yet independently audited or penetration tested, and we claim no compliance certification. Security hardening for production comes before any go-live.

What you need to run it

  1. 01A box. Hosted by us in our cloud, or at your office. It runs on its own, with its own database and vault. Its size is agreed when we scope the pilot [CHECK: sizing is not stated in the source].
  2. 02Read-only access in your tools. A person on your side who can create a read-only token or app in each tool you want connected, for example a Microsoft 365 or Google admin.
  3. 03A list of what to include. The repos, projects, channels, mailboxes, folders, drives and database views CombBase may read. It reads nothing else.
  4. 04People and their AI agents. Who gets a seat. Each person enrols a passkey from an invitation. Meeting organisers also give their opt-in.
  5. 05An outbound connection. The box calls out to the tools you connect. Nothing needs to reach into your network from outside.

How a pilot works

Because no real company account has been connected yet, the first pilot is also the first real test. We say so at the start.

  1. 01Talk and scope. A free consultation. We agree which tools, which people and which AI agents are in the pilot, how long it runs and what counts as success. Cost is scoped per pilot.
  2. 02Set up the box. We prepare your box, in our cloud or at your office, and link it to your IT Labs India account.
  3. 03Connect, read-only. Your admin creates a read-only token in each tool and enters it on the box, straight into the vault. CombBase checks that the token cannot write.
  4. 04Choose what is read. You pick the repos, channels, mailboxes, drives and views. People enrol passkeys. Meeting organisers opt in.
  5. 05Fill the index. The index builds. You check what it found and how fresh it is, and your AI agents ask it questions, for one person at a time.
  6. 06Review and decide. We look at what worked, widen or remove connections, and agree the next step together.

Ready today, and what is next

In testing Built, tested on simulated services

  • The read-only connectors for code and issues, chat, mail, drives, meeting transcripts and databases
  • The index of systems and spaces
  • Reads for one person, checked at every read
  • The credential vault and isolation between clients
  • Passkey sign-in and onboarding

Built and in testing. Anything that does not pass testing will be removed. Nothing is in customer use yet, so nothing is marked "Available now".

Roadmap Next

  • First runs against a real company's accounts, in a pilot with you
  • Security hardening for production use, before any go-live

Works with

BeeBoxits AI agents read your work data through CombBase The AI Hivemeant to take its sources from your index [CHECK]

Try CombBase with your team

A pilot on your own box, scoped with you. Talk to us about cost.

Book a pilot