The core difference
| General agent workspaces | Aselius | |
|---|---|---|
| Shape | One general agent in a chat or desktop app that decides which tools to use | Specialized Rivine engines (TaskForce, Research, Code, Cicero, Creative, Confluence, Assist, Browse) on shared agentic infrastructure |
| Who decides how work runs | The agent chooses inside the conversation | You choose the engine and its specialty in the input bar; that engine runs, with its own tools and verification |
| Verification | Model-led checks and approval prompts | A runtime verification floor, an independent critic on Rivine Code, Confluence figures computed by code with a ledger, and a pause for your decision on low-confidence or high-risk steps |
| Results | Answers and files beside the chat | Deliverables in Assets: Word as pages, Excel as a real grid, decks slide by slide, code projects with live preview, follow-up edits with Rivine Assist |
| Sharing | Inside the vendor's app or as exported files | Publish a snapshot to preview.aselius.beunec.com with an access code, Open, or Members only |
| Where you use it | The vendor's own app | The web app, Rivine Browse in your real tabs, the Rivine Code CLI in your terminal, Aselius MCP from any MCP-compatible AI app, and Telegram, Discord or WhatsApp |
| Memory and context | Projects, memory and connectors inside one product | Artificial Experience and Context Extender under every engine, scoped to the workspace |
| Scheduled work | Scheduled tasks in the app | Automation runs Research, TaskForce, Cicero and Confluence in the cloud on a schedule, gated by a passing test run, whether or not your computer is on |
| Operations | Usage views inside the vendor account | Observability for cost, latency, retries and Artificial Experience on your own turns, one credit wallet with per-engine start floors, Manage Teams with CloudHandle |
See it, do not take our word for it
- Pick the engine. Open a taskspace and set the engine and specialty in the input bar, or start from an Agent Note.
- Watch the steps. Every step the engine takes appears in the thread while it runs, and the trail stays afterwards.
- Approve the action. Before an engine acts in a connected app, it shows the exact action and waits for Deny or Approve & run.
- Open the deliverable. Files land in Assets and open in the Preview Panel exactly as generated.
- Publish it. Send a link anyone can open on any device, protected by its own access code.
- Use it elsewhere. Connect any MCP-compatible AI app to https://workspace.beunec.com/mcp and start the same engines from there.
Note: The screenshots on this page are real Aselius screens. Every capability listed here is live today.
When a general agent is the better fit
- You want one assistant to operate the apps on your own desktop. Aselius works in the cloud, in your browser tabs through Rivine Browse, and on your local files through the Rivine Code CLI.
- You want a conversation, not a deliverable. Aselius is built for work that ends in a file, a project or a decision you can audit.
- Aselius is not here to replace your IDE, your legal counsel or your brokerage stack. It runs governed agentic work and hands you deliverables.

