Vybe vs Superblocks vs Claude Tag vs Viktor

Specialized coworkers with their own responsibilities and tools.

Earlier record: Builds only. Clark AI builds apps but doesn't operate autonomously. Not reverified.

Claude takes on tasks from a channel or DM.

An AI coworker that works across business tools.

Shared conversations and Slack threads with people and AI.

Not verified in this review

Teammates can review and refine work in the same thread.

Workspace members can work with Viktor in channels and DMs.

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

Earlier record: Not supported. No multi-channel messaging. Not reverified.

Slack channels and DMs with different access scopes.

Slack and Microsoft Teams.

Delegate work to other AI coworkers.

Not verified in this review

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

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.

Earlier record: Enterprise. Clark Memory — Enterprise plan only. Not reverified.

Persistent channel context, memory, and standing instructions.

Workspace-scoped skills and memory.

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

Earlier record: Enterprise. Enterprise plan only. Not reverified.

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

Recurring tasks and proactive automations.

Hosted browser with persistent sessions; browser service required.

Earlier record: Not supported. No browser automation. Not reverified.

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

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.

Earlier record: Not supported. No meeting capabilities. Not reverified.

Not offered: no meeting recording or transcription documented.

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.

Earlier record: 50+. Growing but limited compared to Vybe. Not reverified.

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

3,200+ business-tool integrations advertised.

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

Not verified in this review

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

Build and deploy internal apps connected to business tools.

Private, individual, and organization-wide app sharing.

Earlier record: Supported. Not reverified.

Hosted artifacts accessible to people in the channel.

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.

Earlier record: Enterprise RBAC. RBAC on Enterprise plan. Not reverified.

Not offered: access is scoped per channel and by organization roles; 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.

Earlier record: Not supported. VPC deployment available on Enterprise. Not reverified.

Not offered: the ephemeral cloud sandbox reaches tools through configured connections; 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.

Not verified in this review

Choose from permitted Claude models, including Opus and Sonnet.

Choice across OpenAI, Anthropic, and Google.

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

Not verified in this review

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

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

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

Not verified in this review

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

Workspace defaults and individual scheduled-task settings.

Separate conversation and coding routing policies.

Not verified in this review

Not offered: admins choose permitted Claude models per scope; 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 verified in this review

Not offered: Claude uses admin-provided tool accounts with credentials kept out of the sandbox; no customer model 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 verified in this review

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

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

SAML single sign-on for enterprise.

Earlier record: Enterprise. Enterprise plan only (SSO/SAML/OIDC). Not reverified.

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

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

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

Earlier record: Enterprise. Enterprise plan only. Not reverified.

Documented activity trails; review your required audit scope.

Enterprise audit logging; confirm required event coverage.

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

Not verified in this review

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

Sensitive actions can wait for explicit approval in chat.

Usage visibility and per-agent credit budgets.

Not verified in this review

Monthly organization usage limit; DMs use personal accounts separately.

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.

Not verified in this review

Channel work draws from the organization’s usage balance.

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

Unlimited builders and viewers in your organization.

Earlier record: $49-80/seat. $49-80 per AI builder/month. Not reverified.

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

No per-seat licenses; credits reflect model usage.