Personal accounts and loose keys
Subscriptions on cards, API keys in spreadsheets and tools nobody approved. When someone leaves, the access stays.
Memory for IT
Kluco puts models, agents and the company's memory behind the same access profiles, limits and audit log. AI tools query the memory over MCP or API, and switching vendors stops being a migration.
The problem
Without knowing who uses them, what leaves the company and what it costs.
Subscriptions on cards, API keys in spreadsheets and tools nobody approved. When someone leaves, the access stays.
There is no way to say who used which model, with which data, or who changed the configuration.
If the knowledge and the agents live inside one tool, switching vendors means starting over.
Before and after
From model access to a memory that stays with the company.
| Without the company's memory | With Kluco |
|---|---|
| Without the company's memoryEach team uses whatever account it could get | With KlucoOne company chat with the models each profile allows |
| Without the company's memoryAPI keys spread across teams | With KlucoProviders are set up in one place, by whoever administers them |
| Without the company's memoryNobody knows who changed what | With KlucoAn audit log for configuration and chat |
| Without the company's memoryEach AI tool has its own knowledge base | With KlucoChatGPT, Claude, Gemini and other tools query the same memory over MCP |
| Without the company's memorySwitching vendors means migrating everything | With KlucoThe memory, the agents and the rules stay with the company |
What goes into memory
Documents come in from Google Drive, OneDrive, SharePoint, file upload, API or webhook, and become articles that AI keeps up to date.
Use cases
The most common use cases in IT, with the part of the platform that does each one.
Each group of people uses the models, agents, skills and memory its profile allows.
LLM Management and ChatGPT, Claude, Gemini and other models, all in the Chat, with the access the company sets and an audit log.
LLM Management and ChatChatGPT, Claude, Gemini and other MCP-compatible tools query the same knowledge base, each person with their own access.
BrainAn agent sorts new requests with an owner, a deadline and a priority, and a person approves before anything is saved.
AgentsThe use-case report shows, with aggregate data, what each team uses AI for and what it costs.
LLM Management and ChatInternal rules and procedures live in one knowledge base, with an owner, a review deadline and a version history.
BrainLLM Management and Chat
LLM Management gives every model one entrance: who uses it, which models, up to how much, with an audit log.
Brain · the memory
The Brain organises knowledge in a base with an owner and a review deadline. Any compatible tool queries it through the MCP server or the API.
Agents · AI agents
Each agent has an owner, approvers, per-tool rules and a budget. Every run is recorded, step by step, with its cost.
Control
The company sets up each control below in the console.
FAQ
OpenAI, Anthropic, Google Gemini, DeepSeek, Grok and OpenRouter. The company chooses which to allow and for whom.
Through the MCP server, the open standard AI tools use to connect, with access isolated per company, or through the API.
No. Kluco is a cloud service, with data isolated per company. The Security page covers the controls.
The memory, the agents and the rules stay in Kluco, outside the vendor. Switching models becomes a purchasing decision, and the whole wiki can be exported in an open format.
Next step
In the demo, we show the access profiles, the providers, the audit log and the MCP server.