From request to evidenced result.
Botster connects a language model, company knowledge and permitted tools in a controlled flow. Every run respects permissions and leaves behind sources as well as an audit entry.
The control loop
Every request runs through the same controlled loop – from understanding to evidence. Scroll through the stations.
-
Understand
Classify the request, the user role, the tenant and the permitted data sources.
-
Know and act
Search for relevant evidence; only call tools that are approved for this context.
-
Control and evidence
High-risk actions wait for approval; sources, decisions, calls and results remain traceable.
The model: selected, measured, self-hosted
Botster’s default is a self-hosted model on Swiss infrastructure. The selection is based on an in-house benchmark with 27 models, real cases and four languages. We also score each model on knowing when not to call a tool.
Knowledge: RAG with evidence
PDF, Word, Markdown and text are processed with tenant separation and searched together in one hybrid search. Answers carry source evidence; quality is measured in DE, FR, IT and EN.
Tools: skills on a leash
Skills bundle the permitted tools for business systems and flows. Risk class, role and autonomy level determine what is executed; your own systems can be connected in a controlled way.
Governance and operations
Inputs, tool results and outputs are checked; actions end up in the exportable audit trail. Details on data protection, hosting and approvals are on Trust.
Common questions about the technology
What is an agentic AI platform?+
An agentic AI platform connects a language model with knowledge, tools and clear permissions. Unlike a plain chat, it can plan multi-step tasks and carry out permitted actions. What matters for enterprise use are sources, roles, approvals, logging and controlled limits.
Which systems can Botster connect to?+
Botster connects knowledge sources and business systems through controlled skills and APIs. Areas already covered include company knowledge, document processing, ITSM search and troubleshooting, and defined maintenance and operations flows. Which integration can be used productively is assessed per use case. A general interface capability is not automatically advertised as a finished product integration.