Functioning of Klax!
Every agent runs on the same platform, reachable from chat, your own systems, or a schedule, with each company's data and execution kept separate by default.
User
Tasks arrive through the chat function, your own systems or on a schedule.
Klax! AGENT PLATFORM
Chat Interface
Write in your own words what your AI agent should do.
API Access
For all systems you use.
Scheduled Tasks & Triggers
Recurring runs and trigger-based automation.
The operating space
Interprets the request, plans the tasks, calls the systems it needs, and delivers the answer.
Agents
Tasks specific assistants your team can configure and deploy.
Agent Builder
From prompt to production: build, preview, iterate and deploy.
AI Models
Multiple providers, especially selected per agent and task.
Knowledge Base
Your documents, searchable by meaning, not only keywords.
Skills
Modular instructions for agents to process logical and recurring tasks.
Tools
Connection to specific tools of a system for the completion of concrete tasks.
Integrations
Direct access to the systems your company uses.
Memory
Context that moves and is retained across different conversations.
Files & Documents
Reads and creates documents, images and datasets.
Code Sandbox
A safe and isolated workspace for analysis and generated code.
Projects
Scopes context into narrow sessions to focus work.
Trust & Operations
Applies to every layer above
CONNECT TOYour Content & Systems
- Document libraries
- Cloud drives and storage
- Business applications
- Internal APIs and databases
How a request moves through the platform
Work arrives. You ask a question in the chat, a system calls your agent, or a scheduled job starts on its own.
An agent takes it up. The operating space loads the right agent, with its instructions, its permitted tools and its AI model, then works out what the request actually needs.
Skills are called as needed. The agent searches your knowledge base, invokes a tool, reads a connected system, or runs code in the sandbox, often several of these in sequence, deciding each step from what it learned in the last.
An answer comes back. The result returns through the same channel it arrived on, with its sources and its work recorded.
Security Boundary
Every step above is scoped to a single organisation. Data, credentials, memory, and code execution are separated per Organisation, and generated code runs in an isolated environment with no access to anything it was not explicitly given.