See how the parts of Kluff work together, from your team’s conversations and connected tools to the security and multi-agent orchestration under the hood.
Kluff /Platform architecture How Kluff worksWhere people and agents work together. Every request starts here.
Who is asking, and what they are allowed to reach. An agent runs with the permissions of the person behind it.
A checkpoint on the way in and the way out. Every prompt and response passes through.
The engine of the platform. It plans the work, picks the model for the job, and carries out each step.
The same agents, running with nobody in the room — on a schedule, on an event, or as a flow.
Nothing happens out of sight. Sensitive steps wait for a person, and every run is traceable afterwards.
What the company already knows, available to every agent and every run above.
Knowledge carried from one piece of work into the next, held as a graph of what the company knows and how it connects.
How it runs
Every request — typed by a person or started by a schedule — takes the same path down the stack.
A request starts in a project, a topic, a Slack thread, or on a schedule that nobody has to remember.
Company memory, workspace search, and connected accounts bring in what the company already knows.
Personal data is redacted before any model call, and the request runs with the asker’s own permissions.
It plans the work, routes to the right model, and carries out each step with the tools it has been granted.
Sensitive steps wait for approval, every run is traceable, and what was learned goes back into memory.
Questions
Kluff is a workspace where people and agents share company context and get work done. Search finds it, the assistant works with you, and agents keep running after the conversation.
Search covers the workspace: projects, threads, and people, and it follows membership. Connected accounts are a separate path. An agent uses an account the company granted when the answer lives in a tool like a CRM or an inbox.
It can draft, file, update records through a connected account, build an app, change a repository on a session branch, run a flow, and work in a browser or on a Mac. Writes and other sensitive steps can wait for a person.
Admins set roles and groups. Projects and topics have their own members. Each action can be allowed, denied, or held for approval, and the decision is kept for audit.
A thread runs in Instant, Balanced, or Thinking. Kluff routes the request to the model for that kind of work. Personally identifiable information is redacted before the call, and the company context stays in Kluff.
In the browser, in desktop apps for Mac, Windows, and Linux, on iPhone and Android, in the Chrome extension, and in Slack.
Connect your tools, ask your first question in a project, and watch memory, spend, and visibility stay in one place—not scattered across personal chats.
$15 / user · Unlimited AI
@kluff build a launch dashboard from HubSpot and the Q4 budget sheet. Refresh it every morning.

Done. Signups come from HubSpot, spend from the Q4 budget sheet. It refreshes at 7:00 AM.
v2 adds the channel split you asked for.

Can we flag any channel over $40 per trial?

Added. Paid social is flagged.
It sends from your Gmail, as you, with the draft attached. Nothing else leaves the project.
Ana Chen confirmed net 45 at 9:18 AM. Your rule: every customer email waits for you.