Mention the box in Slack and it answers from your knowledge base with the source named, kicks off existing chores, and posts results back to the channel. Approvals happen where you already are — a tick from the named approver in the thread. The answering itself runs onboard, behind your firewall.
starts when: Someone mentions the Aivell in a Slack channel
Internal questions go where the people are, and the people are in Slack. “What’s our travel policy?” gets typed into a channel, three colleagues stop working, someone links a doc from 2023, and tomorrow the same question scrolls past again. The alternative is email — adding to the 121 messages a day everyone is already not reading.
Meanwhile the actual answers sit in a knowledge base nobody opens, and the routine reports wait for whoever owns the button to get out of a meeting. The distance between “asked in Slack” and “done on the system” is a person alt-tabbing.
Slack is rolling out to early-access customers first — here is what it looks like installed:
Slack stays what it is: the place your company talks. What changes is that the colleague who has read everything and runs the routine work is now in the channel — while every document, lookup and decision it handles stays on the box in your office.
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:
answer mentions in the ask-the-box channel from the knowledge base, citing the document
questions about a specific client go to the account owner, not the channel
kick off the weekly report runs the existing chore and posts when done
approvals arrive as a thread message; a tick from the named approver is a yes
after 19:00, only Petra's requests run — the rest queue for morning
no source found? say so in the thread, never improvise
private channels are off-limits unless an admin invites the box
friday, post the week's five most-asked questions back to the channel
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. It sees only the channels an admin invited it to, and speaks only when mentioned. Private channels stay private unless someone with admin rights deliberately brings the box in.
The intelligence. Your question travels through Slack as messages always do, but the searching, reasoning and drafting run on the box, and your documents and data are never uploaded to Slack or to any AI cloud. Slack sees the final answer, nothing more.
The Slack channel is rolling out to early-access customers first. What's on this page is the working design; ask us and we'll tell you where your workspace sits in the queue.
Anyone can ask questions. Actions are narrower — chat can only start chores that already exist, a guardrail blocks creating new ones from Slack, and anything needing sign-off waits for a tick from the specific person named as approver.
Every manual, contract and memo indexed on a box in your office. Your team asks in plain language and gets cited answers — nothing leaves the building.
Leave, benefits, expenses — employees ask in chat and get answers quoting your own HR handbook. Questions never leave the box in your office.
An on-premise AI colleague watches your database and speaks up only when a threshold breaks — with the numbers, the trend and the context attached.
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