eacks is a Czech company that cleans up business and public-sector data and connects it safely to AI agents. It also audits AI agents for risk and builds custom systems, with a working MVP in 30 days.
The agent drafts, a person approves. Your data and your accountability stay with you.
The gate between the agent and your data. If it is not on the list, the agent cannot do it.
May
Read selected sources and draft. Write only allowed actions, and only after approval.
May not
Delete, send anything out, change permissions, read outside its scope.
Record
Who, what, when and in which role. Model in the EU or on-premises.
Hover over or click a step · illustrative diagramWe promise neither full automation nor savings up front.
How do you connect an AI agent to company data safely?
Through a connector with rules, roles and a log that is read-only by default. The agent may only take actions on an allow-list, every access is logged and nothing irreversible happens without a person. Writing is an exception you switch on. The model runs locally, or in the cloud in an EU data centre with a contractual ban on training on your data. We clean the data before connecting it. A pilot on one workflow takes 4–6 weeks and typically costs CZK 150,000 (range CZK 120,000–160,000). Prices valid as of October 2026.
How it works
Three steps. A person always takes the last one.
We start with the data, not the model. Most disappointment with AI comes from agents reading duplicates, old versions and scans without text.
01
Data audit and clean-up
We find out where your data lives and what shape it is in: duplicates, old versions, code lists, scans without text (OCR). From invoices and files we pull the fields the workflow needs. The result is a clean, documented dataset that stays yours.
02
MCP connection with rules
The agent sees only what it is allowed to: read-only access, an allow-list of actions, roles and a record of every access. Model in the EU or on-premises.
03
A person approves
The agent proposes; your person confirms, corrects or rejects. Nothing irreversible happens without a person.
Fields pulled from documents
Invoice
supplier, variable symbol, amount, date, due date
File and document
reference number, subject, deadline, status, where it belongs
Review
clear fields in a batch for approval, unclear ones in a queue
Before anything is matched, the fields are pulled out. The draft goes to a person. Nothing is written into the system until they have checked it.
Data readiness check
Is your data ready for AI?
Six questions, one minute. The result is indicative and is not sent anywhere; it shows whether to start with a pilot or with a clean-up.
This is not an audit. Only the workflow analysis shows the real state.
Packages
How many workflows, and how fast.
The Pilot fee is deducted from Standard if you continue within 3 months. Connectors, documentation and cleaned data stay yours even without Operations.
Package · 1 workflow, 1–2 data sources
Pilot
Proof on a single workflow
CZK 120,000–160,000
one-off · 4–6 weeks · typically CZK 150,000
Workflow analysis (CZK 49,000, deducted)
Data audit and clean-up for the chosen workflow
Read-only MCP connection, drafts for approval
Approval screen and a short risk audit
Workshop for the workflow team
Package · 2–4 workflows or sources
Standard
Roll-out after a successful pilot
from CZK 249,000
one-off · 8–12 weeks · + CZK 90,000 per extra workflow
Audit and clean-up of every source in scope
Reads plus approved writes with sign-off
Approval screen with roles and reporting
Workshops for every team involved
Pilot fee deducted if you continue within 3 months
Package · Follows a Pilot or Standard
Operations
Ongoing running and development
CZK 14,000 / 29,000 a month
Basic 10 h · Extended 22 h + retest · 3 months’ notice
Ongoing data quality monitoring
Changes and new connectors within your hours
Approval screen maintenance
Onboarding new users
Extra hour CZK 1,400
Single-workflow pilot · 6 steps · 4–6 weeks indicative
A description of the workflow, its sources and risks; a proposed scope and a fixed price for the pilot.
What you provide
The workflow owner for 2 h, access to sample data.
All 6 pilot steps
01. Workflow analysis (week 1)
Output: A description of the workflow, its sources and risks; a proposed scope and a fixed price for the pilot.
What you provide: The workflow owner for 2 h, access to sample data.
02. Data audit and clean-up (week 1–3)
Output: A data quality report and a cleaned, documented dataset.
What you provide: Exports or read-only access, a contact for the system administrator.
03. Read-only MCP connection (week 2–4)
Output: A connector with rules, roles and a log.
What you provide: IT: accounts, network, choice of model (on-premises / EU).
04. Approval screen (week 3–5)
Output: A screen where your person confirms, corrects or rejects the draft.
What you provide: 2–3 users to try it out.
05. Risk audit before go-live (week 5)
Output: Tests for prompt injection, data leakage and unauthorised actions; findings fixed.
What you provide: Consent to the tests, a contact for your data protection officer.
06. Live test and evaluation (week 5–6)
Output: Measurement: share of drafts accepted without changes, handling time; recommendations for next steps.
What you provide: The workflow team for 2 weeks of normal operation.
Illustrative schedulelight bar = agent risk audit before go-live
AI agent risk audit
Already have an agent? Do you know everything it could break?
A chatbot on your website, an assistant in your office suite, an agent from another vendor. We test it for prompt injection, personal data leaks and unauthorised actions, and document it against the EU AI Act and the AIUC-1 standard.
A custom system, with a working MVP within a month.
We replace spreadsheets, e-mail and manual work with one system that runs your whole operation. We do not build a single app but an operational core: one source of truth about your operation, with as many interfaces on top as you need.
How much does a custom system cost and how long does it take?
It starts with a System audit from CZK 15,000: we map your operation and design the system with a fixed quote and scope. The audit price is deducted from the MVP price and the plan stays yours even if you do not continue. The MVP, a working core you actually use, costs around CZK 100,000–500,000 depending on the scope set in the audit and is ready within 30 days. Operations afterwards are an optional monthly fee. Code and data are yours from the first version; you can leave any time. Prices valid as of October 2026.
Step 01
System audit
We map your operation, design the system and give you a fixed quote and scope. The plan stays yours even if you do not continue with us.
from CZK 15,000, deducted from the MVP price
Step 02
MVP within a month
Within 30 days, a working core of the system that you actually use. Not a prototype for the drawer, but a deployed version to build on. We fix the deadline and scope in the audit.
around CZK 100,000–500,000 depending on the scope set in the audit
Step 03
Growth (optional)
More features, operations, monitoring and support for a monthly fee. Cancel any time and the system keeps running.
monthly fee depending on involvement
One core, many interfaces
Jobs, documents, materials and people live in one place. The office, the technician in the field and the customer each see them through their own window, not their own spreadsheet.
Controlled autonomy
The system handles the routine. At every irreversible step (a payment, a filing, sending anything out, a deletion) it stops and waits for a person.
Tests, not promises
Automated tests run on every change. They live in a repository you own, and you can run them any time, even without us.
The code and the data are yours from the first version. No lock-in: you can leave any time and keep a working system. Tell us about your operation
Websites & SEO
A custom website, and the care that gets you found.
A custom website built quickly and well with modern tools, plus monthly care so that people find you in search and in AI assistants. The code, the domain and the content are yours.
Records separation, and the other workflows. The official has the last word.
For municipalities, towns and regions. The lead topic is records separation for building authorities (spisova rozluka): an export test, a pilot on one department, then the rest. Alongside that, a register and payment matching for offence debts and local fees, pulling fields out of invoices and files, and a pre-meeting view over connected data. A workflow analysis for CZK 49,000 stays below the public contract register threshold, and the whole pilot fits into a small-scale public contract.
export test → a draft from the data → the official’s decision and record · analysis CZK 49,000 · pilot 4–6 weeks · small-scale contract limit CZK 3 million · separation and the other workflows are priced from the data
Each layer limits what the agent can see and do. Your data is at the centre, a person at the edge. Hover over a layer.
Your data stays with you
On your infrastructure wherever possible. Nothing is copied outside the agreed scope.
Read-only by default
The agent reads data, it does not change it. Writing is an exception you allow.
An allow-list of actions
If it is not on the list, the agent cannot do it. Nothing irreversible without a person.
Logs and roles
Who, what and when. Personal, revocable accounts, log retention under your rules.
A person approves
Your person confirms, corrects or rejects the agent’s draft.
GDPR and DPIA
Data processing agreement, minimisation, pseudonymisation. We prepare the DPIA input; the controller carries out the assessment.
AI Act and the model
Human oversight, transparency, AI literacy. The model runs on-premises, or in the EU with a ban on training on your data.
FAQ
What people ask us most.
How is an agent different from a chatbot on a website?
A chatbot answers from public web pages. An agent works with the workflow’s data (read-only), prepares material or a draft and hands it to a person for approval. That is why it needs clean data, access rules and a log.
Where does the model run, and what happens to the data?
On-premises, or in a cloud with an EU data centre and a contractual ban on training on your data. We choose together during the analysis, depending on how sensitive the workflow is.
What if the pilot does not work out?
The evaluation tells you why. The cleaned data, the connector and the documentation stay with you. You are under no obligation to order anything further.
What is prompt injection?
An attack in which the agent receives an instruction it should not follow. Either directly (a user talks it round in the chat) or indirectly: the instruction is hidden in an e-mail, a document or a web page the agent reads. For agents with tools (send, save, delete) it is the main risk.
Do you also test agents built by other vendors?
Yes. We need access to a test environment, or your consent to test on a copy, and a contact at the vendor for fixes.
Will the audit make us compliant with the AI Act?
Not on its own. It gives you evidence for your obligations (human oversight, transparency, logging, AI literacy) and shows the gaps. Legal interpretation is a job for a lawyer.
Let’s pick one workflow together.
30 minutes, free, no slide deck. We will tell you whether a pilot makes sense, and if it does not, we will tell you that too.