The AI Hiveby IT Labs India
The AI Hive by IT Labs India: Shared Cognitive Memory Layer

Cognitive memory that stays with you, whichever AI you use.

Change AI vendor, or use several at once. Your company's memory stays yours and keeps working.

One governed memory for your company's people and their AI assistants, organised by organisation, project, client, team and person, permission-checked on every request, and kept up to date for everyone at once.

Updated

The memory core

QueenBox is the memory at the centre of The AI Hive.

The AI Hive is one product, the pack, made of its modules. Its memory core is QueenBox: the part that extracts, confirms, updates and disputes what your people and their AI seats know.

The rest of The AI Hive, its scopes, permission checks, approvals and audit trail, governs who may see and change that memory. QueenBox is also a product on its own. Updating memories is still maturing, so a person reviews proposed updates; the QueenBox page says what works and what does not.

  • QueenBoxThe memory core of The AI Hive, and a product on its own. In development

Read about QueenBox

The family

The AI Hive is the hive. Our other products are the colony.

Every product has its own colour and works on its own. Together they make one hive, with The AI Hive at the centre as the memory they share and a person approving what matters.

FIG. 0 · THE HIVE · SEVEN PRODUCTS, ONE COLONYCLICK A CELL
CombBase the comb: your work, indexed IN DEVELOPMENT BeeBox the bees: AI agents at work IN TESTING NectarBox the nectar: private models IN TESTING AI BeeKeeper the keeper: books and GST IN DEVELOPMENT HiveGate the visitors: enquiries to deals IN DEVELOPMENT BroodBox the brood: work tracked IN DEVELOPMENT The AI Hive the hive itself: one shared memory IN DEVELOPMENT You a person approves
  • The AI Hive · the hive itself: one shared memory In development
  • CombBase · the comb: your work, indexed In development
  • BeeBox · the bees: AI agents at work In testing
  • NectarBox · the nectar: private models In testing
  • AI BeeKeeper · the keeper: books and GST In development
  • HiveGate · the visitors: enquiries to deals In development
  • BroodBox · the brood: work tracked In development
  • You · a person approves

Each product also works on its own. Links between them are marked built or planned on each product's page.

  • The AI HiveThe hive itself. One governed memory for your people and every AI tool they use. In development
  • CombBaseThe comb. Reads your git, Slack, Drive and mail into one index on your own box; it is meant to give The AI Hive its sources (planned). In development
  • BeeBoxThe bees. Your AI agents work together in rooms; what they learn is meant to reach The AI Hive (planned). In testing
  • NectarBoxThe nectar. Private AI models that run in house, planned as the models the other products use. In testing
  • HiveGateThe visitors. Enquiries from email and WhatsApp become contacts and deals. A separate product today. In development
  • AI BeeKeeperThe keeper. Bookkeeping and GST returns for Indian businesses and their CAs. A separate product today. In development
The problem

You are paying for intelligence and getting amnesia.

You have already invested in AI. Your teams use it daily. Yet most of that intelligence evaporates every time a session ends.

Most models have memory. Almost none have governed flow.

Without a shared, governed layer, every assistant is a stranger to your projects, your clients and your decisions. The people who do remember are the ones who eventually leave.

What happens now and what it costs
What happens nowWhat it costs
Each AI session starts coldRepeated context-setting and wasted time
Knowledge stays with individualsStaff turnover erases know-how
Agents cannot coordinateDuplicate or conflicting work
No record of what the AI knewHard to explain decisions in regulated work
Personal and team data are mixedPrivacy and leakage risk
How it works

Memory with structure: scopes, and three governed flows

The AI Hive organises what your company knows into scopes and moves knowledge between them under clear rules. Nothing reaches a shared scope by accident.

FIG. 1 · MEMORY SCOPES AND FLOWSSEVEN SCOPES
Memory scopes and the three flows Memory is organised from organisation at the top, through project and client, team, user and agent. Personal memory sits apart and is private. Up arrows show promotion with approval, down arrows show inheritance, and the across arrow shows team knowledge being synthesised into project knowledge. Organisationcompany-wideProjecta programmeClientkept apartTeama group of peopleUserone personAgentthat person's AI appPersonalprivate notes, never promotedDOWN · INHERITUP · PROMOTEACROSSdefault offgovernance approvesproject lead approves3 people confirm Memory scopes and the three flows Memory is organised from organisation at the top, through project and client, team, user and agent. Personal memory sits apart and is private. Up arrows show promotion with approval, down arrows show inheritance, and the across arrow shows team knowledge being synthesised into project knowledge. Organisationcompany-wideProjecta programmeClientkept apartTeama group of peopleUserone personAgentthat person's AI appPersonalprivate notes, never promotedDOWN · INHERITUP · PROMOTEUP · governance approvesACROSSdefault offUP · project leadapprovesUP · 3 people confirm
Memory scopes and the three flows: up with approval, down by inheritance, across by approved synthesis.

Up: promotion Available now

Validated insights move up only with approval. To Team when at least 3 people independently confirm it, to Project by a project lead, to Organisation by governance. Personal memory is private and is never promoted.

Down: inheritance Available now

When a higher scope changes, every affected person's AI gets the update. New members inherit context immediately.

Across: synthesis Available now

Team knowledge can be merged into project knowledge. It is off until an admin switches it on, and always needs approval.

See how it works in depth

Key capabilities

Everything a shared memory needs to be trusted

These capabilities are built. Most are verified in our own simulation; those marked In testing are still being validated. The full list, with what is still on the roadmap, is on the features page.

Context pack Available now

