Agentic automation — software that acts, not just answers
A chatbot answers. An agent does. Agentic automation is the difference between being told how to process the invoice and finding it processed — read, checked, exported and filed — without anyone at the keyboard.
What makes automation “agentic”
Classic automation follows a script someone wrote for every case. An agent is given a goal and a set of tools and works out the steps itself — which is what lets it handle the input that breaks a script: a photographed invoice, a supplier who changed their layout, an email that says the same thing in different words.
- It has tools — files, email, databases, the web, documents, calendars, a phone line. An agent with no tools is a chat window.
- It decides the order — the goal is fixed, the route is not.
- It finishes — the output is a file, a record, a sent message, a booked slot; not a suggestion.
The part most platforms leave out
Software that acts on its own needs brakes, and they have to be in the code rather than in a prompt anyone can edit. In AIK they are platform features:
- Human approval steps — a run stops and waits for a person on the steps you choose, whether it was started by hand or by the scheduler.
- A monthly budget per agent — the run is refused when the money runs out, and every run records what it actually cost.
- A tamper-evident audit trail — actions are written to an append-only log chained with SHA-256, so an edited or deleted line is detectable. EU AI Act Article 12 record-keeping.
- Everything it produces is marked — documents, emails, reports, phone calls and videos carry a mark a person can see or hear and a machine-readable credential inside the file. Article 50, enforced in code, never left to the model.
- Rollback — an update snapshots the application and the database first, and one click restores the working version.
What people actually run
- Documents — invoices, contracts, delivery notes and forms read from PDFs, scans and phone photos, validated, then written to Excel, a database or your own system.
- Inboxes — mail read, sorted, answered, attachments filed.
- The phone — a bilingual voice agent that answers calls, books appointments and writes them to a calendar.
- Multi-step processes — several agents in one workflow with dependencies, retries and an approval gate before anything leaves the building.
Agentic automation and RPA are not rivals
An RPA robot is precise and blind: perfect on a stable screen, helpless when the input varies. An agent is the opposite. The systems that work use both — the agent reads the unstructured thing and decides, the robot does the deterministic clicking. AIK was built by an RPA developer for exactly that pairing.
On your servers, or ours
The whole platform installs on your own machine, and with local models through Ollama nothing leaves the network at all. Or use the hosted version and pick a cloud model. Same product, same features: the model provider is a setting, not an architecture.