# Centaur 2.0 and Viktor. Choose how the work gets done.

Self-hosted, Slack-native agent runtime that runs real work in an isolated sandbox and replies in thread. Compare that with Viktor, an AI employee for shared work in Slack and Microsoft Teams.

[All comparisons](https://viktor.com/compare) · [Open source](https://viktor.com/compare/open-source)

Canonical page: https://viktor.com/compare/viktor-vs-centaur

## Viktor vs Centaur 2.0

| Feature | Viktor | Competitor |
| --- | --- | --- |
| Surface | Slack and Microsoft Teams, in the channel where the work is already discussed. | Slack and Discord, self-hosted. |
| Works for | The whole team. Anyone can tag Viktor; context belongs to the workspace. | Whole team, one shared agent. |
| Who owns the job | Reads the request, uses connected tools, produces the deliverable, and reports back in the thread. | Executes in a sandbox with shell, git, Python and Node, plus durable workflows that sleep, resume and spawn child agents. |
| Memory | Shared workspace context. What one person teaches Viktor can help the team. | Replayable transcript store with org personas, skills and prompts. |
| Tools | 9,800+ integrations, browser access, code execution, and published pages and apps. | Bring your own harness (Claude Code, Codex, Amp) plus shared Python tool plugins. |
| Price shape | Shared workspace credits from $100/month, without a subscription for each teammate. | Check Centaur 2.0's current plans for pricing, included usage, and availability. |
| Best for | Ongoing team work across your connected tools. | You are building a custom agent system and want control over its execution environment. |

## Choose Viktor

- You want to delegate work in Slack or Microsoft Teams.
- Your team needs shared context rather than isolated individual conversations.
- Your work spans several business tools and needs a finished deliverable.
- You prefer a managed employee with a shared workspace credit pool.

## Choose Centaur 2.0

- You are building a custom agent system and want control over its execution environment.
- Self-hosted, Slack-native agent runtime that runs real work in an isolated sandbox and replies in thread.

## More from Open source

- [OpenClaw](https://viktor.com/compare/viktor-vs-openclaw): An open-source, self-hosted AI assistant that plugs into Slack, WhatsApp, and Telegram.
- [Centaur 2.0](https://viktor.com/compare/viktor-vs-centaur): Self-hosted, Slack-native agent runtime that runs real work in an isolated sandbox and replies in thread.
- [Hermes Agent](https://viktor.com/compare/viktor-vs-hermes): Open-source self-improving agent with persistent memory and one gateway that fronts 25+ chat surfaces.
- [Diana](https://viktor.com/compare/viktor-vs-diana): A managed, governed OpenClaw that gives every workspace member their own AI employee in Slack.

## Questions

### What is Centaur 2.0?

Self-hosted, Slack-native agent runtime that runs real work in an isolated sandbox and replies in thread.

### How does Centaur 2.0 differ from Viktor?

Slack and Discord, self-hosted. Executes in a sandbox with shell, git, Python and Node, plus durable workflows that sleep, resume and spawn child agents. Viktor takes requests in Slack and Microsoft Teams and works across the team's connected tools.

### When should I choose Centaur 2.0?

You are building a custom agent system and want control over its execution environment. Self-hosted, Slack-native agent runtime that runs real work in an isolated sandbox and replies in thread.

### Is Centaur 2.0 part of the same family as other tools here?

Centaur 2.0 belongs to Open source in this catalog. Its tool type is Self-hosted. The family groups related products; the tool type describes what this product does.

Product information: https://centaur.run