Vybe vs Claude Tag vs OpenAI Dots vs Viktor

Specialized coworkers with their own responsibilities and tools.

Claude takes on tasks from a channel or DM.

One always-on primary dot per user, working 24/7 toward goals on its own cloud computer; role-based specialist dots are in enterprise preview and teams of dots are not yet available.

An AI coworker that works across business tools.

Shared conversations and Slack threads with people and AI.

Teammates can review and refine work in the same thread.

ChatGPT Space shared workspaces with agent-editable Pages; available on Pro, Business, and Enterprise plans.

Workspace members can work with Viktor in channels and DMs.

In-app chat, Slack, and email; other channels require setup.

Slack channels and DMs with different access scopes.

ChatGPT, Slack, Teams, SMS, and voice calls.

Slack and Microsoft Teams.

Delegate work to other AI coworkers.

Not offered: one Claude works each thread; no delegation between specialized agents documented.

Specialist dots with defined org roles are in enterprise preview; general delegation between dots is not yet available.

External agents can delegate work to Viktor through its MCP server and public API; internal multi-agent handoffs not documented.

Persistent memory, company knowledge, and reusable skills.

Persistent channel context, memory, and standing instructions.

Dots learn your preferences, how you think, and your standards from ongoing feedback.

Workspace-scoped skills and memory.

Schedules, events, and follow-ups with run history.

Routines on a schedule, channel watch, or repository event.

Team tasks act on a schedule or in response to events like a new email or Slack message; MCP events trigger automations from connected apps.

Recurring tasks and proactive automations.

Hosted browser with persistent sessions; browser service required.

Not offered: work runs in an ephemeral cloud sandbox through channel-scoped tool connections; no browser-control tool documented.

Each dot has its own cloud computer and browser; you can open your dot's computer to inspect its work, and dots can connect to your laptop with permission.

Works the web directly: logs in, clicks through pages, fills forms, and pulls data from real sites.

Supported meeting recording, transcripts, and follow-up; meeting service required.

Not offered: no meeting recording or transcription documented.

Meeting note-taking via the ChatGPT Meetings plugin (beta, macOS desktop); no recording or transcription.

Meeting follow-through runs through connected meeting tools like Symbl.ai, Fireflies, or Gong; native recording and transcription not documented.

Prebuilt connectors and custom integrations.

Admin-configured connections scoped to organizations, workspaces, or channels.

Connects to 4,000+ apps through plugins.

3,200+ business-tool integrations advertised.

Build apps with AI, inspect code, and iterate in a live preview.

Interactive pages, charts, and code changes from the thread.

Dots can build working apps and complete PRs as part of their work; evaluate your app deployment workflow separately.

Build and deploy internal apps connected to business tools.

Private, individual, and organization-wide app sharing.

Hosted artifacts accessible to people in the channel.

Not offered: outputs live in ChatGPT and connected surfaces; no internal app-publishing surface documented.

Viktor Pages share finished documents and dashboards at links; Viktor Spaces are internal tools your team signs into.

Role-based access for owners, admins, editors, and members, with apps kept private, shared, or organization-wide.

Not offered: access is scoped per channel and by organization roles; no per-row data permissions documented.

Not offered: access is governed by ChatGPT plan permission rules; no per-row data permissions documented.

Not offered: enterprise access is role-based (RBAC); no per-row data permissions documented.

SSH tunnels and custom connections for private resources.

Not offered: the ephemeral cloud sandbox reaches tools through configured connections; no private-network or SSH access documented.

Not offered: dots run on their own cloud computer and connect through plugins; no private-network or SSH access documented.

Not offered: tools connect through cloud integrations and per-user OAuth; no private-network or SSH access documented.

29 models across 11 providers.

Choose from permitted Claude models, including Opus and Sonnet.

Runs on OpenAI's GPT-6 Astra; no other providers or bring-your-own-model options documented.

Choice across OpenAI, Anthropic, and Google.

Auto routes tasks to Cheap, Balanced, or Smart tiers.

Choose a model for a thread, channel, or DM; automatic task routing not verified.

Not offered: dots run on GPT-6 Astra with no automatic cross-model routing documented.

Workspace model and task-level cost presets; automatic category routing not verified.

Choose tier models, map task categories, or pin a model.

Admins set workspace and channel defaults; individual threads can switch models.

Not offered: no task-category-to-model routing rules documented.

Workspace defaults and individual scheduled-task settings.

Separate conversation and coding routing policies.

Not offered: admins choose permitted Claude models per scope; no separate coding policy documented.

Not offered: one OpenAI model experience; no separate coding policy documented.

Not offered: model governance is workspace-wide with per-task presets; no separate coding policy documented.

Bring your own provider keys as part of an enterprise setup.

Not offered: Claude uses admin-provided tool accounts with credentials kept out of the sandbox; no customer model keys documented.

Not offered: dots run on OpenAI-managed credentials; no customer provider keys documented.

Not offered: model providers run under Viktor-managed agreements; tool credentials are per-user OAuth handled by the Viktor gateway.

OpenRouter and Vercel AI Gateway.

Not offered: no bring-your-own model gateway documented.

Not offered: no bring-your-own AI gateway documented.

Not offered: models run through the Viktor-managed stack; no bring-your-own gateway documented.

SAML single sign-on for enterprise.

Claude Team and Enterprise organizations support SAML SSO and JIT provisioning via WorkOS.

SAML SSO for Business, Enterprise, and Edu workspaces, configured workspace-wide via the Global Admin Console.

SAML SSO via Okta, Entra ID, Google Workspace, OneLogin, or any SAML 2.0 IdP.

Access, agent activity, and tool usage for enterprise review.

Documented activity trails; review your required audit scope.

Compliance Logs Platform exports audit events for Enterprise and Edu workspaces; dot-specific audit coverage not documented.

Enterprise audit logging; confirm required event coverage.

Action-specific permissions and contact controls on every channel; explicit approval gates not documented.

Every action passes a permission checker; admins pre-approve action types per scope with auto-mode allow rules.

Custom permission rules; dots request approval before sensitive actions like sending an invoice or making a purchase.

Sensitive actions can wait for explicit approval in chat.

Usage visibility and per-agent credit budgets.

Monthly organization usage limit; DMs use personal accounts separately.

Not offered: no usage-tracking or per-agent budget controls documented; usage follows ChatGPT plan allowances.

Auto-topups with monthly spend caps; per-user spend caps on Enterprise.

Free plan with $10 in credits every month; paid plans from $20/month. $1 = 100 credits; top-ups available.

Channel work draws from the organization’s usage balance.

Included with Pro and Business Premium in eligible markets; the Enterprise, Edu, and Healthcare beta is admin-enabled and off by default.

Credit-based plans from $50/month, with trial credits.

Unlimited builders and viewers in your organization.

Channel usage is not charged against individual seats; account eligibility still applies.

Teammates can work with @ChatGPT in Slack or Teams without their own license; dot access follows ChatGPT plans.

No per-seat licenses; credits reflect model usage.