Your Aivell does the work; you keep the judgment. It prepares each sensitive step, pauses, and waits for approval — a notification on your phone, answered in a tap. Choose the level per chore and per tool: get notified on every action, on specific tools, or approve each request individually.
The scary version of AI automation is the one that acts first and explains later. An Aivell is built around the opposite move: the pause. It reads the invoice, checks the math, drafts the reply, fills the form — and then, if the step is sensitive, it stops. The work is done up to the point of commitment; the commitment stays yours.
You get a notification on your phone: who, what, how much. “Giulia · needs approval · Invoice €1,240 doesn’t match the order, register it?” One tap to approve, one to reject. Approve and the chore resumes exactly where it paused. Reject and it follows the chore’s instructions for a no — which you also wrote.
Trust isn’t binary, so the control level isn’t either. Per chore, per tool, you choose one of three:
Notify on everything. Your Aivell acts on its own and every action shows up in your feed. You watch the new colleague work without standing behind their chair.
Notify on specific tools. Routine tools run silently; the ones that matter — anything leaving your domain, edits to the master sheet, writes to the ERP — ping you as they happen.
Approve each request. The hard stop. Chosen actions are prepared, then held until a human says yes. No approval, no action — not eventually, not by timeout, not ever.
Most teams run all three at once: watch the email triage, get pinged on customer-facing replies, hold every reply that goes to a customer. The levels also tighten or relax over time — week one everything is held, month three only what leaves the building is. And they compose with guardrails: approval decides when an action runs, guardrails decide what actions are possible at all.
Approvals cover the steps you planned for. For everything else there is a red button. “Stop everything” freezes every chore on the box at once; “Stop this chore” and “Stop this folder” hold one chore or a whole group — all of their runs, or only the new ones while those under way finish. Every conversation, and the chat while your Aivell is working, has its own Stop.
A stop never cuts a step in half: the email being sent is sent, then the chore halts. Nothing is thrown away either — stopped work waits in place, new requests wait with it, and Reactivate shows who stopped it, when and why before letting it carry on.
This is the honest division of labor. Your Aivell is better than anyone at reading two hundred pages without losing focus; you are better at knowing that this particular supplier gets a phone call, not an email. Human-in-the-loop keeps each side doing what it’s good at — the machine prepares, the human decides.
Every request, decision and timestamp lands in the audit trail on the box, so “who approved this?” always has an answer. The box stays in the office. You, demonstrably, don’t have to.
Only if you want to. You pick the control level per chore and per tool — from a running notification feed you can ignore, to a hard stop on everything that leaves your company. Most people start strict and loosen it as the audit trail earns their trust.
It stays parked. The step in question is prepared but not executed, and it cannot execute until someone says yes. Everything else keeps moving — other chores run, and unrelated steps of the same chore that don't need approval carry on.
No. The work, the documents and the models stay on the box in your office. Your phone is a remote control: you see the request and the context you need to decide, and your yes or no travels back — the data itself never moves.
Yes, and that's the best place for them. "Over €2,000, ask first", "new supplier, pause and wait" — thresholds and exceptions are plain-language lines in the chore, so the pause happens exactly where your procedure says it should.
In one click. "Stop everything" freezes the whole box; one chore, a folder of chores or a single conversation can be stopped on its own. Stopped work waits exactly where it was and carries on when you press Reactivate.
Expense, discount and purchase requests arrive pre-checked: case summarized, policy applied, one tap to decide. All prepared on your own hardware.
An on-premise AI colleague reads every supplier invoice — PDF, scan or photo — and books it into your sheet or database. Invoices never leave your office.
Your Aivell drafts a reply to every incoming email, in your voice — you review, edit and send. Drafting happens on the box, in your office.
Overdue invoices from your own database become polite, escalating reminders — sent by an on-premise AI colleague and stopped the moment payment lands.
New suppliers hand in paperwork once — an on-premise AI colleague checks it, chases the gaps and registers the vendor. Documents never leave your network.
An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.
You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.
onboard inference · air-gapped · fixed monthly fee · one-click stop