Sim vs Vellum
Sim is the open-source AI workspace where teams build, deploy, and manage AI agents visually, conversationally, or with code. Here is how Sim compares to Vellum on platform architecture, AI capabilities, integrations, pricing, security, and support. Every fact below is sourced and dated.
Sim is an open-source AI workspace for building, deploying, and managing AI agents. This page compares Sim to Vellum across platform architecture, AI capabilities, integrations, pricing, security and compliance, observability, and support, using sourced, dated facts for buyers evaluating both platforms.
What is Sim?
Sim is the open-source AI workspace where teams build, deploy, and manage AI agents, connecting 1,000+ integrations and every major LLM to automate real work visually, conversationally, or with code.
What is Vellum?
Vellum is an enterprise AI development platform for building, evaluating, and deploying LLM prompts, workflows, and agents.
Sim vs Vellum: feature-by-feature comparison
CompareSim vs Vellum
Sim
Vellum
Platform
Builder type
Visual canvas, chat, or codeVisual drag-and-drop canvas, natural-language (Chat), or code (API/SDK)
Visual builder, code SDK, or natural languageVisual workflow builder plus a code-first SDK, and a natural-language 'Vellum for Agents' mode for non-technical users. Vellum offers a visual graph builder and a code-first SDK that stay in sync, with nodes for model calls, retrieval, tool/API steps, and control flow. A separate 'Vellum for Agents' surface lets non-engineers describe a goal in plain language to generate an agent.
Learning curve
Low, plus natural-language Chat for non-technical usersLow for visual building; natural-language Chat surface for non-technical builders. Chat lets users describe a workflow in plain language and have Sim build it.
Not publicly documentedUnknown. Not publicly documented.
Self-hosting
Deployment options
Cloud-hosted or self-hosted, no mid-tier VPC optionCloud-hosted (managed, multi-tenant SaaS) or self-hosted (Docker/Kubernetes). No documented managed single-tenant/VPC hosting tier in between. The Enterprise plan's only hosting-related row in the pricing comparison table is a boolean "Self Hosting" flag; there is no dedicated-instance/VPC offering.
Cloud, self-hosted, or VPC installVellum Cloud (SaaS), self-hosted, and VPC install on AWS/Azure/GCP or on-prem
Templates
Exists; contents undocumentedA templates page exists on vellum.ai; contents are not publicly detailed.
License
Apache 2.0Apache License 2.0
Proprietary enterprise platform; MIT consumer appProprietary/commercial for the core enterprise Vellum platform. A separate consumer 'Vellum Assistant' product is open-sourced under MIT license.. github.com/vellum-ai/vellum-assistant is MIT-licensed (confirmed live, 825+ stars). No evidence the enterprise workflow/evaluations platform itself is open source.
Environment promotion
Yes: fork a whole workspace into a dev/qa/prod-style child, diff it, and promote or roll back changes in either direction. Credential and env-var remapping is required before every promote, so secrets are never silently copied across environments. Gated to Enterprise plan on hosted Sim, or a FORKING_ENABLED flag on self-hosted deployments.
Dev/Staging/Prod with one-click promotionVellum has Development/Staging/Production environments, each with isolated API keys, release histories, and environment variables/secrets. A 'Promote' button moves a tested Release to another environment, or you can deploy directly to multiple environments at once. Sandboxes (prompt/workflow definitions) are shared across environments; deployments and releases are environment-scoped.. Promotion operates at the level of individual workflow/prompt releases rather than whole-workspace forking.
Version control
Deployment rollback plus Copilot edit diff/revertDeployed-version history with rollback for every workflow; server-persisted checkpoint/revert and visual diff (accept/reject) specifically for Copilot AI edits. Manual drag-and-drop undo/redo is client-side/localStorage only (capped at 100 ops, 5 stacks), not server-synced across devices. Deployment history does not include an arbitrary version-to-version diff tool, and knowledge base documents have no version history.
Release history with one-click rollbackVellum maintains per-environment Release history with instant one-click rollback (no code changes required) and semantic-versioned Release Tags or a rolling LATEST tag. Version comparison is mentioned, but a dedicated diff/side-by-side view is not documented.
Realtime collaboration
No: Vellum's collaboration model is asynchronous, not live multi-user editing. Prompt Sandbox lets team members see each other's history, tag entries, and share/invite others, but there is no documented live-cursor or simultaneous editing of the same workflow or prompt.. Vellum documents shared visibility into sandbox history and sharing/invite mechanisms, framed around sequential iteration rather than simultaneous editing.
Native file storage
Yes: a native Files area with folder hierarchy, link-based sharing (public, password, email OTP, or SSO auth), and a workspace-level Recently Deleted view covering workflows, tables, knowledge bases, files, and folders. Admins can restrict which share-auth modes (public/password/email/SSO) a permission group is allowed to use.
No: Vellum's document handling is scoped to Document Indexes for RAG (upload, indexing, search), not general-purpose file storage. No folder hierarchy, shareable links with password/SSO auth, or trash/recovery feature is documented.. Documents are environment-scoped, uploaded for indexing with size limits (up to 32MB) and supported formats (PDF, DOCX, CSV, etc.), but folder hierarchy, link-sharing with auth, and deleted-item recovery are not documented.
Sub-workflows (composition)
Yes: Vellum has a Subworkflow node that executes a deployed or inline workflow as a step inside a parent workflow, waiting for it to finish and passing/receiving data through defined inputs and outputs.. Both "Deployed Subworkflows" (calling a separately versioned, released workflow) and "Inline Subworkflows" (defined within the parent workflow for modularization/reuse) are documented; the Agent Node can also register subworkflows as callable tools.
Pricing
Pricing model
Credit-based billing, BYOK exempt from capsCredit-based usage billing (Stripe), with bring-your-own-key exemption from metered caps
Pass-through LLM credits + subscriptionPrepaid/pay-as-you-go credits ($1 credit = $1 of underlying LLM/API cost, no markup) plus a tiered monthly subscription for compute/storage. Current pricing pages describe the consumer 'Personal Intelligence' product's plans (Base/Free and Pro $50/mo tiers with configurable vCPU/RAM/storage add-ons) rather than the original enterprise workflow platform's seat/usage-based pricing.
Entry paid plan
Pro plan at $25/user/monthPro: $25 per user/month
~$50/mo example configuration plus usage creditsAround $50/month for a typical Pro-tier setup, plus usage credits. The Pro plan has a $10/month platform fee (includes custom subdomain and priority support). Actual monthly cost depends on the compute tier chosen ($35-$125/mo) and storage tier chosen ($5-$120/mo); Vellum's own example configuration totals $50/month before usage credits.
Free tier
Bring your own key
No BYOK option documentedNot mentioned on current pricing pages. Pricing is structured around Vellum-provided credits passed through at cost, with no bring-your-own-API-key option described.
Security & compliance
SOC 2
Data residency
Full control via self-hosting; Cloud region toggle is global, not per-customerFull data control via self-hosting (Docker/Kubernetes); data never leaves customer infrastructure when self-hosted. On Sim Cloud, async job execution has an internal US/EU region toggle, but it is deployment-wide, not a customer-selectable per-workspace residency option
No selectable residency regions documentedUnknown: no specific region/residency options documented. Docs describe data being stored 'in Vellum's infrastructure, isolated in a dedicated, encrypted container' but do not specify selectable residency regions.
Role-based access control
Yes: workspace-level role-based access control with six predefined roles. Roles are Admin, Deployment Editor, Document Index Editor, Test Suite Editor, Playground Editor, and Member (read-only). Permissions apply workspace-wide rather than per individual resource, and only Admins can change other users' roles.
Audit logging
Not publicly documentedUnknown. Not publicly documented for the enterprise platform; permissions-model docs describe per-action risk badges for the consumer assistant product only.
Additional compliance
SOC2SOC2. Self-hosting is the primary lever Sim offers for data-residency-sensitive compliance needs beyond SOC2, rather than additional certifications.
HIPAA + BAA; no other certs confirmedHIPAA compliant, with a BAA available for enterprise customers; no other certifications (ISO 27001, GDPR-specific attestation, PCI, FedRAMP) confirmed. Vellum's docs and a third-party Drata case study state it is HIPAA compliant and that enterprise customers can sign a Business Associate Agreement (BAA). No mention of ISO 27001, PCI, or FedRAMP certification was found.
Model & tool governance
Yes: enterprise "permission groups" let an admin allow-list/deny-list specific LLM providers and models, and separately deny specific tools/integrations (or disable all MCP or custom tools) per group, layered on top of workspace admin/write/read roles. This does not control whether an LLM provider retains prompts. Sim offers no "zero data retention" mode or governed AI gateway. A separate, Enterprise-gated feature lets orgs set a log-retention window and redact PII, but that only controls how long Sim itself keeps execution logs.
Not publicly documentedUnknown. Not publicly documented.
Credential governance
Yes: shared credentials (connected accounts, service accounts, workspace secrets) are their own nested permission level (Member/Admin) below organization and workspace roles, and enterprise permission groups can further allow-list specific integrations and restrict which file-share auth modes (public/password/email/SSO) a group may use. A user's personal environment variables/secrets are never shared or inherited by anyone, including org owners/admins.
No: Vellum has workspace-level Role-Based Access Control (Admin/Member roles governing create/update/delete permissions), but nothing documents restricting which specific stored credentials or connections a role or permission group may use.. RBAC docs describe workspace-wide role permissions (Admin vs Member) rather than credential-level allow/deny lists. A separate Vellum personal-assistant product describes per-credential allowedTools/allowedDomains scoping, but it is a different product from the B2B workflow platform compared here.
Single sign-on (SSO)
Claimed by third parties, undocumented directlyUnknown: third-party summaries claim Vellum supports SSO/SAML, but no first-party Vellum documentation describes SAML/OIDC setup or auto-provisioning on first login.. Vellum's security/data-privacy documentation does not mention SSO/SAML, and a search of docs.vellum.ai for SSO/SAML configuration returns no dedicated setup page.
Vetted first-party integrations
Yes: every one of Sim's 302 blocks is first-party authored and code-reviewed through the standard pull-request process in the main Sim repository; there is no public marketplace where an arbitrary third party can publish and have other users install executable tool code without going through Sim's own review. Custom code steps run inside Sim's own isolated-vm sandbox rather than as an installable third-party skill package, so the supply-chain trust boundary is Sim's codebase review, not an open registry.
Yes: Vellum's tool ecosystem is closed and vendor/partner controlled, not an open marketplace. Its 100+ native integrations are built and maintained by Vellum, its Composio partnership adds access to Composio's curated tool library, and 'Custom Nodes' are authored by the customer's own team for internal reuse rather than published to a shared marketplace for other tenants.. No documentation describes a public marketplace or community-node/plugin registry where third-party developers publish executable code for other Vellum customers to install, unlike ecosystems such as n8n community nodes. Custom Nodes extend a single customer's own workflows and are not distributed to other organizations. No publicly documented security incidents involving Vellum's integration or tool ecosystem were found.
PII redaction
UnknownUnknown: nothing confirms or denies a dedicated PII detection/redaction feature distinct from generic Guardrail nodes for output validation.. Vellum documents a general Guardrail Node for workflow quality checks, but no page specifically describes PII detection/redaction (emails, SSNs, etc.) in workflow content or logs.
Custom data retention
Yes: Enterprise customers can configure data retention policies to automatically delete monitoring/interaction data after a specified period (30, 60, 90, or 365 days) instead of the default indefinite retention.. Configured from Organization Settings under Advanced Settings; default behavior without this Enterprise configuration is indefinite retention.
White-labeling
Unknown, no white-label branding docs foundUnknown: no documentation describes replacing Vellum's own branding (logo, product name, theme) with a customer's branding across the workspace or deployed apps. Only generic 'white glove' Enterprise service language appears, and that refers to onboarding support, not white-label branding.. Vellum's own branding-guide page addresses Vellum's use of its own brand assets by others, not a customer-facing white-label capability.
AI capabilities
Multi-LLM support
21 providers incl. OpenAI, Anthropic, Google, Bedrock21 provider integrations (OpenAI, Anthropic, Google/Gemini, Azure OpenAI, Azure Anthropic, Groq, Cerebras, Mistral, xAI, Bedrock, Vertex, Ollama, OpenRouter, and more). apps/sim/providers/models.ts defines 21 provider entries; openrouter/litellm/vllm/ollama resolve models dynamically at runtime rather than from a hardcoded model list.
20+ providers, hundreds of modelsModel-agnostic across 20-23+ providers (OpenAI, Anthropic, Google/Gemini, Cohere, Azure OpenAI, Bedrock, Fireworks, Perplexity, Cerebras, Groq, etc.) and hundreds of individual models, including recent additions like GPT-5 and Claude Opus 4.1.
Agent reasoning blocks
Agent Node handles reasoning + tool executionVellum's 'Agent Node' (formerly 'Tool Calling Node') is its dedicated agent/reasoning-and-tool-execution block within Workflows, supporting raw code, subworkflows, MCP tools, and Composio SaaS actions side by side in one node.
Natural-language building
Knowledge base / RAG
Document Indexes + RAG pipeline evaluationVellum supports RAG via 'Document Indexes' and a dedicated 'Evaluating RAG Pipelines' documentation area.
MCP support
Remote MCP servers with auto tool discoveryAgent Nodes support adding a remote MCP server as a tool via a '+ Tool' button, with automatic tool discovery (since August 2025).
Evaluation & guardrails
LLM-judge Evaluator plus Guardrails validation blockEvaluator block (LLM-judge scoring against user-defined named metrics) and Guardrails block (JSON validity, regex, RAG/hallucination scoring, PII detection/masking). These are per-call scoring/validation primitives, not a batch golden-dataset eval-suite runner or A/B prompt-testing harness.
Test suites, scored metrics, production evalsVellum's 'Evaluations' product uses Test Suites and Metrics (0-1 scores) for quantitative evaluation, supports bulk CSV test-case upload, online/production evaluations, custom reusable metrics, and RAG-pipeline evaluation.
Human-in-the-loop
External Input node for approvalsAn 'External Input' node pauses Workflow execution until a human or external system supplies input, enabling human-in-the-loop approval patterns.
Generative media
Image-gen credits exist; blocks undocumentedUnknown. Pricing includes credits for image generation as a billable usage type, but specific image/video/audio blocks or supported providers are not publicly detailed.
Dynamic tool use
No: an Agent block calls tools the workflow author explicitly added to it at build time, rather than browsing and picking from a broader pool (e.g. an entire MCP server catalog) at inference time. Runtime MCP "discovery" exists to resolve/refresh the schema of an already-configured tool. The model does not browse or choose from the server's full tool list.
Not publicly documentedUnknown. Not publicly documented.
Automatic model fallback
No: a failed or rate-limited LLM call is retried using Sim's own hosted API keys for the same model, rather than automatically switching to a different model or provider. A "fallback" comment in the provider layer refers to rotating among Sim's own hosted API keys for the same model, not switching models.
Not publicly documentedUnknown. Not publicly documented.
Agent skills
Yes: named, reusable "Agent Skills" (built on the open Agent Skills / SKILL.md format) that agents load on demand via progressive disclosure, editable in-app or imported from a SKILL.md file or GitHub URL. Only the skill name and description sit in the agent's system prompt (~50-100 tokens each); the full instructions load into context only when the agent calls load_skill.
No: Vellum has no named, reusable prompt or knowledge-snippet feature invoked by reference across multiple agents. Its reuse primitives are Subworkflows (reusable workflow logic blocks) and shared Prompt Sandboxes, not a discrete 'skill' object referenced by name across agents.. Reuse happens via Subflows/subworkflows and deployed prompts, a different mechanism than a discrete named prompt-snippet library referenced across agents. The separate Vellum personal-assistant product does have a 'Skills' concept, but it is not documented as part of the B2B workflow platform compared here.
Native chat deployment
Yes: Vellum Agents can be built with a first-class Chat Message Trigger that maintains chat_history/conversation state across turns, and Workflows/Agents can be deployed with this chat pattern rather than only form/API/webhook targets.. Documented alongside RAG chatbot tutorials and the Agent Node's conversation-state handling; deployment surface details (e.g., a hosted public chat widget URL) were not independently confirmed beyond the trigger/state mechanism.
Parallel execution
Yes: a native Parallel block fans a run out into concurrent branches (fixed count or one per list item) and joins their results back into the workflow automatically. Contained blocks run concurrently instead of sequentially, either a fixed number of times or once per item in a list/collection, and each branch's output aggregates for downstream blocks.
Yes: Vellum Workflows has a Map Node that iterates over an array and executes a subworkflow concurrently for each item, and a Merge Strategy (available on all node types, replacing the older standalone Merge Node) that consolidates divergent execution paths back into one result.. As of the January 2026 release, the standalone Merge Node was replaced by Merge Strategy, a setting on every node type, so branches can fan out via the Map Node and fan back in without a dedicated join node.
Agent2Agent (A2A) protocol
No: Vellum documentation and changelogs show no support for the Agent2Agent (A2A) protocol. Vellum has written about the related Google AP2 payments protocol, but has not documented an A2A implementation or Agent Card support.. No mentions of "Agent2Agent" or "A2A" appear in Vellum product docs, help center, or changelog. This reflects the absence of public documentation, not a statement from Vellum that it will never support it.
Loop / iteration block
No: Vellum's only documented list-iteration mechanism is the Map Node, which executes a subworkflow once per array item concurrently (up to 96 parallel executions) rather than as a dedicated sequential for-each/while container; no separate While/loop node is documented.. The Map Node is already the mechanism counted under parallelExecution (concurrent fan-out plus Merge Strategy join). Vellum does not document a way to force single-lane sequential iteration or a distinct while/repeat-until construct.
Integrations
Integrations
302 blocks, ~3,900 tool actions302 first-party blocks, ~3,900 underlying tool actions. Sim's landing page cites "1,000+ integrations," a broader figure counting individual API actions rather than top-level blocks. Both numbers describe the same integration surface.
10,000+ tools via Composio, 100+ nativeVia a Composio partnership (August 2025), Vellum connects to Composio's library of 10,000+ tools directly inside Agent Nodes (Google Sheets, Slack, Salesforce, Notion, Jira, Linear, Trello, etc.). Vellum separately advertises 100+ of its own native integrations.
Trigger types
Webhook, cron, chat, REST API, triggers for 61 appsWebhook, schedule/cron, chat, REST API, and event-based triggers for 61 apps (Slack, Gmail, GitHub, Stripe, etc.)
Chat trigger confirmed; full list undocumentedUnknown. A 'Chat Message Trigger' exists for chat-first agent building; the full set of trigger types (webhook, API, etc.) is not publicly enumerated.
Custom code steps
Python/TypeScript code node with in-browser IDEVellum has a documented 'Code Execution Node' supporting custom Python or TypeScript code with a required main() function signature, an in-browser IDE, and support for public PyPI/npm packages. Newer 'Custom Nodes' are expected to eventually replace it.
API publishing
One-click deploy to a callable APIDeploying a Workflow from the Vellum UI produces a code snippet to call it in production as an API. Vellum handles execution server-side and callers just supply input variables; each execution is also viewable/shareable via an execution URL.
SDKs & extensibility
Open-source Python Workflows SDKThe Workflows SDK (GitHub: vellum-ai/vellum-python-sdks) is an open-source Python framework for defining and executing agentic workflows as graphs declaratively; docs also describe a 'Custom Nodes' extensibility tutorial.. Language support beyond Python is not publicly confirmed.
Publish as MCP server
No: Vellum's MCP support runs one direction only. Its Agent Node lets a workflow connect to and call external/remote MCP servers as tools (with auto-discovered schemas), but nothing documents the reverse: publishing a deployed Vellum workflow as a callable MCP server for external AI tools to consume.. The August 2025 changelog and blog content describe adding MCP servers as tools inside Agent nodes; Vellum's 'How does MCP work' blog post does not address exposing Vellum workflows as MCP endpoints. Some third-party sources conflate this with Vellum's separate personal-assistant product exposing its own MCP server, a different, non-workflow-platform product.
Observability & durability
Tracing & observability
Yes: execution logs include a per-block/per-span trace view (duration, cost, token counts, and latency stats like TTFT/TPS) with expandable nested iteration groups, plus a "View Snapshot" frozen copy of the workflow structure and block states at run time for debugging. This trace view is built directly into Sim rather than a raw export browsable in an external tool like Jaeger, and does not expose aggregate latency-percentile charts (p50/p95/p99). The run snapshot serves as a log-detail/debugging artifact rather than a resumable mid-run checkpoint.
Full execution tracing with shareable URLsVellum automatically captures every Prompt/Workflow execution in production into filterable, sortable Executions tables, including per-step inputs, outputs, latency, and aggregated cost, plus shareable execution URLs for linking from external tools and alerts.
Durability & retries
Tool-call retries (up to 10x); single-attempt job orchestrationIndividual tool/API calls have configurable exponential-backoff retry (up to 10 attempts). The background job-orchestration layer itself retries only once by design. Durability instead comes from consecutive-failure tracking on schedules and the human-in-the-loop snapshot pause/resume mechanism. Sim does not offer guaranteed-once-only block execution, a failed-run holding queue for manual recovery, or a "replay a past execution with its original inputs" feature. The per-execution debugging snapshot serves as a log-detail artifact rather than a resumable mid-run checkpoint.
Automatic node-level retriesVellum supports 'Retry Node Adornments' (organized under an 'Error Handling' section of node Settings) that automatically re-invoke a failed node up to a configured max-attempts count.
Failure alerting
Not publicly documentedUnknown. Not publicly documented.
Data drains
Yes: Enterprise orgs can continuously export workflow logs, job logs, or audit logs on a schedule to a customer-owned S3 bucket, GCS bucket, Azure Blob container, BigQuery table, Snowflake table, Datadog logs intake, or an HTTPS webhook. Each drain exports exactly one data source; multiple drains are created to export multiple sources. Viewing drain config/run history is restricted to org owners/admins.
Yes: Vellum streams execution/monitoring events (workflow execution initiated/fulfilled/rejected, usage calculation, metric execution events) continuously to external systems via configurable webhooks, including documented support for forwarding to Datadog.. Configured from Organization Settings; supports API key, Bearer token, and HMAC verification for webhook payloads. No native S3 or BigQuery connector exists, but the generic webhook mechanism supports building such an export.
Async execution
Yes: a workflow can be triggered in fire-and-forget async mode, returning HTTP 202 with a job ID immediately, then polled via a dedicated jobs endpoint through queued/processing/completed/failed states. Async jobs are tracked via polling the job endpoint rather than a completion webhook/callback option.
Yes: Vellum offers an Execute Workflow Async API endpoint that starts a workflow run and returns an execution_id immediately, without blocking. A separate status endpoint lets clients poll for the current state (PENDING, FULFILLED, REJECTED, etc.) and outputs once the run finishes.. Introduced November 2025. Vellum also documents an Execute Workflow as Stream endpoint for streaming responses, in addition to the synchronous Execute Workflow call that blocks until completion.
Execution limits
5-50 min sync timeout, 90 min async, 15-300 concurrentPlan-gated: synchronous API calls time out at 5 minutes on the free plan and 50 minutes on paid plans, async calls at 90 minutes on every plan, with 15 to 300 concurrent executions per billing entity depending on plan. These limits are not published in docs; request bodies are separately capped at 10 MB.
Concurrency limit exists, no public numbersUnknown: Vellum confirms a per-account concurrency limit exists and that async executions automatically queue once it is exceeded, but does not publish the actual numbers. No max concurrent executions, max execution duration, or requests-per-minute rate limit is listed on its public docs or pricing pages.. The November 2025 changelog states executions 'automatically queue when you exceed your concurrency limit' but gives no figure. The pricing page describes credit-based billing and machine sizes (vCPU/RAM tiers) but no execution timeout or concurrency figures. Third-party blog posts cite older per-day execution caps, but Vellum's current docs do not confirm them, so they are not included as a verified figure.
Partial-failure handling
Yes: Vellum lets you wrap any workflow node with a Try or Retry adornment for first-class error handling, so a single node's failure does not have to halt the entire run. The Try adornment attempts the node once and continues with an Error output if it fails; the Retry adornment repeatedly re-invokes the node until it succeeds or hits a maximum attempt count.. Adornments are applied from the node's side panel and appear in monitoring as a single-node subworkflow, so downstream branches can consume the Error output and keep the rest of the run going instead of the whole execution stopping.
Support
Support channels
Community support plus Enterprise 'Dedicated Support'Community (open source, GitHub) plus an unquantified "Dedicated Support" flag on the Enterprise plan. Enterprise and pricing pages do not include CSM, onboarding/enablement, or professional-services details beyond a plan-comparison-table "Dedicated Support" flag.
Discord community + priority supportDiscord community; priority support included on paid plans. The pricing and enterprise pages reference a Discord community channel and note that the Pro plan includes priority support.
SLA
No SLA content found on current siteUnknown: no SLA commitments or figures found on current public pages. The enterprise and pricing pages now serve the consumer 'Personal Intelligence' product and contain no SLA language (uptime, response time, or otherwise). An earlier version of this page may have referenced named SLA features, but the live site does not confirm that, so it is not included as a verified claim.
Academy / training
No: Vellum has no documented Academy-style learning resource with courses or certification. It offers standard documentation (docs.vellum.ai), a blog, and webinars, but no dedicated course or certification program.. Searches for 'Vellum academy', 'certification', 'courses' turned up only docs, blog posts, and webinars; no evidence of a structured curriculum.
Sim standout features
AI Copilot / Chat agent-building surface
Chat and in-editor Copilot suggest and build workflow changes directly.
A natural-language surface (Chat) and in-editor Copilot that can explain, suggest, and build workflow changes directly, backed by a dedicated copilot module with its own tool registry.Hybrid semantic + keyword knowledge base
Combines vector and full-text search with configurable chunking across 11 file formats.
Built-in RAG with pgvector embeddings and a generated tsvector column for combined vector + full-text search, plus a token-based chunker with configurable chunk size/overlap and 11 supported file formats (csv, doc, docx, html, json, md, pdf, pptx, txt, xlsx, yaml).Native MCP client and server
Call external MCP servers as tools, or expose Sim workflows as an MCP server.
A dedicated MCP block lets any workflow call external MCP servers as a tool, and a serve/workflow-servers API surface lets Sim expose its own workflows as MCP servers.Fork a workspace into dev, qa, and prod environments
Fork, diff, and promote environments with mandatory credential remapping.
Fork a whole workspace into a dev/qa/prod-style child environment, preview a diff, and promote changes bidirectionally. Credential and env-var remapping is required on every promote, so secrets never cross environments silently.Human-in-the-loop approvals with durable resume
Pause a run for human approval and resume later via a durable snapshot link.
A dedicated block pauses a run and waits for a human-submitted approval form, backed by persisted execution snapshots so the run can resume later via a link, even after a server restart.Self-hostable under Apache 2.0
Fully open source with Docker Compose and Helm deployment options.
Fully open source (Apache 2.0), with Docker Compose files and a Helm chart for Kubernetes deployment, alongside a managed cloud-hosted option.Documented Vellum limitations
Brand/product ambiguity as of mid-2026
Public site now foregrounds a consumer product over the enterprise platform.
Vellum's homepage, pricing page, security docs, and several product pages now serve content for a new consumer 'Personal Intelligence' assistant (an open-source, MIT-licensed Mac app) instead of the original enterprise workflow, evaluations, and prompt-engineering platform. That makes enterprise-specific details, like environment promotion, version-control depth, tracing, alerting, and integration counts, harder to verify from the public site alone.BYOK not documented on pricing
No bring-your-own-key option mentioned on pricing pages.
Vellum's pricing pages describe a prepaid-credit model that passes through LLM costs at cost, with no bring-your-own-API-key option mentioned as an alternative.No enterprise SLA published
No public SLA commitments found.
No uptime or response-time SLA commitments are published on the enterprise or pricing pages.Deprecated legacy workflow nodes
Legacy Merge/Conditional/Output nodes retired in favor of newer equivalents.
As of the January 2026 changelog, Vellum deprecated Merge, Conditional, and Output Nodes from the workflow builder UI (replaced by Merge Strategy, Ports, and Workflow Outputs respectively). Existing workflows using them continue to run but new instances can no longer be created.Bottom line
Choose Sim if you want an open-source, self-hostable AI workspace that treats AI agents as first-class citizens: native multi-LLM support, real-time multiplayer editing, environment promotion (dev/qa/prod), human-in-the-loop approvals, and enterprise governance (SSO, credential-level permissions, audit logs) built in rather than bolted on.
Choose Vellum if you specifically need self-hosted / VPC enterprise deployment: Enterprise customers can run the platform inside their own AWS, Azure, or GCP VPC (or on-prem) via a Replicated-based install, keeping prompts and documents inside the customer's network perimeter.
Frequently asked questions
Sim is an open-source AI workspace where teams build, deploy, and manage AI agents visually, conversationally, or with code. Vellum is an enterprise AI development platform for building, evaluating, and deploying LLM prompts, workflows, and agents. Teams considering a switch typically weigh licensing (Sim is Apache 2.0 and self-hostable), pricing model, and how AI-native the platform's agent-building experience is.