What an AI app receives at the start of a task: the memory inherited for its place, with a manifest for cheap refresh. Less repeated context-setting.

Hybrid search Available now

Meaning plus keyword search, with every result re-checked against permissions before it is returned.

Governed writes Available now

Nothing reaches a shared scope without a role, a time-limited grant or an approval.

Client walls Available now

A client's memory is only returned while working on that client or a project linked to it. Built so that it does not reach another client; checked by our own tests.

Audit log Available now

Every allow and deny is recorded with who, where, which app and which model. "What the AI knew" shows the memory versions behind each answer.

Multi-vendor AI access In testing

Change AI vendor, or use several at once: ChatGPT, Gemini, Copilot, Cursor, Codex, local models and more can connect over MCP and REST. Claude Code and Claude Desktop are available now. Built and in testing; anything that does not pass testing will be removed.

Agents working together In testing

AI agents coordinate one task in rooms with an organisation lobby and claims, under the same permissions and audit as memory.

The AI Hive on your phone In testing

The web console installs on Android and iPhone from the browser, with opt-in push notifications built so that they carry no memory text. Built and in testing. Anything that does not pass testing will be removed.

Read-only connectors In testing

Jira Cloud, PostgreSQL views, IMAP mailboxes and Git repository addresses feed proposed facts into an approval queue. Connectors only read; The AI Hive sends data out only where you set it (webhooks, mail, push). Tested on test copies, not yet on live accounts. Built and in testing. Anything that does not pass testing will be removed.

Browse all features

Built for governance

Deny by default, enforced where the data lives

Row-level securityPostgreSQL row-level security on every table, so tenant isolation is enforced by the database.
Deny-by-defaultA permission service that checks every request. Built so that an agent has no more rights than its user; checked by our own tests.
Audit in the transactionEach audit record is written in the same transaction as the change it describes.
Data, not instructionsMemory is returned labelled as data. Text that looks like instructions is flagged and cannot be bulk-approved.

Read about security and governance

Who it is for

A fit when many people and many agents share the same work

A strong fit

  • Mid-size and large companies where many people and AI agents share projects
  • Consultancies and suppliers with many clients that must be kept apart
  • Companies where answers must be traceable, including regulated fields such as engineering, shipbuilding, automotive, finance and health; no compliance certification yet
  • Companies using several AI tools
  • Long programmes with staff turnover

Probably not a fit

  • Very small teams
  • Companies that barely use AI
  • One-off pieces of work

If that is you, a simpler tool will serve you better, and we would rather say so now.

What you need to run it

Planned: run by us in your cloud, or on your own server

The AI Hive is in development and tested in our own simulation. These options are planned and not offered yet; for a future pilot, where it runs would be agreed in the scoping workshop. Your data stays in your infrastructure, and fact extraction uses a small model on your own server.

Run by us in your cloud

Our recommended first step. The plan is that we operate The AI Hive inside your own cloud account.

Planned: not offered yet

Self-hosted on your premises

The plan is that you run it yourselves with Docker Compose. A customer install package is not offered yet. An air-gapped bundle is on the roadmap.

Docker Compose: planned, not offered yet

Air-gapped bundle: roadmap

Hosted by us

We run it for you. This option is not available yet.

Roadmap

From your side we ask for a sponsor who can decide, one or two teams who use AI regularly, access to the systems you want connected, and a named person to approve promotions. Deployment options and what we ask of design partners

How a pilot would work

  1. 01Scope. A scoping workshop agrees your memory scopes, who approves what, the success metrics, the systems and AI apps to connect, and the deployment option.
  2. 02Deploy and connect. We install The AI Hive, create your organisation structure, people, roles and grants, and connect the agreed systems and AI apps.
  3. 03Run with a first group. A first team uses shared memory in daily work. Approvals, promotion and the audit log are exercised for real.
  4. 04Review. We review the agreed metrics together and decide on next steps. Stopping is a valid outcome.

The plan is agreed per pilot. Cost is scoped per pilot, so talk to us. Pilot programme

Ready today / next

What is built, and what is not

The full lists are on the roadmap page. Nothing here is a promise of a date.

Ready today

Available now

  • Seven memory scopes with promotion, inheritance and synthesis
  • Context pack, hybrid search and versioning
  • Governed writes, client walls and the audit log
  • Claude Code and Claude Desktop

In testing

  • Multi-vendor AI access over MCP and REST
  • Spaces registry and space mapping
  • Agents working together in rooms
  • Read-only connectors: Jira Cloud, PostgreSQL views, IMAP mailboxes, Git repository addresses (tested on test copies, not yet on live accounts)
  • The AI Hive on your phone
  • Microsoft 365, Google Drive and GitHub connectors

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

Next

Roadmap

  • SSO with Microsoft and Google, and SCIM
  • Customer-managed keys (BYOK)
  • PII detection and masking
  • Hash-chained, exportable audit
  • Retention policies per scope
  • Helm chart and air-gapped bundle
  • Hosted option
  • Independent penetration test and SOC 2 readiness work

All features · Full roadmap

In development

Honest status

The AI Hive is in development, tested in our own simulation. Features marked In testing are built and being validated; anything that does not pass testing will be removed. We are looking for a small number of design partners. No outside team uses it yet. This is not a self-serve product, and the roadmap is published openly so you can see what is built and what is not.

See the roadmap · How a pilot would work

Memory is not a feature. It is the foundation.

See how The AI Hive could work in your organisation

We are looking for a small number of design partners for a first pilot. No outside team uses it yet. Tell us about your teams and the AI tools they use, and we will scope a pilot together.