A generalist against specialists
A general assistant does the task a person remembers to send. A functional agent owns the queue, the pipeline or the store, and works it without being asked each time.
afka uses analytics cookies to understand how visitors use the site. No ads, no data sales.
Viktor is a general assistant that sits in Slack or Microsoft Teams and handles the tasks a person sends to it. afka deploys one deep agent per business function, with governance as the product, and this page states the difference plainly.
Viktor is a general assistant in the chat product a team already uses: a person mentions it, hands over a task, and receives the result in the same thread. For one helpful generalist, that is a simple and reasonable shape.
afka is not a better generalist. afka deploys one deep agent per business function, support, sales, recruiting, the store, content, and each agent operates the whole function end to end, with a general assistant covering everything outside those. The distinguishing property is what happens when an agent should not act: autonomy levels, approval gates, caps enforced in code, and an append-only audit log.
A general assistant does the task a person remembers to send. A functional agent owns the queue, the pipeline or the store, and works it without being asked each time.
afka bills for work done, not for seats. Every run debits exactly what it consumed, and the ledger is reconcilable.
The model is not the part afka builds. afka builds what surrounds it: what an agent may do without asking, what it must bring to a person first, what it is forbidden to do at all, and the record of everything it did.
A team that wants one helpful generalist in the chat channel it already uses may find a general assistant the simpler purchase. The comparison changes when whole functions need to run without a person driving each task.
Start free, pick a business function, and get a first finished artifact in under a minute.
Start free