Features: AI workflows, agents and knowledge without developers
A platform for operational AI use: from chat with tools to recurring workflows and a knowledge base with sources, all the way to your own AI endpoints, operated sovereignly from Austria.
Habicht is a platform where business teams build recurring AI workflows themselves: with a visual builder, no code. From chat through multi-step workflows and AI agents with tools to a knowledge base with sources and your own AI endpoints. Same input, reliably the same result.
Chat and AI agents that operate tools.
Questions in natural language, answers with sources. AI agents can connect tools and carry out tasks in multiple steps. Before risky actions the system asks back. Control stays with the human.
Workflows & apps: clicked together, not coded.
Build once, everyone uses it: form → read document → search knowledge → review → approve, clicked together in a visual editor. An AI co-author suggests steps and fields but never applies anything automatically. Ready-made templates and an internal catalogue that only holds approved apps.
An assistant that does everything does nothing well.
A Habicht assistant is not a single prompt trying to do everything at once. It consists of steps that share the work: one reads the document, one checks it against your rules, one writes the result, one obtains approval. Every step is individually traceable and individually auditable. That is exactly why results are reliably repeatable in format and sequence, and exactly why a chat window is not a process.
For technical stakeholders: corresponds to mixture-of-agents patterns; steps can be versioned and logged individually.
Not every task needs the largest model.
In Habicht you decide per work step which AI model does the computing, and where it computes. The step that reads the client file runs on the local model on your own premises; the step that turns it into a standard letter may use a larger model in the EU. Sovereignty becomes something you set per step instead of once for the whole company. As a side effect, costs go down, because a small model is enough for simple tasks. And when a better model appears, you swap it in: the workflow stays as it is.
For technical stakeholders: model routing at step level, OpenAI-compatible interface, external tools connected via MCP.
Knowledge base with sources, down to the PDF page.
Answers rely on your own documents, with sources down to the right page in the PDF. Upload files (incl. text recognition), connect websites and SharePoint/OneDrive, and control fine-grained who may see what, with a “who sees what” preview.
Every answer with its source, down to the page in the PDF.
Your own AI endpoints and an embeddable chat widget.
Provide approved AI workflows as your own AI endpoint (OpenAI-compatible interface) or as an embeddable chat widget for your website, with the same permissions and evidence as internally. External tools connect through open standards such as MCP.
SSO, white-label and three operating models.
Sign-in via SSO (Microsoft 365, OIDC, SAML), white-label look, operation on-premise, hybrid or in the EU cloud.
Data protection & complianceThree examples from practice
Read client files, check against internal templates. Confidentiality stays preserved.
Pre-sort applications in a structured way, with evidence and processed sovereignly in the EU.
A consistent quote from key figures: same format, every time.
See Habicht in your own environment.
A short demo, tailored to your use case.