Features, and where each one stands.
Every feature below is built and has been tested against simulated services. None has yet run against a real company's accounts, so none is marked "Available now".
Reading for AI agents
Who reads the index, and how far they can see.Every read is made by an AI agent working for one person, and it sees only what that person may see. The check happens at the moment of the read, with no cached permissions. Item text comes back as labelled data with its source, never as instructions.
For each organisation, CombBase keeps an index of your systems and the spaces in them: repos, projects, channels, mailboxes, drives, meetings and databases. It records which connection holds each one, who may read it and how fresh it is. Meetings, mail and databases are always restricted; other spaces are open or restricted by the tool's own signal.
Built and in testing. Anything that does not pass testing will be removed.
Connectors (read-only)
Each connector reads and never writes. Every one is built and tested against simulated services, and none has yet run against a real company account.Issues, pull or merge requests and comments from GitHub, GitLab and Bitbucket, plus Jira, Linear, and Confluence or Notion pages. Each connection uses a read-only token, and CombBase proves at setup that the token cannot write. Only the repos, projects, teams or pages you choose are read. Confidential issues, security-level items and code are never read.
Channel messages from Slack and Microsoft Teams, read by a read-only app. Private chats and direct messages are not read.
Microsoft 365 mail, Gmail (organisation) and IMAP mailboxes. Only the mailboxes, folders and sender domains you choose are read. Each item carries its DKIM and DMARC result, so an AI agent can tell forged mail from genuine mail.
Microsoft 365 and SharePoint drives, Google Drive for organisations and personal Google Drive. Text-like office files up to 5 MB from the sites, libraries or drives you choose. Personal Google Drive connects with the person's own sign-in. Shared drives and "shared with me" are read only if you opt in. Removing the connection revokes the grant at Google.
Transcripts of Google Meet, Microsoft Teams and Zoom meetings, only for organisers who have opted in. An admin enters an opt-in date per organiser: no date means never read, and meetings before the date are never read. A transcript with anyone from outside the organisation is left out. Recordings, chat and notes are never read.
Rows of the views you choose in PostgreSQL, MySQL or MariaDB, and SQL Server, through a login that CombBase proves is read-only. It reads views, never tables, refuses a login that could write or reach other servers, and puts a time limit on every query.
Built and in testing. Anything that does not pass testing will be removed.
Security and control
How your keys, your data and your people are kept apart.Keys and tokens are encrypted in a vault on your box, are never shown again after entry, and are decrypted only for one run. They never appear in logs, error messages, audit records or the management channel.
Every table in the database is fenced by forced row-level security, so one client's data never reaches another. A person's rows are fenced per account and shared rows per place membership. Admins and organisation accounts manage connections and seats but never read content.
People sign in with passkeys, enrolled from an invitation, and can see and end their own sessions. A lost passkey is reset only with a second person's approval. Accounts and seats are managed from your IT Labs India account.
Built and in testing. Anything that does not pass testing will be removed.
See it on your own tools
A pilot on your own box, scoped with you. Talk to us about cost.