One customer, told in full: what the team needed, what we built and what is different now.
„When it comes to AI solutions, we could not be working with a better team than aigentcy, and we can not wait to have them work on a number of other valuable opportunities.“
Stephan Hostert CEO, Steffen Holzbau S.A. Tell us which systems your team works in and where the time goes. We walk you through eokit with those in mind.
eokit is designed to be natively GDPR-compliant. It runs in the EU or inside your own network, and prompts are checked for personal data before they can go to an external model. We provide a data processing agreement and a list of subprocessors.
Trust centerWhere you choose to run eokit: in your own data centre, in our EU cloud in Germany or Luxembourg, or in your own cloud account. It is not copied to other regions.
Hosting optionsYes. You describe once how your company writes, and drafts follow that tone. You can also add your logo and colours.
Exactly the people who can open the document today. eokit uses the permissions from your directory and file systems, so people get answers only from documents they are allowed to open.
Your documents stay where they are, because eokit does not move them. We remove our components and can hand over your activity logs.
A digital team member with one job. It knows which systems to read, which steps to follow and what to hand back, for example a report or a draft.
Yes. Someone who knows the task describes it in plain words, eokit sets up the agent, and you check it before it runs.
The one you choose: a self-hosted model, a model from an EU provider or a large commercial model. Each department can use a different one. Access rights stay the same.
Reading and drafting happen automatically. Sending, booking or changing a record needs a person's approval, unless you decide otherwise. Every step is logged.
Workflows take on recurring tasks with a clear result, for example writing weekly reports, preparing reminders, summarizing meetings or comparing quotes. Your team decides how the agent works and what a good result looks like.
A workflow starts on a schedule, when something changes in a connected system, or when someone asks in the chat. You choose the trigger that fits the task.
Yes. You can run workflows outside working hours, for example for large monthly reports. Actions that need approval still wait for the person in charge.
The person in charge is told about the error and its cause. The log shows which steps ran and where the run stopped.
Every run is logged. You see which information the agent used and what came out. Your team checks whether the result meets its guidelines. You decide which actions also need approval.
eokit has connectors for SharePoint, Google Drive, Outlook and Gmail. Other tools connect through MCP servers. Which triggers and actions are available depends on the connector and on existing access rights.
eokit is designed to be natively GDPR-compliant. It runs in the EU or inside your own network, and prompts are checked for personal data before they can go to an external model. We provide a data processing agreement and a list of subprocessors.
Where you choose to run eokit: in your own data centre, in our EU cloud in Germany or Luxembourg, or in your own cloud account. It is not copied to other regions.
Yes. You describe once how your company writes, and drafts follow that tone. You can also add your logo and colours.
Exactly the people who can open the document today. eokit uses the permissions from your directory and file systems, so people get answers only from documents they are allowed to open.
Your documents stay where they are, because eokit does not move them. We remove our components and can hand over your activity logs.
A digital team member with one job. It knows which systems to read, which steps to follow and what to hand back, for example a report or a draft.
Yes. Someone who knows the task describes it in plain words, eokit sets up the agent, and you check it before it runs.
The one you choose: a self-hosted model, a model from an EU provider or a large commercial model. Each department can use a different one. Access rights stay the same.
Reading and drafting happen automatically. Sending, booking or changing a record needs a person's approval, unless you decide otherwise. Every step is logged.
Workflows take on recurring tasks with a clear result, for example writing weekly reports, preparing reminders, summarizing meetings or comparing quotes. Your team decides how the agent works and what a good result looks like.
A workflow starts on a schedule, when something changes in a connected system, or when someone asks in the chat. You choose the trigger that fits the task.
Yes. You can run workflows outside working hours, for example for large monthly reports. Actions that need approval still wait for the person in charge.
The person in charge is told about the error and its cause. The log shows which steps ran and where the run stopped.
Every run is logged. You see which information the agent used and what came out. Your team checks whether the result meets its guidelines. You decide which actions also need approval.
eokit has connectors for SharePoint, Google Drive, Outlook and Gmail. Other tools connect through MCP servers. Which triggers and actions are available depends on the connector and on existing access rights.
Bring your own systems, keep your own rules.
Write a few lines, and we will get back to you.
Welcome, I'm eo
I live inside eokit and help your team find, write and act. Tap me anytime to get around.
