Hand your Aivell a messy export and say what you need — merge, dedupe, convert, reformat. It writes a small script and runs it in a sandbox on the box with no network access at all, shows you a sample first, and returns a new file. Originals are never touched.
starts when: You hand your Aivell a file and describe what you need
Between “we have the data” and “we can use the data” sits an afternoon of drudgery. Two exports that almost match. A customer list with three flavors of the same company name. Four hundred files in a format the new system refuses to read. Too irregular for a spreadsheet formula, too small to buy software for — so someone senior does it by hand, badly, quarterly.
The obvious shortcut — paste it into some online converter or a chatbot — means mailing your customer list to a stranger. The careful people know that, which is exactly why the careful people are still doing it by hand.
It’s the difference between “who can write me a quick script?” and having the colleague who always could — one who works in a room with no windows and no door to the outside.
No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:
take the file and the ask — merge, convert, dedupe, reformat
copy it into the sandbox; the sandbox has no network, by design
write the script and run it on the first ten rows only
show that sample and wait for a go before the full run
never touch the original — every output is a new file
anything over a thousand rows gets a row-count check, before and after
return the result the way it came — reply, chat, or the processed folder
keep the script, so Franca's monthly ask runs without a rewrite
Connected with single-click passkeys — no copied tokens, no OAuth hell.
Every tool can be limited to exactly what this chore needs. For this one, you might set:
No. You describe the outcome — "one sheet, no duplicates, dates the European way" — and judge the sample it shows you before the full run. The script is kept and reused, but reading it is optional, like checking a colleague's formulas.
Nowhere — twice over. The box already keeps everything inside your office, and the sandbox is a sealed room within it — no network, no access to the rest of the share, just the files handed in and the output it creates.
Then a new, wrong file exists and nothing else happened. Originals are read-only by rule, the ten-row sample catches most nonsense before the full run, and the row-count check flags anything that silently vanished.
Yes — the script is kept with the chore, so "same as last month, new file" is the entire brief. If the routine settles down, it becomes a scheduled chore and stops needing you at all.
An Aivell dedupes and normalizes customer records on a schedule, logs every proposed change, and touches nothing until a human approves. All onboard.
Your Aivell compares spreadsheets with the database, explains every mismatch in one line, and mails the list — financial data checked behind your firewall.
Describe a task in chat and your Aivell drafts the chore — steps, guardrails, schedule. Nothing runs until you have read it and said yes.
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