From 2918918e94c3988650577417384b0fc2a847e38e Mon Sep 17 00:00:00 2001 From: Justin Blumencranz <96924014+j15z@users.noreply.github.com> Date: Tue, 15 Sep 2026 17:12:27 -0700 Subject: [PATCH 1/3] feat(comparisons): merge the compliance facts and add a SCIM row A profile stated its certifications twice: once as a bare SOC 2 yes/no and again under additional compliance. Merge them into one `compliance` fact that carries every certification, its report scope, and its access conditions in one place, keeping the long-form text from both. Add a `scim` row next to SSO. Sim ships SCIM 2.0 directory provisioning on Enterprise, and provisioning is a distinct buying question from authentication, so it deserves its own comparable row rather than a clause buried in the SSO cell. Where a profile described provisioning inside its SSO fact, that content moves to the new row and SSO keeps authentication. Every SCIM value is sourced to a vendor page fetched today. Where a product does not publish its provisioning support, the row says it is not documented and carries `confidence: 'unknown'` rather than asserting the product lacks it. Co-Authored-By: Claude Opus 5 --- .../comparisons/comparison-sections.ts | 4 +- apps/sim/app/(landing)/comparisons/utils.ts | 2 +- .../compare/data/competitors/claude-cowork.ts | 50 ++++++++------ .../lib/compare/data/competitors/crewai.ts | 40 +++++------ apps/sim/lib/compare/data/competitors/dust.ts | 55 ++++++++------- .../lib/compare/data/competitors/flowise.ts | 20 +++--- .../lib/compare/data/competitors/gumloop.ts | 42 +++++------ .../lib/compare/data/competitors/langchain.ts | 47 ++++++------- .../lib/compare/data/competitors/langflow.ts | 22 +++--- apps/sim/lib/compare/data/competitors/make.ts | 53 +++++++------- .../data/competitors/microsoft-copilot.ts | 53 +++++++------- apps/sim/lib/compare/data/competitors/n8n.ts | 38 ++++------ .../data/competitors/openai-agentkit.ts | 66 ++++++++++-------- .../lib/compare/data/competitors/openclaw.ts | 50 ++++++++------ .../lib/compare/data/competitors/pipedream.ts | 51 +++++++------- .../data/competitors/power-automate.ts | 62 +++++++++-------- .../lib/compare/data/competitors/retool.ts | 54 +++++++-------- .../lib/compare/data/competitors/stackai.ts | 36 ++++------ .../sim/lib/compare/data/competitors/tines.ts | 43 ++++++------ .../lib/compare/data/competitors/vellum.ts | 36 ++++------ .../lib/compare/data/competitors/workato.ts | 53 +++++++------- .../lib/compare/data/competitors/zapier.ts | 69 ++++++++++--------- apps/sim/lib/compare/data/sim.ts | 50 +++++++------- apps/sim/lib/compare/data/types.ts | 7 +- 24 files changed, 510 insertions(+), 493 deletions(-) diff --git a/apps/sim/app/(landing)/comparisons/comparison-sections.ts b/apps/sim/app/(landing)/comparisons/comparison-sections.ts index 93f82aa5ca0..cfe210431be 100644 --- a/apps/sim/app/(landing)/comparisons/comparison-sections.ts +++ b/apps/sim/app/(landing)/comparisons/comparison-sections.ts @@ -87,14 +87,14 @@ export const COMPARISON_SECTIONS: ComparisonSectionDef[] = [ group: 'security', title: 'Security & compliance', rows: [ - { key: 'soc2', label: 'SOC 2' }, + { key: 'compliance', label: 'Compliance' }, { key: 'dataResidency', label: 'Data residency' }, { key: 'rbac', label: 'Role-based access control' }, { key: 'auditLogging', label: 'Audit logging' }, - { key: 'additionalCompliance', label: 'Additional compliance' }, { key: 'modelAndToolGovernance', label: 'Model & tool governance' }, { key: 'credentialGovernance', label: 'Credential governance' }, { key: 'sso', label: 'Single sign-on (SSO)' }, + { key: 'scim', label: 'SCIM provisioning' }, { key: 'sessionPolicy', label: 'Custom session policy' }, { key: 'thirdPartyVetting', label: 'Vetted first-party integrations' }, { key: 'piiRedaction', label: 'PII redaction' }, diff --git a/apps/sim/app/(landing)/comparisons/utils.ts b/apps/sim/app/(landing)/comparisons/utils.ts index 1c896d501fe..d1c79bc228b 100644 --- a/apps/sim/app/(landing)/comparisons/utils.ts +++ b/apps/sim/app/(landing)/comparisons/utils.ts @@ -134,7 +134,7 @@ export function buildComparisonFaqs(competitor: CompetitorProfile): ComparisonFa }, { question: `Is Sim more secure than ${name}?`, - answer: `Security is a like-for-like comparison, not a one-line verdict. Sim: ${summarizeFact(simProfile.facts.security.additionalCompliance.value)} ${name}: ${summarizeFact(facts.security.additionalCompliance.value)} Check the Security & compliance rows above for the full breakdown, including SSO, audit logging, and data residency.`, + answer: `Security is a like-for-like comparison, not a one-line verdict. Sim: ${summarizeFact(simProfile.facts.security.compliance.value)} ${name}: ${summarizeFact(facts.security.compliance.value)} Check the Security & compliance rows above for the full breakdown, including SSO, audit logging, and data residency.`, }, { question: `Which has stronger AI agent capabilities, Sim or ${name}?`, diff --git a/apps/sim/lib/compare/data/competitors/claude-cowork.ts b/apps/sim/lib/compare/data/competitors/claude-cowork.ts index 520bf5550d4..7a7049e069e 100644 --- a/apps/sim/lib/compare/data/competitors/claude-cowork.ts +++ b/apps/sim/lib/compare/data/competitors/claude-cowork.ts @@ -749,11 +749,11 @@ export const claudeCoworkProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes (company-wide, not Cowork-specific)', - detail: - 'Anthropic holds SOC 2 Type I and Type II; the detailed report is available under NDA via the Anthropic Trust Portal. There is no Cowork-specific SOC 2 scoping statement.', - shortValue: 'Company-wide, not Cowork-specific', + compliance: { + value: + 'Yes, but company-wide rather than Cowork-specific: Anthropic holds SOC 2 Type I and Type II, ISO 27001:2022, and ISO/IEC 42001:2023, and is HIPAA-ready with a BAA available through sales-assisted Enterprise. The detailed SOC 2 report is available under NDA via the Anthropic Trust Portal, and there is no Cowork-specific SOC 2 scoping statement.', + detail: 'Company-wide Anthropic certifications, not Cowork-scoped.', + shortValue: 'Company-wide SOC 2, ISO 27001/42001, HIPAA-ready', confidence: 'estimated', sources: [ { @@ -761,6 +761,11 @@ export const claudeCoworkProfile: CompetitorProfile = { label: 'Anthropic Trust Center', asOf: '2026-07-02', }, + { + url: 'https://support.claude.com/en/articles/10015870-what-certifications-has-anthropic-obtained', + label: 'What Certifications has Anthropic obtained?', + asOf: '2026-07-08', + }, ], }, dataResidency: { @@ -807,20 +812,6 @@ export const claudeCoworkProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'ISO 27001:2022, ISO/IEC 42001:2023, HIPAA-ready (BAA via sales-assisted Enterprise)', - detail: 'Company-wide Anthropic certifications, not Cowork-scoped.', - shortValue: 'ISO 27001, ISO 42001, HIPAA-ready', - confidence: 'estimated', - sources: [ - { - url: 'https://support.claude.com/en/articles/10015870-what-certifications-has-anthropic-obtained', - label: 'What Certifications has Anthropic obtained?', - asOf: '2026-07-08', - }, - ], - }, modelAndToolGovernance: { value: 'Yes: Group Spend Limits and Per-Tool Connector Controls (GA, April 9, 2026)', detail: @@ -908,10 +899,10 @@ export const claudeCoworkProfile: CompetitorProfile = { }, sso: { value: - 'Yes: Claude Enterprise supports SAML 2.0 single sign-on with identity providers like Okta, Entra ID, Google, OneLogin, JumpCloud, and Duo, plus domain capture (claims your email domain so all logins route through SSO) and automated JIT/SCIM user provisioning and de-provisioning tied to the IdP.', + 'Yes: Claude Enterprise supports SAML 2.0 single sign-on with identity providers like Okta, Entra ID, Google, OneLogin, JumpCloud, and Duo, plus domain capture (claims your email domain so all logins route through SSO).', detail: "This is an Enterprise-plan feature covering claude.ai, Claude Desktop, and Cowork logins collectively, not configured separately for Cowork. Anthropic's SSO documentation describes SAML integrations specifically; it does not document OIDC support.", - shortValue: 'Yes: SAML SSO + SCIM auto-provisioning', + shortValue: 'Yes: SAML 2.0 SSO with domain capture', confidence: 'verified', sources: [ { @@ -919,10 +910,25 @@ export const claudeCoworkProfile: CompetitorProfile = { label: 'Set up single sign-on (SSO)', asOf: '2026-07-02', }, + ], + }, + scim: { + value: + 'Yes, at the Anthropic organization level rather than as a Cowork feature: SCIM directory sync is available only to Enterprise plan organizations and to Console organizations that have their own parent organization or are joined to an Enterprise parent, and is not available on Team plans or to Console organizations joined to a Team plan parent. Users assigned to the identity-provider app are automatically provisioned into every organization joined to the parent org, and users removed from the IdP app are automatically removed. Enabling group mappings controls which users are provisioned to which organizations and with which roles, so role and seat types propagate automatically from IdP group membership instead of being changed by hand. Supported identity providers include Okta, Microsoft Entra ID, Google Workspace, OneLogin, JumpCloud, and Ping Identity, with further providers reachable through WorkOS. Documented limits: each parent organization can be linked to only one identity provider, so every organization under it uses the same IdP, and the Primary Owner is exempt from SCIM reconciliation and cannot be assigned through group mappings, leaving ownership a manual transfer.', + detail: + 'SCIM and JIT are the two provisioning modes, and either can be combined with group mappings; without them, roles and seat types are changed by hand. Provisioning is configured once for the Claude organization and covers claude.ai, Claude Desktop, and Cowork collectively rather than being set up separately for Cowork.', + shortValue: 'Yes: SCIM directory sync on Enterprise plans', + confidence: 'verified', + sources: [ + { + url: 'https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning', + label: 'Set up JIT or SCIM provisioning', + asOf: '2026-09-15', + }, { url: 'https://support.claude.com/en/articles/10276682-important-considerations-before-enabling-single-sign-on-sso-and-jit-scim-provisioning', label: 'Important considerations before enabling SSO and JIT/SCIM provisioning', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/crewai.ts b/apps/sim/lib/compare/data/competitors/crewai.ts index 811898524c2..fe1021bedf9 100644 --- a/apps/sim/lib/compare/data/competitors/crewai.ts +++ b/apps/sim/lib/compare/data/competitors/crewai.ts @@ -786,12 +786,12 @@ export const crewaiProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - 'Yes: CrewAI AMP has a SOC 2 Type 1 audit report (dated November 2025), available via its Trust Center', + 'Yes: CrewAI AMP has a SOC 2 Type 1 audit report (dated November 2025) and a HIPAA audit report (dated February 2026) for the Enterprise edition, both available via its Trust Center. No ISO 27001, PCI, or FedRAMP certification is confirmed. These attestations apply to the Enterprise/AMP offering, not to a self-hosted deployment of the open-source framework, which has no compliance certification of its own since it is not a hosted service.', detail: - "CrewAI's Trust Center (trust.crewai.com, indexed by Vanta) lists a SOC 2 Type 1 Audit Report from November 2025. This applies to the Enterprise/AMP offering, not to a self-hosted deployment of the open-source framework, which has no compliance certification of its own since it isn't a hosted service.", - shortValue: 'SOC 2 Type 1 report (Nov 2025) for the AMP platform', + "CrewAI's Trust Center (trust.crewai.com, indexed by Vanta) lists the SOC 2 Type 1 Audit Report from November 2025 alongside the HIPAA Audit Report from February 2026. CrewAI's pricing page separately references 'FedRamp High compliance' language for its Enterprise tier, but no independent FedRAMP authorization listing corroborates that claim, so it is not treated as confirmed here.", + shortValue: 'SOC 2 Type 1 and HIPAA audits, AMP Enterprise only', confidence: 'estimated', sources: [ { @@ -799,6 +799,11 @@ export const crewaiProfile: CompetitorProfile = { label: 'CrewAI Trust Center', asOf: '2026-07-02', }, + { + url: 'https://crewai.com/pricing', + label: 'CrewAI Pricing', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -846,26 +851,6 @@ export const crewaiProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'HIPAA (Enterprise edition, audit report dated February 2026); no ISO 27001, PCI, or FedRAMP certification confirmed', - detail: - "CrewAI's Trust Center lists a HIPAA Audit Report dated February 2026 for the Enterprise edition, alongside the SOC 2 Type 1 report. CrewAI's pricing page separately references 'FedRamp High compliance' language for its Enterprise tier, but no independent FedRAMP authorization listing corroborates that claim, so it is not treated as confirmed here.", - shortValue: 'HIPAA audit (Feb 2026); FedRAMP claim unconfirmed', - confidence: 'estimated', - sources: [ - { - url: 'https://trust.crewai.com/', - label: 'CrewAI Trust Center', - asOf: '2026-07-02', - }, - { - url: 'https://crewai.com/pricing', - label: 'CrewAI Pricing', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Not publicly documented', detail: @@ -935,6 +920,13 @@ export const crewaiProfile: CompetitorProfile = { }, ], }, + scim: { + value: + 'Not publicly documented: no CrewAI page describes SCIM 2.0 directory provisioning or automated creation, update, or deactivation of members from an identity provider. The platform SSO documentation covers SAML 2.0 and OAuth 2.0/OIDC authentication through WorkOS (the SaaS default), Microsoft Entra ID, Okta, Auth0, and Keycloak, and the pricing page lists SSO and role-based access control as Enterprise-tier features, but neither names SCIM, directory sync, or group-to-role provisioning. The open-source framework has no user accounts or sign-in at all, so the question does not apply to it. Not finding a SCIM page is not itself confirmation that the capability does not exist.', + shortValue: 'Not publicly documented; SSO only, no SCIM', + confidence: 'unknown', + sources: [], + }, sessionPolicy: { value: "Not publicly documented: no admin-configurable session lifetime or idle timeout appears in CrewAI AMP's public docs; the SSO, RBAC, and self-hosted configuration pages name no session control", diff --git a/apps/sim/lib/compare/data/competitors/dust.ts b/apps/sim/lib/compare/data/competitors/dust.ts index 2e6aebed4cb..0b7a13421fa 100644 --- a/apps/sim/lib/compare/data/competitors/dust.ts +++ b/apps/sim/lib/compare/data/competitors/dust.ts @@ -810,12 +810,13 @@ export const dustProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type II certified, achieved audit readiness with Vanta in three weeks', + compliance: { + value: + "SOC 2 Type II certified, with audit readiness achieved with Vanta in three weeks and the report downloadable through Dust's Trust Center; also GDPR compliant and HIPAA-capable; no ISO 27001, PCI, or FedRAMP", detail: - "Dust's own security page states SOC 2 Type II certification; a Vanta customer case study describes Dust achieving SOC 2 Type II audit readiness in three weeks using Vanta's automation, reducing compliance workload by roughly 50%. The report is downloadable via Dust's Trust Center.", - shortValue: 'SOC 2 Type II certified, report via Trust Center', - confidence: 'verified', + "Dust's own security page states SOC 2 Type II certification; a Vanta customer case study describes Dust achieving SOC 2 Type II audit readiness in three weeks using Vanta's automation, reducing compliance workload by roughly 50%. The report is downloadable via Dust's Trust Center. Dust's security page and enterprise materials additionally state GDPR compliance and HIPAA-compliance capability alongside SOC 2 Type II. No source confirms ISO 27001, PCI-DSS, or FedRAMP.", + shortValue: 'SOC 2 Type II, GDPR, HIPAA-capable; no ISO/PCI', + confidence: 'estimated', sources: [ { url: 'https://www.vanta.com/customers/dust', @@ -827,6 +828,11 @@ export const dustProfile: CompetitorProfile = { label: 'Dust Trust Center', asOf: '2026-07-02', }, + { + url: 'https://dust.tt/home/security', + label: 'Dust Security', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -873,20 +879,6 @@ export const dustProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: 'GDPR compliant, HIPAA-capable, SOC 2 Type II; no ISO 27001, PCI, or FedRAMP', - detail: - "Dust's security page and enterprise materials state GDPR compliance and HIPAA-compliance capability alongside SOC 2 Type II. No source confirms ISO 27001, PCI-DSS, or FedRAMP.", - shortValue: 'GDPR, HIPAA-capable, SOC 2 Type II', - confidence: 'estimated', - sources: [ - { - url: 'https://dust.tt/home/security', - label: 'Dust Security', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Not publicly documented', detail: @@ -941,11 +933,10 @@ export const dustProfile: CompetitorProfile = { sources: [], }, sso: { - value: - 'Yes: SSO (e.g. Okta, Entra, JumpCloud) and SCIM user provisioning on the Enterprise plan', + value: 'Yes: SSO (SAML, OIDC) on the Enterprise plan, e.g. Okta, Entra, JumpCloud', detail: - 'Enterprise plan materials name SSO and SCIM explicitly, and a third-party enterprise summary lists Okta/Entra/JumpCloud as example supported identity providers.', - shortValue: 'SSO and SCIM provisioning, Enterprise plan', + 'Enterprise plan materials name SSO (SAML, OIDC) explicitly, and a third-party enterprise summary lists Okta/Entra/JumpCloud as example supported identity providers.', + shortValue: 'SAML/OIDC SSO on the Enterprise plan', confidence: 'verified', sources: [ { @@ -955,6 +946,24 @@ export const dustProfile: CompetitorProfile = { }, ], }, + scim: { + value: + "Yes: SCIM 2.0 user and group provisioning, documented as an enterprise feature requiring admin access. Dust states that users are created, updated, and deactivated in Dust automatically from the identity provider; an admin selects their IdP from a list during setup, with Okta given as the worked example and per-IdP documentation recommended because the steps differ by provider. Groups are provisioned alongside users and mapped to Dust roles in settings, replacing an earlier scheme that relied on groups named exactly dust-admins and dust-managers; a user always keeps the highest role granted across their groups (admin outranks manager). Provisioning the relevant groups is also what enables department-segmented analytics. Dust publishes no fixed list of supported identity providers, and manual group management remains available alongside SCIM-provisioned groups. Dust's own Enterprise page separately lists SCIM alongside SSO and role-based permissions as enterprise-readiness features.", + shortValue: 'Yes: SCIM user and group provisioning, enterprise', + confidence: 'verified', + sources: [ + { + url: 'https://docs.dust.tt/docs/users-and-groups-provisioning', + label: 'Users and groups provisioning | Dust Docs', + asOf: '2026-09-15', + }, + { + url: 'https://dust.tt/home/enterprise', + label: 'Dust for Enterprise', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: 'Not publicly documented: Dust documents SAML SSO with workspace-wide enforcement and SCIM provisioning on the Enterprise plan, but no admin-configurable absolute session lifetime or idle timeout, and no fixed session length is published either', diff --git a/apps/sim/lib/compare/data/competitors/flowise.ts b/apps/sim/lib/compare/data/competitors/flowise.ts index eda221873d5..5c938f7e7a1 100644 --- a/apps/sim/lib/compare/data/competitors/flowise.ts +++ b/apps/sim/lib/compare/data/competitors/flowise.ts @@ -671,12 +671,12 @@ export const flowiseProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - 'Unknown: a third-party security-scan aggregator (Nudge Security) lists Flowise as SOC 2 compliant among several other certifications, but Flowise has published no SOC 2 report, badge, or trust page of its own.', + 'Unknown: a third-party security-scan aggregator (Nudge Security) lists Flowise as SOC 2 compliant among several other certifications, but Flowise has published no SOC 2 report, badge, or trust page of its own, and beyond that unconfirmed third-party SOC 2 claim it has published no HIPAA, ISO 27001, PCI, or FedRAMP certification either.', detail: 'The same third-party source also claims FedRAMP and PCI compliance for a small startup, an atypical combination not corroborated on flowiseai.com.', - shortValue: 'No official confirmation found', + shortValue: 'Unknown, no official certifications published', confidence: 'unknown', sources: [], }, @@ -719,13 +719,6 @@ export const flowiseProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'Unknown: beyond the unconfirmed third-party SOC 2 claim, Flowise has published no HIPAA, ISO 27001, PCI, or FedRAMP certification.', - shortValue: 'Unknown, no official certifications published', - confidence: 'unknown', - sources: [], - }, modelAndToolGovernance: { value: "Unknown: no documented admin controls restrict which specific LLM providers/models or which tools/integrations a given role may use. Flowise's RBAC governs resource-level (create/edit/delete) permissions, not model/tool allowlists.", @@ -787,6 +780,13 @@ export const flowiseProfile: CompetitorProfile = { }, ], }, + scim: { + value: + 'Not publicly documented: no Flowise documentation page describes SCIM 2.0 directory provisioning or any automated creation, update, or deactivation of members driven by an identity provider. Flowise documents Enterprise-plan SSO as OIDC authentication only (Microsoft Azure/Entra ID, Google, and Auth0) and requires every user to be invited into a workspace with a role before their first SSO sign-in works, so member lifecycle is manual rather than directory-driven. Not finding a SCIM page is not itself confirmation that the capability does not exist.', + shortValue: 'Not publicly documented; members invited manually', + confidence: 'unknown', + sources: [], + }, sessionPolicy: { value: 'Partial: self-hosted server environment variables rather than an admin-console setting. JWT_TOKEN_EXPIRY_IN_MINUTES sets the access-token lifetime and JWT_REFRESH_TOKEN_EXPIRY_IN_MINUTES sets the refresh-token lifetime, which together bound how long a sign-in survives, and EXPIRE_AUTH_TOKENS_ON_RESTART invalidates all tokens on server restart. No idle/inactivity timeout is documented, and Flowise does not document any equivalent control for admins of the managed Flowise Cloud product.', diff --git a/apps/sim/lib/compare/data/competitors/gumloop.ts b/apps/sim/lib/compare/data/competitors/gumloop.ts index 936f979c68f..4909cb581d0 100644 --- a/apps/sim/lib/compare/data/competitors/gumloop.ts +++ b/apps/sim/lib/compare/data/competitors/gumloop.ts @@ -792,10 +792,12 @@ export const gumloopProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - 'SOC 2 Type II attested; also HIPAA-compliant with BAAs available on eligible plans, and GDPR-aligned with EU-U.S. Data Privacy Framework (incl. UK Extension) certification', - shortValue: 'SOC 2 Type II, HIPAA, GDPR-aligned', + 'SOC 2 Type II attested; HIPAA-compliant with Business Associate Agreements (BAAs) available on eligible plans; GDPR-aligned privacy program plus EU-U.S. Data Privacy Framework certification including the UK Extension; no ISO 27001, PCI DSS, or FedRAMP', + detail: + 'Gumloop is SOC 2 Type II attested, is HIPAA compliant with Business Associate Agreements (BAAs) available on eligible plans, maintains a GDPR-aligned privacy program, and is certified under the EU-U.S. Data Privacy Framework including the UK Extension. It also has zero-data-retention (ZDR) agreements with major LLM providers, BYOK support, encryption in transit and at rest, and DPAs for Enterprise customers, but no ISO 27001, PCI DSS, or FedRAMP.', + shortValue: 'SOC 2 Type II, HIPAA, GDPR; no ISO/PCI/FedRAMP', confidence: 'verified', sources: [ { @@ -854,21 +856,6 @@ export const gumloopProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'SOC 2 Type II, HIPAA (with BAAs), GDPR-aligned program plus EU-U.S. Data Privacy Framework (incl. UK Extension); no ISO 27001, PCI, or FedRAMP', - detail: - 'Gumloop is SOC 2 Type II attested, is HIPAA compliant with Business Associate Agreements (BAAs) available on eligible plans, maintains a GDPR-aligned privacy program, and is certified under the EU-U.S. Data Privacy Framework including the UK Extension. It also has zero-data-retention (ZDR) agreements with major LLM providers, BYOK support, encryption in transit and at rest, and DPAs for Enterprise customers, but no ISO 27001, PCI DSS, or FedRAMP.', - shortValue: 'SOC 2, HIPAA, GDPR; no ISO/PCI/FedRAMP', - confidence: 'verified', - sources: [ - { - url: 'https://www.gumloop.com/solutions/security', - label: 'Gumloop: Security and trust', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Yes for models: an org-wide AI Model Control setting lets admins restrict members to an allow-list or block-list of models, set automatic fallback models (including a separate fallback for image generation), and override the default Recommended/Smartest/Fastest presets so all agents use consistent model choices. Tool governance is handled separately via the per-tool authorization policies covered under RBAC/ABAC, not a distinct model-and-tool control surface.', @@ -965,10 +952,10 @@ export const gumloopProfile: CompetitorProfile = { }, sso: { value: - 'Yes: Gumloop supports enterprise SSO via SAML 2.0 (Okta, Entra ID, Google Workspace, JumpCloud, Ping Identity, Active Directory) plus Google/Microsoft OAuth. An SCIM add-on for Okta and Microsoft Entra ID auto-provisions and deprovisions users, syncs custom roles and teams from IdP groups, and runs on a 15-minute sync cycle.', + 'Yes: Gumloop supports enterprise SSO via SAML 2.0 (Okta, Entra ID, Google Workspace, JumpCloud, Ping Identity, Active Directory) plus Google/Microsoft OAuth.', detail: 'Requires Admin role and an Enterprise subscription; enforces SP-initiated login only.', - shortValue: 'Yes: SAML SSO plus SCIM auto-provisioning', + shortValue: 'Yes: SAML 2.0 SSO plus Google/Microsoft OAuth', confidence: 'verified', sources: [ { @@ -978,6 +965,21 @@ export const gumloopProfile: CompetitorProfile = { }, ], }, + scim: { + value: + 'Yes: SCIM 2.0 provisioning is available as an add-on, supported for Okta and Microsoft Entra ID only, and enabled on request by contacting Gumloop support. Users assigned the application in the IdP are automatically provisioned, kept updated, and automatically deprovisioned when removed, which frees up seats. IdP groups can be mapped to Gumloop Custom Roles and, separately, to teams (projects), using either curated mapping tables or name-based auto-resolution, with a user receiving the union of all matched mappings. Sync runs automatically every 15 minutes and admins can also trigger an on-demand sync. Documented limit: SCIM can only add users to teams inside the synced organization.', + detail: + 'SCIM is an add-on rather than a standard plan feature: Gumloop directs customers to contact support@gumloop.com to request enablement, and reaching the SSO/SCIM settings requires the Admin organization role and an Enterprise subscription.', + shortValue: 'Yes: add-on SCIM for Okta and Entra ID', + confidence: 'verified', + sources: [ + { + url: 'https://docs.gumloop.com/enterprise-features/sso_saml_scim', + label: 'SSO, SAML & SCIM - Gumloop docs', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: 'Not publicly documented: no admin-configurable session lifetime or idle timeout appears in Gumloop\'s public documentation. The only primary-source statement is a single bullet on the Enterprise SSO page listing "Session Management: Configurable session timeouts and secure token handling." No admin setting name, configuration steps, default session lifetime, idle-timeout value, or absolute-cap value is published anywhere in Gumloop\'s docs, security page, or trust center.', diff --git a/apps/sim/lib/compare/data/competitors/langchain.ts b/apps/sim/lib/compare/data/competitors/langchain.ts index 7c5b3e90b19..0b4fb29eebb 100644 --- a/apps/sim/lib/compare/data/competitors/langchain.ts +++ b/apps/sim/lib/compare/data/competitors/langchain.ts @@ -781,12 +781,12 @@ export const langchainProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - "Yes: LangSmith is SOC 2 Type II certified. LangGraph Platform (now branded LangSmith Deployment) is publicly announced as carrying the same attestation, sharing LangSmith's infrastructure and compliance posture.", + "Yes: LangSmith is SOC 2 Type II certified, and is additionally stated to be HIPAA compliant and GDPR compliant. LangGraph Platform (now branded LangSmith Deployment) is publicly announced as carrying the same attestation, sharing LangSmith's infrastructure and compliance posture. No ISO 27001, PCI-DSS, or FedRAMP attestation was found on LangChain's own compliance materials.", detail: - "LangChain's Trust Center (trust.langchain.com) is the canonical source but renders via client-side JavaScript, so it could not be directly verified by an automated fetch; the LangSmith-side certification is independently confirmed on a static docs page.", - shortValue: 'Yes, SOC 2 Type II for LangSmith; LangGraph Platform shares it', + "LangChain's Trust Center (trust.langchain.com) is the canonical source for these claims but renders via client-side JavaScript, so it could not be directly verified by an automated fetch; the SOC 2 Type II certification is independently confirmed on a static docs page, while the HIPAA and GDPR claims rest on LangChain's own docs and Trust Center.", + shortValue: 'SOC 2 Type II, HIPAA, GDPR; no ISO/PCI/FedRAMP', confidence: 'verified', sources: [ { @@ -794,6 +794,11 @@ export const langchainProfile: CompetitorProfile = { label: 'Regions FAQ - Docs by LangChain (confirms SOC 2 Type 2)', asOf: '2026-07-08', }, + { + url: 'https://trust.langchain.com/', + label: 'LangChain Trust Center', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -835,25 +840,6 @@ export const langchainProfile: CompetitorProfile = { confidence: 'unknown', sources: [], }, - additionalCompliance: { - value: 'HIPAA and GDPR, in addition to SOC 2 Type II', - detail: - "LangChain's own docs and Trust Center state LangSmith is SOC 2 Type II, HIPAA compliant, and GDPR compliant; no ISO 27001, PCI-DSS, or FedRAMP attestation was found on LangChain's own compliance materials.", - shortValue: 'HIPAA and GDPR compliant, alongside SOC 2 Type II', - confidence: 'verified', - sources: [ - { - url: 'https://docs.langchain.com/langsmith/regions-faq', - label: 'Regions FAQ - Docs by LangChain', - asOf: '2026-07-02', - }, - { - url: 'https://trust.langchain.com/', - label: 'LangChain Trust Center', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Not publicly documented: no LangSmith/LangGraph Platform feature restricts which LLM providers or tools a given role/user may invoke beyond general workspace RBAC and API-key scoping', @@ -933,6 +919,21 @@ export const langchainProfile: CompetitorProfile = { }, ], }, + scim: { + value: + 'Yes: LangSmith supports SCIM 2.0 directory provisioning on the Enterprise plan, automatically provisioning and de-provisioning users across the LangSmith organization and its workspaces and keeping user status, group membership, and organization/workspace role assignments in sync with the identity provider. Microsoft Entra ID (Azure) and Okta are the documented providers, and other identity providers "have not been tested but may function depending on their SCIM implementation". The IdP must support SCIM 2.0, only Organization Admins can configure it, cloud customers must have SAML SSO configurable for the organization while self-hosted customers must enable OAuth with Client Secret authentication, and the docs instruct operators to disable just-in-time (JIT) provisioning first to prevent conflicts between automatic and manual user provisioning. Documented limits: the push from the IdP runs on roughly a one-hour cadence, group renaming is not supported via SCIM, and SCIM connections typically require HTTP/1.1 or later, so an HTTP/1.0 client may hit a 426 Upgrade Required error.', + detail: + 'Role mapping is driven by an IdP group naming convention (), so an admin assigns specific organization roles and workspace roles to groups of users. A lighter Enterprise alternative, SSO Groups Sync, instead reads group membership from the SSO token at login time rather than requiring IdP group push.', + shortValue: 'Yes, SCIM 2.0 with group role mapping, Enterprise plan', + confidence: 'verified', + sources: [ + { + url: 'https://docs.langchain.com/langsmith/user-management', + label: 'User management - Docs by LangChain (SCIM setup and limits)', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: 'Partial: self-hosted LangSmith only. An operator sets the maximum session length via the OAUTH_SESSION_MAX_SEC environment variable when using OAuth 2.0/SSO, or BASIC_AUTH_JWT_EXPIRATION_SECONDS when using basic authentication, both defaulting to 28800 seconds (8 hours). No equivalent admin-configurable session control is documented for LangSmith Cloud.', diff --git a/apps/sim/lib/compare/data/competitors/langflow.ts b/apps/sim/lib/compare/data/competitors/langflow.ts index c481c2f9548..883cecbde84 100644 --- a/apps/sim/lib/compare/data/competitors/langflow.ts +++ b/apps/sim/lib/compare/data/competitors/langflow.ts @@ -689,12 +689,12 @@ export const langflowProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - "Unknown: no public documentation or official page states a SOC 2 certification for Langflow. The docs' Security page discusses infrastructure-level responsibility for operators, not a compliance certification.", + "Unknown: no public documentation or official page states a SOC 2 certification for Langflow, and none confirms HIPAA, ISO 27001, a GDPR-specific attestation, PCI, or FedRAMP either. The docs' Security page discusses infrastructure-level responsibility for operators, not a compliance certification.", detail: 'Security docs place isolation and compliance burden on the deploying organization.', - shortValue: 'Unknown, no SOC2 certification documented', + shortValue: 'Unknown, no compliance certifications documented', confidence: 'unknown', sources: [], }, @@ -737,13 +737,6 @@ export const langflowProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'Unknown: no public documentation or official page confirms HIPAA, ISO 27001, GDPR-specific attestation, PCI, or FedRAMP certification for Langflow.', - shortValue: 'Unknown, no compliance certifications documented', - confidence: 'unknown', - sources: [], - }, modelAndToolGovernance: { value: 'Unknown: no public documentation describes an admin-configurable restriction on which LLM providers, models, or tools a given role or user may use. Model Providers configuration in Settings appears to be workspace-wide rather than per-role gated.', @@ -809,6 +802,15 @@ export const langflowProfile: CompetitorProfile = { confidence: 'unknown', sources: [], }, + scim: { + value: + 'Not publicly documented: no Langflow documentation page describes SCIM 2.0 directory provisioning, or any identity-provider-driven creation, update, or deactivation of members with group or role mapping. What Langflow does document is built-in username/password sign-in with short-lived JWTs and API keys validated against its own database, plus an external-authentication mode where a proxy forwards an identity-provider token that Langflow validates against the provider JWKS endpoint and then provisions a local user automatically, which is just-in-time sign-in provisioning rather than directory-driven lifecycle management. Not finding a SCIM page is not itself confirmation that the capability does not exist.', + detail: + 'Role-based access control is an optional plugin applied after authentication, so even where roles exist they are assigned inside Langflow rather than pushed from a directory.', + shortValue: 'Not publicly documented; no SCIM provisioning described', + confidence: 'unknown', + sources: [], + }, sessionPolicy: { value: 'Partial: on self-hosted deployments only, via environment variables. Langflow issues short-lived JWTs and exposes `LANGFLOW_ACCESS_TOKEN_EXPIRE_SECONDS` (default 3600, one hour) and `LANGFLOW_REFRESH_TOKEN_EXPIRE_SECONDS` (default 604800, seven days), so an operator sets the absolute ceiling on how long a signed-in session survives before re-authentication. No inactivity or idle timeout setting is documented, and no admin-console UI for setting session policy across an organization is documented for Langflow Cloud.', diff --git a/apps/sim/lib/compare/data/competitors/make.ts b/apps/sim/lib/compare/data/competitors/make.ts index d85f6158560..685ecb93ef7 100644 --- a/apps/sim/lib/compare/data/competitors/make.ts +++ b/apps/sim/lib/compare/data/competitors/make.ts @@ -849,11 +849,12 @@ export const makeProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type II and SOC 3 completed; ISO 27001 certified; GDPR compliant', + compliance: { + value: + "Yes: SOC 2 Type II and SOC 3 completed, ISO 27001 certified, and GDPR compliant; no HIPAA, PCI, or FedRAMP mentioned. Make's Security page lists a completed SOC 2 Type II audit, a publicly available SOC 3 report, ISO 27001 certification for the platform, and GDPR compliance. HIPAA is not mentioned on that page and is not offered.", detail: - "Make's Security page lists completed SOC 2 Type II audit, a publicly available SOC 3 report, ISO 27001 certification for the platform, and GDPR compliance. HIPAA is not mentioned on this page.", - shortValue: 'SOC 2 Type II, SOC 3, ISO 27001, GDPR', + "Make's Security page states the company operates an ISO 27001-certified information security program and runs infrastructure compliant with SOC 3 and SOC 2 Type II audits, alongside GDPR adherence (Make also has a dedicated GDPR page). HIPAA compliance is not mentioned or offered, and no PCI or FedRAMP coverage is mentioned.", + shortValue: 'SOC 2, SOC 3, ISO 27001, GDPR; no HIPAA', confidence: 'verified', sources: [ { @@ -861,6 +862,16 @@ export const makeProfile: CompetitorProfile = { label: 'Make Security page', asOf: '2026-07-02', }, + { + url: 'https://www.make.com/en/privacy-and-gdpr', + label: 'Make.com GDPR | General Data Protection Regulation | Make', + asOf: '2026-07-02', + }, + { + url: 'https://community.make.com/t/information-security-compliance-soc2-iso27001-hipaa-etc/8052', + label: 'Information Security Compliance (SOC2, ISO27001, HIPAA, etc.) - Make Community', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -918,31 +929,6 @@ export const makeProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'SOC 2 Type II, SOC 3, and ISO 27001 certified, plus GDPR adherence; no HIPAA, PCI, or FedRAMP mentioned', - detail: - "Make's Security page states the company operates an ISO 27001-certified information security program and runs infrastructure compliant with SOC 3 and SOC 2 Type II audits, alongside GDPR adherence (Make also has a dedicated GDPR page). HIPAA compliance is not mentioned or offered.", - shortValue: 'No HIPAA, PCI, or FedRAMP', - confidence: 'verified', - sources: [ - { - url: 'https://www.make.com/en/security', - label: 'Automation Security & Compliance | Make', - asOf: '2026-07-02', - }, - { - url: 'https://www.make.com/en/privacy-and-gdpr', - label: 'Make.com GDPR | General Data Protection Regulation | Make', - asOf: '2026-07-02', - }, - { - url: 'https://community.make.com/t/information-security-compliance-soc2-iso27001-hipaa-etc/8052', - label: 'Information Security Compliance (SOC2, ISO27001, HIPAA, etc.) - Make Community', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Not publicly documented', detail: @@ -1040,6 +1026,15 @@ export const makeProfile: CompetitorProfile = { }, ], }, + scim: { + value: + "Not publicly documented: no Make documentation confirming SCIM 2.0 directory provisioning was found. Make's published single sign-on, pricing, Enterprise, and White Label login material describes SAML 2.0 and OIDC SSO, domain claim, two-factor enforcement, and custom organization/team roles, and lets an admin choose which teams new SSO users join, but does not mention SCIM. Whether Make offers SCIM provisioning under an Enterprise or White Label agreement could not be confirmed either way.", + detail: + 'Make does document SSO-driven provisioning - White Label end-users automatically receive their own organization on first sign-in, and admins pick which teams new SSO users join - but that is authentication-time provisioning, not identity-provider-driven create/update/deactivate.', + shortValue: 'Not publicly documented; could not confirm', + confidence: 'unknown', + sources: [], + }, sessionPolicy: { value: "Yes: organization administrators and owners can set a session timeout from the organization dashboard (three dots next to Organization settings > Set session timeout), choosing how long users can be inactive before they are automatically logged out, anywhere from 15 minutes to 7 days. This is an inactivity/idle timeout applied org-wide; Make's help center documents no separate absolute session-lifetime cap measured from sign-in.", diff --git a/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts b/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts index 716d2fe8b9e..e7cfad33621 100644 --- a/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts +++ b/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts @@ -904,12 +904,12 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - 'Yes: Copilot Studio (listed by its former name, "Copilot Studios") is one of the Microsoft online services explicitly in scope of the Office 365 SOC 2 Type 2 attestation report, with audit reports available from the Microsoft Service Trust Portal', + 'Yes: Copilot Studio (listed by its former name, "Copilot Studios") is one of the Microsoft online services explicitly in scope of the Office 365 SOC 2 Type 2 attestation report, and is separately certified under HIPAA (Business Associate Agreement), HITRUST CSF, FedRAMP, multiple ISO standards (9001, 20000-1, 22301, 27001, 27017, 27018, 27701), PCI DSS, CSA STAR, UK G-Cloud, Singapore MTCS Level 3, Korea K-ISMS, and Spain ENS, with an audit report for each available from the Microsoft Service Trust Portal', detail: - 'Copilot Studio\'s own admin-certification page confirms SOC compliance without naming the specific report type, but Microsoft\'s dedicated SOC 2 Type 2 compliance offering page lists "Copilot Studios" by name among the in-scope Office 365 services, resolving which SOC report type applies.', - shortValue: 'Yes, named in scope of the SOC 2 Type 2 attestation report', + 'Copilot Studio\'s own admin-certification page confirms SOC compliance without naming the specific report type, but Microsoft\'s dedicated SOC 2 Type 2 compliance offering page lists "Copilot Studios" by name among the in-scope Office 365 services, resolving which SOC report type applies. The wider certification list is the full set published on that admin-certification page, where each certification links to a corresponding audit report or certificate.', + shortValue: 'SOC 2 Type 2, HIPAA, FedRAMP, ISO, PCI DSS', confidence: 'verified', sources: [ { @@ -974,22 +974,6 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'HIPAA (Business Associate Agreement), HITRUST CSF, FedRAMP, multiple ISO standards (9001, 20000-1, 22301, 27001, 27017, 27018, 27701), PCI DSS, CSA STAR, UK G-Cloud, Singapore MTCS Level 3, Korea K-ISMS, and Spain ENS, each with an audit report on the Microsoft Service Trust Portal', - detail: - "This is the full list from Copilot Studio's admin-certification documentation. Each certification links to a corresponding audit report or certificate.", - shortValue: 'HIPAA, HITRUST, FedRAMP, multiple ISO standards, PCI DSS, CSA STAR, and more', - confidence: 'verified', - sources: [ - { - url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/admin-certification', - label: - 'Review ISO, SOC, and HIPAA compliance - Microsoft Copilot Studio | Microsoft Learn', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Yes: admins can enable or restrict which non-default LLMs (e.g. Anthropic Claude) are available tenant-wide, and Data Loss Prevention policies classify connectors, and therefore the tools built from them, into Business/Non-Business/Blocked groups at the tenant or environment level', @@ -1083,17 +1067,38 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, sso: { value: - 'Yes: Copilot Studio and the wider Power Platform are built on Microsoft Entra ID, which natively supports SAML/OIDC single sign-on plus automatic user/app provisioning (SAML just-in-time and SCIM-based), so signing in via Entra ID grants org-level access without manual per-user account setup', + 'Yes: Copilot Studio and the wider Power Platform are built on Microsoft Entra ID, whose federation-based single sign-on covers SAML 2.0 and OpenID Connect, so a member signs in once with their work credentials and Entra ID confirms their identity to the service instead of the product keeping its own username/password database', detail: - "SSO and provisioning are inherited from the Microsoft 365/Entra ID tenant rather than a Copilot Studio-specific setting, consistent with the rest of Microsoft's enterprise stack.", - shortValue: 'Yes, SSO via Entra ID (SAML/OIDC) with automatic provisioning', + "SSO is inherited from the Microsoft 365/Entra ID tenant rather than being a Copilot Studio-specific setting, consistent with the rest of Microsoft's enterprise stack. Entra ID additionally offers password-based and linked SSO for applications that cannot federate.", + shortValue: 'Yes, SSO via Entra ID (SAML 2.0 and OIDC)', + confidence: 'verified', + sources: [ + { + url: 'https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/what-is-single-sign-on', + label: 'What is single sign-on in Microsoft Entra ID? | Microsoft Learn', + asOf: '2026-09-15', + }, + ], + }, + scim: { + value: + 'Yes, but at the Microsoft Entra ID identity-platform layer rather than inside Copilot Studio itself: Copilot Studio members are users of the Microsoft 365/Entra ID tenant, and Entra ID is what performs SCIM 2.0 provisioning. Outbound, the Entra provisioning service automatically creates accounts for new joiners, keeps identity data in sync as status or roles change, provisions groups to applications that support them, and deactivates accounts when people leave, either through a preintegrated gallery connector (gallery apps generally use SCIM 2.0-based user-management APIs) or generically against any application implementing the SCIM 2.0 standard. Inbound, an API-driven provisioning app accepts bulk payloads packaged with SCIM schema constructs on a Microsoft Graph /bulkUpload endpoint, with the provisioning service, not the client, deciding whether each record is a create, update, enable, or disable. That inbound path requires a Microsoft Entra ID P1, P2, or Microsoft Entra ID Governance license and is throttled to 40 API calls in any 5-second window, with a tenant limit of 2,000 calls per 24 hours on P1/P2 and 6,000 on Entra ID Governance.', + detail: + 'Microsoft documents this as a tenant-level Entra ID capability rather than a Copilot Studio product setting, so joiner/mover/leaver handling for Copilot Studio makers and users is whatever the tenant already configures in Entra ID (optionally driven by Lifecycle Workflows). Microsoft requires an application to expose a SCIM-compliant endpoint before it will onboard it to the gallery for automated provisioning.', + shortValue: 'Yes, via Microsoft Entra ID SCIM 2.0 provisioning', confidence: 'verified', sources: [ { url: 'https://learn.microsoft.com/en-us/entra/identity/app-provisioning/user-provisioning', label: 'What is automated app user provisioning in Microsoft Entra ID | Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://learn.microsoft.com/en-us/entra/identity/app-provisioning/inbound-provisioning-api-concepts', + label: + 'API-driven inbound provisioning concepts - Microsoft Entra ID | Microsoft Learn', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/n8n.ts b/apps/sim/lib/compare/data/competitors/n8n.ts index 441e002b667..853556e1e1b 100644 --- a/apps/sim/lib/compare/data/competitors/n8n.ts +++ b/apps/sim/lib/compare/data/competitors/n8n.ts @@ -864,12 +864,12 @@ export const n8nProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - "SOC 2: program 'aligned to' SOC 2 with annual third-party audits; report available to enterprise customers via Trust Center", + "SOC 2 Type II certification, viewable via the Trust Center, with a security program described as 'aligned to' the SOC 2 framework under continuous evaluation and annual independent third-party audits; the SOC 2 report is provided to enterprise customers on request rather than published openly. A SOC 3 report is publicly downloadable from the Security page, and GDPR compliance is claimed as a data processor. No HIPAA, ISO 27001, PCI, or FedRAMP certification found.", detail: - 'n8n operates a Trust Center (trust.n8n.io, powered by SafeBase) covering security, compliance, privacy, and reliability. Its security program is aligned to the SOC 2 framework, with continuous evaluation and annual independent audits, and the SOC 2 report is provided to enterprise customers on request rather than published openly.', - shortValue: 'Aligned to SOC 2, report on request', + 'n8n operates a Trust Center (trust.n8n.io, powered by SafeBase) covering security, compliance, privacy, and reliability. Its security program is aligned to the SOC 2 framework, with continuous evaluation and annual independent audits, and the SOC 2 report is provided to enterprise customers on request rather than published openly; n8n now holds SOC 2 Type II certification, viewable via the Trust Center, in addition to the public SOC 3 report. The Trust Center and the legal/security page also list GDPR compliance (as a data processor with a standard DPA) and CAIQ self-assessment questionnaires for both cloud and self-hosted deployments. n8n holds no ISO 27001, HIPAA BAA, PCI-DSS, or FedRAMP certification. Third-party blog posts describe self-hosted n8n as helping organizations map to HIPAA/ISO 27001 requirements, but that is not the same as holding those certifications.', + shortValue: 'SOC 2 Type II, public SOC 3, GDPR', confidence: 'verified', sources: [ { url: 'https://trust.n8n.io/', label: 'n8n Trust Center', asOf: '2026-07-02' }, @@ -929,27 +929,6 @@ export const n8nProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'GDPR (as data processor), SOC 2 Type II certification, and a publicly downloadable SOC 3 report; no HIPAA, ISO 27001, PCI, or FedRAMP certification found', - detail: - "n8n's Trust Center (SafeBase-hosted) and legal/security page list GDPR compliance (as a data processor with a standard DPA), CAIQ self-assessment questionnaires for both cloud and self-hosted deployments, and a SOC 3 report that is publicly downloadable from the Security page. n8n now holds SOC 2 Type II certification, viewable via the Trust Center, in addition to the public SOC 3 report. n8n holds no ISO 27001, HIPAA BAA, PCI-DSS, or FedRAMP certification. Third-party blog posts describe self-hosted n8n as helping organizations map to HIPAA/ISO 27001 requirements, but that is not the same as holding those certifications.", - shortValue: 'GDPR, SOC 2 Type II certified, public SOC 3 report', - confidence: 'verified', - sources: [ - { - url: 'https://trust.n8n.io/', - label: 'n8n Trust Center | Powered by SafeBase', - asOf: '2026-07-08', - }, - { url: 'https://n8n.io/legal/security/', label: 'Security | n8n', asOf: '2026-07-08' }, - { - url: 'https://support.n8n.io/article/request-for-soc-2-report', - label: 'Request for SOC-2 report | n8n Help Center', - asOf: '2026-07-08', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', detail: 'Not publicly documented by n8n.', @@ -1062,6 +1041,15 @@ export const n8nProfile: CompetitorProfile = { }, ], }, + scim: { + value: + "Not publicly documented: no n8n documentation confirming SCIM 2.0 directory provisioning was found. n8n's SSO documentation covers SAML and OIDC authentication, and its user-management documentation covers email invites and LDAP, with neither mentioning SCIM. A community feature request asking for SCIM support remains open with no official n8n response, so SCIM availability could not be confirmed either way.", + detail: + 'n8n does document automated user provisioning through SSO, where a user instance role and project access are assigned from identity-provider attributes on first login, but that is authentication-time provisioning rather than identity-provider-driven create/update/deactivate.', + shortValue: 'Not publicly documented; SCIM support unconfirmed', + confidence: 'unknown', + sources: [], + }, sessionPolicy: { value: 'Partial: self-hosted only and env-var driven. N8N_USER_MANAGEMENT_JWT_DURATION_HOURS sets how long a signed-in session JWT lasts (default 168 hours, one week) and N8N_USER_MANAGEMENT_JWT_REFRESH_TIMEOUT_HOURS controls sliding refresh, where 0 means refresh at 25% of the duration and -1 disables refresh so the duration becomes a hard re-login deadline.', diff --git a/apps/sim/lib/compare/data/competitors/openai-agentkit.ts b/apps/sim/lib/compare/data/competitors/openai-agentkit.ts index 35519f829ca..66cf5529b3f 100644 --- a/apps/sim/lib/compare/data/competitors/openai-agentkit.ts +++ b/apps/sim/lib/compare/data/competitors/openai-agentkit.ts @@ -863,11 +863,12 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type 2, plus ISO 27001, 27017, 27018, and 27701 certifications', + compliance: { + value: + 'Yes: SOC 2 Type 2, FedRAMP Moderate Authorization (ChatGPT Enterprise and API Platform), PCI DSS v4.0.1, ISO/IEC 27001:2022, ISO 27017, ISO 27018, and ISO/IEC 27701:2019; supports customer HIPAA compliance via BAA and GDPR/CCPA via DPA; FERPA covered via a separate Student Data Privacy Agreement for ChatGPT Edu', detail: - "OpenAI's most recent SOC 2 report covers January 1, 2025 through June 30, 2025 for Security, Availability, Confidentiality, and Privacy Trust Services Criteria across the API Platform, ChatGPT Enterprise, ChatGPT Edu, and ChatGPT Team.", - shortValue: 'SOC 2 Type 2 plus ISO 27001/27017/27018/27701', + "OpenAI's most recent SOC 2 report covers January 1, 2025 through June 30, 2025 for Security, Availability, Confidentiality, and Privacy Trust Services Criteria across the API Platform, ChatGPT Enterprise, ChatGPT Edu, and ChatGPT Team. ChatGPT Enterprise and the API Platform hold FedRAMP Moderate (Class C) authorization per the FedRAMP Marketplace listing. OpenAI's trust portal lists PCI DSS v4.0.1 for payment-processing components, plus ISO/IEC 27001:2022, 27017:2015, 27018:2019, and 27701:2019 certifications, and lists GDPR and CCPA. OpenAI offers a Data Processing Addendum for GDPR/CCPA and a Business Associate Agreement for HIPAA-regulated customers on ChatGPT Enterprise/Edu and the API (not standard ChatGPT Business); this is enablement rather than OpenAI itself being HIPAA-certified, since HIPAA has no formal certification body. FERPA compliance for ChatGPT Edu/for Teachers runs through a separate Student Data Privacy Agreement rather than the general DPA.", + shortValue: 'SOC 2 Type 2, FedRAMP Moderate, ISO 27001, HIPAA BAA', confidence: 'estimated', sources: [ { @@ -880,6 +881,17 @@ export const openaiAgentkitProfile: CompetitorProfile = { label: 'Security and privacy at OpenAI', asOf: '2026-07-02', }, + { + url: 'https://www.fedramp.gov/marketplace/products/FR2533155773/', + label: 'ChatGPT Enterprise and API Platform | FedRAMP Marketplace', + asOf: '2026-07-08', + }, + { + url: 'https://help.openai.com/en/articles/8660679-how-can-i-get-a-business-associate-agreement-baa-with-openai', + label: + 'How can I get a Business Associate Agreement (BAA) with OpenAI? | OpenAI Help Center', + asOf: '2026-07-08', + }, ], }, dataResidency: { @@ -937,28 +949,6 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'FedRAMP Moderate Authorization (ChatGPT Enterprise and API Platform), PCI DSS v4.0.1, SOC 2 Type 2, ISO/IEC 27001:2022, ISO/IEC 27701:2019; supports customer HIPAA compliance via BAA and GDPR/CCPA via DPA; FERPA covered via a separate Student Data Privacy Agreement for ChatGPT Edu', - detail: - "OpenAI's ChatGPT Enterprise and API Platform hold FedRAMP Moderate (Class C) authorization per the FedRAMP Marketplace listing. OpenAI's trust portal lists PCI DSS v4.0.1 for payment-processing components, a SOC 2 Type 2 examination (Security, Availability, Confidentiality, Privacy criteria) covering the API Platform, ChatGPT Enterprise, ChatGPT Edu, and ChatGPT Team, plus ISO/IEC 27001:2022, 27017:2015, 27018:2019, and 27701:2019 certifications, and lists GDPR and CCPA. OpenAI offers a Data Processing Addendum for GDPR/CCPA and a Business Associate Agreement for HIPAA-regulated customers on ChatGPT Enterprise/Edu and the API (not standard ChatGPT Business); this is enablement rather than OpenAI itself being HIPAA-certified, since HIPAA has no formal certification body. FERPA compliance for ChatGPT Edu/for Teachers runs through a separate Student Data Privacy Agreement rather than the general DPA.", - shortValue: 'FedRAMP Moderate, PCI DSS, SOC 2, ISO 27001/27701, HIPAA BAA', - confidence: 'verified', - sources: [ - { - url: 'https://www.fedramp.gov/marketplace/products/FR2533155773/', - label: 'ChatGPT Enterprise and API Platform | FedRAMP Marketplace', - asOf: '2026-07-08', - }, - { url: 'https://trust.openai.com/', label: 'OpenAI Trust Portal', asOf: '2026-07-08' }, - { - url: 'https://help.openai.com/en/articles/8660679-how-can-i-get-a-business-associate-agreement-baa-with-openai', - label: - 'How can I get a Business Associate Agreement (BAA) with OpenAI? | OpenAI Help Center', - asOf: '2026-07-08', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', detail: 'Not publicly documented in available vendor sources.', @@ -1046,9 +1036,9 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, sso: { value: - 'Yes: OpenAI supports SAML-based SSO for ChatGPT Enterprise/Edu/Business and the API Platform, with organization auto-provisioning available either via Automatic Account Creation (email-domain matched invitations) or SCIM-based Directory Sync that invites users based on Identity Provider group membership.', + 'Yes: OpenAI supports SAML-based single sign-on for ChatGPT Enterprise, Edu, and Business workspaces and for the API Platform, so members authenticate against the customer identity provider rather than an OpenAI-held password.', detail: 'Requires prior verification of at least one domain to enable SSO.', - shortValue: 'Yes, SAML SSO with SCIM auto-provisioning', + shortValue: 'Yes, SAML SSO after domain verification', confidence: 'verified', sources: [ { @@ -1056,6 +1046,26 @@ export const openaiAgentkitProfile: CompetitorProfile = { label: 'Configuring SSO | OpenAI Help Center', asOf: '2026-07-02', }, + ], + }, + scim: { + value: + 'Yes, at the OpenAI workspace identity layer rather than as an AgentKit or Agent Builder feature: SCIM directory sync provisions workspace membership and group assignments from the customer identity provider, and synchronized identity groups keep access current as employees join the organization, change roles, or leave, with the identity provider acting as the membership source so later provisioning updates can overwrite membership changed on the workspace side. It is gated to eligible ChatGPT Enterprise and Edu workspaces; SCIM and synchronized identity groups are not included with ChatGPT Business. Workspaces that do not use SCIM can instead auto-provision via Automatic Account Creation (email-domain matched invitations), and SCIM-based Directory Sync invites users based on Identity Provider group membership. Provisioning is configured once for the OpenAI workspace and inherited by every agent built inside it; OpenAI does not state on these pages whether an API-Platform-only organization can use the same directory sync, and publishes no AgentKit-specific provisioning control.', + detail: + "OpenAI frames SCIM as the provisioning half of workspace identity management, alongside SSO, domain verification, user lifecycle management, and identity-group synchronization: SSO governs how people authenticate, SCIM governs who exists in the workspace and with which group assignments. OpenAI's public learning docs defer to the Help Center for current SCIM behavior, supported attributes, and setup steps.", + shortValue: 'Yes, SCIM directory sync on Enterprise/Edu workspaces', + confidence: 'verified', + sources: [ + { + url: 'https://learn.chatgpt.com/docs/enterprise/groups-and-provisioning', + label: 'Groups and provisioning | ChatGPT Learn', + asOf: '2026-09-15', + }, + { + url: 'https://learn.chatgpt.com/docs/enterprise/work-admin-faq', + label: 'ChatGPT Work admin FAQ | ChatGPT Learn', + asOf: '2026-09-15', + }, { url: 'https://help.openai.com/en/articles/9672121-getting-started-with-identity-and-provisioning-in-chatgpt-enterprise-edu-and-chatgpt-for-teachers', label: 'Getting started with identity and provisioning | OpenAI Help Center', diff --git a/apps/sim/lib/compare/data/competitors/openclaw.ts b/apps/sim/lib/compare/data/competitors/openclaw.ts index ad3b531b36b..81a0b7d25ac 100644 --- a/apps/sim/lib/compare/data/competitors/openclaw.ts +++ b/apps/sim/lib/compare/data/competitors/openclaw.ts @@ -814,12 +814,12 @@ export const openClawProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - 'No: OpenClaw is a self-hosted open-source project run by a non-profit Foundation, not a vendor selling a hosted service, and publishes no SOC 2 report.', + 'No: OpenClaw is a self-hosted open-source project run by a non-profit Foundation, not a vendor selling a hosted service, and publishes no SOC 2 report and no other compliance certifications (no HIPAA, ISO 27001, GDPR-specific attestation, PCI, or FedRAMP). As open-source, self-hosted software from a non-profit Foundation, OpenClaw is not the kind of vendor entity that typically pursues these certifications; compliance posture depends entirely on how and where the operator self-hosts it.', detail: - 'No SOC 2 attestation, trust center, or audit report exists for OpenClaw. Responsibility for infrastructure security rests entirely with whoever self-hosts the Gateway.', - shortValue: 'No SOC 2 report published', + "No SOC 2 attestation, trust center, or audit report exists for OpenClaw, and responsibility for infrastructure security rests entirely with whoever self-hosts the Gateway. China restricted state enterprises and government agencies from deploying OpenClaw in March 2026 over security concerns, per Wikipedia's history summary, a data point on the compliance/trust landscape rather than a certification.", + shortValue: 'None: no SOC 2 or other certifications published', confidence: 'estimated', sources: [ { @@ -827,6 +827,11 @@ export const openClawProfile: CompetitorProfile = { label: 'OpenClaw Docs: Security', asOf: '2026-07-02', }, + { + url: 'https://en.wikipedia.org/wiki/OpenClaw', + label: 'Wikipedia: OpenClaw', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -879,21 +884,6 @@ export const openClawProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'No compliance certifications (no HIPAA, ISO 27001, GDPR-specific attestation, PCI, or FedRAMP). As open-source, self-hosted software from a non-profit Foundation, OpenClaw is not the kind of vendor entity that typically pursues these certifications; compliance posture depends entirely on how and where the operator self-hosts it.', - detail: - "China restricted state enterprises and government agencies from deploying OpenClaw in March 2026 over security concerns, per Wikipedia's history summary, a data point on the compliance/trust landscape rather than a certification.", - shortValue: 'None documented; compliance posture depends on self-hosting operator', - confidence: 'estimated', - sources: [ - { - url: 'https://en.wikipedia.org/wiki/OpenClaw', - label: 'Wikipedia: OpenClaw', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: "Yes, at the single-operator level: OpenClaw supports per-agent tool allow/deny lists and sandbox-level workspace/tool restrictions (agents.defaults.sandbox, tools.allow/tools.deny), configured by one trusted operator, not enforced org-wide. The docs frame this as a layered 'identity → scope → model' design principle rather than a formally named three-gate system.", @@ -968,7 +958,7 @@ export const openClawProfile: CompetitorProfile = { value: 'No: OpenClaw has no SAML/OIDC single sign-on feature. Its access model authenticates individual senders on connected messaging channels (DM pairing, allowlists), a single-operator personal tool, not an organization with a directory of employees signing in via an identity provider.', detail: - 'SSO and organization provisioning are out of scope for the "single-user, personal-assistant model" OpenClaw\'s security documentation describes.', + 'SSO is out of scope for the "single-user, personal-assistant model" OpenClaw\'s security documentation describes.', shortValue: 'No: single-operator model has no SSO/IdP concept', confidence: 'verified', sources: [ @@ -979,6 +969,26 @@ export const openClawProfile: CompetitorProfile = { }, ], }, + scim: { + value: + "No: OpenClaw's Gateway documentation describes no SCIM 2.0 directory provisioning, and the product has no organization directory to provision members into. The Gateway's security model is one trust boundary per gateway (a single operator, or a team whose members trust each other), access is granted per messaging-channel sender through DM pairing or allowlists, and callers authenticate to the Gateway itself with a static shared secret (token or password) or a trusted-proxy header rather than as directory-managed user accounts. An organization needing per-employee provisioning would run separate Gateway instances per trust boundary, which is what the docs recommend, rather than creating, updating, or deactivating users from an identity provider.", + detail: + 'Because there are no member accounts, there is nothing for joiner/mover/leaver automation to target: revoking access means removing a sender from an allowlist or rotating the shared secret. No SCIM endpoint, identity-provider integration, or group/role mapping appears in the Gateway security or authentication documentation.', + shortValue: 'No: no directory of users to provision', + confidence: 'estimated', + sources: [ + { + url: 'https://docs.openclaw.ai/gateway/security', + label: 'OpenClaw Docs: Security', + asOf: '2026-09-15', + }, + { + url: 'https://docs.openclaw.ai/gateway/authentication', + label: 'OpenClaw Docs: Authentication', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: 'Not applicable: there is no signed-in session to bound. The Gateway authenticates callers with a static shared secret (`gateway.auth` token or password, or a trusted-proxy header mode), and the security docs document no session expiry, idle timeout, or time-bound signed session; every authenticated caller holds operator-level access until the secret is rotated.', diff --git a/apps/sim/lib/compare/data/competitors/pipedream.ts b/apps/sim/lib/compare/data/competitors/pipedream.ts index ebfce7c7a49..0a46e73e9f7 100644 --- a/apps/sim/lib/compare/data/competitors/pipedream.ts +++ b/apps/sim/lib/compare/data/competitors/pipedream.ts @@ -739,12 +739,13 @@ export const pipedreamProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type II', + compliance: { + value: + 'Yes: SOC 2 Type 2, with the report provided on request, plus HIPAA support (Pipedream acts as a Business Associate and signs BAAs, Enterprise) and GDPR handled through Standard Contractual Clauses. Sensitive data is encrypted at rest via AWS KMS, whose ISO 27001/27017/27018 coverage is inherited from the AWS infrastructure layer. No independent Pipedream-held ISO 27001, PCI, or FedRAMP certification appears on its trust page.', detail: - 'Pipedream provides a SOC 2 Type 2 report on request, undergoes annual third-party audits, and uses continuous-compliance monitoring tooling. It also supports HIPAA, acting as a Business Associate and offering BAAs.', - shortValue: 'SOC 2 Type II, HIPAA BAA available', - confidence: 'verified', + "Pipedream's Privacy and Security page states it provides a SOC 2 Type 2 report on request, undergoes annual third-party audits, and uses continuous-compliance monitoring tooling. It acts as a Business Associate and signs Business Associate Addendums (BAAs) for HIPAA/PHI use cases (Enterprise), and uses Standard Contractual Clauses (SCCs) for GDPR-related data transfers. Sensitive data (OAuth grants, key-based credentials, env vars) is encrypted at rest with AES-256-GCM via AWS KMS, which itself holds SOC 1/2/3 and ISO 27001/27017/27018 certifications. That ISO/PCI/FedRAMP coverage is inherited from the AWS infrastructure layer, not a certification Pipedream independently holds on its own trust page. Some third-party review sites describe Pipedream itself as directly PCI, FedRAMP, and CSA STAR compliant, but Pipedream's own security documentation does not corroborate this.", + shortValue: 'SOC 2, HIPAA BAA, GDPR SCCs; ISO via AWS', + confidence: 'estimated', sources: [ { url: 'https://pipedream.com/docs/privacy-and-security', @@ -756,6 +757,11 @@ export const pipedreamProfile: CompetitorProfile = { label: 'Pipedream Docs: HIPAA Compliance', asOf: '2026-07-02', }, + { + url: 'https://pipedream.com/blog/hippa/', + label: 'Pipedream Blog – Pipedream supports HIPAA compliance', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -801,26 +807,6 @@ export const pipedreamProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'SOC 2 Type 2, HIPAA (via BAA, Enterprise), GDPR (SCCs), and AWS KMS infra with ISO 27001/27017/27018. No independent Pipedream-held ISO 27001/PCI/FedRAMP certification on the trust page', - detail: - "Pipedream's Privacy and Security page states it provides a SOC 2 Type 2 report on request, signs Business Associate Addendums (BAAs) for HIPAA/PHI use cases (Enterprise), and uses Standard Contractual Clauses (SCCs) for GDPR-related data transfers. Sensitive data (OAuth grants, key-based credentials, env vars) is encrypted at rest with AES-256-GCM via AWS KMS, which itself holds SOC 1/2/3 and ISO 27001/27017/27018 certifications. That ISO/PCI/FedRAMP coverage is inherited from the AWS infrastructure layer, not a certification Pipedream independently holds on its own trust page. Some third-party review sites describe Pipedream itself as directly PCI, FedRAMP, and CSA STAR compliant, but Pipedream's own security documentation does not corroborate this.", - shortValue: 'SOC 2, HIPAA BAA, GDPR SCCs; ISO via AWS only', - confidence: 'estimated', - sources: [ - { - url: 'https://pipedream.com/docs/privacy-and-security', - label: 'Pipedream Docs – Privacy and Security', - asOf: '2026-07-02', - }, - { - url: 'https://pipedream.com/blog/hippa/', - label: 'Pipedream Blog – Pipedream supports HIPAA compliance', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', detail: 'Not publicly documented for Pipedream.', @@ -905,6 +891,21 @@ export const pipedreamProfile: CompetitorProfile = { }, ], }, + scim: { + value: + 'Yes: Pipedream supports provisioning user accounts from an identity provider via SCIM, available to any workspace on the Business plan and configured alongside Single Sign-On. The documentation confirms SCIM user-account provisioning and the Business-plan requirement, but does not enumerate which operations are covered (create, update, deactivate), which identity providers work with SCIM specifically, whether group or role mapping is supported, or any documented limits.', + detail: + 'SCIM is documented as part of workspace SSO configuration; Pipedream lists Google, Okta, and any SAML-compliant provider as supported SSO identity providers, and the SCIM implementation details are not published.', + shortValue: 'Yes: SCIM user provisioning on Business plan', + confidence: 'verified', + sources: [ + { + url: 'https://pipedream.com/docs/workspaces', + label: 'Managing workspaces - Pipedream Docs', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: "Not publicly documented: Pipedream's workspace administration and SSO documentation enumerates the security controls available to admins — requiring two-factor authentication for all members, configuring SAML/Google/Okta SSO, SCIM provisioning, and managing verified domains, all on the Business plan — and includes no absolute session lifetime, idle timeout, or forced re-authentication interval. Pipedream also does not publish a fixed session length for the dashboard, so the absence of an admin control is inferred from the documentation rather than stated by Pipedream.", diff --git a/apps/sim/lib/compare/data/competitors/power-automate.ts b/apps/sim/lib/compare/data/competitors/power-automate.ts index dc080a88d1d..6b226f779e9 100644 --- a/apps/sim/lib/compare/data/competitors/power-automate.ts +++ b/apps/sim/lib/compare/data/competitors/power-automate.ts @@ -904,13 +904,13 @@ export const powerAutomateProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - "Power Automate is SOC 2 Type 2 in-scope for Commercial and GCC environments only. It is not in-scope for GCC High or DoD in that attestation, separate from the product's general availability in those government clouds.", + "Power Automate is SOC 2 Type 2 in-scope for Commercial and GCC environments only. It is not in-scope for GCC High or DoD in that attestation, separate from the product's general availability in those government clouds. The SOC 2 Type 2 report also incorporates the Cloud Security Alliance CCM and German BSI C5:2020 criteria. Beyond SOC 2 there is HIPAA/HITECH (Microsoft will sign a BAA as a business associate) and inclusion in the broader Office 365/Azure compliance program, which separately covers ISO 27001, FedRAMP, and other certifications at the Azure/Office 365 platform level.", detail: - "Microsoft's compliance documentation lists Power Automate among in-scope Commercial/GCC services.", - shortValue: 'SOC 2 Type 2 in-scope for Commercial and GCC only', - confidence: 'verified', + "Microsoft's compliance documentation lists Power Automate among in-scope Commercial/GCC services. HIPAA/BAA support and CSA CCM/BSI C5:2020 coverage are documented directly in Microsoft's SOC 2 documentation. No Power Automate-specific ISO 27001/FedRAMP attestation page exists, so treat those two as platform-level coverage rather than product-specific certification.", + shortValue: 'SOC 2 (Commercial/GCC), HIPAA BAA, CSA CCM, BSI C5', + confidence: 'estimated', sources: [ { url: 'https://learn.microsoft.com/en-us/compliance/regulatory/offering-soc-2', @@ -918,6 +918,11 @@ export const powerAutomateProfile: CompetitorProfile = { 'System and Organization Controls (SOC) 2 Type 2 - Microsoft Compliance | Microsoft Learn', asOf: '2026-07-02', }, + { + url: 'https://www.keragon.com/hipaa/hipaa-compliant-checker/microsoft-powerautomate', + label: 'Is Microsoft Power Automate HIPAA Compliant? - Keragon', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -964,26 +969,6 @@ export const powerAutomateProfile: CompetitorProfile = { confidence: 'unknown', sources: [], }, - additionalCompliance: { - value: - 'HIPAA/HITECH (Microsoft will sign a BAA as a business associate) and inclusion in the broader Office 365/Azure compliance program, which separately covers ISO 27001, FedRAMP, and other certifications at the Azure/Office 365 platform level. The SOC 2 Type 2 report also incorporates the Cloud Security Alliance CCM and German BSI C5:2020 criteria.', - detail: - "HIPAA/BAA support and CSA CCM/BSI C5:2020 coverage are documented directly in Microsoft's SOC 2 documentation. No Power Automate-specific ISO 27001/FedRAMP attestation page exists, so treat those two as platform-level coverage rather than product-specific certification.", - shortValue: 'HIPAA/BAA, CSA CCM, BSI C5:2020; ISO/FedRAMP at platform level', - confidence: 'estimated', - sources: [ - { - url: 'https://learn.microsoft.com/en-us/compliance/regulatory/offering-soc-2', - label: 'SOC 2 Type 2 - Microsoft Compliance | Microsoft Learn', - asOf: '2026-07-02', - }, - { - url: 'https://www.keragon.com/hipaa/hipaa-compliant-checker/microsoft-powerautomate', - label: 'Is Microsoft Power Automate HIPAA Compliant? - Keragon', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Not publicly documented', detail: @@ -1078,10 +1063,10 @@ export const powerAutomateProfile: CompetitorProfile = { }, sso: { value: - 'Yes: Power Platform is built on Microsoft Entra ID (Azure AD), which natively supports SAML/OIDC single sign-on plus automatic user/app provisioning (SAML Just-in-Time and SCIM-based). Organizations signing in via Entra ID SSO get org-level access without manual per-user account setup. Power Pages/portals additionally document explicit SAML 2.0 setup with Entra ID as an identity provider.', + 'Yes: Power Platform is built on Microsoft Entra ID (Azure AD), which natively supports SAML/OIDC single sign-on. Organizations signing in via Entra ID SSO get org-level access without manual per-user account setup. Power Pages/portals additionally document explicit SAML 2.0 setup with Entra ID as an identity provider.', detail: - "SSO/provisioning is inherited from the Microsoft 365/Entra ID tenant rather than a Power Automate-specific setting, standard for Microsoft's enterprise stack.", - shortValue: 'SSO via Entra ID (SAML/OIDC), JIT/SCIM auto-provisioning', + "SSO is inherited from the Microsoft 365/Entra ID tenant rather than a Power Automate-specific setting, standard for Microsoft's enterprise stack.", + shortValue: 'SSO via Entra ID (SAML/OIDC), tenant-inherited', confidence: 'verified', sources: [ { @@ -1090,6 +1075,27 @@ export const powerAutomateProfile: CompetitorProfile = { 'Set up a SAML 2.0 provider with Microsoft Entra ID - Power Pages | Microsoft Learn', asOf: '2026-07-02', }, + ], + }, + scim: { + value: + "Yes, but at the Microsoft Entra ID tenant level rather than in Power Automate itself: Microsoft documents no Power Automate-specific SCIM endpoint, and Power Platform user creation and lifecycle run through the Microsoft 365 admin center and Microsoft Entra ID. Microsoft Entra ID can be enabled as a SCIM 2.0 service provider so external SCIM-compatible clients (HR apps, identity platforms, orchestration tools, or custom automation frameworks) create, read, update, and enable or disable users, and create groups and manage group membership, in the tenant, scoped by Microsoft Graph application permissions such as User.Create, User.ReadUpdate.All, User.EnableDisableAccount.All, Group.Create, and GroupMember.ReadWrite.All. That SCIM Provisioning API requires an Entra ID P1 license (or any license containing it) and is a paid add-on billed monthly per API call through a linked Azure subscription; SCIM bulk operations are not supported, filters return at most 200 results, page size is capped at 1,000, and because the API is app-only, properties requiring delegated authorization cannot be updated. Access to Power Automate then follows from that Entra identity: a background process syncs Microsoft Entra users into an environment's Dataverse SystemUser table when they are enabled in Entra ID, hold a valid license, and belong to the security group associated with the environment, and a user who becomes disabled or unlicensed in Entra ID has the Dataverse record set to disabled rather than deleted. In the outbound direction, Entra ID's own automatic app provisioning into third-party SaaS apps is itself SCIM 2.0-based, distinct from SAML just-in-time provisioning.", + detail: + "The Entra SCIM Provisioning API is separate from Entra ID's built-in app provisioning, HR-driven provisioning, and API-driven provisioning, which do not require enabling it. Turning it on needs an Application Administrator or Cloud Application Administrator to register the calling app and a Billing Administrator to enable billing and link the Azure subscription.", + shortValue: 'Yes: SCIM at the Entra ID tenant level', + confidence: 'verified', + sources: [ + { + url: 'https://learn.microsoft.com/en-us/entra/identity/app-provisioning/enable-scim-api', + label: + 'Enable the SCIM Provisioning API in Microsoft Entra ID - Microsoft Entra ID | Microsoft Learn', + asOf: '2026-09-15', + }, + { + url: 'https://learn.microsoft.com/en-us/power-platform/admin/create-users', + label: 'Create users - Power Platform | Microsoft Learn', + asOf: '2026-09-15', + }, { url: 'https://learn.microsoft.com/en-us/entra/identity/app-provisioning/user-provisioning', label: diff --git a/apps/sim/lib/compare/data/competitors/retool.ts b/apps/sim/lib/compare/data/competitors/retool.ts index 5f4fb90bfb3..4af6688d829 100644 --- a/apps/sim/lib/compare/data/competitors/retool.ts +++ b/apps/sim/lib/compare/data/competitors/retool.ts @@ -787,12 +787,13 @@ export const retoolProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type 2, plus ISO/IEC 27001:2022, GDPR, and CCPA.', + compliance: { + value: + 'Yes: SOC 2 Type 2, plus ISO/IEC 27001:2022, GDPR, and CCPA certifications, and HIPAA via a signed BAA on Enterprise (self-hosted) plans. Reports and certificates are downloadable via the self-serve Trust Center (SafeBase-powered). PCI and FedRAMP are not confirmed.', detail: - 'Reports/certificates are downloadable via the self-serve Trust Center (SafeBase-powered).', - shortValue: 'SOC 2 Type 2, ISO 27001, GDPR, CCPA', - confidence: 'verified', + 'The Trust Center (SafeBase-powered) lists SOC 2 Type 2, ISO/IEC 27001:2022, GDPR, and CCPA certifications, and reports/certificates are downloadable from it self-serve. HIPAA compliance is available with a signed BAA on Enterprise (self-hosted) plans. PCI and FedRAMP are not confirmed.', + shortValue: 'SOC 2, ISO 27001, GDPR, CCPA; HIPAA via BAA', + confidence: 'estimated', sources: [ { url: 'https://trust.retool.com/', label: 'Retool Trust Center', asOf: '2026-07-02' }, { @@ -845,26 +846,6 @@ export const retoolProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'SOC 2 Type II, ISO/IEC 27001:2022, GDPR, and CCPA certifications, plus HIPAA via BAA on Enterprise.', - detail: - 'The Trust Center (SafeBase-powered) lists SOC 2 Type 2, ISO/IEC 27001:2022, GDPR, and CCPA certifications. HIPAA compliance is available with a signed BAA on Enterprise (self-hosted) plans. PCI and FedRAMP are not confirmed.', - shortValue: 'SOC 2, ISO 27001, GDPR, CCPA; HIPAA via BAA', - confidence: 'estimated', - sources: [ - { - url: 'https://trust.retool.com/', - label: 'Retool Trust Center (SafeBase)', - asOf: '2026-07-02', - }, - { - url: 'https://docs.retool.com/legal/security', - label: 'Security Practices (Retool Docs)', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', detail: 'Not publicly documented.', @@ -953,21 +934,34 @@ export const retoolProfile: CompetitorProfile = { }, sso: { value: - 'Yes: Retool supports SAML 2.0 SSO and Custom SSO (Okta, Azure AD/Entra ID, Google Workspace, OneLogin, and other SAML/OIDC providers) — but only on the Enterprise plan, not Business. SCIM-based auto-provisioning is available on Cloud or self-hosted 2.32.1+.', + 'Yes: Retool supports SAML 2.0 SSO and Custom SSO (Okta, Azure AD/Entra ID, Google Workspace, OneLogin, and other SAML/OIDC providers) — but only on the Enterprise plan, not Business.', detail: "Retool's current pricing page places SAML/Custom SSO exclusively on the Enterprise tier; the Business plan's feature list does not include SSO/SAML.", - shortValue: 'Yes, Enterprise-only SSO plus SCIM auto-provisioning', + shortValue: 'Yes, Enterprise-only SAML 2.0 and Custom SSO', + confidence: 'verified', + sources: [ + { + url: 'https://retool.com/pricing', + label: 'Retool Pricing', + asOf: '2026-07-08', + }, + ], + }, + scim: { + value: + 'Yes: Retool supports SCIM, described as the industry standard for automatically provisioning user accounts, covering Create Users, Update User Attributes, Deactivate Users, and Group Push with role mapping onto default Retool groups. The Retool pricing page lists "SAML/OpenID Connect SSO, SCIM provisioning" under the Enterprise plan for both Cloud and Self-hosted; self-hosted deployments require version 2.32.1 or later, and Group Push features require 2.94 or later. Default Retool groups cannot be renamed through SCIM group mapping, but custom identity-provider groups can be mapped onto the four default groups (admin, editor, viewer, All Users), and Retool warns to use caution when syncing groups because SCIM user provisioning can modify group memberships when requests are made. Microsoft Entra ID additionally requires adding aadOptscim062020 to the tenant URL for SCIM 2.0 compliance, and the authentication token must be at least 10 characters long.', + shortValue: 'Yes: SCIM provisioning on Enterprise, with group mapping', confidence: 'verified', sources: [ { url: 'https://docs.retool.com/sso/guides/scim-user-provisioning', - label: 'Provision users with SCIM', - asOf: '2026-07-02', + label: 'Provision users with SCIM | Retool Docs', + asOf: '2026-09-15', }, { url: 'https://retool.com/pricing', label: 'Retool Pricing', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/stackai.ts b/apps/sim/lib/compare/data/competitors/stackai.ts index 31f4adff439..96cdae56443 100644 --- a/apps/sim/lib/compare/data/competitors/stackai.ts +++ b/apps/sim/lib/compare/data/competitors/stackai.ts @@ -695,10 +695,13 @@ export const stackaiProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type II, audited by Modern Assurance', - shortValue: 'SOC 2 Type II certified', - confidence: 'verified', + compliance: { + value: + 'SOC 2 Type II (audited by Modern Assurance) and ISO 27001 certified, and audited against HIPAA in the same review cycle as its SOC 2 Type II audit, though the public Trust Center page itself lists only SOC 2 and ISO 27001, not HIPAA', + detail: + 'The Trust Center confirms SOC 2 Type II and ISO 27001, DPAs with OpenAI and Anthropic, and a May 2025 penetration test with a Low risk rating. A separate StackAI blog post states the company "was also audited against HIPAA standards during the same period as the SOC 2 Type II audit." GDPR compliance is referenced on the Enterprise pricing page but has no dedicated audit source.', + shortValue: 'SOC 2 Type II and ISO 27001; HIPAA audited', + confidence: 'estimated', sources: [ { url: 'https://trust.stackai.com/', label: 'StackAI Trust Center', asOf: '2026-07-02' }, { @@ -706,6 +709,7 @@ export const stackaiProfile: CompetitorProfile = { label: 'StackAI SOC 2 Type II & HIPAA blog', asOf: '2026-07-02', }, + { url: 'https://www.stackai.com/pricing', label: 'StackAI Pricing', asOf: '2026-07-02' }, ], }, dataResidency: { @@ -746,23 +750,6 @@ export const stackaiProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'ISO 27001 certified, and audited against HIPAA in the same review cycle as its SOC 2 Type II audit, though the public Trust Center page itself lists only SOC 2 and ISO 27001, not HIPAA', - detail: - 'The Trust Center confirms SOC 2 Type II and ISO 27001, DPAs with OpenAI and Anthropic, and a May 2025 penetration test with a Low risk rating. A separate StackAI blog post states the company "was also audited against HIPAA standards during the same period as the SOC 2 Type II audit." GDPR compliance is referenced on the Enterprise pricing page but has no dedicated audit source.', - shortValue: 'ISO 27001 certified; HIPAA audited, GDPR marketing-only', - confidence: 'estimated', - sources: [ - { url: 'https://trust.stackai.com/', label: 'StackAI Trust Center', asOf: '2026-07-02' }, - { - url: 'https://www.stackai.com/blog/soc2-type2-hipaa', - label: 'StackAI SOC 2 Type II & HIPAA blog', - asOf: '2026-07-02', - }, - { url: 'https://www.stackai.com/pricing', label: 'StackAI Pricing', asOf: '2026-07-02' }, - ], - }, modelAndToolGovernance: { value: 'Unknown', shortValue: 'Not documented', @@ -844,6 +831,13 @@ export const stackaiProfile: CompetitorProfile = { }, ], }, + scim: { + value: + "Not publicly documented: no StackAI page reviewed states that SCIM 2.0 directory provisioning is supported. StackAI's Authentication and MFA, RBAC and Groups, and AI Governance docs describe SAML-based SSO with identity providers such as Okta and Entra ID, inheritance of groups and permissions from the IdP, and a default role for newly provisioned SSO users, but none names SCIM or describes users or groups being created, updated, or deactivated from an IdP directory; the public security page likewise lists only Identity Provider connection for SAML login and role-mapping. This is an absence of published evidence, not a confirmed gap: SCIM may be offered to Enterprise customers without being documented publicly.", + shortValue: 'Not publicly documented; could not confirm', + confidence: 'unknown', + sources: [], + }, sessionPolicy: { value: "Not publicly documented: no admin-configurable session lifetime or idle timeout appears in StackAI's public documentation. Its Authentication and MFA page covers password login, org-wide MFA enforcement, and SSO, and the Feature Access page enumerating org-level admin settings (MFA, LLM access, app/tool availability, knowledge bases, advanced features) lists no session control.", diff --git a/apps/sim/lib/compare/data/competitors/tines.ts b/apps/sim/lib/compare/data/competitors/tines.ts index 348a1813fd8..b3d33ed2fe1 100644 --- a/apps/sim/lib/compare/data/competitors/tines.ts +++ b/apps/sim/lib/compare/data/competitors/tines.ts @@ -784,9 +784,10 @@ export const tinesProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type II, audited annually', - shortValue: 'SOC 2 Type II, audited annually', + compliance: { + value: + 'Yes: SOC 2 Type II, audited annually, plus ISO 27001, ISO 27701, and ISO 42001 (AI management systems), announced April 14, 2026 as the "ISO trifecta." No HIPAA, PCI, or FedRAMP certification; Tines says self-hosting can help meet regimes like FedRAMP, not that it holds FedRAMP certification', + shortValue: 'SOC 2 Type II, ISO 27001/27701/42001; no HIPAA', confidence: 'verified', sources: [ { @@ -794,6 +795,11 @@ export const tinesProfile: CompetitorProfile = { label: 'Security at Tines', asOf: '2026-07-02', }, + { + url: 'https://www.tines.com/blog/tines-achieves-the-iso-trifecta-iso-27001-iso-27701-and-iso-42001-certification/', + label: 'Tines achieves the ISO trifecta (27001, 27701, 42001)', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -840,24 +846,6 @@ export const tinesProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'ISO 27001, ISO 27701, and ISO 42001 (AI management systems), announced April 14, 2026 as the "ISO trifecta." No HIPAA, PCI, or FedRAMP certification; Tines says self-hosting can help meet regimes like FedRAMP, not that it holds FedRAMP certification', - shortValue: 'ISO 27001, 27701, and 42001 certified', - confidence: 'verified', - sources: [ - { - url: 'https://www.tines.com/blog/tines-achieves-the-iso-trifecta-iso-27001-iso-27701-and-iso-42001-certification/', - label: 'Tines achieves the ISO trifecta (27001, 27701, 42001)', - asOf: '2026-07-02', - }, - { - url: 'https://www.tines.com/security/', - label: 'Security at Tines', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', detail: 'Not publicly documented.', @@ -942,6 +930,19 @@ export const tinesProfile: CompetitorProfile = { }, ], }, + scim: { + value: + 'Yes: Tines exposes SCIM v2-compliant endpoints for provisioning users and groups, pushing profile updates, adding and removing users from groups, and deprovisioning users, with the tenant owner role assignable through the SCIM userType field and identity-provider group to Tines permissions mapping that grants teams, roles, and permissions by configured rules. SCIM is turned on or off per tenant under Authentication settings, and Tines states that SCIM support is not available in all plans and that customers should contact their Tines point of contact or Tines support to learn more about enabling it. Enabling it is exclusive: SCIM is not compatible with just-in-time user provisioning, and once it is on, users can only be added and modified via SCIM because the regular methods of inviting and modifying users through the UI or the API are disabled. Deprovisioned users are marked inactive rather than removed, so a tenant owner may still have to delete them manually.', + shortValue: 'Yes: SCIM v2 with group and role mapping', + confidence: 'verified', + sources: [ + { + url: 'https://www.tines.com/docs/admin/user-administration/scim/', + label: 'SCIM | Docs | Tines', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: 'Yes: Tines states it "supports the ability for administrators to set a custom session timeout length to adhere to your organization\'s policies." Users are automatically logged out of the Tines UI after a period of inactivity, defaulting to 1 day.', diff --git a/apps/sim/lib/compare/data/competitors/vellum.ts b/apps/sim/lib/compare/data/competitors/vellum.ts index 1b9046b0dfc..a27c480ed81 100644 --- a/apps/sim/lib/compare/data/competitors/vellum.ts +++ b/apps/sim/lib/compare/data/competitors/vellum.ts @@ -760,11 +760,12 @@ export const vellumProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC 2 Type 2', + compliance: { + value: + 'SOC 2 Type 2 attested and HIPAA compliant, with a Business Associate Agreement (BAA) available for enterprise customers; no other certifications (ISO 27001, GDPR-specific attestation, PCI, FedRAMP) confirmed', detail: - 'Documented at docs.vellum.ai and corroborated by a third-party Drata customer case study noting Vellum achieved SOC 2 Type 1 and Type 2 attestations.', - shortValue: 'SOC 2 Type 2 attested', + 'SOC 2 Type 2 is documented at docs.vellum.ai and corroborated by a third-party Drata customer case study noting Vellum achieved SOC 2 Type 1 and Type 2 attestations. Those same docs and case study state Vellum 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.', + shortValue: 'SOC 2 Type 2 and HIPAA; no other certs', confidence: 'verified', sources: [ { @@ -821,26 +822,6 @@ export const vellumProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'HIPAA compliant, with a BAA available for enterprise customers; no other certifications (ISO 27001, GDPR-specific attestation, PCI, FedRAMP) confirmed', - detail: - "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.", - shortValue: 'HIPAA + BAA; no other certs confirmed', - confidence: 'verified', - sources: [ - { - url: 'https://docs.vellum.ai/product/security/data-privacy-and-storage', - label: 'Vellum Docs: Data Privacy and Storage', - asOf: '2026-07-02', - }, - { - url: 'https://drata.com/customers/vellum', - label: 'Vellum Case Study: Drata', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', detail: 'Not publicly documented.', @@ -905,6 +886,13 @@ export const vellumProfile: CompetitorProfile = { confidence: 'unknown', sources: [], }, + scim: { + value: + 'Not publicly documented: no first-party Vellum documentation reviewed confirms SCIM 2.0 directory provisioning. The Manage Organization Access page describes members joining only by manual invitation or by a pre-approved email-domain automatic-join policy, and the RBAC page covers workspace roles (Admin/Member) with no identity-provider sync, group-to-role mapping, or automated create/update/deactivate flow; the enterprise marketing page reviewed names no SCIM either. This mirrors the uncertainty already recorded for SSO, which third-party summaries claim but Vellum itself does not document, so SCIM may be offered to enterprise customers without being published.', + shortValue: 'Not publicly documented; could not confirm', + confidence: 'unknown', + sources: [], + }, sessionPolicy: { value: 'Not publicly documented: no admin-configurable session lifetime cap or idle timeout is documented for Vellum workspaces. The docs index lists four security pages (Data Privacy and Storage, HMAC Authentication, RBAC, Static IPs) and two organization-settings pages (Manage Organization Access, Data Retention Policies), none of which describe session length, inactivity expiry, or forced re-authentication; the only admin-configurable access controls documented are workspace roles and domain-based automatic join.', diff --git a/apps/sim/lib/compare/data/competitors/workato.ts b/apps/sim/lib/compare/data/competitors/workato.ts index 78bb10089cd..3b941256c4c 100644 --- a/apps/sim/lib/compare/data/competitors/workato.ts +++ b/apps/sim/lib/compare/data/competitors/workato.ts @@ -899,10 +899,12 @@ export const workatoProfile: CompetitorProfile = { }, }, security: { - soc2: { + compliance: { value: - 'Workato maintains SOC 1 Type II, SOC 2 Type II, and SOC 3 reports (SOC 2 aligned to AICPA Trust Services Criteria, reports available to customers under NDA), plus PCI-DSS v4.0.1 Level 1, ISO 27001/27701/42001, HIPAA (with BAAs), IRAP, and NIST 800-171A r2 certifications', - shortValue: 'SOC 1/2/3, PCI-DSS, ISO, HIPAA, IRAP, NIST', + 'Workato maintains SOC 1 Type II, SOC 2 Type II, and SOC 3 reports (SOC 2 aligned to AICPA Trust Services Criteria, reports available to customers under NDA), plus PCI-DSS v4.0.1 Level 1, ISO 27001, ISO 27701, ISO 42001, HIPAA (with BAAs), IRAP (PROTECTED, Australia), and NIST 800-171A r2 certifications.', + detail: + "Workato's certifications go well beyond SOC 2: SOC 1 Type II covers financial reporting controls, ISO 27001 covers infosec management, ISO 27701 covers privacy (PIMS extending 27001, aligning with GDPR handling of PII), ISO 42001 covers AI governance, HIPAA compliance runs through signable BAAs with annual third-party attestation, PCI-DSS v4.0.1 Level 1 covers cardholder data, IRAP is assessed at the Australian government PROTECTED level, and NIST 800-171A r2 supports federal contractors handling Controlled Unclassified Information. There is no FedRAMP authorization or a standalone GDPR certification; GDPR compliance is represented through the ISO 27701 PIMS alignment.", + shortValue: 'SOC 1/2/3, ISO 27001/27701/42001, HIPAA, PCI-DSS, IRAP, NIST', confidence: 'verified', sources: [ { @@ -915,6 +917,11 @@ export const workatoProfile: CompetitorProfile = { label: 'Workato Security Overview', asOf: '2026-07-02', }, + { + url: 'https://www.workato.com/platform/security', + label: 'Automation Governance and Data Security | Workato', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -961,26 +968,6 @@ export const workatoProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - 'SOC1 Type II, SOC2 Type II, SOC3, ISO 27001, ISO 27701, ISO 42001, HIPAA (BAA), PCI-DSS v4.0.1 Level 1, IRAP (PROTECTED, Australia), NIST 800-171A r2', - detail: - "Workato's certifications go well beyond SOC 2: SOC 1 Type II covers financial reporting controls, ISO 27001 covers infosec management, ISO 27701 covers privacy (PIMS extending 27001, aligning with GDPR handling of PII), ISO 42001 covers AI governance, HIPAA compliance runs through signable BAAs with annual third-party attestation, PCI-DSS v4.0.1 Level 1 covers cardholder data, IRAP is assessed at the Australian government PROTECTED level, and NIST 800-171A r2 supports federal contractors handling Controlled Unclassified Information. There is no FedRAMP authorization or a standalone GDPR certification; GDPR compliance is represented through the ISO 27701 PIMS alignment.", - shortValue: 'SOC, ISO 27001/27701/42001, HIPAA, PCI-DSS, IRAP, NIST', - confidence: 'verified', - sources: [ - { - url: 'https://docs.workato.com/security/security-compliance.html', - label: 'Security compliance | Workato docs', - asOf: '2026-07-02', - }, - { - url: 'https://www.workato.com/platform/security', - label: 'Automation Governance and Data Security | Workato', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', shortValue: 'Not publicly documented', @@ -1086,6 +1073,26 @@ export const workatoProfile: CompetitorProfile = { }, ], }, + scim: { + value: + 'Yes: Workato supports SCIM 2.0 in compliance with the IETF SCIM specification, automatically provisioning users into the workspace from an identity provider, updating custom user attributes such as workato_role directly from the identity provider, assigning users to collaborator groups through the workato_user_groups attribute, and automatically de-provisioning users. It is configured under Workspace admin > Settings > Authentication > SCIM Provisioning by generating a SCIM token and base URL (https://workato.com/scim/v2, which varies by data center), and requires SAML SSO to be active in the identity provider first. SCIM 2.0 is included only in specific pricing plans: the organization must have the Data Monitoring/Advanced Security & Compliance capability, arranged with a Workato account executive or Customer Success Representative. Okta, OneLogin, and Microsoft Entra ID are the documented identity providers.', + detail: + 'Configuring SCIM requires being the workspace root account holder, holding the admin role, or holding a custom role with the SCIM provisioning privilege. One documented limitation: profile names are not updated automatically after initial provisioning, even if SCIM mappings change, so an excessively long profile name coming from identity-provider attributes must be corrected manually.', + shortValue: 'Yes: SCIM 2.0 with group mapping, plan-gated', + confidence: 'verified', + sources: [ + { + url: 'https://docs.workato.com/scim.html', + label: 'System for Cross-domain Identity Management (SCIM 2.0) | Workato docs', + asOf: '2026-09-15', + }, + { + url: 'https://docs.workato.com/scim-workato.html', + label: 'Configure and use SCIM in Workato | Workato Docs', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: 'Yes: a workspace-wide session timeout duration is set by admins under Workspace admin > Settings > Workspace > General, documented as "the time of inactivity after which users are logged out." Workato\'s security FAQs state the default is seven days and the value is configurable from 15 minutes to 14 days.', diff --git a/apps/sim/lib/compare/data/competitors/zapier.ts b/apps/sim/lib/compare/data/competitors/zapier.ts index 55632637da7..57a34b24c60 100644 --- a/apps/sim/lib/compare/data/competitors/zapier.ts +++ b/apps/sim/lib/compare/data/competitors/zapier.ts @@ -804,11 +804,12 @@ export const zapierProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'SOC 2 Type II and SOC 3 certified', + compliance: { + value: + "SOC 2 Type II and SOC 3 certified, plus GDPR and CCPA compliance. Reports are published and available via the Zapier Trust Center (trust.zapier.com). Not HIPAA-compliant (no BAAs, PHI unsupported). Some third-party sources also cite ISO 27001 and PCI DSS, though these aren't confirmed on Zapier's trust page.", detail: - 'Reports are published and available via the Zapier Trust Center (trust.zapier.com). Zapier also maintains GDPR and CCPA compliance.', - shortValue: 'SOC 2 Type II and SOC 3 certified', + "Zapier maintains SOC 2 Type II, SOC 3, GDPR, and CCPA compliance, with enterprise customers auto-opted-out of AI data training and full reports published and available via the Zapier Trust Center. Zapier does not support regulated healthcare or PHI data under HIPAA and will not sign BAAs. It also certifies to the EU-US/UK/Swiss-US Data Privacy Framework. ISO 27001 and PCI DSS are cited by secondary sources only and are not listed on Zapier's trust or security page.", + shortValue: 'SOC 2 Type II, SOC 3, GDPR, CCPA; no HIPAA', confidence: 'verified', sources: [ { @@ -817,6 +818,21 @@ export const zapierProfile: CompetitorProfile = { asOf: '2026-07-02', }, { url: 'https://trust.zapier.com/', label: 'Zapier Trust Center', asOf: '2026-07-02' }, + { + url: 'https://zapier.com/security-compliance', + label: 'Zapier | Secure and Compliant AI Orchestration at Scale', + asOf: '2026-07-02', + }, + { + url: 'https://help.zapier.com/hc/en-us/articles/8496181993613-Security-and-Compliance', + label: 'Security and Compliance – Zapier Help Center', + asOf: '2026-07-02', + }, + { + url: 'https://zapier.com/legal/data-privacy', + label: 'Data Privacy Overview | Zapier', + asOf: '2026-07-02', + }, ], }, dataResidency: { @@ -861,36 +877,6 @@ export const zapierProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: - "SOC 2 Type II, SOC 3, GDPR, and CCPA compliant. Not HIPAA-compliant (no BAAs, PHI unsupported). Some third-party sources also cite ISO 27001 and PCI DSS, though these aren't confirmed on Zapier's trust page.", - detail: - "Zapier maintains SOC 2 Type II, SOC 3, GDPR, and CCPA compliance, with enterprise customers auto-opted-out of AI data training and full reports available via the Zapier Trust Center. Zapier does not support regulated healthcare or PHI data under HIPAA and will not sign BAAs. It also certifies to the EU-US/UK/Swiss-US Data Privacy Framework. ISO 27001 and PCI DSS are cited by secondary sources only and are not listed on Zapier's trust or security page.", - shortValue: 'SOC 2, SOC 3, GDPR, CCPA. Not HIPAA-compliant', - confidence: 'verified', - sources: [ - { - url: 'https://zapier.com/security-compliance', - label: 'Zapier | Secure and Compliant AI Orchestration at Scale', - asOf: '2026-07-02', - }, - { - url: 'https://help.zapier.com/hc/en-us/articles/8496181993613-Security-and-Compliance', - label: 'Security and Compliance – Zapier Help Center', - asOf: '2026-07-02', - }, - { - url: 'https://trust.zapier.com/', - label: 'Zapier Trust Center | Powered by Conveyor', - asOf: '2026-07-02', - }, - { - url: 'https://zapier.com/legal/data-privacy', - label: 'Data Privacy Overview | Zapier', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: 'Unknown', detail: 'Not publicly documented.', @@ -993,6 +979,21 @@ export const zapierProfile: CompetitorProfile = { }, ], }, + scim: { + value: + "Yes: Zapier supports version 2.0 of the SCIM protocol, but only on Enterprise accounts that have Workspaces (an Enterprise account without Workspaces must contact its account manager). The API is served from https://zapier.com/scim/v3 and exposes both Users and Groups at the organization level: it pushes newly created users from the identity provider into Zapier, syncs profile updates to existing accounts, deactivates users, and reactivates previously deactivated ones, with GET/POST/PATCH/PUT/DELETE endpoints for creating team groups and adding or removing their members. Documented limits: users are deactivated rather than permanently deleted, the account owner cannot be removed, usernames must match the user's email address, the domain must be verified, filter DSL support is restricted, and the API is rate limited. Once provisioning is enabled, members must be managed from the identity provider rather than Zapier's Members page, and users cannot edit their own account details.", + detail: + 'Groups map to team workspaces inside the organization rather than to roles, so group membership drives which team account a member belongs to.', + shortValue: 'Yes: SCIM 2.0 users and groups, Enterprise-only', + confidence: 'verified', + sources: [ + { + url: 'https://help.zapier.com/hc/en-us/articles/8496291497741-Provision-user-accounts-with-SCIM', + label: 'Provision user accounts with SCIM - Zapier', + asOf: '2026-09-15', + }, + ], + }, sessionPolicy: { value: "No: Zapier's session timeout is a fixed platform default of 7 days that an admin cannot change. The only way to shorten it is indirectly, through SAML SSO: if the identity provider sends a session timeout, Zapier honors it when it is shorter than the 7-day default, and falls back to its own default when it is longer.", diff --git a/apps/sim/lib/compare/data/sim.ts b/apps/sim/lib/compare/data/sim.ts index 044f0887581..8d53e616342 100644 --- a/apps/sim/lib/compare/data/sim.ts +++ b/apps/sim/lib/compare/data/sim.ts @@ -833,15 +833,18 @@ export const simProfile: CompetitorProfile = { }, }, security: { - soc2: { - value: 'Yes: SOC2 compliant', - shortValue: 'SOC2 compliant', + compliance: { + value: + 'Yes: SOC 2 Type II, ISO 27001:2022, and GDPR are listed on the Sim Trust Center, which also publishes the control set and the subprocessor list. HIPAA, PCI DSS, and FedRAMP are not listed there', + detail: + 'Self-hosting, rather than additional certifications, is the primary lever Sim offers for data-residency-sensitive compliance needs.', + shortValue: 'SOC 2 Type II, ISO 27001, GDPR', confidence: 'verified', sources: [ { - url: 'https://sim.ai', - label: 'Sim Landing Page', - asOf: '2026-07-02', + url: 'https://trust.sim.ai', + label: 'Sim Trust Center', + asOf: '2026-09-15', }, { url: 'https://sim.ai/enterprise', @@ -912,20 +915,6 @@ export const simProfile: CompetitorProfile = { }, ], }, - additionalCompliance: { - value: 'SOC2', - detail: - 'Self-hosting is the primary lever Sim offers for data-residency-sensitive compliance needs beyond SOC2, rather than additional certifications.', - shortValue: 'SOC2', - confidence: 'estimated', - sources: [ - { - url: 'https://sim.ai/enterprise', - label: 'Sim Enterprise Page', - asOf: '2026-07-02', - }, - ], - }, modelAndToolGovernance: { value: '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', @@ -1008,8 +997,8 @@ export const simProfile: CompetitorProfile = { }, sso: { value: - 'Yes: SAML 2.0 and OIDC single sign-on, with users routed to SSO by their email domain, plus SCIM 2.0 directory provisioning for Okta, Microsoft Entra ID, OneLogin, and JumpCloud that creates, updates, deactivates, and removes members and maps pushed groups to permission groups, workspace access, and the organization admin role', - shortValue: 'SAML 2.0 and OIDC SSO with SCIM 2.0 provisioning', + 'Yes: SAML 2.0 and OIDC single sign-on, with users routed to SSO by their email domain', + shortValue: 'SAML 2.0 and OIDC SSO', confidence: 'verified', sources: [ { @@ -1017,10 +1006,25 @@ export const simProfile: CompetitorProfile = { label: 'Sim Docs: Single Sign-On (SSO)', asOf: '2026-07-02', }, + ], + }, + scim: { + value: + 'Yes: SCIM 2.0 directory provisioning on Enterprise plans, configured under Single sign-on then Provisioning, with documented setup for Okta, Microsoft Entra ID, OneLogin, and JumpCloud. The identity provider creates members when someone joins, updates them when their details change, and deactivates them on a deactivation request, and pushed groups map to permission groups, workspace access, and the organization admin role', + detail: + 'Each user email domain must be verified in Sim first, and a self-hosted deployment has to be reachable by the identity provider over HTTPS. Deactivation suspends access while retaining organization membership, ownership, and the seat rather than deleting the user.', + shortValue: 'SCIM 2.0 on Enterprise', + confidence: 'verified', + sources: [ { url: 'https://docs.sim.ai/platform/enterprise/scim', label: 'Sim Docs: Directory provisioning (SCIM)', - asOf: '2026-09-07', + asOf: '2026-09-15', + }, + { + url: 'https://docs.sim.ai/platform/enterprise/scim/okta', + label: 'Sim Docs: Okta provisioning', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/types.ts b/apps/sim/lib/compare/data/types.ts index 0889269badc..cce7149a950 100644 --- a/apps/sim/lib/compare/data/types.ts +++ b/apps/sim/lib/compare/data/types.ts @@ -116,12 +116,11 @@ export interface ComparisonFacts { byok: Fact } security: { - soc2: Fact + /** Every compliance certification and attestation a product claims: SOC 2, ISO 27001, GDPR, HIPAA, PCI, FedRAMP, and the report scope or access conditions attached to them. */ + compliance: Fact dataResidency: Fact rbac: Fact auditLogging: Fact - /** Compliance certifications beyond a bare SOC2 mention. HIPAA, ISO 27001, GDPR-specific attestations, PCI, FedRAMP, etc. */ - additionalCompliance: Fact /** Admin-configurable restrictions on which LLM providers/models members may use, and which specific tools/integrations a role can call. Finer-grained than plain workspace admin/write/read. */ modelAndToolGovernance: Fact /** Restricting which specific stored credentials/connections a role or permission group may use, distinct from feature-level RBAC or integration-level allow/deny. */ @@ -134,6 +133,8 @@ export interface ComparisonFacts { piiRedaction: Fact /** SAML/OIDC single sign-on with organization auto-provisioning on first login. */ sso: Fact + /** SCIM 2.0 directory provisioning: creating, updating and deactivating members from an identity provider, and any group or role mapping that comes with it. Distinct from SSO, which only authenticates an existing user. */ + scim: Fact /** Admin-configurable bounds on how long a signed-in session may live: an absolute lifetime cap from sign-in and/or an inactivity timeout, enforced org-wide. Distinct from SSO itself and from a fixed platform-wide session length the customer cannot change. */ sessionPolicy: Fact /** Whether integrations/tools/skills come from a vetted first-party catalog authored and reviewed by the vendor, versus an open marketplace where any third party can publish and users install executable code from unvetted authors. */ From 41111952ed9748922b15ee146512a41e74c7f935 Mon Sep 17 00:00:00 2001 From: Justin Blumencranz <96924014+j15z@users.noreply.github.com> Date: Tue, 15 Sep 2026 17:12:27 -0700 Subject: [PATCH 2/3] feat(skills): add the audit-comparisons skill Runs the comparison-page fact check end to end with no arguments: preflight that web fetching and the browser both work, one read-only checker per profile, then a fresh fixer that sees only that profile's flags and decides for itself which are real. Encodes what three review rounds taught us. Long-form value and detail are never shortened, because answer engines read them and a previous run cut 456 KB of sourced text. Absence of evidence is written as "not documented", never as absence of the feature. Pages that defeat fetching are retried in a browser and then reported as unverifiable rather than guessed. Dates refresh only for pages actually read. Nothing is written to the repo except edits to the data files. Co-Authored-By: Claude Opus 5 --- .claude/skills/audit-comparisons/SKILL.md | 140 ++++++++++++++++++ .../audit-comparisons/agents/checker.md | 96 ++++++++++++ .../skills/audit-comparisons/agents/fixer.md | 80 ++++++++++ 3 files changed, 316 insertions(+) create mode 100644 .claude/skills/audit-comparisons/SKILL.md create mode 100644 .claude/skills/audit-comparisons/agents/checker.md create mode 100644 .claude/skills/audit-comparisons/agents/fixer.md diff --git a/.claude/skills/audit-comparisons/SKILL.md b/.claude/skills/audit-comparisons/SKILL.md new file mode 100644 index 00000000000..593b35eda11 --- /dev/null +++ b/.claude/skills/audit-comparisons/SKILL.md @@ -0,0 +1,140 @@ +--- +name: audit-comparisons +description: Re-verify every claim on the comparison pages against its own citations, fix what is wrong, refresh the check dates, and report what could not be verified. Runs end to end with no input. Use when comparison data may be stale, before publishing comparison pages, or when asked to fact-check, re-verify, or refresh /comparisons. +--- + +# Audit comparisons + +Re-checks `apps/sim/lib/compare/data/` — 20 competitor profiles plus Sim's own — against the +sources each claim already cites. Wrong or unsupported wording gets corrected, check dates move +to today for sources that were actually read, and anything unreadable is reported instead of +being quietly asserted or quietly dropped. + +Run it with no arguments. It needs one thing from the user, once, before any work starts: a +working browser. Everything after that is automatic. + +## What this protects + +These pages exist to be read by answer engines and LLMs. The long-form text IS the product. +Earlier audits destroyed value by "tidying" — they cut 456 KB of sourced detail, dropped 250 +`detail` fields, and reshaped the schema. That is the single worst outcome of a run. + +1. **Never shorten `value` or `detail`.** They are long on purpose. `shortValue` (3-10 words) is + the only short field; it is a compression of `value` that introduces no new claim. If a + correction makes a claim narrower, the text stays long — it gets *more* precise, not smaller. + A run that reduces total bytes of `apps/sim/lib/compare/data/competitors/` without a + correction to justify each cut has failed. +2. **Never change shape.** No new fields, no renamed keys, no new files, no edits outside + `apps/sim/lib/compare/data/`. The audit updates language and dates in files that already exist. +3. **Absence of evidence is not evidence of absence.** If a capability cannot be confirmed, say + it is not documented and set `confidence: 'unknown'`. Never write that a product lacks a + feature because the docs could not be found. +4. **Cite only pages actually read in this run,** and only where the page really contains the + claim. A 200 response is not support. +5. **Preserve qualifications.** Plan gating, report scope and NDA conditions, preview/beta + labels, region limits, self-hosted-vs-cloud splits. Losing a qualification is a factual error. +6. **No artifacts.** No reports, notes, manifests or scratch files in the repo. Findings travel + in agent messages. The tree ends PR-ready. + +## Step 0 — Preflight (before spawning anything) + +Fail here, loudly, rather than halfway through 21 profiles. + +1. `git status --porcelain` in the repo. If `apps/sim/lib/compare/data/` already has uncommitted + edits, tell the user and stop — the audit needs a clean baseline to diff against. +2. **Static fetch:** WebFetch `https://docs.sim.ai/platform/enterprise/scim`. Expect real prose. +3. **Client-rendered fetch:** WebFetch `https://trust.sim.ai/`. This one is expected to come back + as a bare title — that is the failure mode the browser exists for, not a problem. +4. **Browser:** navigate to `https://trust.sim.ai/`, wait ~3s for the client render, then read the + page text. It must list the compliance certifications. If the browser pane is unavailable, the + navigation is refused, or the text stays empty: + + > Stop. Tell the user the audit needs browser access, name what failed, and ask them to enable + > it. Do not start the checkers — without the browser fallback every JavaScript-rendered + > pricing page and trust centre in the set becomes "unverifiable", which is a useless run. + +Only when all four pass, continue. Say so in one line and keep going — do not ask permission. + +## Step 1 — Units + +One unit per profile file: every `apps/sim/lib/compare/data/competitors/*.ts` plus +`apps/sim/lib/compare/data/sim.ts`. A unit is roughly 85 claims and 50-90 URLs, which is the +largest chunk one agent can check without losing precision. Never batch two profiles into one +checker. + +`sim.ts` is cited by every competitor page, so audit it too — its claims are load-bearing +everywhere. + +## Step 2 — Check (bounded, read-only) + +Spawn checkers in batches of 5. Each gets the verbatim prompt in +`agents/checker.md` with `{{PROFILE_PATH}}` replaced. The checker reads one file, opens every +cited URL, and returns two things: a per-URL verdict list, and flags for claims that are wrong, +unsupported, over-stated, or unverifiable. It edits nothing. + +## Step 3 — Fix (fresh eyes, flags only) + +For each profile that came back with flags, spawn a *fresh* agent with the verbatim prompt in +`agents/fixer.md`. It receives only the file path and that profile's flags plus per-URL verdicts — +no checker reasoning, no conversation history, nothing about the other profiles. It re-opens the +cited page itself, decides whether it agrees, and only then edits. + +The split is the point: the checker is free to be suspicious because it cannot change anything, +and the fixer is a genuine second opinion because it never sees the argument, only the claim. +Roughly a quarter of flags are false positives — usually a retrieval that got truncated or a +second attached source that already supported the claim — and the fixer is what catches them. + +## Step 4 — Dates + +The page's "verified as of" line is derived from the citation dates in the data +(`getLatestVerifiedDate`, and the page review date from the oldest citation), so there is no +separate date to maintain. The fixer sets `asOf` to **today** for every source it or the checker +actually read and confirmed supports its claim, and leaves `asOf` untouched for any source that +came back unverifiable. That way a refreshed date always means "a machine read this page today +and the claim still stood". + +## Step 5 — Verify the tree + +After every fixer returns: + +```bash +cd apps/sim && bun run type-check # expect 0 errors +cd apps/sim && bunx vitest run "app/(landing)/comparisons" "lib/compare" +bunx biome check $(git diff --name-only | grep -E '\.tsx?$' | tr '\n' ' ') +git status --porcelain # MUST contain no '??' lines +git diff --stat # MUST touch only lib/compare/data +``` + +Then compare size: `cat apps/sim/lib/compare/data/competitors/*.ts | wc -c` against the same +command at `git stash`-free HEAD. A large drop means someone truncated long-form text — find it +and restore it before reporting success. + +## Step 6 — Report + +Print to the conversation only. No files. + +- One line per profile: claims checked, URLs read, flags raised, fixes applied, flags rejected. +- **Unverifiable list** — every page that could not be read after both WebFetch and the browser, + and every cell whose claim now rests on one. This is the most important section; surface it + even when it is long. +- Anything a fixer disagreed with, with its reason. +- Confirmation that the tree has no new files and no changes outside `lib/compare/data`. + +## Known-hard sources + +Lessons from previous runs — these are traps, not edge cases: + +- **Trust centres and status pages** (`trust.sim.ai` and most vendor equivalents) are client + rendered. WebFetch returns a bare title. Always browser. +- **Pricing pages with interval toggles** (make.com, pipedream.com) hide the other interval's + prices behind a control. Read them in the browser and operate the toggle. +- **Plan matrices with tick marks** (Zapier SSO/SCIM) list every plan name in text while the + ticks restrict the feature to two of them. Text extraction reads the names and loses the + restriction. Browser, and look at the marks. +- **Docs that carry two generations of guidance** (CrewAI's agent docs kept old Docker examples + beside an explicit deprecation notice). Prefer the explicit deprecation or "current" section, + and never "correct" a claim to match a stale example. +- **OpenAI help-centre and product pages** return 403 to automated browsers. Expect + unverifiable; say so rather than guessing. +- **A flag may be wrong because the fact already cites a second source** that supports it. Check + every attached source before agreeing with a flag. diff --git a/.claude/skills/audit-comparisons/agents/checker.md b/.claude/skills/audit-comparisons/agents/checker.md new file mode 100644 index 00000000000..62b3525f3eb --- /dev/null +++ b/.claude/skills/audit-comparisons/agents/checker.md @@ -0,0 +1,96 @@ +# Checker prompt + +Spawn one per profile. Replace `{{PROFILE_PATH}}`. Pass verbatim. + +--- + +You are fact-checking one competitor profile that backs Sim's public comparison pages. You are +read-only: you will not edit anything, and a separate reviewer decides what to do with your +findings. + +File: `{{PROFILE_PATH}}` (repo root: the current working directory) + +## What to check + +Read the whole file. Every one of these is a claim that must be supported by the sources attached +to it: + +- each fact in `facts.*`: its `value`, its `detail`, and its `shortValue` +- each entry in `standoutFeatures` and `limitations` (`title`, `description`, `shortDescription`) +- `oneLiner` +- any prose fields present: `leadAnswer`, `betterThanAnswer`, `sectionIntros` + +A compound claim needs support for every clause. "SOC 2 Type II and ISO 27001, report under NDA" +is three checks, not one. + +## How to read a source + +1. **WebFetch** the URL and ask a question specific to the claim. +2. If that returns an error, a 403, an empty body, a bare title, or an obvious JavaScript shell, + **use the browser**: navigate to the URL, wait ~3 seconds for the client render, then read the + page text. If the page hides what you need behind a control — a monthly/annual pricing toggle, + an expander, a tab — operate the control and read again. +3. Only if both fail is the URL `unreachable`. + +Text extraction silently loses meaning. A plan matrix lists every plan name in text while tick +marks restrict the feature to two of them; a pricing page shows one interval at a time. When a +claim depends on a table, a tick, a badge or a toggle, look at it in the browser before judging. + +Beware pages carrying two generations of guidance — an old code example left beside an explicit +deprecation notice. The explicit "this was removed / current behaviour" section wins. Never +propose a correction that matches the stale half. + +## Verdicts + +For every URL: `supported` (you read it and it contains the claim), `contradicted`, `absent` (you +read it, the claim is not there), or `unreachable` (you could not read it, after the browser). + +## What to flag + +Flag only concrete defects: + +- the source contradicts the wording +- the source does not contain the claim at all +- the wording overstates: asserts as general something the page gates to a plan, a region, a + preview, or a specific product tier +- a material qualification present in the source is missing from the wording +- the claim's only support is an unreachable page +- `shortValue` or `shortDescription` states something `value`/`description` does not + +**Do not flag:** style, tone, wanting stronger certainty, hypothetical objections, or wording you +would have phrased differently. A fact carrying an explicit uncertainty label is correct, not +defective. + +**Before flagging, check the fact's other sources.** Facts often cite two or three pages, and the +claim you cannot find in the first is frequently stated plainly in the second. A flag that +ignores an attached source wastes the reviewer's time. + +## Proposed corrections + +Where you propose replacement wording, it must be **at least as long and as specific** as what it +replaces. These pages exist so LLMs and answer engines can read comprehensive detail. Never +propose shortening, summarizing, or deleting `value` or `detail`. Corrections make a claim more +precise, not smaller. If a capability turns out to be narrower than stated, the text says exactly +how it is narrow — with the plan, the scope and the condition spelled out. + +Never propose asserting that a product lacks a feature because you could not find evidence of it. +The correct form is that it is not publicly documented, with `confidence: 'unknown'`. + +## Rules + +- Edit nothing. Create no files, anywhere, for any reason. Keep notes in your own context. +- Do not run git, tests, or formatters. + +## Report back + +Plain text, compact, in your final message: + +1. `CHECKED: claims, URLs — supported , contradicted , absent , unreachable ` +2. `FLAGS:` a numbered list. For each: the object path (e.g. `facts.security.compliance.value`), + the current text verbatim, the URL, a **verbatim quote** from the page that justifies the flag + (or "page unreachable: "), and your proposed wording. +3. `URL VERDICTS:` one line per URL — ` — ` — so dates can be refreshed. This list + must cover every URL in the file. +4. `UNREACHABLE:` every URL that defeated both WebFetch and the browser, with what you tried. + +If nothing is wrong, say so. Zero flags is a good outcome, not a failed review. diff --git a/.claude/skills/audit-comparisons/agents/fixer.md b/.claude/skills/audit-comparisons/agents/fixer.md new file mode 100644 index 00000000000..9cd0f380bba --- /dev/null +++ b/.claude/skills/audit-comparisons/agents/fixer.md @@ -0,0 +1,80 @@ +# Fixer prompt + +Spawn fresh, one per flagged profile. Replace `{{PROFILE_PATH}}`, `{{FLAGS}}` and +`{{URL_VERDICTS}}`. Pass verbatim. Never include the checker's reasoning, the conversation +history, or any other profile's findings — the independence is what makes this step worth doing. + +--- + +You are reviewing proposed corrections to one data file behind Sim's public comparison pages. +Someone else flagged these claims. You do not know who, and you do not have their reasoning. Your +job is to decide, from the sources themselves, which flags are real — and to apply only those. + +File: `{{PROFILE_PATH}}` (repo root: the current working directory) + +## Flags + +{{FLAGS}} + +## URL verdicts from the check pass + +{{URL_VERDICTS}} + +## For each flag + +1. Open the cited page yourself. **WebFetch** first; if it returns an error, a 403, an empty body, + a bare title, or a JavaScript shell, **use the browser** — navigate, wait ~3 seconds for the + render, operate any toggle or tab hiding the answer, and read the text. +2. Read the fact's *other* sources too. A flag is wrong whenever another attached source already + supports the wording. +3. Decide: + - **agree** — the page contradicts the text, omits the claim, or the text loses a + qualification the page states. Fix it. + - **disagree** — the wording is supported, or the flag is a style preference, or it asks for + certainty the data honestly does not claim. Change nothing. + - **unverifiable** — you could not read the page either. Do not guess. Set the fact's + `confidence` to `'unknown'` only if nothing else supports it, leave the `asOf` date alone, + and report it. + +Expect to disagree with some. Retrievals get truncated and pages hide text behind controls; +roughly a quarter of flags do not survive a second look. Record a verbatim quote for every +decision, in both directions. + +## How to edit + +- **Never shorten `value` or `detail`.** They are long deliberately: answer engines and LLMs read + them. A correction makes a claim more precise, never smaller. If a capability is narrower than + stated, spell out exactly how — the plan it needs, the scope it covers, the condition attached. + Deleting a `detail` field is a defect, not a cleanup. +- `shortValue` / `shortDescription` stay 3-10 words and remain a pure compression of the long + text. If your fix changes what the long text claims, re-compress it — never let the short form + assert something the long form does not. +- Keep the file's conventions: a yes/no capability starts `Yes: ` or `No: `; single quotes, + trailing commas, 2-space indent; valid TypeScript. +- Never assert a product lacks a feature because evidence was not found. The honest form is that + it is not publicly documented, with `confidence: 'unknown'`. +- Do not change the shape: no new fields, no renamed keys, no reordering, no new files anywhere. +- Touch nothing in the file except the flagged claims and the dates below. + +## Dates + +Today is the date given to you by the environment. For every URL marked `supported` in the +verdict list above, and every URL you confirmed yourself, set that source's `asOf` to today — +including sources whose wording needed no change. A refreshed date means "read today, claim still +stands". + +Leave `asOf` exactly as it is for any URL that was `unreachable` or that you could not read. Never +refresh a date for a page nobody opened. + +## Rules + +- Create no files, anywhere, for any reason. +- Do not run git, tests, or formatters. + +## Report back + +1. `DISPOSITIONS:` one line per flag — `: agreed | disagreed | unverifiable — ` + plus the verbatim quote you relied on. +2. `EDITS:` the object paths you changed. +3. `DATES:` how many `asOf` values you refreshed, and which URLs you deliberately left stale. +4. `UNVERIFIABLE:` every claim now resting on a page nobody could read. From 17545d5f4b9bddf80322ca3e7db01a480392bce6 Mon Sep 17 00:00:00 2001 From: Justin Blumencranz <96924014+j15z@users.noreply.github.com> Date: Tue, 15 Sep 2026 20:07:12 -0700 Subject: [PATCH 3/3] fix(comparisons): reverify every profile against primary sources Recheck all 20 competitor profiles and Sim's own against public primary sources in batches of 5 (checker + independent fixer per profile), correcting stale capability, pricing, licensing, and product lifecycle claims while preserving explicit uncertainty and scope qualifications. Notable corrections: Flowise wound down and archived its repo; LangChain now holds ISO 27001 certification the profile said it lacked; OpenAI AgentKit's ZDR/background-mode compatibility was stated backwards; Gumloop repositioned from visual builder to chat-agent product and dropped its free tier; Retool self-hosting is Enterprise-only, not all tiers; Tines audit-log retention is now configurable, not fixed; Power Automate is SOC 2 GCC High in-scope, contrary to the prior claim. Refreshed Sim's own internal counts cited across every profile: blocks 266->356, tool actions ~3,900->~5,500, providers 21->25, KB connectors 51->65, trigger apps 61->64. Claims that could not be independently confirmed are marked confidence: 'unknown' rather than asserted, and the sources arrays that support each claim were refreshed to the date they were actually re-read: docs.sim.ai, trust.sim.ai, and each competitor's own docs, security/trust center, and pricing pages, per the audit-comparisons skill. Co-Authored-By: Claude Sonnet 5 --- .../compare/data/competitors/claude-cowork.ts | 260 +++++------ .../lib/compare/data/competitors/crewai.ts | 227 +++++----- apps/sim/lib/compare/data/competitors/dust.ts | 295 +++++++------ .../lib/compare/data/competitors/flowise.ts | 305 ++++++++----- .../lib/compare/data/competitors/gumloop.ts | 402 +++++++++--------- .../lib/compare/data/competitors/langchain.ts | 248 ++++++----- .../lib/compare/data/competitors/langflow.ts | 221 +++++----- apps/sim/lib/compare/data/competitors/make.ts | 293 +++++++------ .../data/competitors/microsoft-copilot.ts | 107 +++-- apps/sim/lib/compare/data/competitors/n8n.ts | 112 +++-- .../data/competitors/openai-agentkit.ts | 126 +++--- .../lib/compare/data/competitors/openclaw.ts | 95 +++-- .../lib/compare/data/competitors/pipedream.ts | 229 +++++----- .../data/competitors/power-automate.ts | 39 +- .../lib/compare/data/competitors/retool.ts | 85 ++-- .../lib/compare/data/competitors/stackai.ts | 52 ++- .../sim/lib/compare/data/competitors/tines.ts | 53 +-- .../lib/compare/data/competitors/vellum.ts | 125 ++++-- .../lib/compare/data/competitors/workato.ts | 73 ++-- .../lib/compare/data/competitors/zapier.ts | 85 ++-- apps/sim/lib/compare/data/sim.ts | 142 ++++--- 21 files changed, 2049 insertions(+), 1525 deletions(-) diff --git a/apps/sim/lib/compare/data/competitors/claude-cowork.ts b/apps/sim/lib/compare/data/competitors/claude-cowork.ts index 7a7049e069e..fa38143129a 100644 --- a/apps/sim/lib/compare/data/competitors/claude-cowork.ts +++ b/apps/sim/lib/compare/data/competitors/claude-cowork.ts @@ -26,7 +26,7 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://claude.com/product/cowork', label: 'Claude Cowork product page (Claude)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -38,7 +38,7 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Anthropic/Claude documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -49,7 +49,7 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities', label: 'Anthropic/Claude documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -61,7 +61,7 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://claude.com/blog/cowork-for-enterprise', label: 'Anthropic/Claude documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -73,7 +73,7 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://claude.com/blog/cowork-plugins', label: 'Anthropic/Claude documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -87,7 +87,7 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Anthropic/Claude documentation', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -98,19 +98,19 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://claude.com/product/cowork', label: 'Anthropic/Claude documentation', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { - title: 'Cowork activity is not captured in audit logs / Compliance API', + title: 'Compliance API returns session transcripts, not a live per-action audit stream', description: - 'Cowork activity does not appear in the Compliance API or standard data exports. OpenTelemetry (Team/Enterprise only) is the only visibility mechanism documented for streaming Cowork events to SIEM/observability tools; Anthropic does not document a way to reconcile it with Compliance API records, so it is not a full audit trail on its own.', + "Cowork sessions — both local sessions run through the Claude Desktop app and remote sessions started on claude.ai web or mobile — are retrievable through the Compliance API's session endpoints as full transcripts. The remaining limitation is granularity: the Compliance API returns session-level transcripts after the fact, not the live, per-tool-call, per-approval event stream (with a shared user identifier for SIEM correlation) that OpenTelemetry provides. A team wanting real-time visibility into individual connector calls, file edits, and approval decisions as they happen still needs the Team/Enterprise-only OpenTelemetry pipeline in addition to, not instead of, the Compliance API.", shortDescription: - 'Cowork actions are absent from the Compliance API and standard data exports.', + 'Captured in Compliance API as transcripts; OpenTelemetry adds real-time detail.', source: { url: 'https://support.claude.com/en/articles/13364135-use-claude-cowork-safely', label: 'Anthropic/Claude documentation', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -122,7 +122,7 @@ export const claudeCoworkProfile: CompetitorProfile = { source: { url: 'https://support.claude.com/en/articles/13364135-use-claude-cowork-safely', label: 'Anthropic/Claude documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -138,7 +138,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://www.anthropic.com/product/claude-cowork', label: 'Claude Cowork product page (Anthropic)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -152,7 +152,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://www.anthropic.com/product/claude-cowork', label: 'Claude Cowork product page (Anthropic)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -166,7 +166,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -174,14 +174,19 @@ export const claudeCoworkProfile: CompetitorProfile = { value: 'Claude Desktop app (macOS, Windows, Linux beta); companion mobile messaging while desktop app stays active', detail: - "Tasks execute in an isolated virtual machine on the user's computer. Pro/Max users can message and monitor from a phone while the desktop app remains open.", + "Local sessions run the agent loop natively on the user's device, with shell commands and any code Claude writes executing inside a dedicated, isolated Linux VM on that same machine (Apple Virtualization.framework on macOS, Hyper-V on Windows); cloud sessions instead run entirely in a temporary sandbox on Anthropic's servers. Through the 'Dispatch' capability — in limited beta for Pro and Max plans on Claude Cowork — a user can message Claude from their phone and have it work on their desktop via a single persistent thread, provided the Claude Desktop app stays open and the computer stays awake; this differs from a full cloud session, which keeps working even when the computer is off.", shortValue: 'Desktop app (Mac/Windows/Linux beta) + mobile', confidence: 'verified', sources: [ { url: 'https://support.claude.com/en/articles/13947068-assign-tasks-from-anywhere-in-claude-cowork', label: 'Assign tasks from anywhere in Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview', + label: 'Claude Cowork architecture overview', + asOf: '2026-09-15', }, ], }, @@ -195,7 +200,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://claude.com/blog/cowork-plugins', label: 'Customize Cowork with plugins', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -206,7 +211,7 @@ export const claudeCoworkProfile: CompetitorProfile = { shortValue: 'Closed-source proprietary product', confidence: 'verified', sources: [ - { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-07-02' }, + { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-09-15' }, ], }, environmentPromotion: { @@ -227,7 +232,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://claude.com/blog/cowork-plugins', label: 'Customize Cowork with plugins', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -240,12 +245,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans', label: 'Use Claude Cowork on Team and Enterprise plans', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://fast.io/resources/claude-cowork-shared-workspace/', label: 'How to Set Up a Claude Cowork Shared Workspace', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -260,12 +265,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://github.com/anthropics/claude-code/issues/32637', label: '[BUG] Cowork destroys user files when reorganizing (GitHub issue)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -280,12 +285,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude', label: 'Create and edit files with Claude', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://composio.dev/toolkits/excel/framework/claude-cowork', label: 'How to connect Excel to Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -293,19 +298,19 @@ export const claudeCoworkProfile: CompetitorProfile = { value: "No: Claude's document surface (Artifacts) is generated and edited by Claude itself. Artifacts remain view-only for the user (only Claude can edit the content), unlike a true inline WYSIWYG editor. Claude for Word is a separate Microsoft Word add-in, not an in-platform rich text editor for documents stored in Claude.", detail: - 'Anthropic shipped faster inline-edit updates to Artifacts in October 2025, but this is Claude regenerating content, not a user-drivable rich text editor.', + 'When a user requests a change to an Artifact, Claude regenerates the affected content itself rather than exposing direct inline editing controls, so this remains Claude-driven revision, not a user-drivable rich text editor.', shortValue: 'No: Artifacts are Claude-edited, not user WYSIWYG', confidence: 'estimated', sources: [ { url: 'https://unmarkdown.com/blog/claude-artifacts-vs-chatgpt-canvas', label: 'Claude Artifacts vs ChatGPT Canvas vs Gemini Gems', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/14465370-use-claude-for-word', label: 'Use Claude for Word', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -320,12 +325,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -333,19 +338,19 @@ export const claudeCoworkProfile: CompetitorProfile = { value: "No: Claude Cowork has no visual workflow builder, so there is no completed workflow to publish as a reusable block. The closest adjacent capability is org-wide Skills sharing: a member enables 'Share with organization' on a Skill (a SKILL.md instruction file, optionally with reference docs/scripts), and it becomes available to everyone in Customize > Skills. Recipients can enable and use a shared Skill but cannot edit its contents.", detail: - "This does not meet the bar of a published-workflow-as-block. A Skill is read-only prompt/instruction text Claude consults at runtime, not an encapsulated, deployed multi-step workflow with auto-derived inputs, hand-picked named outputs, and a hidden internal implementation that always tracks the source's latest version. Cowork Projects, the closest thing to a saved unit of work, explicitly do not support sharing for members of Team and Enterprise plans; separately, Anthropic notes projects are 'desktop-only and stored locally,' with no cloud sync.", + "This does not meet the bar of a published-workflow-as-block. A Skill is read-only prompt/instruction text Claude consults at runtime, not an encapsulated, deployed multi-step workflow with auto-derived inputs, hand-picked named outputs, and a hidden internal implementation that always tracks the source's latest version. Cowork Projects, the closest thing to a saved unit of work, do support 'Can view'/'Can edit' sharing with other members on Team and Enterprise plans, and a project created from scratch or imported from a Claude chat project syncs to the user's Claude account across devices; only a project created from an existing local folder stays on that computer and isn't synced. Either way, a Project is a container of files/instructions/memory a human works in, not a self-contained, callable block with defined inputs/outputs the way a published workflow step would be.", shortValue: 'No: no publish-workflow-as-block feature exists', confidence: 'verified', sources: [ { url: 'https://support.claude.com/en/articles/13119606-provision-and-manage-skills-for-your-organization', label: 'Provision and manage skills for your organization', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/14116274-organize-your-tasks-with-projects-in-claude-cowork', label: 'Organize your tasks with projects in Claude Cowork', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -361,7 +366,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -375,7 +380,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -389,7 +394,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://www.anthropic.com/product/claude-cowork', label: 'Claude Cowork product page (Anthropic)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -403,7 +408,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -417,12 +422,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities', label: "Use connectors to extend Claude's capabilities", - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://claude.com/blog/cowork-for-enterprise', label: 'Making Claude Cowork ready for enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -436,7 +441,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13364135-use-claude-cowork-safely', label: 'Use Claude Cowork safely', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -451,7 +456,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13364135-use-claude-cowork-safely', label: 'Use Claude Cowork safely', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -465,7 +470,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://www.anthropic.com/news/claude-design-anthropic-labs', label: 'Introducing Claude Design by Anthropic Labs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -479,7 +484,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -502,12 +507,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://genaiunplugged.substack.com/p/claude-skills-reusable-workflows-code-cowork', label: 'Claude Skills 2.0: Reusable AI Workflows That Save Hours', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -522,12 +527,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://www.cometapi.com/how-do-i-take-a-claude-project-public-and-publish/', label: 'How do I take a Claude project public and publish', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/9547008-publish-and-share-artifacts', label: 'Publish and share artifacts', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -551,12 +556,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://code.claude.com/docs/en/workflows', label: 'Orchestrate subagents at scale with dynamic workflows', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -571,7 +576,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://www.anthropic.com/webinars/deploying-multi-agent-systems-using-mcp-and-a2a-with-claude-on-vertex-ai', label: 'Deploying multi-agent systems using MCP and A2A with Claude on Vertex AI', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -586,12 +591,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -608,7 +613,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities', label: "Use connectors to extend Claude's capabilities", - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -622,7 +627,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -636,12 +641,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13837440-use-plugins-in-claude', label: 'Use plugins in Claude', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview', label: 'Claude Cowork architecture overview', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -656,17 +661,17 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/14479288-claude-cowork-architecture-overview', label: 'Claude Cowork architecture overview', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude', label: 'Create and edit files with Claude (network egress settings)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans', label: 'Use Claude Cowork on Team and Enterprise plans', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -680,7 +685,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://claude.com/product/cowork', label: 'Claude Cowork product page (Claude)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -694,7 +699,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://claude.com/blog/cowork-plugins', label: 'Customize Cowork with plugins', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -716,7 +721,7 @@ export const claudeCoworkProfile: CompetitorProfile = { shortValue: 'Included in Claude subscription plans', confidence: 'verified', sources: [ - { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-07-02' }, + { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-09-15' }, ], }, entryPaidPlan: { @@ -726,7 +731,7 @@ export const claudeCoworkProfile: CompetitorProfile = { shortValue: '$17/mo annual ($20/mo monthly)', confidence: 'verified', sources: [ - { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-07-02' }, + { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-09-15' }, ], }, freeTier: { @@ -736,7 +741,7 @@ export const claudeCoworkProfile: CompetitorProfile = { shortValue: 'Free plan excludes Cowork', confidence: 'verified', sources: [ - { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-07-02' }, + { url: 'https://claude.com/pricing', label: 'Plans & Pricing', asOf: '2026-09-15' }, ], }, byok: { @@ -759,56 +764,61 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://trust.anthropic.com/', label: 'Anthropic Trust Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/10015870-what-certifications-has-anthropic-obtained', label: 'What Certifications has Anthropic obtained?', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, dataResidency: { value: - 'No Cowork-specific residency controls; company-wide default is multi-region processing, US-based storage', + "No Cowork-specific residency controls; company-wide default is inference_geo: 'global' (inference may run in any available geography), with data at rest currently limited to a single available workspace geo, 'us'", detail: - "Anthropic's general policy processes data in the US, Europe, Asia, and Australia by default, with data at rest stored in the US. Guaranteed regional inference is only available via AWS Bedrock, GCP Vertex AI, or Microsoft Foundry deployments of the Claude API. This is not a Cowork feature.", - shortValue: 'US storage by default, no regional control', - confidence: 'estimated', + "Anthropic's current data-residency model uses two independent settings rather than a fixed default region list: an `inference_geo` API parameter, set to 'global' (any available geography, the default) or 'us' (US-only inference), and a `workspace geo` setting controlling data at rest, for which 'us' is currently the only available option. US-only guaranteed inference (`inference_geo: 'us'`) is available directly through the first-party Claude API and Claude Platform on AWS (at a 1.1x pricing multiplier); it is explicitly not applicable on Amazon Bedrock or Google Cloud Vertex AI, where the inference region instead follows the endpoint/inference-profile a customer chooses, and Microsoft Foundry offers a separate 'US Data Zone Standard' deployment type instead of the inference_geo parameter. This is not a Cowork-specific feature.", + shortValue: 'No Cowork control; global default inference, US-only workspace storage', + confidence: 'verified', sources: [ { url: 'https://platform.claude.com/docs/en/manage-claude/data-residency', label: 'Data residency - Claude Platform Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, rbac: { value: 'Yes: GA enterprise feature (April 9, 2026)', detail: - 'Enterprise/Team admins organize users into groups manually or via SCIM integration with existing identity providers, and assign roles defining which Claude capabilities (including Cowork) members can access.', + "Admins on Claude Enterprise plans organize users into groups — manually or via SCIM integration with existing identity providers — and assign each group a custom role defining which Claude capabilities (including Cowork) its members can access. Anthropic's announcement does not extend this group/custom-role RBAC to Team plan admins.", shortValue: 'GA enterprise RBAC (Apr 2026)', confidence: 'verified', sources: [ { url: 'https://claude.com/blog/cowork-for-enterprise', label: 'Making Claude Cowork ready for enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, auditLogging: { value: - 'Limited: not in Compliance API/exports; OpenTelemetry is the primary visibility path', + 'Yes: Cowork activity is captured in the Compliance API as session transcripts (local desktop sessions and remote web/mobile sessions), and Team/Enterprise customers can additionally stream a finer-grained per-action event feed via OpenTelemetry.', detail: - 'Cowork activity is not captured in the Compliance API. Team/Enterprise customers can stream tool/file/skill/approval events via OpenTelemetry to SIEM tools, with a shared user identifier allowing correlation with, but not replacing, Compliance API records.', - shortValue: 'OTel only, not in Compliance API', + "The Compliance API's session endpoints return full transcripts of Cowork sessions run through the Claude Desktop app and of sessions started on claude.ai web or mobile that run in Anthropic's cloud, captured while the user is signed in with their Claude Enterprise account. Team/Enterprise customers can layer OpenTelemetry on top for a live, per-tool-call, per-approval event stream to SIEM tools — a capability the Compliance API's after-the-fact transcript model doesn't provide by itself.", + shortValue: 'Yes: Compliance API transcripts, plus OpenTelemetry real-time events', confidence: 'verified', sources: [ { url: 'https://support.claude.com/en/articles/13364135-use-claude-cowork-safely', label: 'Use Claude Cowork safely', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://platform.claude.com/docs/en/manage-claude/compliance-api', + label: 'Compliance API - Claude Platform Docs', + asOf: '2026-09-15', }, ], }, @@ -822,7 +832,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://claude.com/blog/cowork-for-enterprise', label: 'Making Claude Cowork ready for enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -837,17 +847,17 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13930452-manage-custom-roles-on-enterprise-plans', label: 'Manage custom roles on Enterprise plans', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/13930458-set-up-role-based-permissions-on-enterprise-plans', label: 'Set up role-based permissions on Enterprise plans', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilities', label: "Use connectors to extend Claude's capabilities", - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -860,27 +870,33 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://www.anthropic.com/news/claude-design-anthropic-labs', label: 'Introducing Claude Design by Anthropic Labs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, dataRetention: { value: - "Yes for org-wide Claude data, but this does not cover Cowork: Enterprise plan Owners/Primary Owners can set a custom data retention period (minimum 30 days) for conversation and project data in Organization settings > Data and Privacy, and data is kept indefinitely without customization. Cowork conversation history is stored locally on users' computers, is not subject to this standard retention policy, and cannot be centrally managed or exported by admins; Cowork activity is also not currently captured in the Compliance API.", + "Yes for org-wide Claude data, but this does not cover Cowork: Enterprise plan Owners/Primary Owners can set a custom data retention period (minimum 30 days) for conversation and project data in Organization settings > Data and Privacy, and data is kept indefinitely without customization. Cowork conversation history itself is stored locally on users' computers and isn't subject to the standard org-wide retention-period setting; however, Cowork sessions (local and remote) are retrievable centrally by admins as transcripts through the Compliance API's session endpoints, which sit outside — and aren't limited by — the org's custom retention-period configuration for chats and projects.", detail: - "This is an org-wide Claude Enterprise setting, not per-resource-type the way Sim's granular retention is, and it explicitly excludes Cowork. Cowork's local session history sits outside this policy entirely, stored only on-device. No Zero-Data-Retention addendum is described for conversation data.", - shortValue: 'Org retention is min 30 days, but Cowork history stays local, unmanaged', + "This is an org-wide Claude Enterprise setting, not per-resource-type the way Sim's granular retention is, and it explicitly excludes Cowork. Cowork's local session history is stored only on-device and sits outside this retention policy, though Compliance API session endpoints let admins centrally retrieve session transcripts (local and remote) independent of this org-wide setting. No Zero-Data-Retention addendum is described for conversation data.", + shortValue: + 'Org retention min 30 days; Cowork history local but Compliance-API-retrievable', confidence: 'verified', sources: [ { url: 'https://privacy.claude.com/en/articles/10440198-configure-custom-data-retention-controls-for-enterprise-plans', label: 'Configure custom data retention controls for Enterprise plans', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans', label: 'Use Claude Cowork on Team and Enterprise plans', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://platform.claude.com/docs/en/manage-claude/compliance-api', + label: 'Compliance API - Claude Platform Docs', + asOf: '2026-09-15', }, ], }, @@ -893,7 +909,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://mcpmanager.ai/blog/pii-redaction-for-mcp-servers/', label: 'PII Redaction for MCP Servers: 3 Methods to Block Sensitive Data', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -908,7 +924,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso', label: 'Set up single sign-on (SSO)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -943,7 +959,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13163631-configuring-session-security-settings', label: 'Configuring session security settings', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -958,17 +974,17 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://code.claude.com/docs/en/plugin-marketplaces', label: 'Create and distribute a plugin marketplace', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/anthropics/skills', label: 'anthropics/skills: Public repository for Agent Skills', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://snyk.io/blog/toxicskills-malicious-ai-agent-skills-clawhub/', label: 'Snyk: ToxicSkills - malicious AI agent skills on ClawHub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -984,7 +1000,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://claude.com/blog/cowork-for-enterprise', label: 'Making Claude Cowork ready for enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -998,7 +1014,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1012,37 +1028,37 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, dataDrains: { value: - "Yes: Claude Enterprise's Compliance API (GET /v1/compliance/activities) gives programmatic, ongoing access to the organization's activity feed and configuration state. Anthropic supports pull-based pipelines that continuously land this data in S3/Azure Blob and feed SIEM tools like Datadog Cloud SIEM. There is also a narrower manual CSV audit-log export in claude.ai org settings.", + "Yes: Claude Enterprise's Compliance API (GET /v1/compliance/activities) gives programmatic, ongoing access to the organization's activity feed and configuration state. Anthropic documents dozens of named third-party Compliance API integrations (e.g., Datadog Cloud SIEM, Cribl Stream, CrowdStrike, Elastic) for ingesting and normalizing the organization's activity feed into SIEM/observability tooling; a generic pull-to-S3/Azure-Blob landing pattern is not documented by Anthropic itself and should be treated as not publicly documented rather than confirmed. There is also a narrower manual CSV audit-log export in claude.ai org settings.", detail: - "This is a general Claude Enterprise platform feature (Compliance API), not a Cowork-specific setting. Cowork's own local session history is not centrally exportable by admins.", - shortValue: 'Yes: Compliance API to S3/SIEM (Datadog)', + "This is a general Claude Enterprise platform feature (Compliance API), not a Cowork-specific setting. Cowork's local session history is centrally retrievable by admins through the Compliance API's session-transcript endpoints (a Compliance Access Key is required), in addition to remote web/mobile session transcripts; this is separate from the org-wide chat/project data-retention setting, which does not govern these session endpoints.", + shortValue: 'Yes: Compliance API feeds Datadog and 70+ other SIEM tools', confidence: 'verified', sources: [ { url: 'https://platform.claude.com/docs/en/manage-claude/compliance-api', label: 'Compliance API - Claude Platform Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.datadoghq.com/blog/cloud-siem-claude-compliance-api-integration/', label: 'Monitor Claude Enterprise activity with Datadog Cloud SIEM', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/15167101-get-started-with-claude-compliance-api-integrations', label: 'Get started with Claude Compliance API integrations', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/13455879-use-claude-cowork-on-team-and-enterprise-plans', label: 'Use Claude Cowork on Team and Enterprise plans', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1058,17 +1074,17 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork', label: 'Get started with Claude Cowork (Claude Help Center)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork (Claude Help Center)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.anthropic.com/product/claude-cowork', label: 'Claude Cowork product page (Anthropic)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1083,17 +1099,17 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://code.claude.com/docs/en/errors', label: 'Error reference: automatic retries and request timeout (Claude Code Docs)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.anthropic.com/news/higher-limits-spacex', label: 'Higher usage limits for Claude and a compute deal with SpaceX (Anthropic)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work', label: 'How do usage and length limits work? (Claude Help Center)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1109,13 +1125,13 @@ export const claudeCoworkProfile: CompetitorProfile = { url: 'https://code.claude.com/docs/en/errors', label: 'Error reference: automatic retries, server errors, and checkpoint recovery (Claude Code Docs)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/anthropics/claude-code/issues/60577', label: 'Transient 529 Overloaded API errors abort long-running tasks with no auto-recovery (GitHub issue)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1130,7 +1146,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork', label: 'Schedule recurring tasks in Claude Cowork', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1147,7 +1163,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://support.claude.com/en/articles/9015913-how-to-get-support', label: 'How to get support', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1160,16 +1176,16 @@ export const claudeCoworkProfile: CompetitorProfile = { sources: [], }, community: { - value: 'City-based community program + open-source plugin repo (no dedicated forum found)', + value: 'City-based community program + official Discord server and subreddit.', detail: - "Anthropic runs a city-based 'Claude Community' program; an open-source knowledge-work-plugins repo exists for sharing Cowork/Claude Code plugins. There is no dedicated public discussion forum comparable to n8n's or Sim's community forum.", - shortValue: 'City meetups + open-source plugin repo', - confidence: 'estimated', + "Anthropic runs a city-based 'Claude Community' Ambassador program and a Claude Campus Program, and its official community page directs builders to a Claude Discord server ('real-time help, project sharing, and active discussions with thousands of developers') and to r/ClaudeAI ('long-form discussions, project showcases, and community knowledge that sticks around') as its dedicated online discussion spaces, alongside an open-source knowledge-work-plugins repo for sharing Cowork/Claude Code plugins.", + shortValue: 'City meetups + official Discord and subreddit', + confidence: 'verified', sources: [ { url: 'https://claude.com/community', label: 'Community | Claude by Anthropic', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1184,7 +1200,7 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://claude.com/blog/cowork-for-enterprise', label: 'Making Claude Cowork ready for enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1204,12 +1220,12 @@ export const claudeCoworkProfile: CompetitorProfile = { { url: 'https://anthropic.skilljar.com/introduction-to-claude-cowork', label: 'Introduction to Claude Cowork course', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.pearsonvue.com/us/en/anthropic.html', label: 'Claude Certification Program by Anthropic - Pearson VUE', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/crewai.ts b/apps/sim/lib/compare/data/competitors/crewai.ts index fe1021bedf9..1465b646ec0 100644 --- a/apps/sim/lib/compare/data/competitors/crewai.ts +++ b/apps/sim/lib/compare/data/competitors/crewai.ts @@ -25,7 +25,7 @@ export const crewaiProfile: CompetitorProfile = { source: { url: 'https://docs.crewai.com/en/concepts/flows', label: 'Flows - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -36,7 +36,7 @@ export const crewaiProfile: CompetitorProfile = { source: { url: 'https://github.com/crewAIInc/crewAI', label: 'crewAIInc/crewAI (GitHub)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -47,7 +47,7 @@ export const crewaiProfile: CompetitorProfile = { source: { url: 'https://docs.crewai.com/en/concepts/llms', label: 'LLMs - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -59,7 +59,7 @@ export const crewaiProfile: CompetitorProfile = { source: { url: 'https://docs.crewai.com/en/learn/a2a-agent-delegation', label: 'Agent-to-Agent (A2A) Protocol - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -67,59 +67,61 @@ export const crewaiProfile: CompetitorProfile = { description: 'CrewAI AMP (the commercial Agent Management Platform) adds Crew Studio, a chat-and-canvas interface where a builder describes an automation in natural language and the AI generates agents, tasks, and tools as an editable drag-and-drop workflow, exportable to Python code. This gives the code-first framework an optional visual entry point for non-developers. Sim ships an equivalent natural-language builder (Chat and in-editor Copilot) as a core, free part of the product, not a separate paid add-on layered on top of a code-only open-source base.', shortDescription: - "Natural-language chat generates an editable visual workflow, exportable to code, as a paid AMP add-on; Sim's Chat and Copilot ship the same capability free.", + "Natural-language chat generates an editable visual workflow, exportable to code, via the separate AMP platform (included on its free Basic tier); Sim's Chat and Copilot ship the same capability free in the core product.", source: { url: 'https://docs.crewai.com/en/enterprise/features/crew-studio', label: 'Crew Studio - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], limitations: [ { - title: 'Core framework is code-only; no visual builder without the paid AMP platform', + title: 'Core framework is code-only; visual builder is a separate AMP platform feature', description: 'The open-source crewAI framework is authored entirely in Python (classes, YAML configs, decorators), with no built-in drag-and-drop canvas. Visual building (Crew Studio) is a feature of the separate, commercial CrewAI AMP platform, not the free self-hosted framework.', - shortDescription: 'No visual canvas in the free framework; Studio requires paid AMP.', + shortDescription: + 'No visual canvas in the free framework; Studio is a separate AMP platform feature.', source: { url: 'https://docs.crewai.com/en/enterprise/features/crew-studio', label: 'Crew Studio - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { title: 'Human-in-the-loop input is a blocking, single-step primitive, not a rich approval workflow', description: - "HITL in the open-source framework is now the @human_feedback decorator on Flows (v1.8.0+), which pauses for synchronous, console-based review in local runs, replacing the older Task human_input=True flag. Production HITL, via webhooks, an in-platform pending-review state, responder assignment, SLAs, and escalation policies (the 'Flow HITL Management Platform'), requires CrewAI AMP/Enterprise.", + "HITL in the open-source framework includes the @human_feedback decorator on Flows (v1.8.0+), which pauses for synchronous, console-based review in local runs, alongside the separate, still-documented Task-level human_input=True flag (a per-task input prompt that predates Flows and remains a current, undeprecated part of the docs, not superseded by it). Production HITL, via webhooks, an in-platform pending-review state, responder assignment, SLAs, and escalation policies (the 'Flow HITL Management Platform'), requires CrewAI AMP/Enterprise.", shortDescription: 'OSS HITL is console-based via @human_feedback; rich approval needs AMP.', source: { url: 'https://docs.crewai.com/en/learn/human-in-the-loop', label: 'Human-in-the-Loop (HITL) Workflows - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { title: 'Governance, security, and hosted deployment features gated to CrewAI AMP', description: - 'SSO (Microsoft Entra, Okta), role-based access control, dedicated VPC networking, on-premise/private deployment (AMP Factory), audit trails, and the SOC 2/HIPAA-compliant hosted environment are Enterprise-tier CrewAI AMP features, not part of the free open-source framework.', + "SSO (Microsoft Entra, Okta), role-based access control, dedicated VPC networking, and on-premise/private deployment (AMP Factory) are Enterprise-tier CrewAI AMP features per CrewAI's pricing page; audit trails are described in third-party CrewAI production write-ups rather than itemized on CrewAI's own pricing page, and the SOC 2 Type 2 and HIPAA-compliant hosted environment is documented separately on CrewAI's Trust Center. None of this is part of the free open-source framework.", shortDescription: 'SSO, RBAC, and compliance are Enterprise AMP features, not the free framework.', source: { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { title: 'Requires Python fluency; no low-code entry point in the core product', description: - 'Crews and Flows are authored as Python classes, decorators, and YAML configuration, so using the core framework directly requires working knowledge of Python, virtual environments, and package management. Non-developers depend on the separate, paid AMP Studio layer; there is no built-in low-code mode in the open-source package.', - shortDescription: 'Core framework requires Python; no low-code mode without paid AMP.', + "Crews and Flows are authored as Python classes, decorators, and YAML configuration, so using the core framework directly requires working knowledge of Python, virtual environments, and package management. Non-developers depend on the separate CrewAI AMP platform's Studio layer, which is included even on AMP's free Basic tier (capped at 50 executions/month) as well as on paid Enterprise; there is no built-in low-code mode in the open-source package itself.", + shortDescription: + 'Core framework requires Python; low-code mode is a separate AMP platform feature.', source: { url: 'https://docs.crewai.com/en/concepts/agents', label: 'Agents - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -127,35 +129,36 @@ export const crewaiProfile: CompetitorProfile = { platform: { builderType: { value: - 'Code-first Python framework (Crews and Flows); visual Studio only via paid CrewAI AMP', + "Code-first Python framework (Crews and Flows); visual Studio is a separate CrewAI AMP platform feature, available on AMP's free Basic tier as well as paid Enterprise", detail: - 'The open-source core is authored in Python: Agents, Tasks, and Crews are Python classes/YAML config, and Flows use Python decorators (@start, @listen, @router) for event-driven orchestration. A drag-and-drop visual canvas (Crew Studio) exists only inside the commercial CrewAI AMP platform, generated from natural-language chat and exportable back to Python.', - shortValue: 'Python code framework; visual builder is a paid AMP add-on', + "The open-source core is authored in Python: Agents, Tasks, and Crews are Python classes/YAML config, and Flows use Python decorators (@start, @listen, @router) for event-driven orchestration. A drag-and-drop visual canvas (Crew Studio) exists inside the separate, commercial CrewAI AMP platform, generated from natural-language chat and exportable back to Python; it ships even on AMP's free Basic tier (capped at 50 executions/month), not only on paid Enterprise.", + shortValue: + "Python code framework; visual builder is a separate AMP platform feature, available on AMP's free Basic tier", confidence: 'verified', sources: [ { url: 'https://docs.crewai.com/en/concepts/flows', label: 'Flows - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.crewai.com/en/enterprise/features/crew-studio', label: 'Crew Studio - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, learningCurve: { value: "Steep for the core framework; low for Crew Studio's natural-language mode", detail: - 'Using the open-source framework directly requires Python fluency (classes, YAML, async/await, package management). Crew Studio, the paid AMP visual/chat layer, targets non-developers who describe an automation in plain language.', - shortValue: 'Steep in code; low via paid Studio chat interface', + "Using the open-source framework directly requires Python fluency (classes, YAML, async/await, package management). Crew Studio, the separate CrewAI AMP platform's visual/chat layer (available on AMP's free Basic tier as well as paid Enterprise), targets non-developers who describe an automation in plain language.", + shortValue: "Steep in code; low via Studio's chat interface, free on AMP's Basic tier", confidence: 'estimated', sources: [ { url: 'https://docs.crewai.com/en/concepts/agents', label: 'Agents - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://blog.crewai.com/enabling-domain-experts-to-build-and-deploy-agentic-workflows-without-the-need-to-write-code/', @@ -180,7 +183,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://github.com/crewAIInc/crewAI', label: 'crewAIInc/crewAI (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -195,12 +198,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { - url: 'https://sambanova.ai/blog/sambanova-and-crewai-partner-to-deliver-agentic-ai-at-scale-on-crewai-amp', - label: 'SambaNova and CrewAI Partner on CrewAI AMP', - asOf: '2026-07-02', + url: 'https://docs-platform.crewai.com/platform/en/features/sso', + label: 'SSO - CrewAI Platform Docs', + asOf: '2026-09-15', }, ], }, @@ -215,7 +218,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/flows', label: 'Flows - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -230,7 +233,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://github.com/crewAIInc/crewAI/blob/main/LICENSE', label: 'crewAI/LICENSE (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -254,7 +257,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/guides/deploy-to-amp', label: 'Deploy to AMP - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -269,7 +272,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/features/crew-studio', label: 'Crew Studio - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -284,7 +287,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/knowledge', label: 'Knowledge - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -299,7 +302,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/knowledge', label: 'Knowledge - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -322,12 +325,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/flows', label: 'Flows - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://community.crewai.com/t/flows-calling-crews-or-crews-tasks-calling-flows/3684', label: 'Flows calling Crews or Crews/Tasks calling Flows - CrewAI Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -343,17 +346,17 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/guides/tool-repository', label: 'Tool Repository - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.crewai.com/en/enterprise/features/crew-studio', label: 'Crew Studio - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://community.crewai.com/t/crew-method-as-tool/400', label: 'Crew method as tool - CrewAI Community', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -370,7 +373,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/llms', label: 'LLMs - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -385,7 +388,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/agents', label: 'Agents - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -393,14 +396,14 @@ export const crewaiProfile: CompetitorProfile = { value: 'Yes: Crew Studio (CrewAI AMP) generates an editable workflow from a chat description', detail: - 'Crew Studio lets a builder describe an automation in natural language; the platform generates agents, tasks, and tools as an editable drag-and-drop canvas, exportable to Python. This is a CrewAI AMP (paid) feature, not part of the free open-source framework, where crews are authored directly in code.', - shortValue: 'Yes, via Crew Studio chat interface (paid AMP feature)', + "Crew Studio lets a builder describe an automation in natural language; the platform generates agents, tasks, and tools as an editable drag-and-drop canvas, exportable to Python. This is a feature of the separate CrewAI AMP platform, included even on AMP's free Basic tier (capped at 50 executions/month) as well as on paid Enterprise, not part of the free open-source framework, where crews are authored directly in code.", + shortValue: 'Yes, via Crew Studio chat interface (separate AMP platform, free Basic tier)', confidence: 'verified', sources: [ { url: 'https://docs.crewai.com/en/enterprise/features/crew-studio', label: 'Crew Studio - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -414,7 +417,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/knowledge', label: 'Knowledge - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -428,7 +431,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/mcp/overview', label: 'MCP Servers as Tools in CrewAI - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -443,12 +446,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/tasks', label: 'Tasks (Guardrails) - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.crewai.com/en/enterprise/features/hallucination-guardrail', label: 'Hallucination Guardrail - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -463,7 +466,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/learn/human-in-the-loop', label: 'Human-in-the-Loop (HITL) Workflows - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -478,7 +481,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://github.com/crewAIInc/crewAI/tree/main/lib/crewai-tools', label: 'crewAIInc/crewAI - lib/crewai-tools (GitHub)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -493,7 +496,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/agents', label: 'Agents - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.crewai.com/en/learn/tool-hooks', @@ -521,7 +524,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/agents', label: 'Agents - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -536,12 +539,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://github.com/zinyando/crewai_chat_ui', label: 'crewai_chat_ui (GitHub, community package)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.copilotkit.ai/blog/how-to-add-a-frontend-to-any-crewai-agent-using-ag-ui-protocol', label: 'How to add a Frontend to any CrewAI Agent using AG-UI Protocol - CopilotKit', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -564,7 +567,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/flows', label: 'Flows - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.crewai.com/en/concepts/tasks', + label: 'Tasks - CrewAI Docs', + asOf: '2026-09-15', }, ], }, @@ -579,7 +587,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/learn/a2a-agent-delegation', label: 'Agent-to-Agent (A2A) Protocol - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -594,7 +602,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/flows', label: 'Flows - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://community.crewai.com/t/loops-in-a-flow/1306', @@ -616,12 +624,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://github.com/crewAIInc/crewAI/tree/main/lib/crewai-tools/src/crewai_tools/tools', label: 'crewAIInc/crewAI - lib/crewai-tools/tools directory (GitHub)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.crewai.com/en/tools/automation/composiotool', label: 'Composio Tool - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -636,7 +644,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/guides/webhook-automation', label: 'Webhook Automation - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -650,7 +658,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/agents', label: 'Agents - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -665,22 +673,22 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/tools/ai-ml/codeinterpretertool', label: 'Code Interpreter (removal notice) - CrewAI Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://www.kb.cert.org/vuls/id/221883', label: 'VU#221883 vendor statement - CERT Coordination Center', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs-platform.crewai.com/platform/en/guides/deploy-to-amp', label: 'Deploy to AMP - CrewAI Platform Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs-platform.crewai.com/platform/en/guides/private-package-registry', label: 'Private Package Registries - CrewAI Platform Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -694,7 +702,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/enterprise/guides/use-crew-api', label: 'Trigger Deployed Crew API - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -709,7 +717,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://github.com/crewAIInc/crewAI', label: 'crewAIInc/crewAI (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -735,7 +743,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -750,7 +758,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -765,7 +773,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -780,7 +788,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/llms', label: 'LLMs - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -788,21 +796,21 @@ export const crewaiProfile: CompetitorProfile = { security: { compliance: { value: - 'Yes: CrewAI AMP has a SOC 2 Type 1 audit report (dated November 2025) and a HIPAA audit report (dated February 2026) for the Enterprise edition, both available via its Trust Center. No ISO 27001, PCI, or FedRAMP certification is confirmed. These attestations apply to the Enterprise/AMP offering, not to a self-hosted deployment of the open-source framework, which has no compliance certification of its own since it is not a hosted service.', + 'Yes: CrewAI AMP has a SOC 2 Type 2 audit report (released June 2026, covering the November 15, 2025 - February 14, 2026 examination period) and a HIPAA audit report (dated February 2026) for the Enterprise edition, both available via its Trust Center. No ISO 27001, PCI, or FedRAMP certification is confirmed. These attestations apply to the Enterprise/AMP offering, not to a self-hosted deployment of the open-source framework, which has no compliance certification of its own since it is not a hosted service.', detail: - "CrewAI's Trust Center (trust.crewai.com, indexed by Vanta) lists the SOC 2 Type 1 Audit Report from November 2025 alongside the HIPAA Audit Report from February 2026. CrewAI's pricing page separately references 'FedRamp High compliance' language for its Enterprise tier, but no independent FedRAMP authorization listing corroborates that claim, so it is not treated as confirmed here.", - shortValue: 'SOC 2 Type 1 and HIPAA audits, AMP Enterprise only', + "CrewAI's Trust Center (trust.crewai.com, indexed by Vanta) lists the SOC 2 Type 2 Report for CrewAI, released June 2026 with an examination period of November 15, 2025 to February 14, 2026, alongside the HIPAA Audit Report from February 2026. CrewAI's pricing page separately references 'FedRamp High compliance' language for its Enterprise tier, but no independent FedRAMP authorization listing corroborates that claim, so it is not treated as confirmed here.", + shortValue: 'SOC 2 Type 2 and HIPAA audits, AMP Enterprise only', confidence: 'estimated', sources: [ { url: 'https://trust.crewai.com/', label: 'CrewAI Trust Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -817,7 +825,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/features/sso', label: 'SSO - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://crewai.com/pricing', + label: 'CrewAI Pricing', + asOf: '2026-09-15', }, ], }, @@ -832,7 +845,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/features/sso', label: 'SSO - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -847,7 +860,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://techjacksolutions.com/ai-tools/crewai/crewai-production-guide/', label: 'CrewAI in Production: Deployment, Monitoring & Scaling - TechJack Solutions', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -870,7 +883,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/features/secrets-manager/gcp', label: 'Google Cloud Secret Manager - CrewAI Docs', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -901,7 +914,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/features/pii-trace-redactions', label: 'PII Redaction for Traces - CrewAI Docs', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -916,7 +929,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -938,17 +951,17 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs-platform.crewai.com/platform/en/features/sso', label: 'SSO - CrewAI Platform Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs-platform.crewai.com/platform/en/features/rbac', label: 'RBAC - CrewAI Platform Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://enterprise-docs.crewai.com/features/workos-sso', label: 'WorkOS SSO - CrewAI Platform Helm Chart', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -963,12 +976,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/guides/tool-repository', label: 'CrewAI Enterprise Tool Repository docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/crewAIInc/crewAI/tree/main/lib/crewai-tools', label: 'crewAIInc/crewAI - lib/crewai-tools (GitHub)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -985,7 +998,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/observability/tracing', label: 'CrewAI Tracing - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1008,7 +1021,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/guides/webhook-automation', label: 'Webhook Automation - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1023,17 +1036,17 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/guides/capture_telemetry_logs', label: 'Capture Telemetry Logs - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.dynatrace.com/hub/detail/crewai-observability/', label: 'CrewAI monitoring & observability - Dynatrace Hub', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://signoz.io/docs/crewai-observability/', label: 'CrewAI Observability & Monitoring with OpenTelemetry - SigNoz Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.ibm.com/docs/en/instana-observability/1.0.304?topic=frameworks-crewai', @@ -1053,7 +1066,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/learn/kickoff-async', label: 'Kickoff Crew Asynchronously - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1068,7 +1081,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1083,7 +1096,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/concepts/tasks', label: 'Tasks (Guardrails - guardrail_max_retries) - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1098,12 +1111,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://docs.crewai.com/en/enterprise/guides/webhook-automation', label: 'Webhook Automation - CrewAI Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.crewai.com/en/enterprise/guides/kickoff-crew', label: 'Kickoff Crew - CrewAI Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1120,7 +1133,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://crewai.com/pricing', label: 'CrewAI Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1142,7 +1155,7 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://github.com/crewAIInc/crewAI', label: 'crewAIInc/crewAI (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1157,12 +1170,18 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://siliconangle.com/2024/10/22/agentic-ai-startup-crewai-closes-18m-funding-round/', label: 'Agentic AI startup CrewAI closes $18M funding round - SiliconANGLE', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.insightpartners.com/ideas/behind-the-investment-crewai/', label: 'Behind the Investment: CrewAI - Insight Partners', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.globenewswire.com/news-release/2024/10/22/2966872/0/en/CrewAI-Launches-Multi-Agentic-Platform-to-Deliver-on-the-Promise-of-Generative-AI-for-Enterprise.html', + label: + 'CrewAI Launches Multi-Agentic Platform to Deliver on the Promise of Generative AI for Enterprise - GlobeNewswire', + asOf: '2026-09-15', }, ], }, @@ -1177,12 +1196,12 @@ export const crewaiProfile: CompetitorProfile = { { url: 'https://learn.crewai.com', label: 'CrewAI Academy (learn.crewai.com)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.deeplearning.ai/short-courses/multi-ai-agent-systems-with-crewai/', label: 'Multi AI Agent Systems with crewAI - DeepLearning.AI', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/dust.ts b/apps/sim/lib/compare/data/competitors/dust.ts index 0b7a13421fa..5bb2e93474a 100644 --- a/apps/sim/lib/compare/data/competitors/dust.ts +++ b/apps/sim/lib/compare/data/competitors/dust.ts @@ -54,7 +54,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://docs.dust.tt/docs/changelog#gitops-sync-for-skills-&-agent-configurations-with-github-action', label: 'GitOps sync for Skills & Agent configurations | Dust changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -65,7 +65,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://docs.dust.tt/docs/skills', label: 'Skills | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -76,7 +76,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://docs.dust.tt/docs/scheduling-your-agent-beta', label: 'Schedules | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -88,7 +88,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://docs.dust.tt/docs/client-side-mcp-server', label: 'Client Side MCP Server (Preview) | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -99,7 +99,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://blog.dust.tt/introducing-frames-interactive-data-visualized/', label: 'Introducing Frames: Interactive data, visualized | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -111,9 +111,9 @@ export const dustProfile: CompetitorProfile = { shortDescription: 'Agent builder is form/instruction-based; the older visual block builder is deprecated.', source: { - url: 'https://docs.dust.tt/reference/dust-apps-core-concepts', + url: 'https://docs.dust.tt/docs/developer-platform/legacy-dust-apps/dust-apps-core-concepts', label: 'Dust Apps: Core Concepts | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -126,7 +126,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://dust.tt/blog/evaluation-to-maintenance', label: 'From Evaluation to Maintenance | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -138,7 +138,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://github.com/dust-tt/dust/blob/main/LICENSE', label: 'dust-tt/dust LICENSE (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -150,7 +150,7 @@ export const dustProfile: CompetitorProfile = { source: { url: 'https://docs.dust.tt/docs/table-queries', label: 'Table queries | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -167,12 +167,12 @@ export const dustProfile: CompetitorProfile = { { url: 'https://deepwiki.com/dust-tt/dust/3.2-agent-builder-interface', label: 'Agent Builder Interface | dust-tt/dust | DeepWiki', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { - url: 'https://docs.dust.tt/reference/dust-apps-core-concepts', + url: 'https://docs.dust.tt/docs/developer-platform/legacy-dust-apps/dust-apps-core-concepts', label: 'Dust Apps: Core Concepts | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -180,14 +180,24 @@ export const dustProfile: CompetitorProfile = { value: 'Low for simple no-code agents from a template; steeper for custom MCP tool integrations, Query Tables/SQL, and GitOps-managed configurations', detail: - 'Dust markets itself as a no-code agent builder for business users starting from templates with Sidekick guidance, while custom MCP servers, SQL-based Query Tables, and Git-based configuration management assume technical familiarity.', + "Dust markets itself as a no-code agent builder that lets business teams build and deploy agents connected to company data without engineering support (per Dust's own blog); separately, Dust's product documentation describes starting from a template gallery with Sidekick-guided instruction drafting as the typical on-ramp, while custom MCP servers, SQL-based Query Tables, and Git-based configuration management assume more technical familiarity.", shortValue: 'Easy for templated agents, steeper for custom tools/SQL/GitOps', confidence: 'estimated', sources: [ { url: 'https://dust.tt/blog/no-code-ai-agent-builder', label: 'No-Code AI Agent Builder | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/docs/agent-builder-sidekick', + label: 'Agent Builder Sidekick | Dust Docs', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/docs/templates', + label: 'Templates | Dust Docs', + asOf: '2026-09-15', }, ], }, @@ -202,7 +212,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://github.com/dust-tt/dust/blob/main/LICENSE', label: 'dust-tt/dust LICENSE (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -217,22 +227,27 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/changelog#-eu-data-hosting-option-available', label: 'EU data hosting option available | Dust changelog', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, templates: { value: - 'Yes: a Template Gallery of pre-built agents organized by department/use case (Sales, Customer Support, Marketing, Engineering, Data Analytics, Knowledge Management, Recruiting, Product Design, Collaboration)', + "Yes: a template gallery of pre-built agents, with Dust's separate Use Cases & Guides documentation organized by department/use case (Sales, Customer Support, Marketing, Engineering, Data Analytics, Knowledge, Recruiting & People, Product, Collaboration)", detail: - "Selecting a template opens a Sidekick-guided creation flow pre-loaded with the template's instructions and suggested tools/data sources; templates are organized by department/use case including Sales, Customer Support, Marketing, Engineering, Data Analytics, Knowledge Management, Recruiting, Product Design, and Collaboration. The builder reviews, adjusts, and publishes from there.", - shortValue: 'Template gallery organized by department/use case', + "Selecting a template opens a Sidekick-guided creation flow pre-loaded with the template's context; Sidekick drafts instructions and suggests tools/data sources for the builder to review, adjust, and publish. Dust's current Templates doc page no longer itself enumerates categories and instead points to a separate Use Cases & Guides section, which organizes use cases by department: Sales, Customer Support, Marketing, Engineering, Data Analytics, Knowledge, Recruiting & People, Product, and Collaboration.", + shortValue: 'Template gallery; Use Cases & Guides organized by department', confidence: 'verified', sources: [ { url: 'https://docs.dust.tt/docs/templates', label: 'Templates | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/index', + label: 'Use Cases & Guides | Dust Docs', + asOf: '2026-09-15', }, ], }, @@ -247,7 +262,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://github.com/dust-tt/dust/blob/main/LICENSE', label: 'dust-tt/dust LICENSE (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -262,7 +277,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/changelog#gitops-sync-for-skills-&-agent-configurations-with-github-action', label: 'GitOps sync for Skills & Agent configurations | Dust changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -277,12 +292,12 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/changelog#-prompt-version-history', label: 'Prompt version history | Dust changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://deepwiki.com/dust-tt/dust/3.1-agent-configuration-and-management', label: 'Agent Configuration and Management | dust-tt/dust | DeepWiki', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -290,14 +305,14 @@ export const dustProfile: CompetitorProfile = { value: "No: Dust calls itself 'multiplayer AI', with shared conversations, mentions, notifications, and to-dos between people and agents in a workspace, but this is asynchronous collaboration, not live concurrent editing of the same agent configuration with synced cursors", detail: - "Dust's own materials describe a shared workspace where 'teams and agents work in the same workspace with shared projects, context, conversations, to-dos, notifications' rather than live co-editing of a single agent's configuration.", + "Dust's own materials describe a shared workspace: its Collaboration docs describe users and AI agents working together in shared conversations through @mentions, notifications, and conversation sharing (not live co-editing of a single agent's configuration), and Dust's homepage separately describes 'shared access to company knowledge, connected tools, conversations, and notifications' between people and agents.", shortValue: 'Shared async workspace, not live co-editing of one config', confidence: 'estimated', sources: [ { url: 'https://docs.dust.tt/docs/collaboration', label: 'Collaboration | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -312,7 +327,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/file-generation', label: 'File Generation | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -327,7 +342,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/table-queries', label: 'Table queries | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -342,12 +357,12 @@ export const dustProfile: CompetitorProfile = { { url: 'https://blog.dust.tt/introducing-frames-interactive-data-visualized/', label: 'Introducing Frames: Interactive data, visualized | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { - url: 'https://docs.dust.tt/changelog/dust-agents-can-now-create-and-edit-google-drive-documents', + url: 'https://docs.dust.tt/docs/changelog', label: 'Dust Agents Can Now Create and Edit Google Drive Documents | Dust changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -362,7 +377,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/run-agent', label: 'Run agent | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -377,12 +392,12 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/skills', label: 'Skills | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/run-agent', label: 'Run agent | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -390,16 +405,17 @@ export const dustProfile: CompetitorProfile = { aiCapabilities: { multiLlmSupport: { value: - 'Yes: agents can be configured with a choice of model (e.g. GPT-4 Turbo, Claude 3, Gemini Pro, Mistral Large) and a Reasoning Effort setting, selectable per agent', + 'Yes: agents can be configured with a choice of specific model from multiple providers, or one of three curated auto-model tiers (Basic, Standard, Premium) that Dust benchmarks and updates, plus a reasoning-effort setting (None, Light, Medium, High) selectable per agent when a specific model is chosen', detail: - 'Advanced agent settings let a builder pick the model and a reasoning-effort level (Light, Medium, High); Dust docs name GPT-4 Turbo, Claude 3, Gemini Pro, and Mistral Large as selectable models.', - shortValue: 'GPT-4 Turbo, Claude 3, Gemini Pro, Mistral Large selectable per agent', + "Dust's model-selection docs list current per-tier models including GPT 5.6 Luna, Claude Sonnet 4.6, Claude Opus 4.8, Claude Opus 5, GPT 5.6 Sol, Gemini 3.1 Pro, Gemini 3.7 Flash, Gemini 3.1 Flash Lite, Mistral Small, Mistral Medium 3.5, and Mistral Large; reasoning effort (None/Light/Medium/High) only applies when a specific model, rather than an auto tier, is selected.", + shortValue: + 'Specific models or Basic/Standard/Premium auto-tiers; reasoning effort None/Light/Medium/High', confidence: 'verified', sources: [ { - url: 'https://docs.dust.tt/docs/what-settings-model-should-i-use', - label: 'What settings / model should I use? | Dust Docs', - asOf: '2026-07-08', + url: 'https://docs.dust.tt/docs/user-documentation/agents/model-selection', + label: 'Model selection | Dust Docs', + asOf: '2026-09-15', }, ], }, @@ -414,7 +430,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://blog.dust.tt/introducing-multi-tool-assistants/', label: 'Introducing: multi-tool agents | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -429,7 +445,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/agent-builder-sidekick', label: 'Agent Builder Sidekick | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -444,7 +460,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/understanding-retrieval-augmented-generation-rag-and-the-search-method-in-dust', label: 'Understanding Retrieval Augmented Generation (RAG) | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -459,12 +475,12 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/remote-mcp-server', label: 'Adding an MCP Server | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/client-side-mcp-server', label: 'Client Side MCP Server (Preview) | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -479,7 +495,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://dust.tt/blog/evaluation-to-maintenance', label: 'From Evaluation to Maintenance | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -487,35 +503,40 @@ export const dustProfile: CompetitorProfile = { value: "Yes: MCP tool execution uses a stakes-tiered approval model (high/medium/low-stake tools, with argument-level approval required for certain medium-stake tool parameters), not a simple 'always ask' vs. auto-execute toggle, and Dust's own guidance recommends human approval before irreversible agent actions", detail: - "Dust's MCP tool architecture tiers tools by stake level and requires argument-level approval for certain medium-stake tool parameters before execution, and Dust recommends 'mandatory steps, and human approval points before any irreversible action' for consequential agent actions. This is a graduated tool-execution approval model, not a single named workflow node like a dedicated approval action in a workflow tool.", + "Dust's MCP tool architecture tiers tools by stake level and requires argument-level approval for certain medium-stake tool parameters before execution. Separately, Dust's own guidance on agent workflow design lists 'human approval checkpoints' as one recommended pattern for high-stakes decisions or sensitive workflows, so agents don't take critical actions autonomously — presented as one design pattern among several (alongside sequential execution, multi-agent collaboration, and parallel processing), not as a mandatory platform-wide gate.", shortValue: 'Stakes-tiered MCP approval model; documented best-practice guidance', confidence: 'estimated', sources: [ { url: 'https://deepwiki.com/dust-tt/dust/4-agent-system', label: 'MCP Tool System | dust-tt/dust | DeepWiki', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://dust.tt/blog/ai-agent-workflows', label: 'AI agent workflows: How they work and how to build your own | Dust Blog', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, generativeMedia: { value: - "Partial: native image generation (via Google's gemini-3-pro-image model) with reference-image consistency (up to 14 reference images) and parallel generation is built in; there is no dedicated native video-generation block, though a separate 'Voice and sound generation' tool exists for audio", + "Partial: native image generation is built in, with reference-image consistency (up to 14 reference images per generation, per current docs) and parallel generation; the underlying default model is not consistently documented — a January 2026 changelog entry named Google's Gemini 3 Pro Image, while an April 2026 changelog entry states GPT Image 2 (OpenAI) is 'already the default image generation model on Dust,' and the current image-generation doc page does not itself name a model; there is no dedicated native video-generation block, though a separate 'Voice and sound generation' tool exists for audio", detail: - "Dust's Image Generation capability uses Google's gemini-3-pro-image model, supports up to 14 reference images for visual consistency across a series, and can run multiple generations in parallel; generated images are filtered for safety. A separate 'Voice and sound generation' tool provides native audio generation, but no dedicated native video-generation block was found.", + "Dust's current Image Generation docs page supports up to 14 reference images for visual consistency across a series and can run multiple generations in parallel, but does not itself name an underlying model. Dust's changelog shows the model attribution changed over time: a January 28, 2026 entry ('More Powerful Image Generation with Gemini 3 Pro') states image generation was upgraded to Google's Gemini 3 Pro model, while a later April 22, 2026 entry ('GPT Image 2: Enhanced Image Generation Now Default on Dust') states OpenAI's GPT Image 2 'is now the default for all image creation on Dust' and that 'GPT Image 2 is already the default image generation model on Dust' — superseding the earlier Gemini attribution. A separate 'Voice and sound generation' tool provides native audio generation, but no dedicated native video-generation block was found.", shortValue: - 'Native image gen (gemini-3-pro-image) + reference images; separate audio tool; no native video', + 'Native image gen + reference images; default model undocumented/conflicting; no native video', confidence: 'estimated', sources: [ { url: 'https://docs.dust.tt/docs/image-generation', label: 'Image Generation | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/docs/changelog', + label: 'Image generation model changelog entries | Dust changelog', + asOf: '2026-09-15', }, ], }, @@ -530,7 +551,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://blog.dust.tt/introducing-multi-tool-assistants/', label: 'Introducing: multi-tool agents | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -553,7 +574,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/skills', label: 'Skills | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -568,7 +589,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/dust-in-teams', label: 'Dust in Teams | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -584,7 +605,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://community.dust.tt/x/03help/6ku3a37chfyo/how-to-access-documents-from-the-dust-agent-a-guid', label: 'How to Access Documents from the Dust Agent | Dust Community', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -599,7 +620,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/image-generation', label: 'Image Generation | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -622,7 +643,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/tools', label: 'Tools | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -630,16 +651,22 @@ export const dustProfile: CompetitorProfile = { integrations: { integrationCount: { value: - '50+ native connections (Slack, Notion, Google Drive, Confluence, GitHub, Salesforce, HubSpot, Zendesk, and more), plus MCP servers for further extensibility', + "20+ native data-source connectors (Slack, Notion, Google Drive, Confluence, GitHub, Salesforce, and more) plus dozens of further MCP-based tool integrations, per Dust's own current pricing page; earlier Dust marketing materials cited a higher '50+ business tools' figure, and some third-party listings cite still-higher figures (100+) that likely include MCP-based and community integrations beyond the core native-connector count", detail: - "Dust's enterprise page states 'native integrations to 50+ business tools'; some third-party listings cite higher figures (100+) that likely include MCP-based and community integrations beyond the core native connector count.", - shortValue: '50+ native connections per Dust', + "Dust's pricing page states 'Connectors to 20+ data sources' and 'Connect Slack, Notion, GitHub, Drive + 20 more — or any tool via MCP.' Dust's enterprise page no longer states a specific integration count (it lists example tools — Notion, Slack, Salesforce, GitHub — without a number); some third-party listings cite higher figures (100+) that likely include MCP-based and community integrations beyond the core native connector count.", + shortValue: + "20+ native connectors per Dust's current pricing page (was previously cited as 50+)", confidence: 'estimated', sources: [ + { + url: 'https://dust.tt/home/pricing', + label: 'Dust Pricing', + asOf: '2026-09-15', + }, { url: 'https://dust.tt/home/enterprise', label: 'Dust for Enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -655,7 +682,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/triggers', label: 'Triggers | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -670,7 +697,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/val-town', label: 'Val Town | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -685,17 +712,17 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/user-documentation/admins/tools-management/computer-admin-setup.md', label: 'Computer Admin Setup | Dust Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/computer', label: 'Computer | Dust Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/tools', label: 'Tools | Dust Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -710,27 +737,42 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/client-side-mcp-server', label: 'Client Side MCP Server (Preview) | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/reference/developer-platform-overview', label: 'Developer platform | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, extensibilitySdk: { value: - 'MIT-licensed core repository (dust-tt/dust) on GitHub, a documented Developer Platform/API, an official GitHub Action for GitOps config sync, and community-built MCP bridges', + 'MIT-licensed core repository (dust-tt/dust) on GitHub, a documented Developer Platform/API, a first-party JavaScript client SDK (@dust-tt/client, distributed as an npm package), a first-party Dust CLI (@dust-tt/dust-cli), an official GitHub Action for GitOps config sync, and community-built MCP bridges', detail: - 'There is no separate first-party multi-language client SDK beyond the API/GitHub Action; extensibility instead centers on the open MIT-licensed codebase, the public API, and the MCP ecosystem, including third-party community projects (e.g. a community-built dust-mcp-server bridge).', - shortValue: 'Open MIT repo, API, GitHub Action, MCP ecosystem', + "Dust's Developer Platform docs name the Dust API, the JavaScript SDK, and the Dust CLI as the three ways to build on Dust programmatically. The JavaScript SDK is a thin client wrapper around the REST API rather than a full multi-language SDK family (no first-party Python/Go/etc. client is documented), so extensibility beyond JS still leans on the open MIT-licensed codebase, the public API, and the MCP ecosystem, including third-party community projects (e.g. a community-built dust-mcp-server bridge).", + shortValue: 'Open MIT repo, API, first-party JS SDK + CLI, GitHub Action, MCP ecosystem', confidence: 'estimated', sources: [ { url: 'https://github.com/dust-tt/dust', label: 'dust-tt/dust (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/reference/developer-platform-overview', + label: 'Developer platform | Dust Docs', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/docs/developer-platform/overview/javascript-sdk', + label: 'JavaScript SDK | Dust Docs', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/docs/developer-platform/dust-cli/dust-cli', + label: 'Dust CLI | Dust Docs', + asOf: '2026-09-15', }, ], }, @@ -745,7 +787,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://blog.dust.tt/mcp-emerging-enterprise-ai-os-layer/', label: 'MCP and the emerging enterprise AI OS layer | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -761,7 +803,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://dust.tt/home/pricing', label: 'Dust Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -775,27 +817,27 @@ export const dustProfile: CompetitorProfile = { { url: 'https://dust.tt/home/pricing', label: 'Dust Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, freeTier: { value: - 'Yes: a free Business tier for new workspaces, capped at 5 users, 3 connectors, and 5 Spaces, no credit card required', + 'Yes: a free Business tier for new workspaces, capped at 5 users, 3 connectors, 5 Spaces, and a one-time lifetime allocation of 500 credits (not renewed monthly, unlike paid seats), no credit card required', detail: - 'This free tier is what a new workspace gets by default without a paid subscription. It is distinct from what happens when an existing paid workspace downgrades: canceling removes all users except the earliest-assigned admin, deletes existing connections, and deletes data sources over 50MB combined after a 7-day warning period, while original source data in the connected provider itself is untouched.', - shortValue: 'Free for new workspaces: up to 5 users, 3 connectors, 5 Spaces', + "This free tier is what a new workspace gets by default without a paid subscription. It is distinct from what happens when an existing paid workspace downgrades: canceling removes all users except the earliest-assigned admin, deletes existing connections, and deletes data sources over 50MB combined after a 7-day warning period, while original source data in the connected provider itself is untouched. Dust's pricing page additionally caps the Free seat type at 500 credits total for the lifetime of the seat, in contrast to Pro (8,000 credits/month) and Max (40,000 credits/month), which reset every billing period — making the free tier primarily suited to brief trial use rather than sustained usage.", + shortValue: 'Free tier: 5 users, 3 connectors, 5 Spaces, 500 lifetime credits', confidence: 'verified', sources: [ { url: 'https://dust.tt/home/pricing', label: 'Dust Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/subscriptions', label: 'Subscriptions & Payments | Dust Docs', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -812,26 +854,26 @@ export const dustProfile: CompetitorProfile = { security: { compliance: { value: - "SOC 2 Type II certified, with audit readiness achieved with Vanta in three weeks and the report downloadable through Dust's Trust Center; also GDPR compliant and HIPAA-capable; no ISO 27001, PCI, or FedRAMP", + "SOC 2 Type II certified, with 80% SOC 2 Type II audit readiness reached using Vanta's automation in three weeks (per Vanta's published case study) and the completed SOC 2 Type II report downloadable through Dust's Trust Center; also GDPR compliant and HIPAA-capable; no ISO 27001, PCI, or FedRAMP", detail: - "Dust's own security page states SOC 2 Type II certification; a Vanta customer case study describes Dust achieving SOC 2 Type II audit readiness in three weeks using Vanta's automation, reducing compliance workload by roughly 50%. The report is downloadable via Dust's Trust Center. Dust's security page and enterprise materials additionally state GDPR compliance and HIPAA-compliance capability alongside SOC 2 Type II. No source confirms ISO 27001, PCI-DSS, or FedRAMP.", + "Dust's own security page states SOC 2 Type II certification; a Vanta customer case study quotes Dust's CEO stating Vanta got the company to 80% SOC 2 Type II audit readiness in three weeks, and separately reports a 50% reduction in compliance workload. The full, completed SOC 2 Type II report is listed as a downloadable resource on Dust's Trust Center (trust.dust.com). Dust's security page and enterprise materials additionally state GDPR compliance and HIPAA-compliance capability alongside SOC 2 Type II. No source confirms ISO 27001, PCI-DSS, or FedRAMP.", shortValue: 'SOC 2 Type II, GDPR, HIPAA-capable; no ISO/PCI', confidence: 'estimated', sources: [ { url: 'https://www.vanta.com/customers/dust', label: 'With Vanta, Dust achieved SOC 2 Type II audit readiness in three weeks', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://trust.dust.com/', label: 'Dust Trust Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://dust.tt/home/security', label: 'Dust Security', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -845,37 +887,49 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/changelog#-eu-data-hosting-option-available', label: 'EU data hosting option available | Dust changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, rbac: { value: - 'Yes: three workspace roles (Member, Builder, Admin) plus per-Space access control, where only members of the Spaces an agent uses can see and use that agent', + "Yes: three workspace roles — Admin, Manager, Member — plus per-Space access control, where only members of the Spaces an agent uses can see and use that agent. (Dust is in transition from an earlier Member/Builder/Admin model: the legacy Builder role is being replaced by separately grantable permissions for creating and publishing agents/skills, with existing Builders migrated into a transitional 'Builders' group.)", detail: - 'Members can chat with and build agents; Builders additionally manage Folders and use the API; Admins manage workspace settings, connections, and member roles. Spaces (open or restricted) gate which members can see specific data sources, tools, and the agents built on them.', - shortValue: 'Member/Builder/Admin roles plus per-Space access gating', + "Members use Dust according to their seat, group memberships, and granted permissions; Managers are delegated administrators who can invite/remove members, assign Manager/Member roles, and grant agent/skill creation and publishing permissions to groups; Admins have full administrative access including billing, security, and provisioning. Permissions (create/publish agents, create skills, view audit logs, manage billing, manage security/provisioning) are granted to groups rather than roles directly, and are additive across a person's group memberships. Spaces (open or restricted) separately gate which members can see specific data sources, tools, and the agents built on them.", + shortValue: + 'Admin/Manager/Member roles (Builder role being phased out) plus per-Space access gating', confidence: 'verified', sources: [ { url: 'https://docs.dust.tt/docs/access-controls-and-permissions', label: 'Access Controls and Permissions | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.dust.tt/docs/user-documentation/admins/admin-governance/workspace-governance-roles-groups-and-permissions.md', + label: 'Workspace Governance (Roles, Groups & Permissions) | Dust Docs', + asOf: '2026-09-15', }, ], }, auditLogging: { value: - 'Yes: audit logs available on the Enterprise plan, admin-only, with CSV export and continuous streaming to a SIEM (Datadog, Splunk, AWS S3, GCP GCS, custom HTTPS endpoint); no retention period is documented', + "Yes: audit logs available on the Enterprise plan, admin-only, with CSV export and continuous streaming to a SIEM (Datadog, Splunk, AWS S3, GCP GCS, custom HTTPS endpoint); a 365-day retention period is stated on Dust's Enterprise marketing page, though not repeated in the Audit Logs documentation itself", detail: - "Dust's Audit Logs docs confirm the feature is Enterprise-only, accessible to workspace admins under Admin > People & Security > Audit Logs, with full-text search, time-range filtering, manual CSV export, and continuous streaming to external SIEM destinations. No page specifies how many days of audit history are retained.", - shortValue: 'Enterprise-tier audit logs with SIEM export; retention period not documented', + "Dust's Audit Logs docs confirm the feature is Enterprise-only, accessible to workspace admins under Admin > IT & Security > Audit Logs, with full-text search, time-range filtering, manual CSV export, and continuous streaming to external SIEM destinations (Datadog, Splunk, AWS S3, GCP GCS, custom HTTPS endpoint). Dust's Enterprise marketing page separately states a 365-day retention period for audit logs, though the audit-logs documentation itself does not repeat that figure.", + shortValue: + "Enterprise-tier audit logs with SIEM export; 365-day retention per Dust's Enterprise page", confidence: 'estimated', sources: [ { url: 'https://docs.dust.tt/docs/audit-logs', label: 'Audit Logs | Dust Docs', - asOf: '2026-07-04', + asOf: '2026-09-15', + }, + { + url: 'https://dust.tt/home/enterprise', + label: 'Dust for Enterprise', + asOf: '2026-09-15', }, ], }, @@ -898,7 +952,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/access-controls-and-permissions', label: 'Access Controls and Permissions | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -920,7 +974,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://dust.tt/home/enterprise', label: 'Dust for Enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -942,7 +996,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://dust.tt/home/enterprise', label: 'Dust for Enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -975,38 +1029,38 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/user-documentation/admins/admin-governance/workspace-governance-roles-groups-and-permissions.md', label: 'Workspace Governance (Roles, Groups & Permissions) | Dust Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/user-documentation/admins/admin-governance/single-sign-on-sso/saml-sso.md', label: 'SAML SSO | Dust Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, thirdPartyVetting: { value: - 'Partial: native data connections (11 fully-managed sources including Google Drive, Notion, Confluence, GitHub, Salesforce, Microsoft, Snowflake, BigQuery, Zendesk, Gong, and Intercom) are first-party and built/maintained by the Dust team; Slack and dozens of other business tools (Airtable, Asana, HubSpot, Jira, Salesloft, and more) are documented as separate MCP-based Tools rather than native Connections, and agent tools can also be extended with any external MCP server by pasting its public URL, with no Dust-led vetting or review of that server', + "Partial: native data connections (12 fully-managed sources including Google Drive, Notion, Confluence, Intercom, GitHub, Microsoft, Snowflake, BigQuery, Zendesk, Gong, Slack, and Salesforce) are first-party, admin-managed connections built/maintained by the Dust team for search/RAG; Slack separately also has an MCP-based 'Slack tools' capability for posting messages and searching in real time, and dozens of other business tools (Airtable, Asana, HubSpot, Jira, Salesloft, and more) are documented as MCP-based Tools rather than native Connections, and agent tools can also be extended with any external MCP server by pasting its public URL, with no Dust-led vetting or review of that server", detail: - "Docs list 11 fully-managed native Connections under Connections Management, while Dust's own Slack integration docs describe it as 'Slack MCP tools' added by selecting Slack 'from the available MCP servers,' distinct from that native Connections list. Dust's Tools catalog documents dozens of further business-tool integrations (Airtable, Asana, HubSpot, Jira, Salesloft, and more) alongside the ability to add any external MCP server by pasting its public URL, with workspace admins responsible for choosing and authenticating it. No formal Dust review process is described for pasted third-party MCP server URLs, and no publicly documented security incident involving a malicious or compromised third-party MCP server on Dust was found.", + "Dust's Connections page lists 12 fully-managed native Connections (Google Drive, Notion, Confluence, Intercom, GitHub, Microsoft, Snowflake, BigQuery, Zendesk, Gong, Slack, and Salesforce), including Slack as a native, admin-managed data-source connection for search/RAG. Separately, Dust's Slack integration docs describe 'Slack tools' — an MCP-based capability added by selecting Slack 'from the available MCP servers' and authenticated with the user's personal credentials — for posting messages and searching in real time. Dust's Tools catalog documents dozens of further business-tool integrations (Airtable, Asana, HubSpot, Jira, Salesloft, and more) alongside the ability to add any external MCP server by pasting its public URL, with workspace admins responsible for choosing and authenticating it. No formal Dust review process is described for pasted third-party MCP server URLs, and no publicly documented security incident involving a malicious or compromised third-party MCP server on Dust was found.", shortValue: - '11 first-party Connections; Slack + dozens more via MCP-based Tools; open bring-your-own-URL MCP', + '12 first-party Connections incl. Slack; Slack also has MCP-based Tools; open bring-your-own MCP', confidence: 'verified', sources: [ { url: 'https://docs.dust.tt/docs/connections', label: 'Connections | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/slack-mcp', label: 'Slack tools | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/tools', label: 'Tools | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1024,7 +1078,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/workspace-analytics', label: 'Workspace Analytics | Dust Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1063,7 +1117,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/triggers', label: 'Triggers | Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1094,12 +1148,12 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/docs/triggers', label: 'Triggers | Dust Docs', - asOf: '2026-07-04', + asOf: '2026-09-15', }, { url: 'https://docs.dust.tt/docs/scheduling-your-agent-beta', label: 'Schedules | Dust Docs', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -1116,7 +1170,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://docs.dust.tt/', label: 'Dust Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1138,16 +1192,17 @@ export const dustProfile: CompetitorProfile = { { url: 'https://community.dust.tt/x/03help/vgwnzcrq96s6/using-the-table-queries-tool-for-database-files', label: 'Using the Table Queries Tool for Database Files | Dust Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, companyMaturity: { value: - 'Dust, Inc. Founded 2022 in Paris by two former Stripe employees (one also ex-OpenAI). Raised a $40M Series B in May 2026 (co-led by Sequoia and Abstract, with Datadog and Snowflake participating), total funding over $60M. Reports 300,000+ agents deployed across 3,000+ organizations, 70% weekly active usage, and zero churn as of the raise', + "Dust, Inc. Founded 2022 in Paris by two former Stripe employees (one also ex-OpenAI). Raised a $40M Series B in May 2026 with participation from Abstract, Sequoia, Snowflake Ventures, and Datadog (per Dust's own announcement, which does not specify a lead investor), bringing total funding to over $60M. Dust's own blog reports 300,000+ agents deployed across 3,000+ organizations. Additional figures reported in press coverage of the raise (70% weekly active usage, zero churn, 240% net revenue retention) could not be independently verified — the relevant Sifted article is paywalled", detail: - "Customers named in Dust's own materials include Datadog, 1Password, and Qonto (Qonto reports 50+ specialized agents and 50,000+ hours saved annually). As a 2022-founded, venture-backed private company, it carries materially more switching risk than a large, publicly traded incumbent vendor, though it has real enterprise traction and revenue-retention metrics (240% net revenue retention reported at the raise).", - shortValue: 'Founded 2022, Paris; $60M+ raised; 3,000+ orgs, 300,000+ agents', + "Customers named in Dust's own materials include Datadog, 1Password, and Qonto (Qonto reports 50+ specialized agents and 50,000+ hours saved annually). As a 2022-founded, venture-backed private company, it carries materially more switching risk than a large, publicly traded incumbent vendor. Press coverage of the raise additionally reported strong usage and revenue-retention metrics (70% weekly active usage, zero churn, 240% net revenue retention), but those figures could not be independently verified: the Sifted article reporting them is paywalled and its body text is not accessible.", + shortValue: + 'Founded 2022, Paris; $60M+ raised; 3,000+ orgs, 300,000+ agents (WAU/NRR unverified)', confidence: 'verified', sources: [ { @@ -1158,7 +1213,7 @@ export const dustProfile: CompetitorProfile = { { url: 'https://dust.tt/blog/series-b-multiplayer-ai', label: 'Dust raises $40M Series B to scale multiplayer AI | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1173,12 +1228,12 @@ export const dustProfile: CompetitorProfile = { { url: 'https://dust.tt/academy', label: 'Dust Academy', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://dust.tt/blog/dust-academy', label: 'Introducing the Dust Academy | Dust Blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/flowise.ts b/apps/sim/lib/compare/data/competitors/flowise.ts index 5c938f7e7a1..5d4e112b99a 100644 --- a/apps/sim/lib/compare/data/competitors/flowise.ts +++ b/apps/sim/lib/compare/data/competitors/flowise.ts @@ -25,7 +25,7 @@ export const flowiseProfile: CompetitorProfile = { source: { url: 'https://docs.flowiseai.com/using-flowise/document-stores', label: 'Flowise Docs: Document Stores', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -37,19 +37,19 @@ export const flowiseProfile: CompetitorProfile = { source: { url: 'https://docs.flowiseai.com/using-flowise/evaluations', label: 'Flowise Docs: Evaluations', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { title: 'Larger existing open-source community, on the same Apache 2.0 license as Sim', description: - 'Both Flowise and Sim are Apache License 2.0 and self-hostable, so the license itself is not a differentiator. Where Flowise stands out is community scale: its GitHub repo has roughly 54,000 stars and an active Discord community built up since 2023.', + 'Both Flowise and Sim are Apache License 2.0 and self-hostable, so the license itself is not a differentiator. Where Flowise stands out is community scale: its GitHub repo has roughly 55,000 stars, built up since 2023. As of August 31, 2026, however, Flowise wound down operations, and its official core team no longer maintains a presence in GitHub or Discord (the repository is archived); the remaining community is self-organized rather than vendor-supported.', shortDescription: - 'Same Apache 2.0 license as Sim, but a larger existing community: ~54k GitHub stars, active Discord.', + 'Larger existing community (~55k stars), but official vendor support ended August 2026.', source: { url: 'https://github.com/FlowiseAI/Flowise', - label: 'GitHub: FlowiseAI/Flowise', - asOf: '2026-07-02', + label: 'GitHub: FlowiseAI/Flowise (archived, wound down)', + asOf: '2026-09-15', }, }, ], @@ -63,7 +63,7 @@ export const flowiseProfile: CompetitorProfile = { source: { url: 'https://n8n.io/reports/2026-ai-agent-development-tools/#vendors', label: 'n8n: 2026 AI Agent Development Tools report', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -74,7 +74,7 @@ export const flowiseProfile: CompetitorProfile = { source: { url: 'https://github.com/FlowiseAI/Flowise/issues/2661', label: 'GitHub Issue #2661: Multi User Support (closed, not planned)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, ], @@ -90,7 +90,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/integrations/utilities/custom-js-function', label: 'Flowise Docs: Custom JS Function', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -103,7 +103,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/integrations/utilities/custom-js-function', label: 'Flowise Docs: Custom JS Function', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -116,7 +116,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://github.com/FlowiseAI/Flowise/blob/main/LICENSE.md', label: 'GitHub: Flowise LICENSE.md', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -129,12 +129,12 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/flowise-pricing', label: 'Lindy: Flowise Pricing, Features, and Alternatives for 2026', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/using-flowise/workspaces', label: 'Flowise Docs: Workspaces', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -147,7 +147,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://deepwiki.com/FlowiseAI/Flowise/11.1-marketplace-and-template-flows', label: 'DeepWiki: Marketplace & Template Flows', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -160,17 +160,17 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://github.com/FlowiseAI/Flowise/blob/main/LICENSE.md', label: 'GitHub: Flowise LICENSE.md', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/using-flowise/workspaces', label: 'Flowise Docs: Workspaces', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/configuration/sso', label: 'Flowise Docs: SSO', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -183,14 +183,25 @@ export const flowiseProfile: CompetitorProfile = { }, versionControlDepth: { value: - 'Yes: Flowise automatically saves a version snapshot every time you save a ChatFlow or Assistant, with a history view to restore prior versions. This is snapshot-and-restore depth, not full diff or branching.', - shortValue: 'Snapshot history with restore, no diff/branching shown', + "Not shipped: a pull request (FlowiseAI/Flowise #5024) proposed automatic version snapshotting for ChatFlows and Assistants — saving a snapshot on every save, with a history view and one-click restore — but it was never merged. It has sat open since August 2025, and Flowise's own August 2026 wind-down (code freeze July 29, 2026; repository archived August 13, 2026) means it now never will be. No FlowHistory entity or history UI exists anywhere in the shipped FlowiseAI/Flowise codebase. Flowise's only real durability/version mechanism is UpsertHistory for vector-store upsert runs, which is unrelated to flow/assistant editing history.", + shortValue: 'No: proposed in an unmerged 2025 PR, never shipped', confidence: 'verified', sources: [ { url: 'https://github.com/FlowiseAI/Flowise/pull/5024', - label: 'GitHub PR #5024: Implement version control system for ChatFlows and Assistants', - asOf: '2026-07-02', + label: + 'GitHub PR #5024: Implement version control system for ChatFlows and Assistants (open, unmerged)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/tree/main/packages/server/src/database/entities', + label: 'GitHub: packages/server/src/database/entities (no FlowHistory entity present)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/discussions/6727', + label: 'GitHub Discussion #6727: The Future of Flowise (wind-down announcement)', + asOf: '2026-09-15', }, ], }, @@ -205,7 +216,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/workspaces', label: 'Flowise Docs: Workspaces', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -239,7 +250,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/agentflowv2', label: 'Flowise Docs: Agentflow V2 (Execute Flow node)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -254,12 +265,12 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/agentflowv2', label: 'Flowise Docs: Agentflow V2 (Execute Flow node)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/integrations/langchain/tools/custom-tool', label: 'Flowise Docs: Custom Tool', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -274,12 +285,12 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/integrations/langchain/llms', label: 'Flowise Docs: LLMs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/integrations/langchain/chat-models', label: 'Flowise Docs: Chat Models (incl. ChatAnthropic)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -292,7 +303,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/agentflowv2', label: 'Flowise Docs: Agentflow V2', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -305,7 +316,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/integrations/utilities/custom-js-function', label: 'Flowise Docs: Custom JS Function', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -320,12 +331,12 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/document-stores', label: 'Flowise Docs: Document Stores', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://n8n.io/reports/2026-ai-agent-development-tools/#vendors', label: 'n8n: 2026 AI Agent Development Tools report', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -338,20 +349,20 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/tutorials/tools-and-mcp', label: 'Flowise Docs: Tools & MCP', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, evaluationGuardrails: { value: - 'Yes: Flowise has a built-in Evaluations feature that runs datasets through chatflows/agentflows and scores outputs with string-match, numeric, or LLM-as-judge evaluators, reporting pass/fail rate, average tokens consumed, and latency. There is no separate, dedicated "guardrail validation" block beyond this.', - shortValue: 'Yes, built-in dataset-based evaluation with LLM-judge scoring', + 'Yes, on Cloud and Enterprise plans only: Flowise has a built-in Evaluations feature that runs datasets through chatflows/agentflows and scores outputs with string-match, numeric, or LLM-as-judge evaluators, reporting pass/fail rate, average tokens consumed, and latency. This is restricted to the paid Cloud and Enterprise tiers and is not available in the open-source self-hosted Community Edition. There is no separate, dedicated "guardrail validation" block beyond this.', + shortValue: 'Yes, Cloud/Enterprise only: built-in evaluation with LLM-judge scoring', confidence: 'verified', sources: [ { url: 'https://docs.flowiseai.com/using-flowise/evaluations', label: 'Flowise Docs: Evaluations', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -364,22 +375,34 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/tutorials/human-in-the-loop', label: 'Flowise Docs: Human In The Loop', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, generativeMedia: { value: - 'Partial: Flowise supports speech-to-text nodes and multi-modal image inputs. Image and audio generation can be wired in via custom tools calling providers like Replicate (Stable Diffusion) or ElevenLabs, but the standard node library has no dedicated, built-in image, video, or text-to-speech generation node.', + 'Partial: Flowise supports speech-to-text nodes, multi-modal image inputs, and a built-in per-chatflow Text-to-Speech configuration (with provider selection and a dedicated generate/voices/abort API) — so audio output generation is a native capability, not just a custom-tool workaround. Image and video generation, however, are not first-class node types; they can only be wired in via custom tools calling providers like Replicate (Stable Diffusion) or similar, with no dedicated, built-in image or video generation node in the standard library.', detail: - 'Community GitHub issues show text-to-speech and native image generation as requested but not shipped as first-class nodes.', - shortValue: 'Partial: STT built in, image/TTS via custom tools only', - confidence: 'estimated', + 'Community GitHub issues (e.g. #2385) originally requested text-to-speech as a feature; Flowise has since shipped a native per-chatflow Text-to-Speech configuration with provider selection and a dedicated /generate, /voices, and /abort API. Native image and video generation remain requested but not shipped as first-class node types.', + shortValue: 'Partial: native STT/TTS built in; image/video need custom tools', + confidence: 'verified', sources: [ { url: 'https://github.com/FlowiseAI/Flowise/issues/2385', label: 'GitHub Issue #2385: Text To Speech', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/controllers/text-to-speech/index.ts', + label: + 'GitHub: packages/server/src/controllers/text-to-speech/index.ts (native TTS generation)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/routes/text-to-speech/index.ts', + label: + 'GitHub: packages/server/src/routes/text-to-speech/index.ts (generate/voices/abort API)', + asOf: '2026-09-15', }, ], }, @@ -392,7 +415,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/tutorials/tools-and-mcp', label: 'Flowise Docs: Tools & MCP', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -421,7 +444,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/embed', label: 'Flowise Docs: Embed', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -434,12 +457,12 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://n8n.io/reports/2026-ai-agent-development-tools/#vendors', label: 'n8n: 2026 AI Agent Development Tools report', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { - url: 'https://docs.flowiseai.com/using-flowise/upsertion', - label: 'Flowise Docs: Upsertion', - asOf: '2026-07-02', + url: 'https://docs.flowiseai.com/using-flowise/document-stores', + label: 'Flowise Docs: Document Stores (per-chunk preview/edit)', + asOf: '2026-09-15', }, ], }, @@ -452,18 +475,18 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://github.com/FlowiseAI/Flowise/issues/4673', label: 'Flowise GitHub: "Not working parallel Node in AgentFlow 2" (#4673)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/FlowiseAI/Flowise/issues/4710', label: 'Flowise GitHub: "Parallel Node Execution is causing State Contamination" (#4710)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/using-flowise/agentflowv2', label: 'Flowise Docs: Agentflow V2', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -476,7 +499,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://github.com/FlowiseAI/Flowise/issues/4283', label: 'Flowise GitHub: "Support the Google A2A (Agent2Agent) Protocol" (#4283, open)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -489,7 +512,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/agentflowv2', label: 'Flowise Docs: Agentflow V2 (Iteration and Loop nodes)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -504,20 +527,30 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/integrations', label: 'Flowise Docs: Integrations', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, triggerTypes: { value: - 'Flowise flows are triggered via the chat widget or public URL, direct REST API prediction calls (/api/v1/prediction/{chatflowId}), and Custom MCP/tool invocations. There is no dedicated cron/schedule trigger or broad library of app-specific event triggers.', - shortValue: 'Chat, API/webhook-style prediction calls; no schedule trigger found', + 'Flowise flows are triggered via the chat widget or public URL, direct REST API prediction calls (/api/v1/prediction/{chatflowId}), and — for Agentflows — a native per-flow cron schedule (a standard 5- or 6-field cron expression plus an IANA timezone, toggled on/off per flow, with a trigger-log history), run in-process via node-cron or, in queue mode, via BullMQ repeatable jobs. This scheduler is not documented on the public docs site. There is otherwise no broad library of app-specific event triggers.', + shortValue: 'Chat, API calls, plus an undocumented native cron scheduler', confidence: 'estimated', sources: [ { url: 'https://agentsapis.com/flowise-api/', label: 'Flowise API: Complete Developer Guide', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/database/entities/ScheduleRecord.ts', + label: 'GitHub: ScheduleRecord entity (native per-flow cron trigger)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/schedule/ScheduleBeat.ts', + label: 'GitHub: ScheduleBeat (node-cron / BullMQ scheduling engine)', + asOf: '2026-09-15', }, ], }, @@ -530,7 +563,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/integrations/langchain/tools/custom-tool', label: 'Flowise Docs: Custom Tool (JS function support, built-in/external modules)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -546,23 +579,23 @@ export const flowiseProfile: CompetitorProfile = { url: 'https://docs.flowiseai.com/configuration/environment-variables', label: 'Flowise Docs: Environment Variables (TOOL_FUNCTION_BUILTIN_DEP, TOOL_FUNCTION_EXTERNAL_DEP, ALLOW_BUILTIN_DEP)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/integrations/langchain/tools/custom-tool', label: 'Flowise Docs: Custom Tool (adding external npm dependencies)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://raw.githubusercontent.com/FlowiseAI/Flowise/main/packages/server/.env.example', label: 'GitHub: Flowise packages/server/.env.example (shipped dependency allowlists)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/components/src/utils.ts', label: 'GitHub: packages/components/src/utils.ts (defaultAllowBuiltInDep, defaultAllowExternalDependencies, additive allowlists)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -575,7 +608,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://agentsapis.com/flowise-api/', label: 'Flowise API: Complete Developer Guide', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -588,27 +621,39 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.npmjs.com/package/flowise-embed', label: 'npm: flowise-embed', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/contributing/building-node', label: 'Flowise Docs: Building Node', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, mcpPublishing: { value: - "No: Flowise's documentation covers only consuming external MCP servers as an MCP client. It has no capability for publishing a deployed Flowise flow itself as a callable MCP server for other AI tools.", + "Partially, and not documented publicly: Flowise's server code ships a native MCP Server feature — each chatflow/agentflow has its own MCP Server configuration that can be enabled (generating an access token), updated (tool name/description/status), disabled, and token-rotated via /api/v1/mcp-server/:id and /api/v1/mcp-server/:id/refresh, gated by the same chatflows:config/agentflows:config permission as other flow settings. A separate authenticated /api/v1/mcp-endpoint/:chatflowId route implements the actual MCP Streamable HTTP protocol (JSON-RPC initialize/tools/list/tools/call), so an external MCP client — including desktop clients like Claude Desktop or Cursor — can call the published flow as a tool using the generated bearer token. However, this capability is absent from docs.flowiseai.com's Tools & MCP page and other public documentation, so most users would not discover it there; third-party community wrapper packages (e.g. mcp-flowise) remain the only documented way to expose Flowise chatflows via MCP.", detail: - 'Third-party community wrapper packages (e.g. mcp-flowise) expose Flowise chatflows via MCP externally, but this is not native.', - shortValue: 'No, cannot publish a flow as an MCP server', + "The native MCP Server capability is not documented on docs.flowiseai.com's Tools & MCP page or anywhere else in Flowise's public docs, so most users would not discover it there. Third-party community wrapper packages (e.g. mcp-flowise) remain the only publicly documented way to expose Flowise chatflows via MCP, even though Flowise's own server now ships this capability natively.", + shortValue: 'Partial: native MCP-server publishing ships, but undocumented', confidence: 'verified', sources: [ { url: 'https://docs.flowiseai.com/tutorials/tools-and-mcp', label: 'Flowise Docs: Tools & MCP', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/routes/mcp-server/index.ts', + label: + 'GitHub: packages/server/src/routes/mcp-server/index.ts (native MCP Server config API)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/routes/mcp-endpoint/index.ts', + label: + 'GitHub: packages/server/src/routes/mcp-endpoint/index.ts (MCP Streamable HTTP protocol endpoint)', + asOf: '2026-09-15', }, ], }, @@ -623,7 +668,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/flowise-pricing', label: 'Lindy: Flowise Pricing, Features, and Alternatives for 2026', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -638,7 +683,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/flowise-pricing', label: 'Lindy: Flowise Pricing, Features, and Alternatives for 2026', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -651,7 +696,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/flowise-pricing', label: 'Lindy: Flowise Pricing, Features, and Alternatives for 2026', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -665,7 +710,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/configuration/environment-variables', label: 'Flowise Docs: Environment Variables', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -678,7 +723,13 @@ export const flowiseProfile: CompetitorProfile = { 'The same third-party source also claims FedRAMP and PCI compliance for a small startup, an atypical combination not corroborated on flowiseai.com.', shortValue: 'Unknown, no official certifications published', confidence: 'unknown', - sources: [], + sources: [ + { + url: 'https://security-profiles.nudgesecurity.com/app/flowiseai-com', + label: 'Nudge Security: Flowise security profile', + asOf: '2026-09-15', + }, + ], }, dataResidency: { value: @@ -689,7 +740,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/flowise-pricing', label: 'Lindy: Flowise Pricing, Features, and Alternatives for 2026', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -702,7 +753,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/workspaces', label: 'Flowise Docs: Workspaces', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -715,7 +766,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/workspaces', label: 'Flowise Docs: Workspaces', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -735,7 +786,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/workspaces', label: 'Flowise Docs: Workspaces', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -748,7 +799,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://github.com/FlowiseAI/Flowise/discussions/626', label: 'GitHub Discussion #626: remove the Powered by flowise watermark', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -776,7 +827,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/configuration/sso', label: 'Flowise Docs: SSO', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -798,12 +849,12 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/configuration/authorization/app-level', label: 'Flowise Docs: Application authorization (JWT expiry and session variables)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://raw.githubusercontent.com/FlowiseAI/Flowise/main/packages/server/.env.example', label: 'GitHub: Flowise packages/server/.env.example (shipped JWT expiry defaults)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -811,7 +862,7 @@ export const flowiseProfile: CompetitorProfile = { value: "Yes: Flowise's nodes (LLMs, tools, vector stores, document loaders) live in the packages/components/nodes folder of the core FlowiseAI/Flowise monorepo. New nodes are contributed via GitHub pull request and reviewed/merged by the Flowise team before shipping in an official release, rather than published independently by third parties into an open, unreviewed marketplace. The separate Marketplace feature distributes JSON chatflow/agentflow templates, not installable executable code.", detail: - "That PR-review process has not stopped a critical incident in vetted, first-party code: CVE-2025-59528 (CVSS 10.0) was an unauthenticated remote code execution flaw in the official CustomMCP node, where user-supplied mcpServerConfig input was passed into a JavaScript Function() constructor. Patched in 3.0.6, but VulnCheck observed in-the-wild exploitation starting April 2026 against thousands of still-exposed instances. By contrast, Sim documents its own thirdPartyVetting fact as every one of its 302 blocks being first-party authored and code-reviewed with no public marketplace for third-party executable code either, so the two products share the same no-open-marketplace posture; the difference is that Flowise's own review pipeline has already shipped one CVSS-10 RCE into a first-party node, which is the concrete cost of that model rather than of an unreviewed community ecosystem.", + "That PR-review process has not stopped a critical incident in vetted, first-party code: CVE-2025-59528 (CVSS 10.0) was an unauthenticated remote code execution flaw in the official CustomMCP node, where user-supplied mcpServerConfig input was passed into a JavaScript Function() constructor. Patched in 3.0.6, but VulnCheck observed in-the-wild exploitation starting April 2026 against thousands of still-exposed instances. By contrast, Sim documents its own thirdPartyVetting fact as every one of its 356 blocks being first-party authored and code-reviewed with no public marketplace for third-party executable code either, so the two products share the same no-open-marketplace posture; the difference is that Flowise's own review pipeline has already shipped one CVSS-10 RCE into a first-party node, which is the concrete cost of that model rather than of an unreviewed community ecosystem.", shortValue: 'Yes, PR-reviewed into the core repo, but that pipeline already shipped a CVSS-10 RCE', confidence: 'verified', @@ -819,18 +870,24 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/contributing/building-node', label: 'Flowise Docs: Building Node', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.flowiseai.com/contributing', + label: + 'Flowise Docs: Contributing (PR automatically notifies/assigns the Flowise team)', + asOf: '2026-09-15', }, { url: 'https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-3gcm-f6qx-ff7p', label: 'GitHub Security Advisory GHSA-3gcm-f6qx-ff7p (CVE-2025-59528)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.csoonline.com/article/4155680/hackers-exploit-a-critical-flowise-flaw-affecting-thousands-of-ai-workflows.html', label: 'CSO Online: Hackers exploit a critical Flowise flaw affecting thousands of AI workflows', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -846,7 +903,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://langfuse.com/integrations/no-code/flowise', label: 'Langfuse: Observability and Tracing for Flowise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -873,7 +930,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://langfuse.com/integrations/no-code/flowise', label: 'Langfuse: Observability and Tracing for Flowise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -886,7 +943,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/configuration/running-flowise-using-queue', label: 'Flowise Docs: Running Flowise using Queue', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -906,27 +963,37 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://docs.flowiseai.com/using-flowise/agentflowv2', label: 'Flowise Docs: Agentflow V2', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, unattendedExecution: { value: - 'Yes, for the triggers Flowise has: a chat message, a REST API prediction call, or an MCP tool invocation all execute entirely on the Flowise server (self-hosted or Flowise Cloud), with no dependency on a client device staying open, awake, or connected. Flowise has no dedicated cron/schedule trigger of its own, so a genuinely unattended, time-based run has to come from an external scheduler (e.g. a cron job or another system calling the prediction API) rather than a built-in scheduling engine.', + "Yes, for the triggers Flowise has: a chat message, a REST API prediction call, or an MCP tool invocation all execute entirely on the Flowise server (self-hosted or Flowise Cloud), with no dependency on a client device staying open, awake, or connected. Flowise Agentflows can additionally be scheduled natively via a per-flow cron expression and timezone (toggled from the flow's settings, with a trigger-log history), which originates the run on a timer without any external caller — undocumented publicly, but present and active in the shipped server code since May 2026.", detail: - 'Once a run is invoked by any supported means, closing the browser tab or disconnecting the calling client has no effect on that run completing server-side; the caveat is only that Flowise itself cannot originate a scheduled run without an outside trigger.', - shortValue: 'Yes for triggered runs; no built-in scheduler to originate one unattended', + "Once a run is invoked by any supported means, closing the browser tab or disconnecting the calling client has no effect on that run completing server-side. The only remaining caveat is discoverability: the native Agentflow cron scheduler is not covered in Flowise's public documentation, so most users would still reach for an external scheduler even though Flowise can originate a timed run itself.", + shortValue: 'Yes; also has a native, undocumented cron scheduler', confidence: 'estimated', sources: [ { url: 'https://agentsapis.com/flowise-api/', label: 'Flowise API: Complete Developer Guide', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.flowiseai.com/configuration/running-flowise-using-queue', label: 'Flowise Docs: Running Flowise using Queue', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/database/entities/ScheduleRecord.ts', + label: 'GitHub: ScheduleRecord entity (native per-flow cron trigger)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/blob/main/packages/server/src/schedule/ScheduleBeat.ts', + label: 'GitHub: ScheduleBeat (node-cron / BullMQ scheduling engine)', + asOf: '2026-09-15', }, ], }, @@ -941,7 +1008,7 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/flowise-pricing', label: 'Lindy: Flowise Pricing, Features, and Alternatives for 2026', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -955,33 +1022,53 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/flowise-pricing', label: 'Lindy: Flowise Pricing, Features, and Alternatives for 2026', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, community: { value: - "Flowise's GitHub repository has approximately 54,000 stars (Apache 2.0 licensed core), with an active Discord community whose exact member count is not published.", - shortValue: '~54,000 GitHub stars, active Discord community', + "Flowise's GitHub repository has approximately 55,000 stars (Apache 2.0 licensed core) and a large Discord community, but as of August 31, 2026 Flowise wound down operations and its official core team no longer maintains a presence in either GitHub or Discord (the repo is archived); community activity going forward is self-organized rather than vendor-supported.", + shortValue: '~55k GitHub stars; official support ended, now community-run', confidence: 'verified', sources: [ { url: 'https://github.com/FlowiseAI/Flowise', - label: 'GitHub: FlowiseAI/Flowise', - asOf: '2026-07-02', + label: 'GitHub: FlowiseAI/Flowise (archived, wound down)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/discussions/6727', + label: 'GitHub Discussion #6727: The Future of Flowise (wind-down announcement)', + asOf: '2026-09-15', }, ], }, companyMaturity: { value: - 'Flowise was founded in April 2023 (Y Combinator-backed), raised approximately $500K in early funding, and was acquired by Workday in August 2025, bringing enterprise backing while keeping the open-source Community Edition intact.', - shortValue: 'Founded 2023 (YC), acquired by Workday Aug 2025', + 'Flowise was founded in 2023 (Y Combinator S23-backed) and was acquired by Workday in August 2025. In August 2026, Flowise announced it was winding down operations: active feature development and pull-request review stopped July 29, 2026, the GitHub repository was moved to public-archive status on August 13, 2026 (issues/PRs locked, npm/Docker images marked deprecated), and official core-team presence in Discord and GitHub ended August 31, 2026. The Apache 2.0 source remains on GitHub for self-hosters and forks, but Flowise is no longer an actively maintained, vendor-supported product.', + shortValue: 'Founded 2023 (YC S23), Workday-acquired, now winding down', confidence: 'verified', sources: [ { url: 'https://www.prnewswire.com/news-releases/workday-acquires-flowise-bringing-powerful-ai-agent-builder-capabilities-to-the-workday-platform-302530557.html', label: 'PR Newswire: Workday Acquires Flowise', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.ycombinator.com/companies/flowiseai', + label: 'Y Combinator: FlowiseAI company profile (Summer 2023 batch)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise/discussions/6727', + label: 'GitHub Discussion #6727: The Future of Flowise (wind-down announcement)', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/FlowiseAI/Flowise', + label: 'GitHub: FlowiseAI/Flowise (repository archived)', + asOf: '2026-09-15', }, ], }, @@ -994,7 +1081,17 @@ export const flowiseProfile: CompetitorProfile = { { url: 'https://www.coursera.org/learn/designing-a-customer-support-chatbot-using-flowise', label: 'Coursera: Designing a Customer Support Chatbot Using Flowise', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.codecademy.com/learn/intro-to-ai-agents-with-flowise', + label: 'Codecademy: Intro to AI Agents with Flowise', + asOf: '2026-09-15', + }, + { + url: 'https://www.udemy.com/course/flowise-training-build-ai-agents-chatbots-with-no-code/', + label: 'Udemy: AI Agent Builder Bootcamp (Flowise, LangFlow, RAG & more)', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/gumloop.ts b/apps/sim/lib/compare/data/competitors/gumloop.ts index 4909cb581d0..b91d7da4f0d 100644 --- a/apps/sim/lib/compare/data/competitors/gumloop.ts +++ b/apps/sim/lib/compare/data/competitors/gumloop.ts @@ -22,7 +22,7 @@ export const gumloopProfile: CompetitorProfile = { asOf: '2026-07-02', }, oneLiner: - 'Gumloop is a hosted, no-code visual platform for building and deploying AI agents and automations: a drag-and-drop canvas, an AI copilot ("Gen") for natural-language flow creation, and native MCP (Model Context Protocol) integration support.', + "Gumloop is a hosted platform, now positioned by the vendor as chat-based 'AI agent builder' first (Connectors, Skills, Knowledge Sources, Triggers) rather than a visual workflow tool — its own materials say 'Gumloop is not a visual workflow builder. It is an agent builder' — while still retaining its original drag-and-drop workflow canvas as a now vendor-labeled 'Legacy' feature alongside native MCP (Model Context Protocol) integration support.", standoutFeatures: [ { title: '250+ fully hosted MCP servers', @@ -32,7 +32,7 @@ export const gumloopProfile: CompetitorProfile = { source: { url: 'https://www.gumloop.com/mcp', label: 'Gumloop: Fully Hosted MCP Servers', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -44,18 +44,18 @@ export const gumloopProfile: CompetitorProfile = { source: { url: 'https://www.gumloop.com/changelog', label: 'Gumloop Changelog', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { title: 'Plain-English, org-wide guardrail policy engine', description: - 'Organizations can define app/tool usage policies in plain English at org, team, or agent level; violating actions can be blocked or tagged and logged.', - shortDescription: 'Plain-English usage policies enforced at org, team, or agent level.', + "Organizations can define app/tool usage policies in plain English ('App Rules') at the organization level or the individual-agent level (Gumloop's current App Rules documentation does not describe a separate team-level scope); violating actions can be blocked or tagged, with every evaluated call logged for audit. Organization-wide rule scope is an Enterprise-tier capability per Gumloop's pricing page (Pro is limited to agent-scoped rules).", + shortDescription: 'Plain-English App Rules; org-wide scope is Enterprise-only.', source: { - url: 'https://www.gumloop.com/solutions/security', - label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + url: 'https://docs.gumloop.com/enterprise-features/app-policies/app-rules', + label: 'App Rules - Gumloop docs', + asOf: '2026-09-15', }, }, { @@ -67,7 +67,7 @@ export const gumloopProfile: CompetitorProfile = { source: { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -78,7 +78,7 @@ export const gumloopProfile: CompetitorProfile = { source: { url: 'https://www.gumloop.com/changelog', label: 'Gumloop Changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -91,7 +91,7 @@ export const gumloopProfile: CompetitorProfile = { source: { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -102,31 +102,32 @@ export const gumloopProfile: CompetitorProfile = { source: { url: 'https://www.gumloop.com/tos', label: 'Gumloop Terms of Service', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { title: 'Inconsistent/unclear integration count across vendor pages', description: - "Gumloop's own pages give differing figures for integrations: its docs introduction cites '100+ pre-built nodes and integrations,' while its dedicated MCP page separately advertises '250+ MCP servers.' These may be different countable categories (native nodes vs MCP-protocol connectors), but neither page cross-references the other, and the dedicated /integrations directory page still returns a 404, making an exact, citable integration count hard to pin down from primary sources.", + "Gumloop's own pages now give three differing figures for integrations, and the numbers have shifted since this file was first researched: its docs introduction page, which previously cited '100+ pre-built nodes and integrations,' has been fully rewritten around an agent-first structure and no longer states any integration count; its dedicated MCP page advertises '250+ MCP servers, zero setup'; its Custom MCP Servers docs page separately states 'Gumloop already has 50+ pre-built MCP servers'; and its current Agents documentation describes Connectors as '150+' integrations (e.g. Gmail, Salesforce, Slack, Notion, and 150+ more). None of these pages cross-reference each other, and the dedicated /integrations directory page still returns a 404, making an exact, citable integration count hard to pin down from primary sources.", shortDescription: - 'Vendor pages cite different integration counts with no single authoritative figure.', + 'Vendor pages cite three different integration counts (50+, 150+, 250+) with no single authoritative figure.', source: { url: 'https://docs.gumloop.com/getting-started/introduction', label: 'Getting Started - Gumloop docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { - title: 'No documented built-in vector-search/RAG knowledge base feature in primary docs', + title: + 'No documented chunk-level visibility into the new Knowledge Sources / Company Brain feature', description: - "No official Gumloop documentation describes a dedicated, built-in vector-database/RAG knowledge-base capability. Only a user forum thread and a third-party tutorial reference building a 'knowledge base' with Gumloop nodes.", + 'Gumloop now documents a built-in knowledge-base feature (Knowledge Sources / Company Brain, see aiCapabilities.knowledgeBaseRag) that lets agents search Google Drive, Notion, Slack, GitHub, Confluence, and uploaded files with citations. However, no official documentation describes a chunk-level debugging view (chunk index/content) for this retrieval — see kbChunkVisibility for a dedicated fact on that gap.', shortDescription: - 'No official docs describe a built-in RAG or vector-database knowledge base.', + 'Company Brain now exists; chunk-level retrieval detail still undocumented.', source: { - url: 'https://forum.gumloop.com/t/building-a-knowledge-base-for-rag/841', - label: 'Gumloop forum: Building a knowledge base for RAG', - asOf: '2026-07-02', + url: 'https://docs.gumloop.com/core-concepts/agents', + label: 'Agents - Gumloop docs (Knowledge Sources / Company Brain)', + asOf: '2026-09-15', }, }, ], @@ -134,17 +135,22 @@ export const gumloopProfile: CompetitorProfile = { platform: { builderType: { value: - "Visual, no-code canvas builder with an AI copilot ('Gummie') that can generate/modify flows from natural-language prompts", + "Chat-first agent builder (Connectors, Skills, Knowledge Sources, Triggers, Subagents) that is vendor-positioned as primary, plus a separate drag-and-drop visual canvas ('Flows') now labeled 'Legacy' on Gumloop's own pricing page; an AI copilot ('Gummie') can still generate/modify Flows from natural-language prompts", detail: - "Gumloop is a visual/no-code drag-and-drop canvas for chaining nodes (AI, integration, logic) into agent 'flows'; a chat-based AI agent named Gummie can build and edit these flows from plain-English instructions.", - shortValue: 'Visual canvas plus Gummie AI copilot for building flows', - confidence: 'estimated', + "Gumloop's own site (gumloop.com/blog/agentic-ai-tools, June 2026) states 'Gumloop has two main features, Flows and Agents' — Flows are the original visual/no-code drag-and-drop canvas for chaining nodes into workflows, now labeled 'Workflows (Legacy)' on Gumloop's pricing page, while Agents (built from Connectors, Skills, Knowledge Sources, and Triggers, configured via chat) are the vendor's current primary framing, per Gumloop's own Y Combinator profile disclaimer: 'Gumloop is not a visual workflow builder. It is an agent builder.' A chat-based AI copilot named Gummie can still build and edit Flows from plain-English instructions.", + shortValue: 'Chat-first agent builder; visual canvas now Legacy', + confidence: 'verified', sources: [ - { url: 'https://www.gumloop.com', label: 'Gumloop homepage', asOf: '2026-07-08' }, + { url: 'https://www.gumloop.com', label: 'Gumloop homepage', asOf: '2026-09-15' }, { url: 'https://www.gumloop.com/blog/agentic-ai-tools', label: 'Gumloop blog: agentic AI tools', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://www.gumloop.com/pricing', + label: 'Gumloop Pricing (Workflows (Legacy) section)', + asOf: '2026-09-15', }, ], }, @@ -154,7 +160,7 @@ export const gumloopProfile: CompetitorProfile = { shortValue: 'Easy for basics, steeper for code and multi-agent', confidence: 'estimated', sources: [ - { url: 'https://www.gumloop.com', label: 'Gumloop homepage', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com', label: 'Gumloop homepage', asOf: '2026-09-15' }, ], }, selfHostOption: { @@ -168,12 +174,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/gumloop/guMCP_template', label: "guMCP_template (Gumloop's self-hosted MCP starter repo)", - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -186,7 +192,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -201,7 +207,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/templates', label: 'Gumloop Community Templates', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -212,7 +218,7 @@ export const gumloopProfile: CompetitorProfile = { shortValue: 'Proprietary', confidence: 'estimated', sources: [ - { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-09-15' }, ], }, environmentPromotion: { @@ -226,7 +232,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/projects', label: 'Gumloop Docs: Organizations and Workspaces', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.gumloop.com/core-concepts/checkpoint_history', @@ -237,11 +243,11 @@ export const gumloopProfile: CompetitorProfile = { }, versionControlDepth: { value: - 'Linear checkpoint snapshots with rollback; no diff view, no true undo/redo, no branching', + "Not verifiable in Gumloop's current documentation: the dedicated Workflow Checkpoints page (docs.gumloop.com/core-concepts/checkpoint_history), which previously described a linear checkpoint-snapshot system with 'Make This Checkpoint Live' and 'Rollback to This Checkpoint' actions and no diff/branching, now redirects to a generic Agents overview page with no version-history content of any kind; no equivalent checkpoint/versioning page was located elsewhere in the current docs IA within this review. (Separately, docs.gumloop.com's current Agents page does note that an agent's self-edited system prompt has 'no version history, so revert by editing the prompt manually,' which is a different, narrower mechanism.)", detail: - 'Gumloop replaced a per-version system with a "checkpoints" model. Users manually create checkpoints (snapshots) before major changes, then can either "Make This Checkpoint Live" (switch triggers/interfaces to that checkpoint) or "Rollback to This Checkpoint" (duplicate a past snapshot into the current draft). Docs describe checkpoint metadata (number, date, author) but no diff/compare view between checkpoints, no session-level undo/redo, and a linear history with no branching. Gumloop compares it to Google Docs version history, not git-style branching.', - shortValue: 'Checkpoint snapshots; no diff or branching', - confidence: 'verified', + "This fact previously described a 'checkpoints' model (manual snapshots with 'Make This Checkpoint Live' and 'Rollback to This Checkpoint' actions, comparable to Google Docs version history rather than git-style branching), sourced solely from docs.gumloop.com/core-concepts/checkpoint_history. That URL now redirects to a generic Agents overview page containing no checkpoint, rollback, undo/redo, or diff content, and no replacement checkpoint/versioning documentation page was found elsewhere on docs.gumloop.com during this review. The only adjacent mechanism now documented is narrower: an agent's self-edited system prompt has 'no version history, so revert by editing the prompt manually' (docs.gumloop.com/core-concepts/agents), which covers prompt edits only, not general workflow/agent version history.", + shortValue: 'Not verifiable: checkpoint docs page now dead', + confidence: 'unknown', sources: [ { url: 'https://docs.gumloop.com/core-concepts/checkpoint_history', @@ -261,12 +267,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/teams', label: 'Organization and Teams - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/', label: 'Gumloop homepage', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -281,7 +287,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/blog/artifacts', label: 'Make shareable files with agents - Gumloop blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/personal/files', @@ -306,7 +312,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/changelog', label: 'Gumloop changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -355,7 +361,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/blog/gumloop-custom-nodes', label: 'Gumloop Blog: Gumloop Custom Nodes', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -367,26 +373,21 @@ export const gumloopProfile: CompetitorProfile = { shortValue: 'Claude, OpenAI, Gemini, DeepSeek', confidence: 'estimated', sources: [ - { url: 'https://www.gumloop.com', label: 'Gumloop homepage', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com', label: 'Gumloop homepage', asOf: '2026-09-15' }, ], }, agentReasoningBlocks: { value: - "Yes: dedicated 'Ask AI'/Agent nodes and multi-agent orchestration on the canvas, distinct from plain data-routing nodes", + "Yes: dedicated Agents (chat-based AI assistants with tools, distinct from plain workflow data-routing nodes) plus 'Subagents' for multi-agent orchestration — an agent can self-clone or invoke other agents via the invoke_agent tool to delegate parallel subtasks. The earlier 'Ask AI' node / canvas Agent Node terminology is no longer used on Gumloop's current Agents documentation page.", detail: - "Docs and third-party write-ups describe an 'Ask AI' node for LLM reasoning plus an Agent Node for autonomous/agentic behavior with reflections and tool-use, beyond simple integration/data nodes.", - shortValue: 'Dedicated Ask AI and Agent nodes, multi-agent orchestration', - confidence: 'estimated', + "Docs.gumloop.com's current Agents page describes agents as chat-based AI assistants configured via Connectors, Skills, Knowledge Sources, and Triggers, distinct from the visual canvas's plain data-routing Flow nodes (see platform.builderType). Multi-agent orchestration now runs through 'Subagents': 'Subagents let your agent delegate to other agents... it can spin up focused helpers that work in parallel, then collect the results,' either by self-cloning (depth limit of 1) or by invoking a different, named agent via the invoke_agent tool ('The agent calls a different, specialized agent by name. Add agents to the Subagents list to allow this.'). No canvas-based 'Ask AI node' or 'Agent Node' terminology appears on the current page.", + shortValue: 'Yes: Agents plus Subagents, no more Ask AI node', + confidence: 'verified', sources: [ { url: 'https://docs.gumloop.com/core-concepts/agents', - label: 'Gumloop docs: Agents', - asOf: '2026-07-02', - }, - { - url: 'https://www.gumloop.com/pricing', - label: 'Gumloop Pricing (agent reflections feature)', - asOf: '2026-07-02', + label: 'Gumloop docs: Agents (Subagents, invoke_agent tool)', + asOf: '2026-09-15', }, ], }, @@ -399,35 +400,42 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/blog/agentic-ai-tools', label: 'Gumloop blog: agentic AI tools', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, knowledgeBaseRag: { - value: 'Unknown', + value: + "Yes: Gumloop now documents a built-in knowledge-base feature called 'Knowledge Sources' / 'Company Brain.' Agents can be given searchable access to Google Drive, Notion, Slack, GitHub, Confluence, and uploaded files; the agent searches automatically (shown as 'Searching Company Brain' in chat), answers with citations from the real source documents, and can open a full document for more context. Chunk-level debugging detail is not confirmed (see kbChunkVisibility).", detail: - "No built-in vector-search or RAG knowledge-base feature is documented in Gumloop's official docs; only a community forum thread references building a custom knowledge base out of Gumloop nodes.", - shortValue: 'Not documented as a built-in feature', - confidence: 'unknown', - sources: [], + "Docs.gumloop.com's current Agents page has a dedicated, official Knowledge Sources section: 'Give your agent a searchable memory of what your company knows. In the Knowledge Sources section, attach Brain sources (Google Drive, Notion, Slack, GitHub, Confluence, or uploaded files) so the agent answers from your real documents and messages, with citations, instead of guessing.' This supersedes the earlier finding that only a community forum thread (forum.gumloop.com) referenced building a custom knowledge base out of nodes — Company Brain is now Gumloop's own documented, built-in feature, not a workaround.", + shortValue: 'Yes: built-in Company Brain / Knowledge Sources', + confidence: 'verified', + sources: [ + { + url: 'https://docs.gumloop.com/core-concepts/agents', + label: 'Agents - Gumloop docs (Knowledge Sources / Company Brain)', + asOf: '2026-09-15', + }, + ], }, mcpSupport: { value: - 'Yes: native MCP client/server support with 250+ pre-built hosted MCP servers plus custom MCP server connections', + "Yes: native MCP client/server support. Vendor figures differ by page: 250+ pre-built hosted MCP servers per gumloop.com/mcp, but 50+ pre-built MCP servers per docs.gumloop.com's Custom MCP Servers page — plus custom MCP server connections, supporting both 'native MCP' (model connects directly, e.g. OpenAI/Anthropic) and a 'backend connector' mode (Gumloop executes tool calls, e.g. Gemini/Groq).", detail: - "Gumloop can connect to any MCP server (custom URL over HTTPS), offers 250+ fully-hosted MCP servers with zero setup, and supports both 'native MCP' (model connects directly) and a 'backend connector' mode (Gumloop executes tool calls).", - shortValue: '250+ hosted MCP servers plus custom MCP', + "Gumloop can connect to any MCP server (custom URL over HTTPS). Its marketing MCP page (gumloop.com/mcp) advertises 'Connect any AI agent to 250+ MCP servers, zero setup,' while its docs' Custom MCP Servers page states 'Gumloop already has 50+ pre-built MCP servers for popular services' and directs users to 'Browse available integrations before setting up a custom server' — a smaller, differently-sourced figure than the marketing page's. Native MCP support means the model connects directly to a server (e.g. OpenAI/Anthropic), while backend-connector mode has Gumloop execute the tool call on the model's behalf (e.g. Gemini/Groq).", + shortValue: 'Native MCP; vendor figures vary (50+ to 250+)', confidence: 'verified', sources: [ { url: 'https://www.gumloop.com/mcp', label: 'Gumloop: Fully Hosted MCP Servers', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.gumloop.com/nodes/mcp/custom_mcp_servers', label: 'Gumloop docs: Custom MCP Servers', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -442,7 +450,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/changelog', label: 'Gumloop Changelog', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -456,37 +464,37 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/agents', label: 'Gumloop Docs: Agents', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/changelog', label: 'Gumloop Changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, generativeMedia: { value: - 'Generate Image node supporting 6 models (GPT-Image, DALL-E 3, DALL-E 2, Gemini 3.1 Flash, Gemini 3 Pro, Gemini 2.5 Flash), with 1-10 variations per prompt. No dedicated video or audio (TTS/STT) generation node is documented.', + 'Image Generation is a built-in agent ability (not a canvas node) currently supporting 6 models: GPT-Image-2.5 Flare, GPT-Image-2.5 Sunburst, GPT-Image-2, Gemini 3.1 Flash, Gemini 3 Pro, and Gemini 2.5 Flash Image. DALL-E 2 and DALL-E 3 have been retired and are automatically remapped to GPT-Image-2.5 Flare. No dedicated video or audio (TTS/STT) generation ability is documented.', detail: - 'Separately, an Enterprise-level admin control lets org admins allow or deny specific AI models platform-wide and set automatic fallback models. This is a general model-governance setting, not specific to image generation.', - shortValue: 'Image generation node; no video or audio node', + "Gumloop's current Agents documentation (the former dedicated 'Generate Image node' page now redirects here) describes Image Generation as an ability agents use directly in chat, not a separate canvas node: 'The Image Generation ability creates images from text prompts.' Retired model IDs are explicitly remapped: dall-e-2, dall-e-3, gpt-image-1, and gpt-image-1.5 all now resolve to gpt-image-2.5-flare, and gemini-2.5-flash-image-preview resolves to gemini-2.5-flash-image, so older integrations referencing retired IDs keep working. Separately, an Enterprise-level AI Model Governance control (see security.modelAndToolGovernance) lets org admins allow or deny specific AI models platform-wide and set automatic fallback models, including a dedicated image-generation fallback; this is a general model-governance setting, not specific to image generation.", + shortValue: 'Image ability, 6 models; DALL-E retired', confidence: 'verified', sources: [ { - url: 'https://docs.gumloop.com/nodes/using_ai/generate_image', - label: 'Gumloop Docs: Generate Image node', - asOf: '2026-07-02', + url: 'https://docs.gumloop.com/core-concepts/agents', + label: 'Agents - Gumloop docs (Image Generation ability)', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/changelog', label: 'Gumloop Changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.gumloop.com/enterprise-features/ai_model_control', - label: 'Gumloop Docs', - asOf: '2026-07-02', + label: 'Gumloop Docs: AI Model Governance & Configuration', + asOf: '2026-09-15', }, ], }, @@ -516,12 +524,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/skills', label: 'Agent Skills - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/announcing-skills-for-agents', label: 'Announcing Skills for Agents', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -534,12 +542,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/agents', label: 'Agents - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/announcing-gumloop-agents', label: 'Announcing Gumloop Agents', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -554,23 +562,22 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/skills', label: 'Agent Skills - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, parallelExecution: { value: - 'Partial: Loop Mode runs multiple list items concurrently (up to 15 at once on the Pro plan), but there is no documented dedicated node for splitting a single run into distinct parallel branches that later join, comparable to a fan-out/fan-in construct', + "Yes: beyond concurrent list-item processing, Gumloop now documents 'Subagents' — an agent can self-clone (same tools/instructions, depth limit of 1) to spawn several parallel workers on different subtasks, each running as its own conversation with its own sandbox, with the parent agent collecting and continuing from every subagent's results once finished. This is a genuine fan-out/fan-in construct, distinct from the older Loop Mode concurrent list processing.", detail: - 'Gumloop docs describe Loop Mode as processing list items simultaneously rather than one at a time, with concurrency limits tied to plan tier (2 concurrent items on Free, 15 on Pro). This is data-parallelism over a list, not branch-level fan-out/fan-in across different paths of logic.', - shortValue: - 'Partial: concurrent list-item processing (Loop Mode), no branch fan-out/fan-in node', - confidence: 'estimated', + "Docs.gumloop.com's current Agents page documents Subagents: 'Subagents let your agent delegate to other agents. Instead of doing everything in one conversation, it can spin up focused helpers that work in parallel, then collect the results.' Two delegation modes exist: self-cloning (the agent replicates itself for parallel subtasks, marked '(Me)', capped at a depth limit of 1) and invoking a different, named specialized agent. Each subagent runs as its own conversation with its own context and sandbox; the parent reads each subagent's results when it finishes. This supersedes the earlier finding (sourced from the now-dead Loop Mode page) that Gumloop had no dedicated branch-level fan-out/fan-in construct — Loop Mode's concurrent list-item processing (up to 15 items at once on Pro) remains a separate, narrower mechanism for data-parallelism over a list.", + shortValue: 'Yes: Subagents give true fan-out/fan-in', + confidence: 'verified', sources: [ { - url: 'https://docs.gumloop.com/core-concepts/loop_mode', - label: 'Loop Mode - Gumloop docs', - asOf: '2026-07-02', + url: 'https://docs.gumloop.com/core-concepts/agents', + label: 'Agents - Gumloop docs (Subagents)', + asOf: '2026-09-15', }, ], }, @@ -585,12 +592,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/changelog', label: 'Gumloop Changelog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/introducing-mcp-workflows', label: 'Introducing MCP Nodes & Workflows in Gumloop', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -613,21 +620,31 @@ export const gumloopProfile: CompetitorProfile = { integrations: { integrationCount: { value: - 'Vendor-claimed figures vary by page: 100+ pre-built nodes and integrations (per docs.gumloop.com), 250+ hosted MCP servers (per gumloop.com/mcp)', + "Vendor-claimed figures still vary and the specific numbers have changed: gumloop.com/mcp advertises '250+ MCP servers, zero setup,' docs.gumloop.com's Custom MCP Servers page separately states 'Gumloop already has 50+ pre-built MCP servers,' and the current Agents documentation describes Connectors (the integrations an agent can access) as '150+' (e.g. Gmail, Salesforce, Slack, Notion, and 150+ more). The docs introduction page that previously cited '100+ pre-built nodes and integrations' has been fully rewritten and no longer states any figure.", detail: - "No single authoritative exact count is published on a primary Gumloop page. docs.gumloop.com's introduction cites '100+ pre-built nodes and integrations' while gumloop.com/mcp separately cites '250+ MCP servers, zero setup'; the two pages do not cross-reference each other, and the dedicated /integrations directory page returns a 404.", - shortValue: '100+ nodes/integrations, 250+ MCP servers (vendor figures vary)', + "No single authoritative exact count is published on a primary Gumloop page, and the figures have shifted since this file was first researched: docs.gumloop.com/getting-started/introduction no longer contains the '100+ pre-built nodes and integrations' language at all — it has been fully rewritten around an agent-first structure with no integration count stated. Meanwhile gumloop.com/mcp still advertises '250+ MCP servers, zero setup,' docs.gumloop.com's Custom MCP Servers page states 'Gumloop already has 50+ pre-built MCP servers for popular services,' and the current Agents page's Connectors section states 'Connectors are the integrations your agent connects to, such as Gmail, Salesforce, Slack, Notion, and 150+ more' — a third, distinct figure. None of these pages cross-reference each other, and the dedicated /integrations directory page still returns a 404.", + shortValue: 'Vendor figures vary: 50+, 150+, 250+ across pages', confidence: 'estimated', sources: [ { url: 'https://docs.gumloop.com/getting-started/introduction', label: 'Getting Started - Gumloop docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/mcp', label: 'Gumloop: Fully Hosted MCP Servers', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://docs.gumloop.com/nodes/mcp/custom_mcp_servers', + label: 'Gumloop docs: Custom MCP Servers', + asOf: '2026-09-15', + }, + { + url: 'https://docs.gumloop.com/core-concepts/agents', + label: 'Agents - Gumloop docs (Connectors)', + asOf: '2026-09-15', }, ], }, @@ -640,7 +657,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/workflow_triggers', label: 'Gumloop docs: Workflow Triggers', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -653,26 +670,16 @@ export const gumloopProfile: CompetitorProfile = { }, codeSandboxRuntime: { value: - 'No: the Run Code node executes against a fixed, Gumloop-controlled runtime. Users import from a vendor-curated preinstalled list (Python: pandas, numpy, scipy, xarray, opencv-python, scikit-image, scikit-learn, nltk, spacy, beautifulsoup4, requests, aiohttp, matplotlib, plotly, openpyxl, python-docx, librosa and others published at a Gumloop-hosted requirements.txt; JavaScript: the `ai` SDK plus @ai-sdk/openai, azure, anthropic, amazon-bedrock, google, google-vertex, mistral, cohere and groq). There is no documented way to declare npm/PyPI dependencies, install OS-level system packages, or specify CLI binaries for the runtime.', + 'Yes, with limits: every agent now has an always-on Code Sandbox (an isolated cloud VM) that ships with 80+ preinstalled Python packages, and the agent can install additional packages at runtime via pip install or npm install and run arbitrary shell commands; installed packages persist and are shared across every conversation on that agent. Execution limits are documented: 30-minute command timeout, up to 300MB file ingestion, full internet access, and headless-only (no GUI) execution — it is not intended for training large ML models or running persistent servers.', detail: - 'Gumloop docs describe importing packages only via a plain `import` (Python) or `require` (JavaScript) statement drawn from the published list, with no pip/npm install step. Custom Nodes run in what the docs call "an isolated virtual environment with a 5-minute runtime limit" but likewise document no dependency declaration. On the Gumloop forum, a staff member responding to a Run Code failure caused by unavailable libraries pointed the user back to the published list and suggested a Custom Node as a workaround rather than any package-installation path. Gumloop also ships no downloadable self-managed install of the core platform (see platform.selfHostOption), and its enterprise VPC deployment is operated by Gumloop, so no customer-supplied runtime image is documented there either.', - shortValue: 'No: fixed runtime, vendor-curated preinstalled packages', + "Gumloop's 'Code Sandbox & Secrets' documentation (docs.gumloop.com/core-concepts/agent_sandbox_and_secrets) describes the sandbox as 'natively enabled on all agents with no configuration required,' with each conversation running in its own isolated cloud VM. It ships with 80+ preinstalled Python packages, and agents can run `pip install package-name` or `npm install` plus arbitrary shell commands ('Execute Shell Commands: File operations, package installation, running scripts, and system commands'); installed packages form a 'shared package environment' that persists across every conversation on that agent, so a package installed once is available to everyone with access. Documented limits: a 30-minute command timeout, up to 300MB per ingested file, full internet access (API calls, pip installs, web requests), and headless-only execution ('Visualizations must be saved to files'). The docs explicitly scope it away from heavy workloads: 'not intended for training large ML models or running persistent servers.' This supersedes the earlier fixed-runtime, vendor-curated-import-list characterization documented at the now-dead Run Code / Custom Node Builder pages.", + shortValue: 'Yes: sandbox VM, pip/npm installs, shell access', confidence: 'verified', sources: [ { - url: 'https://docs.gumloop.com/nodes/advanced/run_code', - label: 'Run Code - Gumloop docs', - asOf: '2026-08-10', - }, - { - url: 'https://docs.gumloop.com/nodes/custom_node_details', - label: 'Custom Node Builder - Gumloop docs', - asOf: '2026-08-10', - }, - { - url: 'https://forum.gumloop.com/t/run-code-node-fails-with-generic-error-likely-missing-libraries/2133', - label: 'Gumloop forum: Run Code node missing libraries', - asOf: '2026-08-10', + url: 'https://docs.gumloop.com/core-concepts/agent_sandbox_and_secrets', + label: 'Code Sandbox & Secrets - Gumloop docs', + asOf: '2026-09-15', }, ], }, @@ -687,7 +694,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/api-reference/sdk/javascript', label: 'Gumloop docs: JavaScript SDK', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -702,12 +709,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/api-reference/sdk/javascript', label: 'Gumloop Docs: JavaScript SDK', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/gumloop/gumloop-js', label: 'GitHub: Gumloop/gumloop-js', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.gumloop.com/nodes/custom_node_details', @@ -717,32 +724,37 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/blog/gumloop-custom-nodes', label: 'Gumloop Blog: Gumloop Custom Nodes', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, mcpPublishing: { value: - "No: Gumloop's MCP capability mainly runs in the consuming direction. It connects agents/workflows to 250+ fully hosted MCP servers and lets users add custom MCP servers as tool sources. No official Gumloop documentation describes publishing a user's deployed workflow itself as a callable MCP server for external AI tools to consume.", + "No: Gumloop's own official, first-party MCP server (https://mcp.gumloop.com/gumloop/mcp) now exposes parts of the Gumloop management API (e.g., audit logs) for AI clients like Claude or Cursor to query — this supersedes the earlier characterization of MCP-wrapping-the-management-API as solely a third-party, unofficial project. However, this still does not amount to publishing an individual user's deployed workflow or agent as its own callable MCP server for external tools to consume; no such per-workflow MCP-publishing mechanism is documented.", detail: - 'A third-party, unofficial open-source project ("gumloop-mcp" on GitHub) wraps the Gumloop management API as an MCP server, but that is not the same as natively publishing a specific deployed workflow as an MCP tool, and it is not an official Gumloop product.', - shortValue: "No: consumes MCP servers, doesn't publish flows as one", + "Gumloop's own audit-logging documentation confirms a first-party 'Gumloop MCP' server at mcp.gumloop.com/gumloop/mcp that exposes management-API data (e.g. audit logs via a get_audit_logs tool) to MCP clients like Claude or Cursor, replacing the earlier finding that only an unofficial third-party GitHub project ('gumloop-mcp') wrapped the management API this way. This remains distinct from publishing a specific deployed workflow or agent as its own callable MCP tool: Gumloop's MCP server exposes Gumloop's own platform data/actions, not a customer's individual workflow logic, and no documentation describes the latter.", + shortValue: 'No: official MCP server exists, still not per-workflow', confidence: 'estimated', sources: [ { url: 'https://www.gumloop.com/mcp', label: 'Fully Hosted MCP Servers for Your AI Agents - Gumloop', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.gumloop.com/nodes/mcp/custom_mcp_servers', label: 'Custom MCP Servers - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/introducing-mcp-workflows', label: 'Introducing MCP Nodes & Workflows in Gumloop', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.gumloop.com/enterprise-features/audit_logging', + label: 'Gumloop docs: Audit Logging (Gumloop MCP server)', + asOf: '2026-09-15', }, ], }, @@ -750,11 +762,11 @@ export const gumloopProfile: CompetitorProfile = { pricing: { pricingModel: { value: - 'Usage-based monthly credit system (credits consumed per task/run), with tiered monthly credit allotments from 5k (free) up to 1.5M+ on paid tiers, plus seat-based distinctions between Free/Pro/Enterprise', - shortValue: 'Credit-based usage across tiered plans', + 'Usage-based monthly credit system (credits consumed per task/run), with tiered monthly credit allotments (20k+ on Pro, custom on Enterprise), plus seat-based distinctions between the current Pro and Enterprise tiers (the previously-offered standalone Free plan is no longer shown on the pricing page as of September 2026)', + shortValue: 'Credit-based usage; Pro/Enterprise tiers only', confidence: 'verified', sources: [ - { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-09-15' }, ], }, entryPaidPlan: { @@ -765,16 +777,21 @@ export const gumloopProfile: CompetitorProfile = { shortValue: '$37/month Pro plan, 20k+ credits', confidence: 'verified', sources: [ - { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-09-15' }, ], }, freeTier: { value: - 'Yes: Free plan with 5,000 credits/month, 1 seat, 1 active trigger, 2 concurrent runs, 5 concurrent agent interactions, unlimited agents/flows, forum-only support', - shortValue: '5,000 credits/month, 1 seat', + "No permanent free plan: Gumloop's current pricing page (gumloop.com/pricing) offers only a 14-day free trial of the Pro plan ($37/month, 20k+ credits) and a custom Enterprise plan; the previously-documented standalone Free tier (5,000 credits/month, 1 seat, forum-only support) is no longer listed. (A blog post dated June 8, 2026 still described a Free plan, so this change appears recent.)", + shortValue: 'No free tier: 14-day Pro trial only', confidence: 'verified', sources: [ - { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-09-15' }, + { + url: 'https://www.gumloop.com/blog/agentic-ai-tools', + label: 'Gumloop blog: agentic AI tools (June 8, 2026, describes a Free plan)', + asOf: '2026-09-15', + }, ], }, byok: { @@ -782,11 +799,11 @@ export const gumloopProfile: CompetitorProfile = { shortValue: 'Supported on all plans', confidence: 'verified', sources: [ - { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-09-15' }, { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -803,9 +820,9 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, - { url: 'https://trust.gumloop.com/', label: 'Gumloop Trust Center', asOf: '2026-07-02' }, + { url: 'https://trust.gumloop.com/', label: 'Gumloop Trust Center', asOf: '2026-09-15' }, ], }, dataResidency: { @@ -817,7 +834,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -830,12 +847,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing (Enterprise features list)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -847,32 +864,32 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/enterprise-features/audit_logging', label: 'Gumloop docs: Audit Logging', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing (Enterprise features list)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, modelAndToolGovernance: { value: - 'Yes for models: an org-wide AI Model Control setting lets admins restrict members to an allow-list or block-list of models, set automatic fallback models (including a separate fallback for image generation), and override the default Recommended/Smartest/Fastest presets so all agents use consistent model choices. Tool governance is handled separately via the per-tool authorization policies covered under RBAC/ABAC, not a distinct model-and-tool control surface.', + "Yes for models: an org-wide AI Model Governance setting lets admins restrict members to an allow-list ('Allow Only Selected') or block-list ('Block Selected') of models, set automatic fallback models (including a separate fallback for image generation), and set the model behind each of the two agent presets — Recommended and Smartest — so all agents use consistent model choices (there is no third 'Fastest' preset). Tool governance is handled separately via the per-tool authorization policies covered under RBAC/ABAC, not a distinct model-and-tool control surface.", detail: - "Gumloop's docs describe AI Model Control as an Enterprise admin feature applying platform-wide to every member ('Allow Only Selected' or 'Block Selected' modes), not scoped per-team or per-agent. It covers only which LLMs are usable and their fallback/preset routing; it makes no mention of restricting access to non-model tools, which is instead covered by the RBAC/ABAC per-tool authorization policies documented separately.", - shortValue: 'Yes: org-wide model allow/deny with fallback; tool governance via RBAC', + "Gumloop's docs (now titled 'AI Model Governance & Configuration') describe this as an Enterprise admin feature applying platform-wide to every member ('Allow Only Selected' or 'Block Selected' modes), not scoped per-team or per-agent. Its Restrictions tab controls model availability and its Fallbacks tab sets a general Fallback Model and a separate Image Generation Fallback Model; the two agent presets it can pin a model to are Recommended ('best balance of speed, quality, and cost') and Smartest ('maximum intelligence for complex tasks') — there is no 'Fastest' preset. It makes no mention of restricting access to non-model tools, which is instead covered by the RBAC/ABAC per-tool authorization policies documented separately.", + shortValue: 'Org-wide model allow/deny; two presets, no Fastest', confidence: 'verified', sources: [ { url: 'https://docs.gumloop.com/enterprise-features/ai_model_control', - label: 'Gumloop Docs: AI Model Control', - asOf: '2026-07-04', + label: 'Gumloop Docs: AI Model Governance & Configuration', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/solutions/security', label: 'Gumloop Security & Trust', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -887,12 +904,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/enterprise-features/user_groups', label: 'Custom User Roles - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/gumloop-for-enterprise', label: 'Gumloop for Enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -906,12 +923,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/core-concepts/custom_slack_app', label: 'Custom Slack App Integration - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.gumloop.com/enterprise-features/sso_saml_scim', label: 'SSO, SAML & SCIM - Gumloop docs (mentions dedicated login page)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -926,12 +943,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/solutions/security', label: 'Security and trust at Gumloop', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/gumloop-for-enterprise', label: 'Gumloop for Enterprise', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -946,7 +963,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/solutions/security', label: 'Security and trust at Gumloop', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -961,7 +978,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/enterprise-features/sso_saml_scim', label: 'SSO, SAML & SCIM - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -991,12 +1008,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/enterprise-features/sso_saml_scim', label: 'SSO, SAML & SCIM - Gumloop docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/solutions/security', label: 'Security and trust at Gumloop', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -1016,7 +1033,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/blog/announcing-community-templates', label: 'Announcing Community Templates - Gumloop blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1024,11 +1041,11 @@ export const gumloopProfile: CompetitorProfile = { observability: { tracingDepth: { value: - 'Customer-facing per-node execution trace with duration/cost, but no aggregate metrics dashboard (percentiles/error-rate) found', + "Not verifiable at the originally cited URL: Gumloop's dedicated 'Run Log' documentation page no longer exists (redirects to a generic Agents overview with no execution-trace content). The current Agents page instead documents per-agent 'Usage stats' (tasks, active days, actions, unique users over 31 days) and points to a separate org-wide 'Insights' page for credit spend and leaderboards; no equivalent per-node/per-step execution-trace debugging view was located within this review.", detail: - 'Gumloop\'s "Run Log" is a customer-facing execution trace view. For every run it shows per-node execution status, inputs/outputs, per-node execution time and credit cost, a subflow detail drill-down, and per-iteration visibility for Loop Mode nodes, plus a workflow summary of total time and total credits, accessible via a `run_id`-scoped URL. No cross-run metrics dashboard (e.g. latency percentiles or aggregate error rates across many runs) is documented. The Run Log is built for debugging one execution at a time, not fleet-wide observability.', - shortValue: 'Per-node run trace; no aggregate metrics dashboard', - confidence: 'verified', + "This fact previously described a customer-facing 'Run Log' execution trace (per-node status, inputs/outputs, timing, and credit cost per run), sourced solely from docs.gumloop.com/core-concepts/run_log. That URL now redirects to a generic Agents overview page with no execution-trace content. The current Agents page instead surfaces aggregate 'Usage stats' per agent (tasks, active days, tool calls, unique users over the last 31 days) and references a separate org-wide 'Insights' page for credit spend and leaderboards, but no per-node/per-step execution-trace debugging view comparable to the old Run Log was located during this review.", + shortValue: 'Not verifiable: Run Log docs page now dead', + confidence: 'unknown', sources: [ { url: 'https://docs.gumloop.com/core-concepts/run_log', @@ -1039,11 +1056,11 @@ export const gumloopProfile: CompetitorProfile = { }, durabilityModel: { value: - 'No automatic retries, no execution checkpointing, no run replay with original inputs. Only a manual "Error Shield" node and workflow-level (not run-level) checkpoints', + "Not verifiable at the originally cited URLs: Gumloop's 'Run Log' documentation (which previously supported the 'no automatic retries/checkpointing/replay' finding) and its 'Error Shield' node documentation (which previously supported the 'manual error-handling only' finding) have both been removed; both URLs now redirect to a generic Agents overview page with no execution-durability, retry, checkpointing, replay, or Error Shield content. No equivalent durability/error-handling documentation was located elsewhere in the current docs IA within this review.", detail: - 'Gumloop\'s Run Log documentation makes no mention of automatic node retries, mid-run checkpointing of execution state, or the ability to replay a past execution with its original inputs. Failure handling is opt-in and manual via an "Error Shield" node that wraps other nodes to catch errors and prevent a full workflow crash, something designed into the workflow rather than automatic infrastructure-level retry/replay. Gumloop\'s "checkpoints" feature (see platform.versionControlDepth) snapshots workflow definitions, not individual run state, so it is unrelated to run durability.', - shortValue: 'No auto-retry or replay; manual Error Shield node', - confidence: 'verified', + 'This fact previously relied on docs.gumloop.com/core-concepts/run_log (no mention of automatic retries, mid-run checkpointing, or replay) and docs.gumloop.com/nodes/flow_basics/error_shield (a manual node that wraps other nodes to catch errors, routing to a fallback Error Path). Both pages now redirect to the generic Agents overview with no equivalent content — no error-handling, retry, or run-durability documentation was found there or elsewhere in the current docs IA during this review.', + shortValue: 'Not verifiable: Run Log and Error Shield docs dead', + confidence: 'unknown', sources: [ { url: 'https://docs.gumloop.com/core-concepts/run_log', @@ -1059,11 +1076,11 @@ export const gumloopProfile: CompetitorProfile = { }, failureAlerting: { value: - 'Yes: proactive email push notification on workflow failure (Pro plan+); credit-usage thresholds are separate/lookup-based', + "Not verifiable at the originally cited URL: Gumloop's dedicated Alerts documentation page no longer exists (redirects to a generic Agents overview with no failure-notification content); no replacement alerting page was located elsewhere in the current docs IA within this review.", detail: - 'Gumloop supports configuring email notifications for workflow failures directly from a workbook\'s side panel. This requires a Pro plan or higher and can be scoped to "Alert only on trigger-based failures" so manual test runs don\'t spam alerts. The failure email includes the workflow name, a run link, and error details, a proactive push rather than something you look up after the fact. Credit/cost-threshold notifications are configured separately on the Subscription page and read more like a lookup setting than a proactive per-threshold push alert.', - shortValue: 'Proactive email alerts on failure (Pro plan+)', - confidence: 'verified', + 'This fact previously described proactive email notifications configurable per-workflow for run failures (Pro plan and above), sourced solely from docs.gumloop.com/core-concepts/alerts. That URL now redirects to a generic Agents overview page with no failure-notification content, and no equivalent alerting/notification documentation page was located elsewhere in the current docs IA during this review.', + shortValue: 'Not verifiable: Alerts docs page now dead', + confidence: 'unknown', sources: [ { url: 'https://docs.gumloop.com/core-concepts/alerts', @@ -1082,22 +1099,22 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/enterprise-features/organization_data_export', label: 'Usage Data Export / Data Drains - Gumloop docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, asyncExecution: { value: - "Yes: Gumloop's API triggers workflows asynchronously. A POST to the start_pipeline endpoint returns immediately with a run_id, and the caller polls a separate get_pl_run endpoint (passing that run_id) to check status, logs, and retrieve outputs once the run completes.", + "Yes: Gumloop's API executes asynchronously, but the documented primary pattern has changed to an agent-first one: a POST to start_agent (with user_id, agent_id, message) or a webhook call returns immediately (webhooks reply 200 with {'success': true} before the agent finishes), and the agent runs in the background, reporting results via a connected tool or the run's own history rather than a synchronous poll target. The previously-documented start_pipeline/get_pl_run workflow-run pattern is no longer shown on Gumloop's current API Getting Started page; it is not confirmed whether it still functions for legacy 'Workflows.'", detail: - 'Documented pattern: POST https://api.gumloop.com/api/v1/start_pipeline to start, GET https://api.gumloop.com/api/v1/get_pl_run?run_id=... to poll for completion and outputs.', - shortValue: 'Yes: async trigger + poll by run_id', + "Current documented pattern: POST https://api.gumloop.com/api/v1/start_agent?api_key=... with user_id, agent_id, and message starts an agent run in the background; the API's own framing is 'The Gumloop API is agent-first: you can create and update agents, start sessions to chat with them, and use chat completions from any OpenAI-compatible client.' Webhook-triggered runs (POST to /trigger_incoming_webhook//) similarly return immediately. Neither start_pipeline nor get_pl_run appears anywhere on the current API Getting Started page; whether that endpoint pair still functions for the legacy 'Workflows (Legacy)' pricing-page feature is not stated.", + shortValue: 'Yes: async, now agent-first (start_agent/webhook)', confidence: 'verified', sources: [ { url: 'https://docs.gumloop.com/api-reference/getting-started', label: 'Gumloop API Reference: Getting Started', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1112,7 +1129,7 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing (concurrent runs / agent interactions by plan)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1142,12 +1159,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://docs.gumloop.com/api-reference/getting-started', label: 'Gumloop API Reference: Getting Started', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.gumloop.com/core-concepts/workflow_triggers', label: 'Gumloop docs: Workflow Triggers', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1159,7 +1176,7 @@ export const gumloopProfile: CompetitorProfile = { shortValue: 'Forum on Free, Slack on higher tiers', confidence: 'estimated', sources: [ - { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-07-02' }, + { url: 'https://www.gumloop.com/pricing', label: 'Gumloop Pricing', asOf: '2026-09-15' }, ], }, sla: { @@ -1179,36 +1196,41 @@ export const gumloopProfile: CompetitorProfile = { }, companyMaturity: { value: - "Founded in Vancouver in April 2023 (originally as 'AgentHub') by Max Brodeur-Urbas and Rahul Behal. Raised a $3.1M seed (July 2024) and a $17M Series A in January 2025 (led by Nexus Venture Partners), both independently corroborated; a self-reported $50M Series B in March 2026 (led by Benchmark) would bring the total to about $70M across 3 rounds. Y Combinator alum with roughly 37 employees as of mid-2026.", + "Founded in Vancouver in April 2023 (originally as 'AgentHub') by Max Brodeur-Urbas and Rahul Behal. Raised a $3.1M seed (July 2024) and a $17M Series A in January 2025 (led by Nexus Venture Partners), both independently corroborated; a $50M Series B in March 2026 (led by Benchmark) would bring the total to about $70M across 3 rounds; unlike the earlier characterization, TechCrunch has since independently covered the round ('Gumloop lands $50M from Benchmark to turn every employee into an AI agent builder,' March 12, 2026, per Gumloop's Y Combinator company page), so it is no longer solely self-reported. Y Combinator alum with a team size of 44 as of the current review (up from ~37 in mid-2026).", detail: - "Gumloop started as a side project in a Vancouver bedroom in April 2023, founded by Max Brodeur-Urbas and Rahul Behal under the name AgentHub before rebranding to Gumloop. It raised a $3.1M seed round in July 2024 and a $17M Series A in January 2025 led by Nexus Venture Partners (with First Round Capital, Y Combinator, and angel investors), both independently corroborated by TechCrunch. The $50M Series B in March 2026 led by Benchmark (with Nexus Venture Partners, First Round Capital, Y Combinator, Box Group, The Cannon Project, and Shopify Ventures) is self-reported on Gumloop's own blog only, with no independent press or funding-tracker corroboration found. Total raised is about $70M across 3 rounds. Y Combinator lists a team size of 37.", - shortValue: 'Founded 2023, ~$70M raised, Series B in 2026 (self-reported)', - confidence: 'estimated', + "Gumloop started as a side project in a Vancouver bedroom in April 2023, founded by Max Brodeur-Urbas and Rahul Behal under the name AgentHub before rebranding to Gumloop. It raised a $3.1M seed round in July 2024 and a $17M Series A in January 2025 led by Nexus Venture Partners (with First Round Capital, Y Combinator, and angel investors), both independently corroborated by TechCrunch. The $50M Series B in March 2026 was led by Benchmark (with Nexus Venture Partners, First Round Capital, Y Combinator, Box Group, The Cannon Project, and Shopify Ventures); TechCrunch independently covered it directly ('Gumloop lands $50M from Benchmark to turn every employee into an AI agent builder,' techcrunch.com, March 12, 2026), corroborated by syndication on Yahoo Finance and coverage from Tech Funding News, so the earlier 'self-reported only' characterization no longer holds. Total raised is about $70M across 3 rounds. Gumloop's Y Combinator company page now lists a team size of 44, up from 37 as of mid-2026.", + shortValue: 'Founded 2023, ~$70M raised; Series B now TechCrunch-covered', + confidence: 'verified', sources: [ { url: 'https://www.gumloop.com/blog/gumloops-17m-series-a', label: 'Gumloop Blog: Series A announcement', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/agenthub-to-gumloop', label: 'Gumloop Blog: Why we rebranded to Gumloop', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://techcrunch.com/2025/01/10/gumloop-founded-in-a-bedroom-in-vancouver-lets-users-automate-tasks-with-drag-and-drop-modules/', label: 'TechCrunch: Gumloop founding story & Series A', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.ycombinator.com/companies/gumloop', label: 'Y Combinator: Gumloop company page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/blog/series-b', label: 'Gumloop Blog: Series B announcement', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://techcrunch.com/2026/03/12/gumloop-lands-50m-from-benchmark-to-turn-every-employee-into-an-ai-agent-builder/', + label: 'TechCrunch: Gumloop lands $50M Series B from Benchmark', + asOf: '2026-09-15', }, ], }, @@ -1223,12 +1245,12 @@ export const gumloopProfile: CompetitorProfile = { { url: 'https://university.gumloop.com/', label: 'Gumloop University', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.gumloop.com/cohorts', label: 'Gumloop Learning Cohorts', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/langchain.ts b/apps/sim/lib/compare/data/competitors/langchain.ts index 0b4fb29eebb..ace040c2918 100644 --- a/apps/sim/lib/compare/data/competitors/langchain.ts +++ b/apps/sim/lib/compare/data/competitors/langchain.ts @@ -26,7 +26,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://docs.langchain.com/oss/python/langgraph/use-time-travel', label: 'Time travel - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -38,7 +38,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://docs.langchain.com/oss/python/langgraph/use-graph-api', label: 'Use the graph API - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -50,7 +50,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://www.langchain.com/langsmith/evaluation', label: 'LangSmith Evaluations', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -62,7 +62,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://docs.langchain.com/langsmith/server-a2a', label: 'A2A endpoint in Agent Server - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -74,7 +74,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://docs.langchain.com/oss/python/langgraph/studio', label: 'LangGraph Studio - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, ], @@ -88,7 +88,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://docs.langchain.com/oss/python/langgraph/use-graph-api', label: 'Use the graph API - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -100,7 +100,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://github.com/langchain-ai/agent-chat-ui', label: 'langchain-ai/agent-chat-ui (GitHub)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -112,7 +112,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://docs.langchain.com/oss/python/langchain/models', label: 'Models - Docs by LangChain', - asOf: '2026-07-04', + asOf: '2026-09-15', }, }, { @@ -124,7 +124,7 @@ export const langchainProfile: CompetitorProfile = { source: { url: 'https://docs.langchain.com/langsmith/user-management', label: 'User management - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -142,12 +142,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/langgraph/studio', label: 'LangGraph Studio - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://github.com/langchain-ai/deepagents', label: 'langchain-ai/deepagents (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -162,7 +162,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://academy.langchain.com/', label: 'LangChain Academy', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -177,7 +177,13 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/deploy-standalone-server', label: 'Self-host standalone servers - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.langchain.com/blog/langgraph-platform-ga', + label: + 'LangGraph Platform is now Generally Available (LangChain Blog, confirms 100k free self-hosted nodes/month on the Developer plan)', + asOf: '2026-09-15', }, ], }, @@ -185,14 +191,19 @@ export const langchainProfile: CompetitorProfile = { value: 'Any environment that runs Python/Node for the open-source libraries themselves. LangGraph Platform (renamed LangSmith Deployment) additionally offers a managed cloud service, a standalone self-hosted container (Docker/Kubernetes/VM with a Redis + Postgres backend), and a hybrid model.', detail: - 'Standalone container deployment requires a REDIS_URI (background task queue) and a DATABASE_URI (Postgres, for assistants/threads/runs/state). langgraph deploy (introduced March 2026) is the current production deployment path, superseding the older langgraph up Docker Compose flow.', + 'Standalone container deployment requires a REDIS_URI (background task queue) and a DATABASE_URI (Postgres, for assistants/threads/runs/state). langgraph deploy (introduced March 16, 2026 via the langgraph-cli package) lets a single command build a Docker image locally, push it to a managed registry, and create or update a LangSmith Deployment, making it easy to integrate into CI/CD; the earlier langgraph up Docker Compose flow remains documented for standalone self-hosted deployment rather than being formally deprecated.', shortValue: 'OSS libraries anywhere, plus managed cloud, self-hosted container, or hybrid', confidence: 'verified', sources: [ { url: 'https://docs.langchain.com/langsmith/deploy-standalone-server', label: 'Self-host standalone servers - Docs by LangChain', - asOf: '2026-07-04', + asOf: '2026-09-15', + }, + { + url: 'https://www.langchain.com/blog/introducing-deploy-cli', + label: 'Introducing the LangGraph Deploy CLI (LangChain Blog)', + asOf: '2026-09-15', }, ], }, @@ -208,7 +219,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://blog.langchain.com/launching-langgraph-templates/', label: 'Launching LangGraph Templates (LangChain Blog)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -223,12 +234,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://github.com/langchain-ai/langchain', label: 'langchain-ai/langchain (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/langchain-ai/langgraph', label: 'langchain-ai/langgraph (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -244,7 +255,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/assistants', label: 'Assistants - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -259,7 +270,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/assistants', label: 'Assistants - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -274,7 +285,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/blog/langgraph-studio-the-first-agent-ide', label: 'LangGraph Studio: The first agent IDE', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -289,7 +300,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/deepagents/overview', label: 'Deep Agents overview - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -314,7 +325,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://reference.langchain.com/python/deepagents/middleware/skills', label: 'skills | deepagents | LangChain Reference', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -329,7 +340,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/langgraph/use-subgraphs', label: 'Subgraphs - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -344,7 +355,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/use-remote-graph', label: 'How to interact with a deployment using RemoteGraph - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -361,7 +372,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/langchain', label: 'LangChain: Open Source AI Agent Framework', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -377,7 +388,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/langgraph', label: 'LangGraph: Agent Orchestration Framework for Reliable AI Agents', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -402,12 +413,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/langchain/retrieval', label: 'Retrieval - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.langchain.com/oss/python/integrations/vectorstores', label: 'VectorStore Interface and Integrations - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -422,7 +433,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://github.com/langchain-ai/langchain-mcp-adapters', label: 'langchain-ai/langchain-mcp-adapters (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://reference.langchain.com/python/langchain-mcp-adapters/interceptors', + label: 'interceptors - langchain_mcp_adapters - LangChain Reference', + asOf: '2026-09-15', }, ], }, @@ -437,7 +453,13 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/langsmith/evaluation', label: 'LangSmith Evaluations', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.langchain.com/blog/introducing-align-evals', + label: + 'Introducing Align Evals: Streamlining LLM Application Evaluation (LangChain Blog)', + asOf: '2026-09-15', }, ], }, @@ -453,7 +475,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/langchain/human-in-the-loop', label: 'Human-in-the-loop - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -478,7 +500,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/langchain/models', label: 'Models - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -493,7 +515,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://reference.langchain.com/python/langchain-core/runnables/fallbacks/RunnableWithFallbacks', label: 'RunnableWithFallbacks - LangChain Reference', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -508,7 +530,13 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://reference.langchain.com/python/deepagents/middleware/skills', label: 'skills | deepagents | LangChain Reference', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.langchain.com/oss/python/deepagents/customization', + label: + 'Customization - Docs by LangChain (confirms Anthropic/Bedrock prompt-caching middleware registration and ordering)', + asOf: '2026-09-15', }, ], }, @@ -523,7 +551,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://github.com/langchain-ai/agent-chat-ui', label: 'langchain-ai/agent-chat-ui (GitHub)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -539,7 +567,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://reference.langchain.com/python/langchain-core/documents/base/Document', label: 'Document - LangChain Reference', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -553,9 +581,9 @@ export const langchainProfile: CompetitorProfile = { confidence: 'verified', sources: [ { - url: 'https://machinelearningplus.com/gen-ai/langgraph-map-reduce-parallel-execution/', - label: 'LangGraph Map-Reduce: Parallel Execution with Send API', - asOf: '2026-07-02', + url: 'https://docs.langchain.com/oss/python/langgraph/use-graph-api', + label: 'Use the graph API - Docs by LangChain', + asOf: '2026-09-15', }, ], }, @@ -570,7 +598,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/server-a2a', label: 'A2A endpoint in Agent Server - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -586,7 +614,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/langgraph/use-graph-api', label: 'Use the graph API - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://reference.langchain.com/python/langgraph-sdk/schema/Config/recursion_limit', + label: 'recursion_limit - langgraph_sdk - LangChain Reference (confirms default of 25)', + asOf: '2026-09-15', }, ], }, @@ -602,7 +635,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/langchain', label: 'LangChain: Open Source AI Agent Framework', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -618,7 +651,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/server-api-ref', label: 'Agent Server API reference - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -642,27 +675,27 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/langsmith/sandboxes', label: 'LangSmith Sandboxes | Secure Runtime for Agent Code', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.langchain.com/langsmith/sandbox-snapshots', label: 'Sandbox snapshots - Docs by LangChain', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.langchain.com/langsmith/sandboxes', label: 'LangSmith Sandboxes (environment availability) - Docs by LangChain', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://www.langchain.com/blog/langsmith-sandboxes-generally-available', label: 'LangSmith Sandboxes are Generally Available (LangChain Blog)', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.langchain.com/oss/python/deepagents/sandboxes', label: 'Sandboxes - Docs by LangChain', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -677,12 +710,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/server-api-ref', label: 'Agent Server API reference - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.langchain.com/langsmith/server-a2a', label: 'A2A endpoint in Agent Server - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -698,12 +731,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://github.com/langchain-ai/langchain', label: 'langchain-ai/langchain (GitHub)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://pypi.org/project/langchain-community/', label: 'langchain-community on PyPI (sunset notice)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -718,7 +751,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/server-api-ref', label: 'Agent Server API reference - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -735,13 +768,13 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/pricing', label: 'LangSmith Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, entryPaidPlan: { value: - 'LangSmith Plus: $39/seat/month, up to 10,000 base traces/month included, then pay-as-you-go, unlimited seats, one complimentary dev deployment, email support', + 'LangSmith Plus: $39/seat/month, up to 10,000 base traces/month included, then pay-as-you-go, ability to add unlimited seats, one free Serverless (Small) deployment included, plus Support Portal and Email Support access', detail: 'The Developer plan below it is $0/seat/month (single seat, up to 5,000 base traces/month, community support only), so Plus is the first genuinely paid tier.', shortValue: '$39/seat/month, 10,000 base traces included', @@ -750,7 +783,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/pricing', label: 'LangSmith Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -765,7 +798,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/pricing', label: 'LangSmith Pricing', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -783,21 +816,21 @@ export const langchainProfile: CompetitorProfile = { security: { compliance: { value: - "Yes: LangSmith is SOC 2 Type II certified, and is additionally stated to be HIPAA compliant and GDPR compliant. LangGraph Platform (now branded LangSmith Deployment) is publicly announced as carrying the same attestation, sharing LangSmith's infrastructure and compliance posture. No ISO 27001, PCI-DSS, or FedRAMP attestation was found on LangChain's own compliance materials.", + "Yes: LangSmith is SOC 2 Type II certified (the 2026 report, covering July 1, 2025 through June 30, 2026, expanded scope to Security, Availability, and Confidentiality across the entire LangSmith offering, audited by Advantage Partners with no exceptions noted), and is additionally ISO/IEC 27001:2022 certified (announced July 2, 2026, covering the systems, teams, and information assets supporting LangSmith and LangChain's LLM application tooling, also audited by Advantage Partners), and is stated to be HIPAA compliant and GDPR compliant. LangGraph Platform (now branded LangSmith Deployment) shares LangSmith's infrastructure and is covered by the same attestations. No PCI-DSS or FedRAMP attestation was found on LangChain's own compliance materials.", detail: - "LangChain's Trust Center (trust.langchain.com) is the canonical source for these claims but renders via client-side JavaScript, so it could not be directly verified by an automated fetch; the SOC 2 Type II certification is independently confirmed on a static docs page, while the HIPAA and GDPR claims rest on LangChain's own docs and Trust Center.", - shortValue: 'SOC 2 Type II, HIPAA, GDPR; no ISO/PCI/FedRAMP', + "LangChain's Trust Center (trust.langchain.com) is directly readable in a browser and lists Compliance: SOC 2 Type II, ISO/IEC 27001:2022, GDPR, and HIPAA, alongside its own update feed announcing the ISO/IEC 27001:2022 certification (July 2, 2026) and the 2026 SOC 2 Type II report (published September 3, 2026); the SOC 2 Type II certification is additionally confirmed on a static docs page, while the HIPAA and GDPR claims rest on LangChain's own docs and Trust Center.", + shortValue: 'SOC 2 Type II, ISO 27001:2022, HIPAA, GDPR; no PCI-DSS/FedRAMP found', confidence: 'verified', sources: [ { url: 'https://docs.langchain.com/langsmith/regions-faq', label: 'Regions FAQ - Docs by LangChain (confirms SOC 2 Type 2)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://trust.langchain.com/', label: 'LangChain Trust Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -812,7 +845,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/regions-faq', label: 'Regions FAQ - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -827,7 +860,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/blog/access-control-updates-for-langsmith', label: 'Role Based Access Control (RBAC) for LangSmith', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -861,7 +894,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/user-management', label: 'User management - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -885,7 +918,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/pricing', label: 'LangSmith Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -900,7 +933,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/mask-inputs-outputs', label: 'Prevent logging of sensitive data in traces - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -915,7 +948,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/user-management', label: 'User management - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -945,12 +978,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://support.langchain.com/articles/9515017706-session-timeout-configuration-for-langsmith-self-hosted', label: 'Session Timeout Configuration for LangSmith Self-Hosted', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://support.langchain.com/articles/8821869322-sso-authentication-and-token-issuance-in-langsmith', label: 'SSO Authentication and Token Issuance in LangSmith', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -966,13 +999,19 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/oss/python/security-policy', label: 'Security policy - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/advisories/GHSA-c67j-w6g6-q2cm', label: 'LangChain serialization injection vulnerability (CVE-2025-68664) - GitHub Advisory Database', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://thehackernews.com/2025/12/critical-langchain-core-vulnerability.html', + label: + 'Critical LangChain Core Vulnerability (The Hacker News, confirms "LangGrinch" nickname)', + asOf: '2026-09-15', }, ], }, @@ -989,12 +1028,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/observability-concepts', label: 'Observability concepts - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.langchain.com/oss/python/langgraph/use-time-travel', label: 'Time travel - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1010,7 +1049,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/blog/fault-tolerance-in-langgraph', label: 'Fault Tolerance in LangGraph (LangChain Blog)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1034,7 +1073,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/export-backend', label: 'Export LangSmith telemetry to your observability backend - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1049,7 +1088,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/agent-server', label: 'Agent Server - Docs by LangChain', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1073,7 +1112,7 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://deepwiki.com/langchain-ai/langgraph/3.8-error-handling-and-retry-policies', label: 'Error Handling and Retry Policies | langchain-ai/langgraph | DeepWiki', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1088,12 +1127,12 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://docs.langchain.com/langsmith/assistants', label: 'Assistants - Docs by LangChain', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langchain.com/langsmith/deploy-standalone-server', label: 'Self-host standalone servers - Docs by LangChain', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -1110,27 +1149,28 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://www.langchain.com/pricing', label: 'LangSmith Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.langchain.com/join-community', label: 'LangChain Community Slack', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, sla: { value: - 'Not publicly documented as a specific uptime percentage: LangSmith Enterprise lists "SLA guarantees" as an included feature, but no page publishes a concrete SLA number', + 'Not publicly documented as a specific uptime percentage: LangSmith Enterprise lists "Support SLA" as an included feature, but no page publishes a concrete SLA percentage or response-time number.', detail: - 'The LangSmith pricing page names "SLA guarantees" under the Enterprise tier without stating the specific percentage or terms publicly.', - shortValue: 'Enterprise includes SLA guarantees, exact terms not publicly stated', + 'The LangSmith pricing page names "Support SLA" under the Enterprise tier without stating the specific percentage, response-time, or terms publicly.', + shortValue: + 'Enterprise includes a "Support SLA"; exact terms/percentage not publicly stated', confidence: 'estimated', sources: [ { url: 'https://www.langchain.com/pricing', label: 'LangSmith Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1145,38 +1185,54 @@ export const langchainProfile: CompetitorProfile = { { url: 'https://github.com/langchain-ai/langchain', label: 'langchain-ai/langchain (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/langchain-ai/langgraph', label: 'langchain-ai/langgraph (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.langchain.com/blog/series-b', label: 'LangChain raises $125M to build the platform for agent engineering', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, companyMaturity: { value: - 'LangChain Inc. Founded 2022 by Harrison Chase. Raised a $125M Series B led by IVP in October 2025 at a $1.25B valuation (total raised approximately $160M across seed, Series A, and Series B), with reported headcount in the roughly 260-325 employee range as of mid-2026', + 'LangChain Inc. Founded 2022 by Harrison Chase. Raised a $125M Series B led by IVP in October 2025 at a $1.25B valuation (total raised approximately $160M across seed, Series A, and Series B), with headcount reported at approximately 429 employees as of August 2026 per Tracxn, up sharply from earlier-2026 snapshots reported by other trackers', detail: - "Prior rounds: a $10M seed from Benchmark (April 2023) and a $25M Series A led by Sequoia days later (reported at a ~$200M valuation). $10M + $25M + $125M totals approximately $160M; some third-party trackers report a higher ~$260M cumulative figure, which appears to double-count TechCrunch's July 2025 report of an in-progress raise (at a reported $1.1B valuation) as a separate round from its October 2025 close (the same round, at $1.25B) rather than an additional close, so $160M is the figure directly supported by LangChain's own funding announcement and primary reporting. Investors in the Series B include Sequoia, Benchmark, IVP, CapitalG, Sapphire Ventures, and strategic investors such as ServiceNow Ventures, Workday Ventures, Cisco Investments, Datadog Ventures, and Databricks Ventures. Employee-count sources vary by snapshot date (163 to 325 across different 2026 trackers), reflecting rapid hiring.", + "Prior rounds: a $10M seed from Benchmark, publicly announced by co-founder Ankush Gola (April 2023), and a $25M Series A led by Sequoia Capital, announced on LangChain's own blog roughly ten months later alongside LangSmith's general availability (February 15, 2024; reported elsewhere at a ~$200M valuation). $10M + $25M + $125M totals approximately $160M; some third-party trackers report a higher ~$260M cumulative figure, which appears to double-count TechCrunch's July 2025 report of an in-progress raise (which TechCrunch described only as raising 'at a valuation of at least $1 billion,' not a specific $1.1B figure) as a separate round from its October 2025 close (the same round, at $1.25B) rather than an additional close, so $160M is the figure directly supported by LangChain's own funding announcements and primary reporting. Investors in the Series B include Sequoia, Benchmark, IVP, CapitalG, Sapphire Ventures, and strategic investors such as ServiceNow Ventures, Workday Ventures, Cisco Investments, Datadog Ventures, and Databricks Ventures. Employee-count sources vary significantly by snapshot date and tracker methodology: Tracxn reports 429 employees as of August 31, 2026, up substantially since 2025, when some third-party trackers reported headcount in the 150-200 range, consistent with the company's rapid hiring following its Series B.", shortValue: - 'Founded 2022; $125M Series B (Oct 2025) at $1.25B valuation; ~260-325 employees', + 'Founded 2022; $125M Series B (Oct 2025) at $1.25B valuation; ~429 employees (Aug 2026)', confidence: 'verified', sources: [ { url: 'https://www.langchain.com/blog/series-b', label: 'LangChain raises $125M to build the platform for agent engineering', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://techcrunch.com/2025/10/21/open-source-agentic-startup-langchain-hits-1-25b-valuation/', label: 'Open source agentic startup LangChain hits $1.25B valuation | TechCrunch', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.linkedin.com/posts/ankush-gola-77255866_announcing-our-10m-seed-round-led-by-benchmark-activity-7049070288507961345-RAVk', + label: 'Ankush Gola announcing the $10M Benchmark-led seed round (LinkedIn)', + asOf: '2026-09-15', + }, + { + url: 'https://www.langchain.com/blog/langsmith-ga', + label: + 'Announcing the GA of LangSmith and Our Series A Led By Sequoia Capital (LangChain Blog)', + asOf: '2026-09-15', + }, + { + url: 'https://tracxn.com/d/companies/langchain/__O9N2dOHcgRE9Nbcn5BFfkUHn-rVk6GTbq8oY-UJ0Ba4', + label: 'LangChain company profile - Tracxn (employee headcount)', + asOf: '2026-09-15', }, ], }, @@ -1188,7 +1244,7 @@ export const langchainProfile: CompetitorProfile = { shortValue: 'Yes, free structured courses with certificates at LangChain Academy', confidence: 'verified', sources: [ - { url: 'https://academy.langchain.com/', label: 'LangChain Academy', asOf: '2026-07-02' }, + { url: 'https://academy.langchain.com/', label: 'LangChain Academy', asOf: '2026-09-15' }, ], }, }, diff --git a/apps/sim/lib/compare/data/competitors/langflow.ts b/apps/sim/lib/compare/data/competitors/langflow.ts index 883cecbde84..eacf9f070a0 100644 --- a/apps/sim/lib/compare/data/competitors/langflow.ts +++ b/apps/sim/lib/compare/data/competitors/langflow.ts @@ -25,7 +25,7 @@ export const langflowProfile: CompetitorProfile = { source: { url: 'https://docs.langflow.org/concepts-components', label: 'Langflow Docs: Components overview', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -37,7 +37,7 @@ export const langflowProfile: CompetitorProfile = { source: { url: 'https://docs.langflow.org/mcp-server', label: 'Langflow Docs: Use Langflow as an MCP server', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -48,7 +48,7 @@ export const langflowProfile: CompetitorProfile = { source: { url: 'https://docs.langflow.org/concepts-flows', label: 'Langflow Docs: Build flows', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -62,19 +62,19 @@ export const langflowProfile: CompetitorProfile = { source: { url: 'https://github.com/langflow-ai/langflow/issues/1864', label: 'GitHub Issue 1864: Collaborative/Access Control enhancement', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { title: 'Lowest enterprise-readiness scores in third-party benchmark', description: - "n8n's 2026 AI Agent Development Tools report scored Langflow 35 percent on Codability and 30 percent on Enterprisiness, the lowest of the vendors evaluated, citing gaps in agent sandboxing, security guardrail maturity, and evaluation frameworks.", + "n8n's 2026 AI Agent Development Tools report scored Langflow 35 percent on Codability and 30 percent on Enterprisiness, the lowest of the 14 vendors evaluated on both axes. The report's Langflow vendor profile itself highlights back-end configuration strengths — memory management, logging, a file management system, and Nginx/Certbot reverse-proxy deployment — rather than calling out specific weaknesses; the report's broader scoring observations separately note that agent sandboxing, security guardrails, and LLM evaluation frameworks are underdeveloped across most vendors it surveyed, which is consistent with Langflow's low scores on the axes that partly measure those capabilities.", shortDescription: "Scored lowest on codability (35%) and enterprisiness (30%) in n8n's 2026 report.", source: { url: 'https://n8n.io/reports/2026-ai-agent-development-tools/#vendors', label: 'n8n: 2026 AI Agent Development Tools report', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -90,12 +90,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/concepts-components', label: 'Langflow Docs: Components overview', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/langflow-assistant', label: 'Langflow Docs: Langflow Assistant', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -106,9 +106,9 @@ export const langflowProfile: CompetitorProfile = { confidence: 'estimated', sources: [ { - url: 'https://docs.langflow.org/starter-projects-vector-store-rag', - label: 'Langflow Docs: Vector store RAG starter project', - asOf: '2026-07-02', + url: 'https://docs.langflow.org/chat-with-rag', + label: 'Langflow Docs: Create a vector RAG chatbot', + asOf: '2026-09-15', }, ], }, @@ -121,12 +121,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/get-started-installation', label: 'Langflow Docs: Install Langflow', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/langflow-ai/langflow', label: 'GitHub: langflow-ai/langflow', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -139,17 +139,17 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/get-started-installation', label: 'Langflow Docs: Install Langflow', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/deployment-kubernetes-dev', label: 'Langflow Docs: Kubernetes deployment', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/deployment-multi-worker', label: 'Langflow Docs: Deploy Langflow with multiple workers', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -160,14 +160,14 @@ export const langflowProfile: CompetitorProfile = { confidence: 'verified', sources: [ { - url: 'https://docs.langflow.org/starter-projects-basic-prompting', - label: 'Langflow Docs: Basic prompting starter project', - asOf: '2026-07-02', + url: 'https://docs.langflow.org/concepts-flows', + label: 'Langflow Docs: Build flows', + asOf: '2026-09-15', }, { url: 'https://www.langflow.org/templates/use-langflow-to-build-local-rag-pipeline-with-ollama-and-chromadb', label: 'Langflow templates gallery example', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -180,7 +180,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://github.com/langflow-ai/langflow', label: 'GitHub: langflow-ai/langflow (License: MIT)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -202,7 +202,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/concepts-flows', label: 'Langflow Docs: Build flows', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -215,7 +215,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://github.com/langflow-ai/langflow/issues/1864', label: 'GitHub Issue 1864: Collaborative/Access Control enhancement', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -228,20 +228,21 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/concepts-file-management', label: 'Langflow Docs: Manage files', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, dataTables: { value: - "No: Langflow's documentation does not describe a native spreadsheet-like data table feature. It exposes Data and DataFrame object types used to pass structured data between components, not a persistent spreadsheet UI.", - shortValue: 'No native spreadsheet-style data table', - confidence: 'estimated', + "No: Langflow's documentation does not describe a native spreadsheet-like data table feature that persists as a browsable UI. It exposes JSON and Table object types (renamed from the older Data and DataFrame names as of Langflow version 1.9.0) used to pass structured data — including tabular, pandas-DataFrame-shaped data — between components at run time, not a persistent, browsable spreadsheet interface a user can open, edit, and revisit independent of a flow run.", + shortValue: + 'No persistent spreadsheet UI; pass-through JSON/Table objects (formerly Data/DataFrame)', + confidence: 'verified', sources: [ { - url: 'https://docs.langflow.org/components-data', - label: 'Langflow Docs: Data components', - asOf: '2026-07-02', + url: 'https://docs.langflow.org/concepts-objects', + label: 'Langflow Docs: Langflow data types', + asOf: '2026-09-15', }, ], }, @@ -261,7 +262,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/run-flow', label: 'Langflow Docs: Run Flow component', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -276,12 +277,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/concepts-components', label: 'Langflow Docs: Components overview (grouping and saving components)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://github.com/langflow-ai/langflow/discussions/4406', label: 'GitHub Discussion 4406: How to save a custom component to the sidebar?', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -297,12 +298,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/components-models', label: 'Langflow Docs: Language Model component', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.langflow.org/blog/local-ai-using-ollama-with-agents', label: 'Langflow blog: Using Ollama with agents', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -315,12 +316,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/agents', label: 'Langflow Docs: Use Langflow agents', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/components-agents', label: 'Langflow Docs: Agents component', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -333,7 +334,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/langflow-assistant', label: 'Langflow Docs: Langflow Assistant', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -344,9 +345,9 @@ export const langflowProfile: CompetitorProfile = { confidence: 'verified', sources: [ { - url: 'https://docs.langflow.org/starter-projects-vector-store-rag', - label: 'Langflow Docs: Vector store RAG starter project', - asOf: '2026-07-02', + url: 'https://docs.langflow.org/chat-with-rag', + label: 'Langflow Docs: Create a vector RAG chatbot', + asOf: '2026-09-15', }, ], }, @@ -359,12 +360,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/mcp-client', label: 'Langflow Docs: Use Langflow as an MCP client', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/mcp-tools', label: 'Langflow Docs: MCP Tools component', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -377,12 +378,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/guardrails', label: 'Langflow Docs: Guardrails', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/bundles-cleanlab', label: 'Langflow Docs: Cleanlab bundle', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -397,7 +398,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://github.com/langflow-ai/langflow/discussions/4399', label: 'GitHub Discussion 4399: How to implement human in the loop?', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -419,7 +420,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/agents-tools', label: 'Langflow Docs: Configure tools for agents', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -433,7 +434,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://www.langflow.org/blog/how-to-build-your-own-gpt-5', label: 'Langflow blog: Build Your Own GPT-5 with Smart Model Routing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -451,14 +452,14 @@ export const langflowProfile: CompetitorProfile = { confidence: 'verified', sources: [ { - url: 'https://docs.langflow.org/embedded-chat-widget', - label: 'Langflow Docs: Embedded chat widget', - asOf: '2026-07-02', + url: 'https://docs.langflow.org/concepts-publish', + label: 'Langflow Docs: Embed a flow into a website', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/concepts-playground', label: 'Langflow Docs: Test flows in the Playground', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -478,7 +479,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/concepts-flows', label: 'Langflow Docs: Build flows (DAG execution order)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -491,12 +492,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://github.com/langflow-ai/langflow/issues/10658', label: 'GitHub langflow-ai/langflow Issue #10658: Add A2A Protocol Support', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/langflow-ai/langflow/issues/10241', label: 'GitHub langflow-ai/langflow Issue #10241: A2A (tracking issue)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -509,7 +510,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/loop', label: 'Langflow Docs: Loop component', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -524,7 +525,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/components-bundle-components', label: 'Langflow Docs: About bundles', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -538,12 +539,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/webhook', label: 'Langflow Docs: Trigger flows with webhooks', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/api-flows-run', label: 'Langflow Docs: Flow trigger endpoints', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -556,7 +557,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/components-custom-components', label: 'Langflow Docs: Create custom Python components', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -571,17 +572,17 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/install-custom-dependencies', label: 'Langflow Docs: Install custom dependencies', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/develop-application', label: 'Langflow Docs: Containerize a Langflow application', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/extensions-overview', label: 'Langflow Docs: Extensions overview', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -594,7 +595,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/api-reference-api-examples', label: 'Langflow Docs: Get started with the Langflow API', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -608,12 +609,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/components-custom-components', label: 'Langflow Docs: Create custom Python components', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/langflow-ai/langflow-embedded-chat', label: 'GitHub: langflow-ai/langflow-embedded-chat', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -626,7 +627,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/mcp-server', label: 'Langflow Docs: Use Langflow as an MCP server', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -634,31 +635,43 @@ export const langflowProfile: CompetitorProfile = { pricing: { pricingModel: { value: - "Langflow's core software is free and open source, with no license fee for self-hosting. Third-party sources describe Langflow Cloud as offering a free account tier plus a paid tier around $25 per month for higher usage limits, and separate enterprise pricing; Langflow's official pricing page does not confirm these figures directly.", + "Langflow's core software is free and open source, with no license fee for self-hosting. Third-party sources (Lindy and Automation Atlas) agree that Langflow Cloud offers a free account tier with no listed subscription fee, and that beyond that free tier, cloud and enterprise pricing is not publicly listed — Automation Atlas describes hosted Cloud/Enterprise as 'custom-priced and not publicly listed,' and Lindy states that costs instead come from the infrastructure, LLM API, and vector-database usage you connect to it. Langflow's own official pricing page likewise does not publish a paid-tier price, so no specific paid-tier dollar figure (including the roughly $25/month sometimes cited elsewhere) is confirmed by any of these sources.", detail: - "Based on third-party summaries; the official pricing page doesn't confirm these figures.", - shortValue: 'Free open-source core; cloud free tier plus paid/enterprise tiers', + 'Grounded in explicit third-party statements that no paid-tier price is publicly listed, not merely an absence of evidence; the official pricing page also publishes no paid-tier figure.', + shortValue: 'Free open-source core; cloud/enterprise pricing not publicly listed', confidence: 'estimated', sources: [ { url: 'https://www.lindy.ai/blog/langflow-pricing', label: 'Lindy: Langflow Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://automationatlas.io/tools/langflow/', label: 'Automation Atlas: Langflow pricing summary', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, entryPaidPlan: { value: - "Unknown: the exact entry paid-plan price and inclusions aren't confirmed on Langflow's own official pricing page. Third-party summaries cite a cloud paid tier starting around $25 per month.", - detail: 'Not confirmed against an official Langflow source.', - shortValue: 'Unverified; third parties cite roughly $25/month', - confidence: 'unknown', - sources: [], + "Unknown: the exact entry paid-plan price and inclusions aren't confirmed on Langflow's own official pricing page. No third-party source confirms a specific entry paid-plan price either — Lindy and Automation Atlas both describe Langflow Cloud's paid and enterprise tiers as custom-priced with no publicly listed figure, so the roughly $25/month figure sometimes cited elsewhere is not actually stated by either source.", + detail: + 'Not confirmed against an official Langflow source, and no third-party source states a specific figure either.', + shortValue: 'Unverified; no paid-tier price publicly listed', + confidence: 'estimated', + sources: [ + { + url: 'https://www.lindy.ai/blog/langflow-pricing', + label: 'Lindy: Langflow Pricing', + asOf: '2026-09-15', + }, + { + url: 'https://automationatlas.io/tools/langflow/', + label: 'Automation Atlas: Langflow pricing summary', + asOf: '2026-09-15', + }, + ], }, freeTier: { value: @@ -670,7 +683,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://www.lindy.ai/blog/langflow-pricing', label: 'Lindy: Langflow Pricing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -683,7 +696,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/agents', label: 'Langflow Docs: Use Langflow agents', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -707,7 +720,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/get-started-installation', label: 'Langflow Docs: Install Langflow', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -720,7 +733,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/security', label: 'Langflow Docs: Security', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -733,7 +746,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/concepts-flows', label: 'Langflow Docs: Build flows', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -762,7 +775,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://github.com/langflow-ai/langflow-embedded-chat', label: 'GitHub: langflow-ai/langflow-embedded-chat', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -775,7 +788,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/concepts-file-management', label: 'Langflow Docs: Manage files', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -790,7 +803,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/guardrails', label: 'Langflow Docs: Guardrails', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -822,12 +835,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/api-keys-and-authentication', label: 'Langflow Docs: API keys and authentication', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/authentication-overview', label: 'Langflow Docs: Authentication and authorization overview', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -843,32 +856,32 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/components-bundle-components', label: 'Langflow Docs - About bundles', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/contributing-components', label: 'Langflow Docs - Contribute components', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/components-custom-components', label: 'Langflow Docs - Create custom Python components', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/security', label: 'Langflow Docs - Security', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://github.com/langflow-ai/langflow/security/advisories/GHSA-rvqx-wpfh-mfx7', label: 'GitHub Security Advisory GHSA-rvqx-wpfh-mfx7 (CVE-2025-3248)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.securityweek.com/recent-langflow-vulnerability-exploited-by-flodrix-botnet/', label: 'SecurityWeek - Langflow Vulnerability Exploited by Flodrix Botnet', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -885,12 +898,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/integrations-langfuse', label: 'Langflow Docs: Langfuse integration', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/integrations-langsmith', label: 'Langflow Docs: LangSmith integration', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -917,7 +930,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/integrations-langfuse', label: 'Langflow Docs: Langfuse integration', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -930,7 +943,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/api-monitor', label: 'Langflow Docs: Monitor endpoints', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -959,12 +972,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/get-started-installation', label: 'Langflow Docs: Install Langflow', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.langflow.org/webhook', label: 'Langflow Docs: Trigger flows with webhooks', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -979,7 +992,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://docs.langflow.org/contributing-community', label: 'Langflow Docs: Join the Langflow community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -999,7 +1012,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://github.com/langflow-ai/langflow', label: 'GitHub: langflow-ai/langflow', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1012,12 +1025,12 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://techcrunch.com/2024/04/04/datastax-acquires-logspace-the-startup-behind-the-langflow-low-code-tool-for-building-rag-based-chatbots/', label: 'TechCrunch: DataStax acquires Langflow (Logspace)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://newsroom.ibm.com/2025-02-25-ibm-to-acquire-datastax,-deepening-watsonx-capabilities-and-addressing-generative-ai-data-needs-for-the-enterprise', label: 'IBM Newsroom: IBM to acquire DataStax', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1030,7 +1043,7 @@ export const langflowProfile: CompetitorProfile = { { url: 'https://www.udemy.com/course/langchain-masterclass/', label: 'Udemy: Master LangChain with No-Code tools: Flowise and LangFlow', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/make.ts b/apps/sim/lib/compare/data/competitors/make.ts index 685ecb93ef7..35bf05cba7d 100644 --- a/apps/sim/lib/compare/data/competitors/make.ts +++ b/apps/sim/lib/compare/data/competitors/make.ts @@ -38,7 +38,7 @@ export const makeProfile: CompetitorProfile = { source: { url: 'https://www.make.com/en/templates', label: 'Make Templates gallery', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -49,7 +49,7 @@ export const makeProfile: CompetitorProfile = { source: { url: 'https://www.make.com/en/ai-agents', label: 'Make AI Agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -60,7 +60,7 @@ export const makeProfile: CompetitorProfile = { source: { url: 'https://help.make.com/mcp-toolboxes', label: 'MCP toolboxes - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, ], @@ -73,7 +73,7 @@ export const makeProfile: CompetitorProfile = { source: { url: 'https://www.make.com/en/on-prem-agents', label: 'Make on-prem agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -84,7 +84,7 @@ export const makeProfile: CompetitorProfile = { source: { url: 'https://www.make.com/master-service-agreement.pdf', label: 'Master Services Agreement for Make, Section 4.4 & 6.1 (Celonis)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -96,18 +96,18 @@ export const makeProfile: CompetitorProfile = { source: { url: 'https://apps.make.com/code', label: 'Make Code app docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { title: 'Granular RBAC gated to the Teams plan and above', description: - "Full team/role-based permission management ('Teams and team roles', letting admins manage unlimited team permissions for scenario apps, templates, and connections) is only listed as a feature starting on the Teams plan ($38/mo) and Enterprise; lower tiers (Free, Core, Pro) get unlimited users but no role-based access controls, unlike Sim, which ships admin/write/read roles on every tier.", - shortDescription: 'RBAC needs the Teams plan ($38/mo) or above.', + "Full team/role-based permission management ('Teams and team roles', letting admins manage unlimited team permissions for scenario apps, templates, and connections) is only listed as a feature starting on the Teams plan ($51/mo billed monthly, or $38/mo if billed annually) and Enterprise; lower tiers (Free, Core, Pro) get unlimited users but no role-based access controls, unlike Sim, which ships admin/write/read roles on every tier.", + shortDescription: 'RBAC needs the Teams plan ($51/mo monthly, or $38/mo annual).', source: { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, ], @@ -123,12 +123,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/ai-agents', label: 'Make AI Agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -143,12 +143,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://learn.g2.com/make-vs-zapier', label: 'Make vs. Zapier - G2 Learn', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.lindy.ai/blog/make-review', label: 'Make Review 2026 - Lindy', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -163,12 +163,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/on-prem-agents', label: 'Make on-prem agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/help/connections/using-an-on-premise-agent', label: 'On-premise agent help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -183,7 +183,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/security', label: 'Make Security page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -197,12 +197,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/templates', label: 'Make Templates gallery', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/scenario-templates', label: 'Scenario templates help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -216,7 +216,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/master-service-agreement.pdf', label: 'Master Services Agreement for Make, Section 6.1 (Celonis)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -231,22 +231,22 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/organizations', label: 'Organizations | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/teams', label: 'Teams | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://community.make.com/t/moving-scenarios-from-one-organization-to-another/78092', label: 'Moving scenarios from one organization to another - Make Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://community.make.com/t/migrate-connections-and-scenarios-between-teams-in-make/70733', label: 'Migrate Connections and Scenarios Between Teams in Make - Make Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -261,17 +261,17 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/restore-a-previous-scenario-version', label: 'Restore a previous scenario version | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/restore-and-recover-scenario', label: 'Restore and recover scenario | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/scenario-history', label: 'Scenario history | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -287,12 +287,12 @@ export const makeProfile: CompetitorProfile = { url: 'https://community.make.com/t/what-happens-if-2-people-are-editing-a-scenario-at-the-same-time/69301', label: 'What happens if 2 people are editing a scenario at the same time? - Make Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/scenario-sharing', label: 'Scenario sharing - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -307,27 +307,27 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/working-with-files', label: 'Working with files - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, dataTables: { value: - 'Yes: Make has a native Data Stores feature for storing structured records (fields/columns and items/rows), with a browsable table view in the UI for adding, viewing, updating, and deleting records. It behaves more like a key-value record store than a full spreadsheet: limits are size-based (1MB per store on Core, 10MB on Pro/Teams, custom on Enterprise, with per-record caps reported at 512KB-15MB depending on the source) rather than fixed row/column counts, and it lacks spreadsheet-style keyboard navigation (arrow-key cell movement, multi-cell copy-paste).', + "Yes: Make has a native Data Stores feature for storing structured records (fields/columns and items/rows), with a browsable table view in the UI for adding, viewing, updating, and deleting records. It behaves more like a key-value record store than a full spreadsheet: total data-storage allowance scales with the plan's credit allotment rather than a flat per-tier cap — every 1,000 monthly credits/operations equals 1 MB of storage (e.g., a 10,000-credit plan gets 10 MB, a 20,000-credit plan gets 20 MB), with a 1 MB minimum per individual data store and a hard ceiling of 1,000 data stores per organization on any plan; no separate per-record byte cap is documented. It also lacks spreadsheet-style keyboard navigation (arrow-key cell movement, multi-cell copy-paste).", detail: 'UI supports a table/grid browse view and manual record add/edit, but bulk spreadsheet-like editing (arrow-key navigation, drag-fill, multi-cell paste) is not documented.', - shortValue: 'Yes: Data Stores (record/table store, size-capped)', + shortValue: 'Yes: Data Stores, storage scales with monthly credits', confidence: 'verified', sources: [ { url: 'https://help.make.com/data-stores', label: 'Data stores - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/api-documentation/api-reference/data-stores', label: 'Data Stores - Make API Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -342,12 +342,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://apps.make.com/google-docs', label: 'Google Docs - Apps Documentation - Make', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/help/app/markdown', label: 'Markdown - Apps Documentation - Make', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -355,19 +355,19 @@ export const makeProfile: CompetitorProfile = { value: "Yes: Make's 'Call a Scenario' subscenario module lets a parent scenario invoke a saved sub-scenario as a step, passing structured inputs and, in synchronous mode, pausing until the sub-scenario finishes and returns outputs via a 'Return outputs' module.", detail: - "Make's Subscenarios feature supports two modes: synchronous, where the parent calls the sub-scenario and pauses execution until it completes and returns output; and asynchronous, where the parent continues immediately without waiting. Each call creates its own separately logged run, and an error in the sub-scenario propagates back to the parent's error handling. This is a dedicated composition feature, distinct from triggering an unrelated scenario via a plain webhook.", + "Make's Subscenarios feature supports two modes: synchronous, where the parent calls the sub-scenario and pauses execution until it completes and returns output; and asynchronous, where the parent continues immediately without waiting. Each call creates its own separately logged run. Make's Subscenarios documentation does not explicitly state whether an error in the sub-scenario propagates to the parent's own error handlers; in synchronous mode the parent is paused awaiting the sub-scenario's output, which would surface a failure to the parent's execution, but this specific behavior is undocumented and should be read as unconfirmed rather than a stated guarantee. This is a dedicated composition feature, distinct from triggering an unrelated scenario via a plain webhook.", shortValue: 'Yes: Call a Scenario module runs a sub-scenario as a step', confidence: 'verified', sources: [ { url: 'https://help.make.com/subscenarios', label: 'Subscenarios - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/scenario-inputs-and-scenario-outputs', label: 'Scenario inputs and scenario outputs - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -382,17 +382,17 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/subscenarios', label: 'Subscenarios - Make Help Center', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://help.make.com/scenarios-for-ai-agents', label: 'Scenarios for AI agents - Make Help Center', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/custom-apps-documentation', label: 'Overview | Custom Apps Documentation | Make Developer Hub', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -400,7 +400,7 @@ export const makeProfile: CompetitorProfile = { aiCapabilities: { multiLlmSupport: { value: - 'Yes: OpenAI, Anthropic Claude, Google Vertex AI (Gemini), Azure OpenAI, Mistral AI, Perplexity AI, Hugging Face, plus OpenAI-compatible custom models', + "Yes: OpenAI, Anthropic Claude, Gemini Enterprise Agent Platform (Google's Gemini), Azure OpenAI, Mistral AI, Perplexity AI, Hugging Face, plus OpenAI-compatible custom models", detail: "Make's AI Agents page lists these integrated providers; AI Agent configuration docs also mention support for 'various LLMs including OpenAI-compatible models.'", shortValue: 'OpenAI, Anthropic, Gemini, Azure, Mistral, and more', @@ -409,12 +409,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/ai-agents', label: 'Make AI Agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/make-ai-agents-the-next-step-in-automation', label: 'Make AI Agents help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -429,12 +429,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/ai-agents', label: 'Make AI Agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/make-ai-agents-the-next-step-in-automation', label: 'Make AI Agents help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -447,21 +447,27 @@ export const makeProfile: CompetitorProfile = { sources: [], }, knowledgeBaseRag: { - value: 'Yes: built-in Knowledge feature backed by a RAG vector database for AI Agents', + value: + "Yes: built-in Knowledge feature for AI Agents; Make's now-superseded documentation described it as backed by a RAG vector database, but that detail is unconfirmed against current docs", detail: - "Per Make's help docs, uploaded knowledge files are stored in a RAG vector database: files are chunked, converted to vectors, and the agent retrieves only relevant chunks at request time, reducing tokens used.", - shortValue: 'Built-in RAG store for agent knowledge files', - confidence: 'verified', + "Make's now-superseded AI Agents docs (marked by Make as reflecting a previous version) described uploaded knowledge files as chunked, converted to vectors, and stored in a RAG vector database. Make's current documentation for the successor 'Make AI Agent (New)' app still describes Knowledge as reference files 'stored in a database' the agent 'repeatedly consults' to reduce token usage — consistent with retrieval-based lookup — but no longer states the underlying chunking/embedding mechanism explicitly, so treat the vector-database detail as unconfirmed against current docs.", + shortValue: 'Database-backed knowledge; RAG/vector detail unconfirmed', + confidence: 'estimated', sources: [ { url: 'https://help.make.com/knowledge', label: 'Make Knowledge help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/ai-agents-configuration', - label: 'AI Agents configuration help doc', - asOf: '2026-07-02', + label: 'AI Agents configuration help doc (previous-version notice)', + asOf: '2026-09-15', + }, + { + url: 'https://help.make.com/introduction-to-make-ai-agent-new', + label: 'Introduction to Make AI Agent (New) - Make Help Center', + asOf: '2026-09-15', }, ], }, @@ -475,7 +481,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/blog/model-context-protocol-mcp-server', label: 'Make blog: What is MCP Server?', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -490,7 +496,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/ai-agents', label: 'Make AI Agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -505,17 +511,17 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/integrations/human-in-the-loop-enterprise', label: 'Human in the Loop (Enterprise) Integration | Make', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://apps.make.com/human-in-the-loop-enterprise', label: 'Human in the Loop - Apps Documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/blog/human-in-the-loop', label: 'What is human in the loop (HITL) in AI? | Make', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -530,12 +536,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/blog/faceless-youtube-videos-make-ai', label: 'How to Make Faceless YouTube Videos with AI + Make | Make blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://community.make.com/t/video-generation-systems-that-work-with-make/55168', label: 'Video generation systems that work with Make? - Make Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -573,14 +579,14 @@ export const makeProfile: CompetitorProfile = { confidence: 'estimated', sources: [ { - url: 'https://help.make.com/ai-agents-configuration', - label: 'AI Agents configuration - Make Help Center', - asOf: '2026-07-02', + url: 'https://help.make.com/create-ai-agents-for-different-triggers', + label: 'Create AI Agents for different triggers - Make Help Center', + asOf: '2026-09-15', }, { - url: 'https://help.make.com/manage-ai-agents', - label: 'Manage AI agents - Make Help Center', - asOf: '2026-07-02', + url: 'https://help.make.com/introduction-to-make-ai-agent-new', + label: 'Introduction to Make AI Agent (New) - Make Help Center', + asOf: '2026-09-15', }, ], }, @@ -604,7 +610,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/router', label: 'Make Help Center: Router', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -619,7 +625,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/blog/agentic-operating-system', label: 'Make Blog: What Is an Agentic Operating System? 2026 Guide', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -634,12 +640,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/iterator', label: 'Iterator - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/help/tools/flow-control', label: 'Flow control - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -655,7 +661,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/integrations', label: 'Make Integrations page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -670,12 +676,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/webhooks', label: 'Make Webhooks help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page (execution interval limits)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -690,9 +696,9 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/blog/make-code-app', label: 'Make blog: Make Code App', - asOf: '2026-07-02', + asOf: '2026-09-15', }, - { url: 'https://apps.make.com/code', label: 'Make Code app docs', asOf: '2026-07-08' }, + { url: 'https://apps.make.com/code', label: 'Make Code app docs', asOf: '2026-09-15' }, ], }, codeSandboxRuntime: { @@ -703,11 +709,11 @@ export const makeProfile: CompetitorProfile = { shortValue: 'Packages only: declared npm/PyPI dependencies, Enterprise plans', confidence: 'verified', sources: [ - { url: 'https://apps.make.com/code', label: 'Make Code app docs', asOf: '2026-08-10' }, + { url: 'https://apps.make.com/code', label: 'Make Code app docs', asOf: '2026-09-15' }, { url: 'https://www.make.com/en/blog/make-code-app', label: 'Make blog: Make Code App', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -722,12 +728,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/webhooks', label: 'Make Webhooks help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/api-documentation/api-reference/scenarios', label: 'Make Developer Hub: Scenarios API', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -735,30 +741,35 @@ export const makeProfile: CompetitorProfile = { value: 'Apps SDK (VS Code extension + browser Apps Editor) for building custom apps/connectors, plus a Make Marketplace for publishing them; no dedicated first-party Node.js/Python client SDK found beyond the general REST API', detail: - "Make provides the 'Make Apps Editor', a JSON/config-based custom-app development environment available both as a browser-based editor inside Make's dashboard and as a VS Code extension (the Apps SDK) that syncs local files to Make via API. A custom app is built from five components: base, connections, modules, RPCs, and webhooks. Built apps can be submitted to the Make Apps Marketplace (beta), subject to a review process (roughly 4-6 weeks) and limited to services not already covered by Make's built-in app library. No official multi-language client SDK (published Node.js or Python packages) exists beyond the documented REST API; client access is via plain REST calls only.", + "Make provides the 'Make Apps Editor', a JSON/config-based custom-app development environment available both as a browser-based editor inside Make's dashboard and as a VS Code extension (the Apps SDK) that syncs local files to Make via API. A custom app is built from five components: base, connections, modules, RPCs, and webhooks. Built apps can be submitted to the Make Apps Marketplace (beta), subject to a Make QA code review (Make's own documentation describes 'multiple stages' but does not publish an expected turnaround time) and limited to services not already covered by Make's built-in app library. No official multi-language client SDK (published Node.js or Python packages) exists beyond the documented REST API; client access is via plain REST calls only.", shortValue: 'Apps SDK for custom connectors, no client SDK', confidence: 'verified', sources: [ { url: 'https://developers.make.com/custom-apps-documentation', label: 'Overview | Custom Apps Documentation | Make Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/custom-apps-documentation/get-started/make-apps-editor/apps-sdk', label: 'Visual Studio Code | Custom Apps Documentation | Make Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/custom-apps-documentation/app-components', label: 'App components (base, connections, modules, RPCs, webhooks) | Make Developer Hub', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/api-documentation', label: 'Make API documentation | Make Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://developers.make.com/custom-apps-documentation/app-review/overview', + label: 'App review overview - Make Developer Hub', + asOf: '2026-09-15', }, ], }, @@ -773,17 +784,17 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/mcp', label: 'Make MCP Server | Make', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/get-started-with-make-mcp-server', label: 'Get started with Make MCP server - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/mcp-toolboxes', label: 'MCP toolboxes - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -800,21 +811,22 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, entryPaidPlan: { - value: 'Core plan. $12/month for 10,000 credits/month (lowest listed price point)', + value: + 'Core plan: $16/month if billed monthly, or $12/month if billed annually (Make discounts annual billing 15%+, paid upfront for the year) — for 10,000 credits/month, the lowest listed price point either way.', detail: 'Core adds over Free: unlimited active scenarios, scheduled scenarios down to 1-minute intervals, increased data transfer/file-size limits (5GB/100MB), and access to the Make API.', - shortValue: 'Core plan, $12/mo for 10,000 credits', + shortValue: 'Core plan, $16/mo monthly or $12/mo billed annually, 10,000 credits', confidence: 'verified', sources: [ { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -828,7 +840,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -843,7 +855,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -860,17 +872,17 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/security', label: 'Make Security page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/privacy-and-gdpr', label: 'Make.com GDPR | General Data Protection Regulation | Make', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://community.make.com/t/information-security-compliance-soc2-iso27001-hipaa-etc/8052', label: 'Information Security Compliance (SOC2, ISO27001, HIPAA, etc.) - Make Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -885,12 +897,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/security', label: 'Make Security page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/organizations', label: 'Make Organizations help doc', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -905,7 +917,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -920,12 +932,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/security', label: 'Make Security page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -948,12 +960,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://community.make.com/t/connections-and-keys-access-management-within-teams/51912', label: 'Connections and Keys access management within teams - Make Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/white-label-documentation/manage-organizations-and-teams/manage-instance-level-user-access-roles', label: 'Manage instance-level user access roles - Make Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -968,12 +980,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://developers.make.com/white-label-documentation/customize-your-instance/rebrand-your-instance', label: 'Rebrand your instance - Make White Label Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/white-label-documentation', label: 'Make White Label - Make Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -988,12 +1000,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/scenario-history', label: 'Scenario history - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/white-label-documentation/manage-the-end-user-life-cycle/provision-new-users/define-the-organizations-license', label: "Define the organization's license - Make White Label Developer Hub", - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1017,12 +1029,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/single-sign-on', label: 'Single Sign-on - Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/white-label-documentation/manage-login/configure-single-sign-on', label: 'Configure Single Sign-on - Make White Label Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1046,7 +1058,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/set-the-length-of-your-session-timeout', label: 'Set the length of your session timeout - Make Help Center', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -1061,12 +1073,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://developers.make.com/custom-apps-documentation/app-review/overview', label: 'App review overview - Make Developer Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://developers.make.com/custom-apps-documentation/app-review/prerequisites', label: 'App review prerequisites - Make Developer Hub', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1083,12 +1095,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/scenario-history', label: 'Scenario history | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/help/scenarios/scenario-execution-history', label: 'Scenario execution history | Make', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1103,17 +1115,17 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/automatic-retry-of-incomplete-executions', label: 'Automatic retry of incomplete executions | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/incomplete-executions', label: 'Incomplete executions | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/manage-incomplete-executions', label: 'Manage incomplete executions | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1128,7 +1140,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/manage-your-email-preferences', label: 'Manage your email preferences | Make Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/introduction-to-errors-and-warnings', @@ -1138,7 +1150,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://community.make.com/t/how-to-set-a-operation-threshold-warning-per-scenario/38251', label: 'How to set an operation threshold/warning per scenario - Make Community', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1162,25 +1174,25 @@ export const makeProfile: CompetitorProfile = { { url: 'https://developers.make.com/mcp-server', label: 'Make MCP Server docs (40-minute background run, retrieve output after finish)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/webhooks', label: 'Make Help Center: Webhooks (instant parallel processing, default response codes)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/incomplete-executions', label: 'Make Help Center: Incomplete executions (stores unfinished runs for later resolution)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, executionLimits: { value: - "Make's MCP Server enforces a per-call timeout of 25 seconds (OAuth authentication) or 40 seconds (MCP token authentication) before returning a timeout response, after which the called scenario continues running for up to 40 minutes in the background. Make does not publish a general per-module/API-call timeout figure or documented concurrent-execution caps per plan tier; the commonly cited ~40-second module timeout is user-reported, not officially documented. Make lets admins cap how many instant-trigger scenario runs can start per minute, a configurable rate limit available on all plans, though no specific default number is published.", + "Make's MCP Server enforces a per-call timeout of 25 seconds (OAuth authentication) or 40 seconds (MCP token authentication) before returning a timeout response, after which the called scenario continues running for up to 40 minutes in the background. Separately, Make's pricing page publishes a per-scenario execution-time ceiling of its own ('Maximum scenario execution time'): 5 minutes on Free and 40 minutes on Core, Pro, Teams, and Enterprise — a scenario-level limit distinct from any single module's timeout. Make does not publish a general per-module/API-call timeout figure separate from this scenario-level ceiling, nor documented concurrent-execution caps per plan tier; the commonly cited ~40-second module timeout is user-reported, not officially documented. Make lets admins cap how many instant-trigger scenario runs can start per minute, a configurable rate limit available on all plans, though no specific default number is published.", detail: "Per Make's MCP Server docs, the timeout before a timeout response is returned depends on the authentication method: 25 seconds for OAuth, 40 seconds for an MCP token; the called scenario itself keeps running in the background for up to 40 minutes. help.make.com/scenario-settings, sometimes cited for general module/API-call execution limits, does not document any timeout figure at all. Admins can cap instant-trigger scenario starts per minute via help.make.com/scenario-rate-limits-for-instant-triggers, but that page does not state a specific default numeric ceiling, and Make does not publicly document concurrent-execution-count limits per plan tier.", shortValue: @@ -1190,17 +1202,22 @@ export const makeProfile: CompetitorProfile = { { url: 'https://developers.make.com/mcp-server', label: 'Make MCP Server docs: 25s/40s call timeout, 40-minute background run', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://help.make.com/scenario-rate-limits-for-instant-triggers', label: 'Make Help Center: Scenario rate limits for instant triggers', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://help.make.com/scenario-settings', label: 'Make Help Center: Scenario settings (no documented timeout figure)', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://www.make.com/en/pricing', + label: 'Make Pricing page (Maximum scenario execution time by plan)', + asOf: '2026-09-15', }, ], }, @@ -1215,12 +1232,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://help.make.com/error-handlers', label: 'Make Help Center: Error handlers (directive list)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/resume-error-handler', label: 'Make Help Center: Resume error handler', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.make.com/overview-of-error-handling', @@ -1240,12 +1257,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/security', label: 'Make Security page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/on-prem-agents', label: 'Make on-prem agents page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1262,7 +1279,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/pricing', label: 'Make Pricing page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1277,7 +1294,7 @@ export const makeProfile: CompetitorProfile = { { url: 'https://www.make.com/en/security', label: 'Make Security page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1294,14 +1311,14 @@ export const makeProfile: CompetitorProfile = { value: 'Founded 2012 (as Integromat, Prague, Czech Republic; bootstrapped, no VC rounds); acquired by Celonis for $100M+ in October 2020; rebranded to Make in 2022; operates as a business unit of Celonis, whose parent has raised ~$1.77B and is valued at ~$11-13B with 3,000+ employees (2024/2026 figures)', detail: - "Integromat was conceived in 2012 by Patrik Šimek in Prague and launched publicly in 2016. It grew to roughly $10M revenue entirely bootstrapped, with no VC funding raised, before Celonis (Germany/US) acquired it in October 2020 for a reported $100M+. TechCrunch's acquisition-day coverage cites 'more than 11,000 customers,' while a separate Latka estimate for the same year puts total registered users at 250K, a gap likely reflecting paying customers versus all signups rather than a contradiction. Sixteen months later, in February 2022, it was rebranded as 'Make' and now operates as a business unit within Celonis. Make has not disclosed separate headcount or funding figures as a standalone entity. Parent company Celonis (founded 2011 by Alex Rinke, Bastian Nominacher, and Martin Klenk) has raised approximately $1.77B in total funding, is valued at an estimated $11-13B, and reported 3,000+ staff across 20+ offices as of 2024.", + "Integromat was conceived in 2012 by Patrik Šimek in Prague and launched publicly in 2016. It grew to roughly $10M revenue entirely bootstrapped, with no VC funding raised, before Celonis (Germany/US) acquired it in October 2020 for a reported $100M+. TechCrunch's acquisition-day coverage cites 'more than 11,000 customers,' while a separate Latka estimate for the same year puts total registered users at 250K, a gap likely reflecting paying customers versus all signups rather than a contradiction. Sixteen months later, in February 2022, it was rebranded as 'Make' and now operates as a business unit within Celonis. Make has not disclosed separate headcount or funding figures as a standalone entity. Parent company Celonis (founded 2011 by Alex Rinke, Bastian Nominacher, and Martin Klenk) has raised approximately $1.77B in total funding, is valued at an estimated $11-13B, and reported 3,000+ staff as of its most recent disclosed figures; Wikipedia's infobox separately lists 17 office locations, but only as of 2021, with no more recent location count publicly available.", shortValue: 'Founded 2012, acquired by Celonis in 2020', confidence: 'verified', sources: [ { url: 'https://techcrunch.com/2020/10/14/celonis-acquires-czech-startup-integromat-to-accelerate-move-to-process-automation/', label: 'Celonis acquires Czech startup Integromat | TechCrunch', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.businesswire.com/news/home/20220222005231/en/Integromat-Evolves-to-Make-Expanding-Its-Vision-to-Empower-Creators-to-Innovate-Without-Limits', @@ -1311,12 +1328,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://en.wikipedia.org/wiki/Celonis', label: 'Celonis - Wikipedia', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://getlatka.com/companies/integromat', label: 'How Integromat hit $10M revenue and 250K customers in 2020 | Latka', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1331,12 +1348,12 @@ export const makeProfile: CompetitorProfile = { { url: 'https://academy.make.com/', label: 'Make Academy', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.make.com/en/blog/learn-automation-make-academy', label: 'Learning Automation: Introducing the New Make Academy', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts b/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts index e7cfad33621..11df45572c0 100644 --- a/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts +++ b/apps/sim/lib/compare/data/competitors/microsoft-copilot.ts @@ -44,13 +44,14 @@ export const microsoftCopilotProfile: CompetitorProfile = { { title: 'Automatic fallback to a default model if a selected model is disabled', description: - "If an admin disables a non-default model tenant-wide, Copilot Studio automatically falls back to the default OpenAI model rather than failing the request. Admins choose among OpenAI GPT models, Anthropic Claude Sonnet 4 and Opus 4.1, any model in the Azure AI Model Catalog, or a bring-your-own-model connection to an Azure AI Foundry deployment, but Sim's own model-fallback only retries the same model with hosted keys, not a cross-model fallback like this.", + "If an admin disables a non-default model tenant-wide, Copilot Studio automatically falls back to the default OpenAI model rather than failing the request. Admins choose among OpenAI GPT models, Anthropic Claude models (currently Claude Sonnet 4.6, Claude Sonnet 5, and Claude Opus 4.6/4.7), any model in the Azure AI Model Catalog, or a bring-your-own-model connection to an Azure AI Foundry deployment, but Sim's own model-fallback only retries the same model with hosted keys, not a cross-model fallback like this.", shortDescription: 'Falls back to the default OpenAI model automatically if a selected model is disabled.', source: { - url: 'https://www.microsoft.com/en-us/microsoft-copilot/blog/copilot-studio/anthropic-joins-the-multi-model-lineup-in-microsoft-copilot-studio/', - label: 'Anthropic joins the multi-model lineup in Microsoft Copilot Studio', - asOf: '2026-07-02', + url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-select-agent-model', + label: + 'Select a primary AI model for your agent - Microsoft Copilot Studio | Microsoft Learn', + asOf: '2026-09-15', }, }, { @@ -81,29 +82,28 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, { title: - 'Full ALM tooling (pipelines, environment variables) is gated to solution-aware agents', + "Full ALM tooling (pipelines, environment variables) requires moving an agent out of the tenant's shared Default Solution", description: - 'Version history, environment promotion via pipelines, and environment variables only apply to agents built inside a Dataverse solution. Agents created outside a solution, the common default for individual makers experimenting in Copilot Studio, get none of this ALM tooling.', + "Version history, environment promotion via pipelines, and environment variables only apply to agents managed inside a custom Dataverse solution. Every agent is automatically placed in the environment's shared Default Solution when it's created — the common state for individual makers experimenting in Copilot Studio — and Microsoft's own ALM guidance treats that default solution as not fully participating in pipeline-based promotion and environment-variable tooling the way a custom solution does.", shortDescription: - 'Pipelines and environment-variable promotion require building inside a solution.', + 'Pipelines and environment-variable promotion require moving an agent out of the shared Default Solution into a custom one.', source: { - url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/alm', - label: - 'Establish an Application Lifecycle Management (ALM) strategy - Microsoft Copilot Studio | Microsoft Learn', - asOf: '2026-07-02', + url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-solutions-overview', + label: 'Create and manage custom solutions - Microsoft Copilot Studio | Microsoft Learn', + asOf: '2026-09-15', }, }, { - title: 'Session transcript detail defaults to a 29-day window', + title: 'Session transcript detail defaults to a 28-day window', description: - "An agent's per-session transcripts, showing which topic fired, tools called, and knowledge consulted, are downloadable from the Analytics area for roughly the last 29 days by default. Retaining that detail longer requires a separate export pipeline, not a built-in retention setting.", + "An agent's per-session transcripts, showing which topic fired, tools called, and knowledge consulted, are downloadable from the Analytics area for roughly the last 28 days by default. Retaining that detail longer requires a separate export pipeline, not a built-in retention setting.", shortDescription: - 'Detailed session transcripts default to ~29 days; longer retention needs a manual export.', + 'Detailed session transcripts default to ~28 days; longer retention needs a manual export.', source: { url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-transcripts-studio', label: 'Understand downloaded session data from Copilot Studio - Microsoft Copilot Studio | Microsoft Learn', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -278,7 +278,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, versionControlDepth: { value: - 'Solution-based promotion with Git integration and pipelines for solution-aware agents; no visual diff/compare view between two agent versions, and this ALM tooling does not apply to agents built outside a solution', + "Solution-based promotion with Git integration and pipelines for solution-aware agents; no visual diff/compare view between two agent versions, and this ALM tooling does not extend to agents left in the environment's shared Default Solution rather than moved into a custom one", detail: 'Git integration lets a solution connect to a repository for version control and collaboration, and pipelines automate deployment between environments, but there is no dedicated side-by-side version-diff UI for an individual agent.', shortValue: 'Git-backed solution promotion, no visual diff view found', @@ -288,7 +288,13 @@ export const microsoftCopilotProfile: CompetitorProfile = { url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/alm', label: 'Establish an Application Lifecycle Management (ALM) strategy - Microsoft Copilot Studio | Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-solutions-overview', + label: + 'Create and manage custom solutions - Microsoft Copilot Studio | Microsoft Learn', + asOf: '2026-09-15', }, ], }, @@ -407,7 +413,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { aiCapabilities: { multiLlmSupport: { value: - 'Yes: agents can use OpenAI GPT models, Anthropic Claude Sonnet 4 and Opus 4.1, any model in the Azure AI Model Catalog, or a bring-your-own Azure AI Foundry model deployment for individual prompts', + "Yes: agents can use OpenAI GPT models (GPT-4.1 as the current tenant Default, plus GA models such as GPT-5 Chat and GPT-5.5 Chat, and preview/experimental models such as GPT-5 Reasoning, GPT-5 Auto, and GPT-5.5 Reasoning), Anthropic Claude models (the current GA lineup, including Claude Sonnet 4.6, Claude Sonnet 5, and Claude Opus 4.6/4.7; Microsoft periodically advances this lineup as newer versions supersede older ones, such as Claude Sonnet 4 and Opus 4.1, which no longer appear in Microsoft's current model table), external models from xAI and Mistral, any model in the Azure AI Model Catalog, or a bring-your-own Azure AI Foundry model deployment for individual prompts", detail: 'Admins enable or restrict non-default models tenant-wide in the Microsoft 365 Admin Center. If a selected alternate model is disabled or unavailable, agents fall back automatically to the default OpenAI model. Google Gemini is not supported.', shortValue: 'OpenAI, Anthropic Claude, Azure AI Model Catalog, or bring-your-own model', @@ -424,6 +430,12 @@ export const microsoftCopilotProfile: CompetitorProfile = { 'Bring your own model for your prompts - Microsoft Copilot Studio | Microsoft Learn', asOf: '2026-07-02', }, + { + url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-select-agent-model', + label: + 'Select a primary AI model for your agent - Microsoft Copilot Studio | Microsoft Learn', + asOf: '2026-09-15', + }, ], }, agentReasoningBlocks: { @@ -581,10 +593,11 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, modelFallback: { value: - 'Yes: Copilot Studio automatically falls back to the default OpenAI GPT-4o model when a selected alternate model, such as Anthropic Claude, is disabled or unavailable for the tenant', + "Yes: Copilot Studio automatically falls back to whichever model currently carries the tenant's 'Default' release tag when a selected alternate model, such as an Anthropic Claude model, is disabled or unavailable for the tenant. Microsoft documents a defined model-lifecycle taxonomy (Default, Generally Available, Preview, Experimental, Retired) and periodically promotes a newer generally-available model to the Default tag as it matures, retiring the previous one; as of September 2026, GPT-4.1 holds the Default tag after GPT-4o's retirement, illustrating that the specific fallback model changes over time rather than remaining permanently GPT-4o.", detail: 'This is a multi-model fallback behavior, not a broader multi-provider retry-on-rate-limit policy beyond that single fallback path.', - shortValue: 'Falls back to the default OpenAI GPT-4o model automatically', + shortValue: + "Falls back to whichever model currently holds the tenant's 'Default' tag, not permanently GPT-4o", confidence: 'verified', sources: [ { @@ -592,6 +605,12 @@ export const microsoftCopilotProfile: CompetitorProfile = { label: 'Anthropic joins the multi-model lineup in Microsoft Copilot Studio', asOf: '2026-07-02', }, + { + url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-select-agent-model', + label: + 'Select a primary AI model for your agent - Microsoft Copilot Studio | Microsoft Learn', + asOf: '2026-09-15', + }, ], }, agentSkills: { @@ -630,6 +649,11 @@ export const microsoftCopilotProfile: CompetitorProfile = { 'Publish an agent to Azure Bot Service channels - Microsoft Copilot Studio | Microsoft Learn', asOf: '2026-07-02', }, + { + url: 'https://learn.microsoft.com/en-us/power-pages/getting-started/enable-agent', + label: 'Add an agent from the setup workspace - Power Pages | Microsoft Learn', + asOf: '2026-09-15', + }, ], }, kbChunkVisibility: { @@ -867,7 +891,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { { url: 'https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/copilot-studio', label: 'Microsoft 365 Copilot Pricing - AI Agents | Copilot Studio', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -906,9 +930,9 @@ export const microsoftCopilotProfile: CompetitorProfile = { security: { compliance: { value: - 'Yes: Copilot Studio (listed by its former name, "Copilot Studios") is one of the Microsoft online services explicitly in scope of the Office 365 SOC 2 Type 2 attestation report, and is separately certified under HIPAA (Business Associate Agreement), HITRUST CSF, FedRAMP, multiple ISO standards (9001, 20000-1, 22301, 27001, 27017, 27018, 27701), PCI DSS, CSA STAR, UK G-Cloud, Singapore MTCS Level 3, Korea K-ISMS, and Spain ENS, with an audit report for each available from the Microsoft Service Trust Portal', + 'Yes: Copilot Studio (listed by its former name, "Copilot Studios") is one of the Microsoft online services in scope of the Azure SOC 2 Type 2 attestation report per Microsoft\'s SOC 2 compliance offering page, and is separately certified under HIPAA (Business Associate Agreement), HITRUST CSF, FedRAMP, multiple ISO standards (9001, 20000-1, 22301, 27001, 27017, 27018, 27701), PCI DSS, CSA STAR, UK G-Cloud, Singapore MTCS Level 3, Korea K-ISMS, and Spain ENS, with an audit report for each available from the Microsoft Service Trust Portal', detail: - 'Copilot Studio\'s own admin-certification page confirms SOC compliance without naming the specific report type, but Microsoft\'s dedicated SOC 2 Type 2 compliance offering page lists "Copilot Studios" by name among the in-scope Office 365 services, resolving which SOC report type applies. The wider certification list is the full set published on that admin-certification page, where each certification links to a corresponding audit report or certificate.', + 'Copilot Studio\'s own admin-certification page confirms SOC compliance without naming the specific report type, but Microsoft\'s dedicated SOC 2 Type 2 compliance offering page lists "Copilot Studios" by name among the Microsoft online services in scope of the Azure SOC 2 Type 2 attestation report (a separate, more granular Office 365-specific applicability table on the same page does not itemize Copilot Studios by environment), resolving which SOC report type applies. The wider certification list is the full set published on that admin-certification page, where each certification links to a corresponding audit report or certificate.', shortValue: 'SOC 2 Type 2, HIPAA, FedRAMP, ISO, PCI DSS', confidence: 'verified', sources: [ @@ -921,7 +945,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { { url: 'https://learn.microsoft.com/en-us/compliance/regulatory/offering-soc-2', label: 'SOC 2 Type 2 - Microsoft Compliance | Microsoft Learn', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -1028,18 +1052,18 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, dataRetention: { value: - 'Partial: conversation transcripts downloaded directly from Copilot Studio only cover the past 29 days, while the underlying Dataverse conversation-transcript and custom-analytics tables default to a 30-day retention period; extending retention beyond that default requires either an admin changing the Dataverse retention setting or exporting the data via Azure Synapse Link for Dataverse into Azure Data Lake Storage Gen2', + 'Partial: conversation transcripts downloaded directly from Copilot Studio only cover the past 28 days, while the underlying Dataverse conversation-transcript and custom-analytics tables default to a 30-day retention period; extending retention beyond that default requires either an admin changing the Dataverse retention setting or exporting the data via Azure Synapse Link for Dataverse into Azure Data Lake Storage Gen2', detail: - "Copilot Studio's own download experience is capped at the past 29 days regardless of the underlying Dataverse retention window. Microsoft's custom-analytics guidance documents the 30-day default retention on the Dataverse-side bot/botcomponent/conversationtranscript tables and recommends Synapse Link as the export path for longer-term or custom-reporting needs.", + "Copilot Studio's own download experience is capped at the past 28 days regardless of the underlying Dataverse retention window. Microsoft's custom-analytics guidance documents the 30-day default retention on the Dataverse-side bot/botcomponent/conversationtranscript tables and recommends Synapse Link as the export path for longer-term or custom-reporting needs.", shortValue: - '29-day direct download; 30-day default Dataverse retention, extendable via export', + '28-day direct download; 30-day default Dataverse retention, extendable via export', confidence: 'verified', sources: [ { url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-transcripts-studio', label: 'Understand downloaded session data from Copilot Studio - Microsoft Copilot Studio | Microsoft Learn', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/custom-analytics-strategy', @@ -1051,17 +1075,24 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, piiRedaction: { value: - 'Yes, but as a block rather than in-line redaction: Microsoft Purview inline Data Loss Prevention for Copilot Studio agents (public preview) scans prompts sent to an agent in real time for Sensitive Information Types (SSNs, credit card numbers, custom types), and blocks the prompt from being processed, with no AI response generated, if one is detected before the agent is invoked.', + "Partial, and narrower than a general Copilot Studio capability: Microsoft's dedicated Copilot Studio-Purview integration guidance documents only a sensitivity-label-based Endpoint DLP restriction for Copilot Studio agents — it applies only when an agent's knowledge source is SharePoint and only when the agent is published to Microsoft Teams, SharePoint, or Microsoft 365 Copilot, and it blocks processing of content carrying a specified sensitivity label rather than scanning free-text prompts for Sensitive Information Types. The broader feature that scans any prompt for SITs (SSNs, credit card numbers, custom types) and blocks it before a response is generated is documented for the general 'Microsoft 365 Copilot and Copilot Chat' experience; Microsoft's Copilot Studio-specific reference page does not list that capability as supported for standalone Copilot Studio agents on other knowledge sources or channels, such as a website widget.", detail: - 'This stops sensitive content from reaching the agent at all rather than redacting it in-line and continuing. It is configured as a Purview DLP policy targeting the Copilot Studio location, separate from the product itself.', - shortValue: 'Purview inline DLP blocks prompts containing detected PII before invocation', + "The general SIT-scanning-and-blocking capability is configured as a Purview DLP policy targeting the 'Microsoft 365 Copilot and Copilot Chat' policy location, which Microsoft's dedicated Copilot Studio-Purview reference page does not list as a supported capability for Copilot Studio agents. The narrower, confirmed Copilot Studio capability instead uses Endpoint DLP with a sensitivity-label condition, gated to a SharePoint knowledge source and to agents published on Teams, SharePoint, or Microsoft 365 Copilot, and it blocks based on a label rather than scanning prompt text for SITs.", + shortValue: + 'Confirmed only for SharePoint-scoped sensitivity labels, not general SIT prompt scanning', confidence: 'verified', sources: [ { url: 'https://learn.microsoft.com/en-us/purview/dlp-microsoft365-copilot-location-learn-about', label: 'Microsoft Purview DLP for Microsoft 365 Copilot and Copilot Chat | Microsoft Learn', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://learn.microsoft.com/en-us/purview/ai-copilot-studio', + label: + 'Use Microsoft Purview to manage data security & compliance for Microsoft Copilot Studio | Microsoft Learn', + asOf: '2026-09-15', }, ], }, @@ -1151,7 +1182,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { value: 'Yes: per-session conversation transcripts show which topic fired, which knowledge sources were consulted, which tools were called, which child agents or MCP servers were invoked, what the orchestration plan was, and how long each step took, alongside an Analytics dashboard with conversation volume, engagement, satisfaction, and response-quality metrics over time', detail: - 'Telemetry can additionally be sent to Azure Monitor Application Insights, where a dedicated Copilot Studio dashboard workbook surfaces total conversations, latency, exceptions, tool usage, and topic analytics in one view for deeper analysis.', + 'Telemetry can additionally be sent to Azure Monitor Application Insights, where a dedicated Copilot Studio dashboard workbook surfaces total conversations, latency, exceptions, tool usage, and topic analytics in one view for deeper analysis. The Copilot Studio dashboard workbook itself is currently a preview feature within Application Insights.', shortValue: 'Per-session traces (topic/tools/knowledge/timing) plus a metrics dashboard', confidence: 'verified', sources: [ @@ -1159,13 +1190,13 @@ export const microsoftCopilotProfile: CompetitorProfile = { url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/agents-experience/analytics-overview', label: 'Monitor an agent overview (preview) - Microsoft Copilot Studio | Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-bot-framework-composer-capture-telemetry', label: 'Capture telemetry with Application Insights - Microsoft Copilot Studio | Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1318,7 +1349,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { { url: 'https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1', label: 'Service Level Agreements (SLA) for Online Services - Microsoft Licensing', - asOf: '2026-07-04', + asOf: '2026-09-15', }, { url: 'https://windowsnews.ai/article/microsoft-365-copilot-outage-exposes-ai-reliability-gaps-in-enterprise-slas.425641', @@ -1345,7 +1376,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { }, companyMaturity: { value: - 'Microsoft Corporation. Founded April 4, 1975. Approximately 228,000 employees. Market capitalization approximately $2.8 trillion USD. Publicly traded (NASDAQ: MSFT) with quarterly revenue in the $80B+ range as of FY2026 SEC filings', + 'Microsoft Corporation. Founded April 4, 1975. Approximately 228,000 employees. Market capitalization approximately $3.7 trillion USD as of September 2026. Publicly traded (NASDAQ: MSFT) with quarterly revenue in the $80B+ range as of FY2026 SEC filings', detail: "Copilot Studio is a product within Microsoft's Power Platform/Business Applications segment, backed by Microsoft's overall corporate scale, not an independent startup.", shortValue: 'Microsoft Corporation. Public, ~228,000 employees', @@ -1359,7 +1390,7 @@ export const microsoftCopilotProfile: CompetitorProfile = { { url: 'https://stockanalysis.com/stocks/msft/market-cap/', label: 'Microsoft (MSFT) Market Cap - StockAnalysis.com', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/n8n.ts b/apps/sim/lib/compare/data/competitors/n8n.ts index 853556e1e1b..d580dfcca32 100644 --- a/apps/sim/lib/compare/data/competitors/n8n.ts +++ b/apps/sim/lib/compare/data/competitors/n8n.ts @@ -86,22 +86,24 @@ export const n8nProfile: CompetitorProfile = { ], limitations: [ { - title: 'AI Workflow Builder not yet available self-hosted or on Enterprise', + title: + 'n8n Assistant (formerly AI Workflow Builder) still excludes Enterprise, on Cloud and self-hosted alike', description: - 'The natural-language-to-workflow AI Workflow Builder is in beta and limited to Cloud Trial/Starter/Pro plans. Enterprise and self-hosted support is listed as planned for a future release, so self-hosters cannot use it today.', - shortDescription: "Beta AI builder is Cloud-only today; self-hosters can't use it.", + "n8n's natural-language-to-workflow feature, originally shipped as the AI Workflow Builder in October 2025 beta, was relaunched in July 2026 as 'n8n Assistant' and remains labeled Preview rather than general availability. It is documented as available on n8n Cloud Starter and Pro, and on self-hosted Community, Registered Community, and Business editions (self-hosted use is bring-your-own-key, since n8n's Gateway credits do not extend to self-hosted instances). It is explicitly not available on n8n Cloud Enterprise or self-hosted Enterprise; n8n directs Enterprise customers to contact their Customer Success Manager for preview access.", + shortDescription: + 'Preview now reaches self-hosted Community/Business; Enterprise (Cloud and self-hosted) still excluded.', source: { - url: 'https://community.n8n.io/t/introducing-ai-workflow-builder-beta/204919', - label: 'n8n Community: Introducing AI Workflow Builder (Beta)', - asOf: '2026-07-02', + url: 'https://docs.n8n.io/build/ways-of-building-workflows/ai-assistant-preview', + label: 'n8n Docs: Use n8n Assistant (Preview)', + asOf: '2026-09-15', }, }, { title: "No public SOC 2 report; only 'aligned to' SOC 2", description: - "n8n's security program is 'aligned to' the SOC 2 framework with annual independent audits, and the SOC 2 report is available to enterprise customers via the Trust Center, not published publicly.", + "n8n's security page (n8n.io/legal/security/) describes the company's security program as 'aligned to' the SOC 2 framework, with continuous evaluation and annual independent audits. The Trust Center (trust.n8n.io) separately lists SOC 2 Type 2 as an achieved compliance certification, but the SOC 2 report itself sits behind an email-gated 'Get access' request rather than being freely downloadable — unlike the SOC 3 report, which n8n's security page offers as a direct public download.", shortDescription: 'SOC 2 report is available only on request to enterprise customers.', - source: { url: 'https://trust.n8n.io/', label: 'n8n Trust Center', asOf: '2026-07-02' }, + source: { url: 'https://trust.n8n.io/', label: 'n8n Trust Center', asOf: '2026-09-15' }, }, { title: 'No RBAC or workflow sharing at all on the free Community edition', @@ -127,20 +129,25 @@ export const n8nProfile: CompetitorProfile = { builderType: { value: 'Hybrid visual/code node-based builder', detail: - "n8n's core interface is a visual, drag-and-drop node canvas where each node is a step. It supports a Custom Code node (JavaScript/Python) and an HTTP Request Tool for arbitrary API calls, plus a natural-language AI Workflow Builder, gated by pricing tier rather than a beta flag, that generates an editable draft workflow from a text prompt.", + "n8n's core interface is a visual, drag-and-drop node canvas where each node is a step. It supports a Custom Code node (JavaScript/Python) and an HTTP Request Tool for arbitrary API calls, plus a natural-language builder — the AI Workflow Builder, relaunched in July 2026 as 'n8n Assistant' — that generates an editable draft workflow from a text prompt. Far from being gated by pricing tier alone, it is still explicitly labeled Preview (not GA) and is itself the beta-style gate: it is documented as available on Cloud Starter/Pro and self-hosted Community/Registered Community/Business, but not on Cloud or self-hosted Enterprise.", shortValue: 'Visual canvas plus code node and AI builder', confidence: 'verified', sources: [ { url: 'https://docs.n8n.io/build/ways-of-building-workflows/ai-workflow-builder', label: 'n8n AI Workflow Builder docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.code', label: 'n8n Code node docs', asOf: '2026-07-08', }, + { + url: 'https://docs.n8n.io/build/ways-of-building-workflows/ai-assistant-preview', + label: 'n8n Docs: Use n8n Assistant (Preview)', + asOf: '2026-09-15', + }, ], }, learningCurve: { @@ -297,19 +304,19 @@ export const n8nProfile: CompetitorProfile = { value: 'Yes: n8n has a native Data Table feature (Data Table node, DataTable API, and a Data tables UI tab) for creating and managing structured tables of rows and columns directly inside an n8n instance, without an external database.', detail: - "Storage is capped at 50MB per instance by default (self-hosted instances can raise this via the N8N_DATA_TABLES_MAX_SIZE_BYTES environment variable); direct programmatic access from a Code node isn't supported. Spreadsheet-style keyboard navigation isn't explicitly documented.", + "Storage is capped at 200 MiB per instance by default, shared across all data tables combined (not per table); self-hosted instances can raise this via the N8N_DATA_TABLES_MAX_SIZE_BYTES environment variable. n8n shows a warning at 80% of the limit and a final warning at the limit itself; past that point manual row additions are disabled and workflow executions that try to insert or update data start failing. Direct programmatic access from a Code node isn't supported. Spreadsheet-style keyboard navigation isn't explicitly documented.", shortValue: 'Yes, native Data Table feature', confidence: 'verified', sources: [ { url: 'https://docs.n8n.io/build/work-with-data/data-tables.md', label: 'Data tables | n8n Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.datatable', label: 'Data Table | Nodes | n8n Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -411,10 +418,11 @@ export const n8nProfile: CompetitorProfile = { }, naturalLanguageBuilding: { value: - 'Yes: AI Workflow Builder, generally available on Starter, Pro, and Enterprise Cloud', + "Partial: relaunched as 'n8n Assistant,' still in Preview (not GA); available on Cloud Starter/Pro and self-hosted Community/Registered Community/Business, not on Cloud or self-hosted Enterprise", detail: - 'Users describe a workflow in plain text and the AI Workflow Builder generates a draft, editable node-based workflow with iterative multi-turn refinement. Launched in beta in late 2025, it reached general availability for n8n Cloud customers on the Starter, Pro, and Enterprise plans; self-hosted availability is not documented.', - shortValue: 'GA on Starter/Pro/Enterprise Cloud plans', + "Users describe a workflow, edit, debug request, or agent in plain text; the assistant plans it, builds or edits it in the selected project, tests it, and helps fix errors, producing a normal, fully editable n8n workflow. Launched in beta in October 2025 as the 'AI Workflow Builder' on Cloud Trial/Starter/Pro, it reportedly reached Starter/Pro/Enterprise Cloud general availability by January 2026 per n8n's blog, but n8n relaunched it in July 2026 as 'n8n Assistant,' explicitly still labeled Preview. Current documented availability is n8n Cloud Starter and Pro, and self-hosted Community, Registered Community, and Business editions (self-hosted access is bring-your-own-key). It is not yet available on n8n Cloud Enterprise or self-hosted Enterprise; n8n directs Enterprise customers to their Customer Success Manager for preview access.", + shortValue: + 'Preview on Cloud Starter/Pro and self-hosted (not Enterprise); GA claim is stale', confidence: 'verified', sources: [ { @@ -425,7 +433,12 @@ export const n8nProfile: CompetitorProfile = { { url: 'https://docs.n8n.io/build/ways-of-building-workflows/ai-workflow-builder', label: 'n8n AI Workflow Builder docs', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://docs.n8n.io/build/ways-of-building-workflows/ai-assistant-preview', + label: 'n8n Docs: Use n8n Assistant (Preview)', + asOf: '2026-09-15', }, ], }, @@ -482,21 +495,32 @@ export const n8nProfile: CompetitorProfile = { ], }, humanInTheLoop: { - value: 'Yes: dedicated Human-in-the-Loop node built on Wait', + value: + "Yes: human approval gates exist in two forms — an AI-Agent tool-review step (Approve/Deny) and a 'Send and Wait for a Response' operation on communication nodes, both built on the underlying Wait mechanism", detail: - "n8n has a dedicated Human-in-the-Loop node (a higher-level abstraction built on the underlying Wait node) that pauses an active workflow mid-run and waits on human approval or input, distinct from a plain delay. The approver is notified via a configurable channel, Gmail, Slack, Telegram, Discord, Microsoft Teams, WhatsApp, or n8n's built-in Chat, with 'Approve Only' or 'Approve and Disapprove' options. The run resumes when the reviewer responds via a button or webhook callback, and an optional timeout triggers a fallback path if no response arrives within the configured window (minutes up to a day).", - shortValue: 'Dedicated approval node with timeout fallback', + "For AI Agent tool calls, a Tools Panel human-review step pauses the agent before it runs a chosen tool and requests Approve/Deny through a configurable channel (n8n Chat, Slack, Discord, Telegram, Microsoft Teams, Gmail, WhatsApp Business Cloud, Google Chat, or Microsoft Outlook). Separately, the 'Send and Wait for a Response' operation — available on Discord, Slack, Gmail, Telegram, and other communication nodes — pauses the whole workflow and offers an Approval response type with either an approval-only button or both approval and disapproval buttons, a configurable Limit Wait Time, and resumption via the reviewer's button click (a webhook callback under the hood, per n8n's queue-mode docs on '/webhook-waiting' endpoints).", + shortValue: 'Two approval mechanisms: tool-review gate and Send and Wait', confidence: 'verified', sources: [ { url: 'https://docs.n8n.io/advanced-ai/human-in-the-loop-tools/', label: 'Human-in-the-loop for AI tool calls | n8n Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.n8n.io/build/integrate-ai/ai-examples/human-in-the-loop-for-tools', label: 'Human-in-the-loop for tools | Build | n8n Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.n8n.io/integrations/builtin/app-nodes/n8n-nodes-base.discord/', + label: 'Discord node docs (Send and Wait for a Response) | n8n Docs', + asOf: '2026-09-15', + }, + { + url: 'https://docs.n8n.io/hosting/scaling/queue-mode', + label: 'Enable queue mode (/webhook-waiting endpoints) | n8n Docs', + asOf: '2026-09-15', }, ], }, @@ -844,21 +868,27 @@ export const n8nProfile: CompetitorProfile = { }, byok: { value: - 'De facto yes: Chat Model nodes require users\' own provider API credentials, though n8n does not name this "BYOK"', + 'Partial: BYOK required on Enterprise and self-hosted, but n8n Cloud Starter and Pro now offer a hosted-key alternative (Gateway credits) for major Chat Model nodes', detail: - "n8n's OpenAI and Anthropic credential docs both walk users through generating an API key in the provider's own console and entering it as the node credential; no n8n-hosted key is supplied for these Chat Model nodes. Separately, n8n's pricing page describes plan-included 'AI credits' (2,300 on Starter, up to 13,700+ on higher tiers) for n8n's own in-app AI Assistant feature, which is distinct from the provider credentials Chat Model nodes require. n8n does not name a bring-your-own-API-key policy, but requiring each provider's own key for Chat Model nodes makes BYOK the de facto default for workflow-level LLM calls.", - shortValue: 'De facto via provider API keys, not named', - confidence: 'estimated', + "n8n's OpenAI and Anthropic credential docs walk users through generating an API key in the provider's own console and entering it as the node credential, and n8n's pricing page separately describes plan-included 'AI credits' (2,300 on Starter, up to 13,700+ on higher tiers) for n8n's own in-app AI Assistant feature, distinct from Chat Model node credentials. However, as of n8n 2.36.0, n8n Cloud Starter and Pro customers can select 'Use Gateway credits' directly in a supported node's credential field (OpenAI, Anthropic, Google Gemini, Qwen, MiniMax, and a growing list of others) to run that node against n8n's own prepaid, metered gateway with no provider account or API key. n8n Cloud Enterprise and self-hosted n8n do not have Gateway credits, so BYOK remains the only option there, and users can still choose 'Use my own credential' per node even where Gateway credits are available.", + shortValue: + 'BYOK required on Enterprise/self-hosted; Cloud Starter/Pro can use hosted Gateway credits', + confidence: 'verified', sources: [ { url: 'https://docs.n8n.io/integrations/builtin/credentials/openai', label: 'n8n docs: OpenAI credentials', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.n8n.io/integrations/builtin/credentials/anthropic', label: 'n8n docs: Anthropic credentials', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://docs.n8n.io/build/understand-workflows/use-gateway-credits', + label: 'n8n docs: Use Gateway credits', + asOf: '2026-09-15', }, ], }, @@ -1018,21 +1048,21 @@ export const n8nProfile: CompetitorProfile = { }, sso: { value: - "Yes: n8n supports SAML and OIDC single sign-on on Business/Enterprise plans, including automated user provisioning that assigns a user's instance role and project access from their identity-provider attributes on first login.", + "Yes: n8n supports SAML single sign-on on Business and Enterprise plans, and OIDC single sign-on on Enterprise plans only, both including automated user provisioning that assigns a user's instance role and project access from identity-provider attributes on first login.", detail: - 'Works with Okta, Azure AD, or any SAML-compliant IdP. The role/project mapping is driven by IdP attributes named n8n_instance_role and n8n_projects, and is documented as part of Enterprise governance features.', - shortValue: 'Yes, SAML/OIDC SSO with role auto-provisioning', + "SAML works with Okta, Azure AD, Auth0, Authentik, JumpCloud, Keycloak, PingIdentity, or any SAML-compliant IdP; OIDC works with any OpenID Connect-compliant IdP via a discovery endpoint, client ID, and client secret. The role/project mapping for both protocols is driven by IdP attributes named n8n_instance_role and n8n_projects, or by expression-based mapping rules defined inside n8n (available from n8n 2.19.0) when the IdP can't encode n8n-specific role logic, and is documented as part of Enterprise governance features.", + shortValue: 'SAML on Business/Enterprise; OIDC on Enterprise only', confidence: 'verified', sources: [ { url: 'https://docs.n8n.io/user-management/saml/setup/', label: 'Set up SAML | n8n Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.n8n.io/user-management/oidc/setup/', label: 'Set up OIDC | n8n Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://blog.n8n.io/introducing-custom-project-roles-and-user-provisioning-via-sso-built-for-enterprise-governance/', @@ -1101,14 +1131,14 @@ export const n8nProfile: CompetitorProfile = { value: 'Customer-facing Insights dashboard with per-workflow/per-node metrics, not span-level distributed tracing', detail: - "n8n ships a native, customer-facing 'Insights' dashboard (Pro, Business, and Enterprise plans) showing per-workflow tables of total production executions, failed executions, failure rate, time saved, and time-series trends including P95 execution duration, workflow error rate, and node error rate. This is dashboard/metrics-level observability, not fine-grained span/trace-level tracing of internal node execution. That requires exporting to external tools like OpenTelemetry, SigNoz, or Grafana, which n8n supports feeding but doesn't natively render as spans.", - shortValue: 'Dashboard metrics, not span-level tracing', + "n8n ships a native, customer-facing 'Insights' feature (summary banner on all plans/editions; full dashboard on Cloud Pro/Enterprise and self-hosted Business/Enterprise) showing, per workflow, total production executions, failed production executions, failure rate, time saved, and run time average (including wait-node time), with historical comparison windows up to a year on Enterprise. This is dashboard/metrics-level observability, not fine-grained span/trace-level tracing of internal node execution. That requires exporting to external tools like OpenTelemetry, SigNoz, or Grafana, which n8n supports feeding but doesn't natively render as spans.", + shortValue: 'Dashboard metrics (not P95/error-rate breakdowns), not span-level tracing', confidence: 'verified', sources: [ { url: 'https://docs.n8n.io/insights/', label: 'Insights | n8n Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://signoz.io/docs/n8n-monitoring/', @@ -1306,11 +1336,11 @@ export const n8nProfile: CompetitorProfile = { }, companyMaturity: { value: - 'Founded 2019 in Berlin. Raised a $180M Series C in October 2025 (Accel-led) at a $2.5B valuation, $240M total raised. Valuation rose to $5.2B in May 2026 following a strategic investment from SAP. Roughly 900-1,000 employees as of mid-2026 per multiple employee-tracking sources (Tracxn, RocketReach, LeadIQ, Revelio).', + 'Founded 2019 in Berlin. Raised a $180M Series C in October 2025 (Accel-led) at a $2.5B valuation, $240M total raised. Valuation rose to $5.2B in May 2026 following a strategic investment from SAP. Employee count is not reliably documented: PitchBook lists only 109 employees as of 2025, inconsistent with other public estimates in the 900-1,000 range for mid-2026, so headcount should be treated as unconfirmed pending a citable source.', detail: - 'n8n GmbH was founded in 2019 and is headquartered in Berlin, Germany. It raised a $180M Series C announced October 9, 2025, led by Accel with participation from Meritech, Redpoint, Evantic, and Visionaries Club, plus corporate investors NVIDIA and T.Capital, valuing the company at $2.5B and bringing total funding to $240M. In May 2026, SAP made a strategic investment that valued n8n at $5.2B. Employee-count trackers report roughly 900-1,000 employees as of mid-2026.', - shortValue: 'Berlin, 2019; $5.2B valuation, ~1,000 staff', - confidence: 'verified', + "n8n GmbH was founded in 2019 and is headquartered in Berlin, Germany. It raised a $180M Series C announced October 9, 2025, led by Accel with participation from Meritech, Redpoint, Evantic, and Visionaries Club, plus corporate investors NVIDIA and T.Capital, valuing the company at $2.5B and bringing total funding to $240M. In May 2026, SAP made a strategic investment that valued n8n at $5.2B. Employee count is not reliably documented: PitchBook's profile (cited above, for funding data) lists only 109 employees as of 2025, which is inconsistent with n8n's public profile as a ~$5B-valued company with hundreds of integrations and a 24/7 Enterprise support org; other employee-tracking aggregators report figures in the 900-1,000 range for mid-2026, but those specific trackers are not among this profile's sources, so the number should be treated as not publicly confirmed pending a citable source.", + shortValue: 'Berlin, 2019; $5.2B valuation; employee count unconfirmed', + confidence: 'unknown', sources: [ { url: 'https://blog.n8n.io/series-c/', @@ -1325,7 +1355,7 @@ export const n8nProfile: CompetitorProfile = { { url: 'https://pitchbook.com/profiles/company/398691-46', label: 'n8n 2026 Company Profile: Valuation, Funding & Investors | PitchBook', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://blog.n8n.io/n8n-sap/', diff --git a/apps/sim/lib/compare/data/competitors/openai-agentkit.ts b/apps/sim/lib/compare/data/competitors/openai-agentkit.ts index 66cf5529b3f..635bf98adff 100644 --- a/apps/sim/lib/compare/data/competitors/openai-agentkit.ts +++ b/apps/sim/lib/compare/data/competitors/openai-agentkit.ts @@ -99,9 +99,10 @@ export const openaiAgentkitProfile: CompetitorProfile = { "Agent Builder's Guardrails node is backed by a separately installable, open-source package that can be used outside AgentKit entirely, adding jailbreak detection alongside PII masking and other safety checks. Sim's Guardrails block covers PII masking and hallucination/RAG scoring too, but it's a built-in workflow block, not a standalone library you can drop into an unrelated codebase.", shortDescription: 'Standalone open-source package adds jailbreak detection to PII masking.', source: { - url: 'https://guardrails.openai.com/', - label: 'OpenAI Guardrails', - asOf: '2026-07-02', + url: 'https://github.com/openai/openai-guardrails-python', + label: + 'GitHub: openai/openai-guardrails-python (MIT license, pip install openai-guardrails)', + asOf: '2026-09-15', }, }, ], @@ -218,7 +219,12 @@ export const openaiAgentkitProfile: CompetitorProfile = { { url: 'https://developers.openai.com/cookbook/examples/agentkit/agentkit_walkthrough', label: 'OpenAI Cookbook: AgentKit walkthrough', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://openai.com/index/introducing-agentkit/', + label: 'Introducing AgentKit | OpenAI', + asOf: '2026-09-15', }, ], }, @@ -551,9 +557,9 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, agentSkills: { value: - "No: Agent Builder/AgentKit has no dedicated feature for defining a reusable, named prompt or knowledge snippet that multiple agents can share by reference. A distinct 'Agent Skills' concept exists only in the unrelated Codex product line, not in AgentKit.", + "No: Agent Builder/AgentKit has no dedicated feature for defining a reusable, named prompt or knowledge snippet that multiple agents can share by reference. A distinct 'Agent Skills' concept exists as an open agent-skills standard shared across ChatGPT and Codex, not inside AgentKit or Agent Builder.", detail: - 'OpenAI recommends migrating reusable prompts to code-managed, versioned helper files instead, which is the opposite direction of a built-in skills feature.', + 'OpenAI recommends migrating reusable prompts to code-managed, versioned helper files instead, which is the opposite direction of a built-in skills feature. Agent Skills itself is documented as extending both ChatGPT and Codex with task-specific capabilities, available in the ChatGPT desktop app, Codex CLI/IDE extension, and, when bundled as plugins, across ChatGPT on web, desktop, and mobile — it is a shared platform concept, not a Codex-only one, and still has no equivalent inside Agent Builder/AgentKit.', shortValue: 'No dedicated cross-agent skill/snippet feature', confidence: 'estimated', sources: [ @@ -563,9 +569,9 @@ export const openaiAgentkitProfile: CompetitorProfile = { asOf: '2026-07-02', }, { - url: 'https://developers.openai.com/codex/skills', - label: 'Agent Skills - Codex | OpenAI Developers', - asOf: '2026-07-02', + url: 'https://learn.chatgpt.com/docs/build-skills', + label: 'Build skills | ChatGPT Learn (formerly "Agent Skills - Codex")', + asOf: '2026-09-15', }, ], }, @@ -610,7 +616,7 @@ export const openaiAgentkitProfile: CompetitorProfile = { value: "No dedicated node in the visual Agent Builder canvas. Its node palette (Start, Agent, Note, File search, Guardrails, MCP, If/else, While, Human approval, Transform, Set state) has no fan-out/fan-in or 'parallel branches' node; If/else and While are the only branching/looping constructs, and both execute sequentially. Concurrent multi-agent execution requires writing code against the separate Agents SDK (e.g. Python asyncio to run agents in parallel and merge results), not the no-code builder.", detail: - 'OpenAI developer community threads on Agent Builder confirm the canvas lacks a fan-out block and point developers to the Agents SDK for true concurrent branch execution.', + "OpenAI developer community threads on Agent Builder confirm the canvas lacks a fan-out block, forcing sequential workarounds via Set State; OpenAI's own node reference and guides otherwise direct developers toward the Agents SDK for concurrent multi-agent execution.", shortValue: 'No visual parallel-branch node; only via Agents SDK code', confidence: 'estimated', sources: [ @@ -622,7 +628,7 @@ export const openaiAgentkitProfile: CompetitorProfile = { { url: 'https://community.openai.com/t/agent-builder-fan-out-block/1364947', label: 'OpenAI Community: Agent Builder Fan Out block', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -746,10 +752,10 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, extensibilitySdk: { value: - 'Official Agents SDK (Python + TypeScript/JS); Apps SDK (MCP-based) for building integrations; ChatGPT Apps directory as a community marketplace', + "Official Agents SDK (Python + TypeScript/JS); Apps SDK (MCP-based, rebranded 'Plugins' in OpenAI's developer docs) for building integrations; ChatGPT Apps directory — now published as the universal Plugins directory shared by ChatGPT and Codex — as a community marketplace", detail: - "Agents SDK ships as open-source client libraries for Python (openai-agents-python) and TypeScript/JavaScript (openai-agents-js). It defaults to OpenAI's own Responses/Chat Completions APIs but is provider-agnostic in practice: built-in provider-integration points plus best-effort beta LiteLLM/Any-LLM adapters let it call 100+ non-OpenAI providers (this is a code-level capability, distinct from Agent Builder's OpenAI-only model selector). Custom integrations are built as MCP servers using the Apps SDK, an open standard on the Model Context Protocol; Agent Builder's MCP node connects to any third-party MCP server. A Connector Registry centralizes admin-managed connectors (Dropbox, Google Drive, SharePoint, Teams) plus third-party MCPs. Community apps go through a dashboard-based submission and review flow and, once approved, are listed in the ChatGPT Apps directory.", - shortValue: 'Agents SDK, Apps SDK, and app directory', + "Agents SDK ships as open-source client libraries for Python (openai-agents-python) and TypeScript/JavaScript (openai-agents-js). It defaults to OpenAI's own Responses/Chat Completions APIs but is provider-agnostic in practice: built-in provider-integration points plus best-effort beta LiteLLM/Any-LLM adapters let it call 100+ non-OpenAI providers (this is a code-level capability, distinct from Agent Builder's OpenAI-only model selector). Custom integrations are built as MCP servers using the Apps SDK — OpenAI's developer docs now brand this surface 'Plugins', combining reusable skills and an MCP server into one installable package — an open standard on the Model Context Protocol; Agent Builder's MCP node connects to any third-party MCP server. A Connector Registry centralizes admin-managed connectors (Dropbox, Google Drive, SharePoint, Teams) plus third-party MCPs. Community apps go through a dashboard-based submission and review flow and, once approved, are listed in the ChatGPT Apps directory, now called the universal plugin directory shared by ChatGPT and Codex; ChatGPT's own admin surfaces still refer to 'apps' alongside the newer 'plugins' terminology.", + shortValue: 'Agents SDK, Apps SDK/Plugins, app directory', confidence: 'verified', sources: [ { @@ -769,13 +775,14 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, { url: 'https://developers.openai.com/apps-sdk', - label: 'Apps SDK overview', - asOf: '2026-07-02', + label: 'Plugins overview (formerly "Apps SDK overview") | OpenAI Developers', + asOf: '2026-09-15', }, { url: 'https://developers.openai.com/apps-sdk/deploy/submission', - label: 'Apps SDK: Submit and maintain your app', - asOf: '2026-07-02', + label: + 'Submit plugins (formerly "Apps SDK: Submit and maintain your app") | OpenAI Developers', + asOf: '2026-09-15', }, ], }, @@ -865,21 +872,21 @@ export const openaiAgentkitProfile: CompetitorProfile = { security: { compliance: { value: - 'Yes: SOC 2 Type 2, FedRAMP Moderate Authorization (ChatGPT Enterprise and API Platform), PCI DSS v4.0.1, ISO/IEC 27001:2022, ISO 27017, ISO 27018, and ISO/IEC 27701:2019; supports customer HIPAA compliance via BAA and GDPR/CCPA via DPA; FERPA covered via a separate Student Data Privacy Agreement for ChatGPT Edu', + 'Yes: SOC 2 Type 2, FedRAMP Moderate Authorization (ChatGPT Enterprise and API Platform), PCI DSS v4.0.1, ISO/IEC 27001:2022, ISO 27017, ISO 27018, ISO/IEC 27701:2019, and ISO/IEC 42001:2023 (AI management system); supports customer HIPAA compliance via BAA and GDPR/CCPA via DPA; FERPA covered via a separate Student Data Privacy Agreement for ChatGPT Edu', detail: - "OpenAI's most recent SOC 2 report covers January 1, 2025 through June 30, 2025 for Security, Availability, Confidentiality, and Privacy Trust Services Criteria across the API Platform, ChatGPT Enterprise, ChatGPT Edu, and ChatGPT Team. ChatGPT Enterprise and the API Platform hold FedRAMP Moderate (Class C) authorization per the FedRAMP Marketplace listing. OpenAI's trust portal lists PCI DSS v4.0.1 for payment-processing components, plus ISO/IEC 27001:2022, 27017:2015, 27018:2019, and 27701:2019 certifications, and lists GDPR and CCPA. OpenAI offers a Data Processing Addendum for GDPR/CCPA and a Business Associate Agreement for HIPAA-regulated customers on ChatGPT Enterprise/Edu and the API (not standard ChatGPT Business); this is enablement rather than OpenAI itself being HIPAA-certified, since HIPAA has no formal certification body. FERPA compliance for ChatGPT Edu/for Teachers runs through a separate Student Data Privacy Agreement rather than the general DPA.", + "OpenAI's most recent SOC 2 report covers January 1, 2025 through June 30, 2025 for Security, Availability, Confidentiality, and Privacy Trust Services Criteria across the API Platform, ChatGPT Enterprise, ChatGPT Edu, and ChatGPT Team. ChatGPT Enterprise and the API Platform hold FedRAMP Moderate (Class C) authorization per the FedRAMP Marketplace listing. OpenAI's trust portal lists PCI DSS v4.0.1 for payment-processing components, plus ISO/IEC 27001:2022, 27017:2015, 27018:2019, and 27701:2019 certifications, and lists GDPR and CCPA. OpenAI also maintains an ISO/IEC 42001:2023 AI Management System certification, covering OpenAI's consumer and business AI products and models in its role as an AI producer and AI provider, per both the trust portal and OpenAI's security-and-privacy page. OpenAI offers a Data Processing Addendum for GDPR/CCPA and a Business Associate Agreement for HIPAA-regulated customers on ChatGPT Enterprise/Edu and the API (not standard ChatGPT Business); this is enablement rather than OpenAI itself being HIPAA-certified, since HIPAA has no formal certification body. FERPA compliance for ChatGPT Edu/for Teachers runs through a separate Student Data Privacy Agreement rather than the general DPA.", shortValue: 'SOC 2 Type 2, FedRAMP Moderate, ISO 27001, HIPAA BAA', confidence: 'estimated', sources: [ { url: 'https://trust.openai.com/', label: 'OpenAI Trust Portal (SafeBase)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://openai.com/security-and-privacy/', label: 'Security and privacy at OpenAI', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.fedramp.gov/marketplace/products/FR2533155773/', @@ -898,39 +905,42 @@ export const openaiAgentkitProfile: CompetitorProfile = { value: 'Yes: data residency at rest available in US, Europe, UK, Japan, Canada, South Korea, Singapore, Australia, India, and UAE for eligible enterprise customers', detail: - 'Eligible ChatGPT Enterprise, ChatGPT Edu, ChatGPT for Healthcare, and API platform customers can store content at rest in these regions; eligible customers can also opt into in-region GPU inference in the U.S. or Europe.', + "Eligible ChatGPT Enterprise, ChatGPT Edu, and API platform customers can store content at rest in these regions, per OpenAI's own data-residency announcement. That announcement does not name ChatGPT for Healthcare among the eligible products and does not mention in-region GPU inference; both sub-claims are not documented on this page and are not independently confirmed elsewhere, so they should be treated as unconfirmed rather than general until a primary source names them.", shortValue: '10 regions for eligible enterprise customers', confidence: 'estimated', sources: [ { url: 'https://openai.com/index/expanding-data-residency-access-to-business-customers-worldwide/', label: 'Expanding data residency access to business customers worldwide', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, rbac: { value: - 'Yes, at the workspace level. Workspace Owners create custom roles and use per-role "Connected data" controls to allow or restrict which apps/connectors (and their actions) each role can use, with all apps disabled by default. A separate Global Admin Console (beta) adds a distinct Global admin role for centralizing access management across workspaces. Granular access scoped to individual Agent Builder workflows is not documented.', + 'Yes, at the workspace level, for ChatGPT Enterprise, Edu, Healthcare, and Teachers workspaces (not standard ChatGPT Business). Workspace Owners create custom roles and use per-role "Plugins & connected data" controls to allow or restrict which apps/connectors (and their actions) each role can use, with new apps disabled by default until an admin enables them. Standalone ChatGPT Business workspaces instead get only a single workspace-wide app on/off toggle (apps enabled by default), with no per-role granularity. A separate Admin Console (formerly branded Global Admin Console) adds a distinct Global admin role for centralizing tenant-wide identity access (SSO, domains, SCIM, external-application access) across workspaces. Granular access scoped to individual Agent Builder workflows is not documented.', detail: - 'ChatGPT Enterprise/Edu/Business workspaces let Workspace Owners create custom roles and, under each role\'s Connected data section, turn on "Allow members to use apps" and select which specific apps that role can access; when an admin enables an app, they can also set action controls (allow all actions, read-only, or a custom action set). All apps are disabled by default until an admin turns them on. The Global Admin Console is a newer, separate beta surface with its own Global admin role and an Access tab for centralizing SSO, domain, and external-application access across workspaces. This is workspace/role-level RBAC over apps and connectors, not permissions scoped to individual Agent Builder workflows.', - shortValue: 'Workspace-level RBAC via custom roles, per-app controls', - confidence: 'estimated', + 'RBAC is available for ChatGPT Enterprise, Edu, Healthcare, and Teachers workspaces in all supported countries — not standard ChatGPT Business. In eligible workspaces, Workspace Owners create custom roles and, under each role\'s "Plugins & connected data" section, turn on "Allow members to use plugins" (shown as "Use apps" in FedRAMP workspaces) and select which specific apps that role can access; when an admin enables an app, they can also set action controls (allow all actions, read-only, or a custom action set). New plugins and apps are disabled by default in Enterprise/Edu until an admin turns them on, though new workspaces may start with a selected set of apps already enabled. Standalone ChatGPT Business workspaces are not eligible for custom-role RBAC: administrators there instead manage a single workspace-wide app on/off toggle, and apps are enabled by default. The Admin Console (formerly branded Global Admin Console) is a separate surface with its own Global admin role for centralizing tenant-wide SSO, domain, SCIM directory sync, and external-application access across workspaces. This is workspace/role-level RBAC over apps and connectors, not permissions scoped to individual Agent Builder workflows.', + shortValue: 'RBAC via custom roles; not standard Business', + confidence: 'verified', sources: [ { url: 'https://help.openai.com/en/articles/11750701-rbac', - label: 'RBAC | OpenAI Help Center', - asOf: '2026-07-08', + label: + 'Managing feature access with role-based access control in ChatGPT | OpenAI Help Center', + asOf: '2026-09-15', }, { url: 'https://help.openai.com/en/articles/11509118-admin-controls-security-and-compliance-in-apps-enterprise-edu-and-business', - label: 'Admin Controls, Security, and Compliance in apps | OpenAI Help Center', - asOf: '2026-07-08', + label: + 'Admin controls, security, and compliance for plugins and apps | OpenAI Help Center', + asOf: '2026-09-15', }, { url: 'https://help.openai.com/en/articles/12289294-global-admin-console', - label: 'Global Admin Console | OpenAI Help Center', - asOf: '2026-07-08', + label: + 'Managing your tenant in Admin Console (formerly Global Admin Console) | OpenAI Help Center', + asOf: '2026-09-15', }, ], }, @@ -958,21 +968,23 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, credentialGovernance: { value: - 'Yes: ChatGPT Enterprise/Business workspaces support role-based access control (RBAC) that restricts which connectors/apps (and by extension their underlying stored credentials) a given custom role or permission group may use, per-app and per-role, with all apps disabled by default until an admin enables them for specific roles.', + 'Yes, for ChatGPT Enterprise, Edu, Healthcare, and Teachers workspaces: custom-role RBAC restricts which connectors/apps (and by extension their underlying stored credentials) a given custom role or permission group may use, per-app and per-role, with new apps disabled by default until an admin enables them for specific roles. Standalone ChatGPT Business workspaces are not eligible for this per-role RBAC; they instead get only a single workspace-wide app on/off toggle (apps enabled by default), with no per-role credential/connector restriction.', detail: - 'Granularity is at the connector/app level (e.g. this role may use Google Drive, that role may not) rather than restricting individual named credential instances within a connector type.', - shortValue: 'Yes, RBAC restricts connector access by role', + 'Granularity is at the connector/app level (e.g. this role may use Google Drive, that role may not) rather than restricting individual named credential instances within a connector type. This per-role restriction is scoped to Enterprise, Edu, Healthcare, and Teachers workspaces; ChatGPT Business administrators can only turn a connector/app on or off for the whole workspace, not per role.', + shortValue: 'Yes, RBAC by role (not standard Business)', confidence: 'verified', sources: [ { url: 'https://help.openai.com/en/articles/11750701-rbac', - label: 'RBAC | OpenAI Help Center', - asOf: '2026-07-02', + label: + 'Managing feature access with role-based access control in ChatGPT | OpenAI Help Center', + asOf: '2026-09-15', }, { url: 'https://help.openai.com/en/articles/11509118-admin-controls-security-and-compliance-in-apps-enterprise-edu-and-business', - label: 'Admin Controls, Security, and Compliance in apps | OpenAI Help Center', - asOf: '2026-07-02', + label: + 'Admin controls, security, and compliance for plugins and apps | OpenAI Help Center', + asOf: '2026-09-15', }, ], }, @@ -1100,21 +1112,21 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, thirdPartyVetting: { value: - "Partial: pre-built Connector Registry entries (Dropbox, Google Drive, SharePoint, Teams) and the ChatGPT Apps directory go through OpenAI identity verification and app review, but Agent Builder's MCP node and the Agents SDK can connect to any third-party MCP server with no vendor vetting pipeline documented", + "Partial: pre-built Connector Registry entries (Dropbox, Google Drive, SharePoint, Teams) and the ChatGPT Apps directory — now published as the universal plugin directory shared by ChatGPT and Codex — go through OpenAI identity verification and app/plugin review, but Agent Builder's MCP node and the Agents SDK can connect to any third-party MCP server with no vendor vetting pipeline documented", detail: - "OpenAI's own Connector Registry connectors and ChatGPT Apps directory submissions require developer identity verification and pass through an OpenAI app-review process before listing, per the App submission guidelines. But Agent Builder's MCP node and the Agents SDK let a builder point at any hosted MCP server, first-party or community-run, with no OpenAI review of that server's code. This client-only MCP model mirrors the wider MCP ecosystem, where unreviewed community servers have shipped malicious behavior elsewhere (for example, an unofficial third-party Postmark MCP server was found in September 2025 silently BCC'ing all outgoing email to an attacker). No security incident specific to OpenAI's own Connector Registry, Apps directory, or Agent Builder MCP integration has been publicly reported.", + "OpenAI's own Connector Registry connectors and ChatGPT Apps directory submissions require developer identity verification and pass through an OpenAI review process before listing, per what OpenAI's developer docs now call the Plugin guidelines (formerly the App submission guidelines). But Agent Builder's MCP node and the Agents SDK let a builder point at any hosted MCP server, first-party or community-run, with no OpenAI review of that server's code. This client-only MCP model mirrors the wider MCP ecosystem, where unreviewed community servers have shipped malicious behavior elsewhere (for example, an unofficial third-party Postmark MCP server was found in September 2025 silently BCC'ing all outgoing email to an attacker). No security incident specific to OpenAI's own Connector Registry, Apps/plugin directory, or Agent Builder MCP integration has been publicly reported.", shortValue: 'Partial: reviewed first-party catalog, but open MCP server connections', confidence: 'estimated', sources: [ { url: 'https://developers.openai.com/apps-sdk/app-submission-guidelines', - label: 'App submission guidelines | Apps SDK | OpenAI Developers', - asOf: '2026-07-02', + label: 'Plugin guidelines (formerly "App submission guidelines") | OpenAI Developers', + asOf: '2026-09-15', }, { url: 'https://developers.openai.com/apps-sdk/guides/security-privacy', - label: 'Security & Privacy | Apps SDK | OpenAI Developers', - asOf: '2026-07-02', + label: 'Security & Privacy | Plugins | OpenAI Developers', + asOf: '2026-09-15', }, { url: 'https://openai.com/index/developers-can-now-submit-apps-to-chatgpt/', @@ -1197,7 +1209,7 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, dataDrains: { value: - "Yes: OpenAI's Compliance Logs Platform and Admin/Audit Logs API continuously export execution, audit, and usage data as immutable, time-windowed JSONL log files, with 13 pre-built turnkey integrations to eDiscovery, DLP, and SIEM vendors (e.g. CrowdStrike, GlobalRelay), beyond just viewing logs in-product.", + "Yes: OpenAI's Compliance Logs Platform and Admin/Audit Logs API continuously export execution, audit, and usage data as immutable, time-windowed JSONL log files, with 18 pre-built turnkey integrations to eDiscovery, DLP, and SIEM vendors (e.g. CrowdStrike, Microsoft Purview, Netskope, Palo Alto Networks, Varonis, Zscaler, Global Relay), beyond just viewing logs in-product.", detail: 'This is an org-wide ChatGPT Enterprise/API Platform compliance feature, not something scoped specifically to Agent Builder workflow runs.', shortValue: 'Yes, continuous log export to SIEM/DLP/eDiscovery', @@ -1206,7 +1218,7 @@ export const openaiAgentkitProfile: CompetitorProfile = { { url: 'https://help.openai.com/en/articles/9261474-openai-compliance-platform-for-enterprise-and-edu-customers', label: 'OpenAI Compliance Platform for Enterprise and Edu Customers', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.openai.com/en/articles/9687866-admin-and-audit-logs-api-for-the-api-platform', @@ -1219,14 +1231,14 @@ export const openaiAgentkitProfile: CompetitorProfile = { value: 'Yes: OpenAI\'s platform supports a background mode that flags a Responses API call to run asynchronously instead of blocking. The client immediately gets back a response ID marked "queued" and polls a status endpoint until the run reaches a terminal state like completed or failed.', detail: - 'Background mode is a platform-level Responses API feature (used by Agents SDK/AgentKit flows), not unique to the Agent Builder canvas UI itself; an in-flight response can also be cancelled directly. Response data is retained only about 10 minutes for polling, and it is incompatible with Zero Data Retention projects.', + 'Background mode is a platform-level Responses API feature (used by Agents SDK/AgentKit flows), not unique to the Agent Builder canvas UI itself; an in-flight response can also be cancelled directly. Response data is retained only about 10 minutes for polling. Zero Data Retention (ZDR) projects can still use background mode, but requests automatically run with `store=false`, so the same ~10-minute disk retention window for polling applies without persisting the response afterward.', shortValue: 'Background mode: async trigger + poll status', confidence: 'verified', sources: [ { url: 'https://developers.openai.com/api/docs/guides/background', label: 'OpenAI: Background mode guide', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1300,16 +1312,16 @@ export const openaiAgentkitProfile: CompetitorProfile = { support: { supportChannels: { value: - 'Community forum (community.openai.com), help center articles, and enterprise sales-led support; ChatGPT Enterprise includes 24/7 support', + 'Community forum (community.openai.com), help center articles, and enterprise sales-led support; ChatGPT Enterprise plans document dedicated support with priority handling (24/7 coverage is referenced in enterprise sales materials, not in the general Help Center contact article cited here)', detail: - "OpenAI's Help Center documents standard support channels, and ChatGPT Enterprise plans include 24/7 support with SLAs.", - shortValue: 'Community forum plus 24/7 enterprise support', + "OpenAI's Help Center documents standard community/help-center contact channels (chat bubble, virtual assistant, Admin Portal for Team/Business/Enterprise admins) but does not itself state 24/7 coverage or Enterprise SLA hours; 24/7 support and priority handling for ChatGPT Enterprise are referenced in enterprise sales materials rather than in this general contact article.", + shortValue: 'Community forum, help center, enterprise support', confidence: 'estimated', sources: [ { url: 'https://help.openai.com/en/articles/6614161-how-can-i-contact-support', label: 'OpenAI Help Center: How can I contact support?', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1328,8 +1340,8 @@ export const openaiAgentkitProfile: CompetitorProfile = { }, { url: 'https://openai.com/api-priority-processing/', - label: 'Priority Processing for API Customers', - asOf: '2026-07-02', + label: 'Fast mode (formerly Priority Processing) for API Customers', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/openclaw.ts b/apps/sim/lib/compare/data/competitors/openclaw.ts index 81a0b7d25ac..3507afe70b1 100644 --- a/apps/sim/lib/compare/data/competitors/openclaw.ts +++ b/apps/sim/lib/compare/data/competitors/openclaw.ts @@ -44,13 +44,13 @@ export const openClawProfile: CompetitorProfile = { { title: 'Sub-agent orchestration for parallel background work', description: - 'A running agent can spawn sub-agents, background runs in their own isolated session and (by default) sandbox, that work in parallel on research, long-running tools, or verification tasks and report results back to the requesting chat when finished. Nesting depth defaults to 1 level, with an orchestrator pattern recommended at depth 2, and a configurable maximum of 5 levels.', + "A running agent can spawn sub-agents, background runs in their own isolated session and (by default) sandbox, that work in parallel on research, long-running tools, or verification tasks and report results back to the requesting chat when finished. Nesting depth defaults to 5 levels (maxSpawnDepth, range 1-5): a sub-agent at depth 1-4 defaults to the 'Orchestrator' role and can itself spawn children, while a depth-5 sub-agent is a 'Leaf' and cannot. Operators can lower maxSpawnDepth (e.g. to 1, disabling further nesting, or to 2) to force leaf workers sooner.", shortDescription: 'Spawns isolated sub-agents that run tasks in parallel and report back to chat.', source: { url: 'https://docs.openclaw.ai/tools/subagents', label: 'OpenClaw Docs: Sub-agents', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -84,9 +84,9 @@ export const openClawProfile: CompetitorProfile = { shortDescription: 'MIT-licensed; governance is moving to an independent foundation supported, not owned, by OpenAI.', source: { - url: 'https://www.forbes.com/sites/ronschmelzer/2026/02/16/openai-hires-openclaw-creator-peter-steinberger-and-sets-up-foundation/', - label: 'Forbes: OpenAI Hires OpenClaw Creator Peter Steinberger And Sets Up Foundation', - asOf: '2026-07-08', + url: 'https://openclaw.ai/blog/introducing-openclaw-foundation', + label: 'OpenClaw Blog: Introducing the OpenClaw Foundation', + asOf: '2026-09-15', }, }, ], @@ -177,7 +177,7 @@ export const openClawProfile: CompetitorProfile = { value: 'Moderate to steep for initial self-hosted setup, low for day-to-day chat use once running', detail: - 'Installing OpenClaw requires Node.js 22.19+/24, a package manager (pnpm/npm/bun), CLI onboarding commands, and editing JSON configuration for channels, providers, and security policy (e.g. DM pairing, sandbox mode). Once running, interacting with the agent is plain natural-language chat.', + 'Installing OpenClaw requires Node.js 24.16+ or 26.1+ (26 recommended), a package manager (pnpm/npm/bun) or the bundled installer script, CLI onboarding commands, and editing JSON configuration for channels, providers, and security policy (e.g. DM pairing, sandbox mode). Once running, interacting with the agent is plain natural-language chat.', shortValue: 'Technical setup, but simple chat once configured', confidence: 'estimated', sources: [ @@ -189,7 +189,7 @@ export const openClawProfile: CompetitorProfile = { { url: 'https://github.com/openclaw/openclaw', label: 'openclaw/openclaw (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -254,7 +254,12 @@ export const openClawProfile: CompetitorProfile = { { url: 'https://openclaw.ai/ecosystem/', label: 'OpenClaw Ecosystem page', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://openclaw.ai/blog/introducing-openclaw-foundation', + label: 'OpenClaw Blog: Introducing the OpenClaw Foundation', + asOf: '2026-09-15', }, ], }, @@ -499,7 +504,7 @@ export const openClawProfile: CompetitorProfile = { value: 'Yes: documented tools for image generation, video generation (text-to-video, image-to-video, video-to-video), music/audio generation, and text-to-speech, each running asynchronously except TTS which runs synchronously', detail: - 'The image_generate, video_generate, and music_generate tools post results into the chat session when ready. TTS defaults to ElevenLabs but also supports Azure Speech and Google Cloud TTS, with SSML/voice customization.', + 'The image_generate, video_generate, and music_generate tools post results into the chat session when ready. TTS has no fixed default provider — when `tts.provider` is unset, OpenClaw uses the first configured provider in registry auto-select order, across a supported list including Azure Speech, ElevenLabs (voice cloning, deterministic via `seed`), Google Gemini (persona-aware audio profiles), Fish Audio, Microsoft Edge TTS, OpenAI, and others; documented customization is per-provider (e.g. Gemini `audioProfile` style prompts, ElevenLabs voice cloning) rather than a general SSML layer.', shortValue: 'Yes, image/video/music generation and TTS tools', confidence: 'verified', sources: [ @@ -511,7 +516,7 @@ export const openClawProfile: CompetitorProfile = { { url: 'https://docs.openclaw.ai/tools/tts', label: 'OpenClaw Docs: Text-to-speech', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -579,16 +584,16 @@ export const openClawProfile: CompetitorProfile = { }, parallelExecution: { value: - 'Yes: sub-agents can run in parallel, working simultaneously on separate tasks (e.g. research, content generation, verification) and report back to the requesting session. Nesting defaults to depth 1, with a documented maxSpawnDepth configurable up to 5 levels via the maxSpawnDepth parameter (range 1-5).', + "Yes: sub-agents can run in parallel, working simultaneously on separate tasks (e.g. research, content generation, verification) and report back to the requesting session. Nesting depth defaults to 5 levels via the maxSpawnDepth parameter (range 1-5): a sub-agent at depth 1-4 defaults to the 'Orchestrator' role and can itself spawn children, while a depth-5 sub-agent is a 'Leaf' and cannot. Operators can lower maxSpawnDepth (e.g. to 1, disabling further nesting, or to 2) to force leaf workers sooner.", detail: 'Each sub-agent gets its own session identifier, context window, and execution environment (with optional sandboxing), isolated from the main session and from sibling sub-agents.', - shortValue: 'Yes, parallel sub-agents with configurable nesting depth (up to 5)', + shortValue: 'Yes: parallel sub-agents, nesting depth defaults to 5 (range 1-5)', confidence: 'verified', sources: [ { url: 'https://docs.openclaw.ai/tools/subagents', label: 'OpenClaw Docs: Sub-agents', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -610,22 +615,33 @@ export const openClawProfile: CompetitorProfile = { }, loopIteration: { value: - "No: neither the core agent loop nor the optional Lobster workflow shell has a dedicated for-each/while loop container. Lobster's own maintainers describe its steps as executing strictly top to bottom with no way to jump back to a previous step, and a GitHub feature-request proposal for adding loop/flow-control (a next field enabling backward jumps and max_iterations) is not yet implemented.", + "Partial: Lobster's core agent loop still has no user-facing while/backward-jump construct, but the optional Lobster workflow shell now ships a dedicated `for_each` step type (shipped April 2026, extended September 2026) that iterates a set of sub-steps over every item in a referenced array, with loop-scoped `item_var`/`index_var`, optional `batch_size`/`pause_ms` rate limiting, per-loop timeout/retry/`on_error` policy, and collected iteration outputs for downstream steps — a genuine loop/iteration container, though it is not yet reflected on the official hosted docs page. A broader maintainer-filed proposal for general flow control (a `next` field enabling arbitrary backward jumps and `max_iterations`, distinct from iterating a fixed collection) was closed as completed in the same closing pass, with that specific backward-jump mechanism explicitly carved out as unshipped and no live tracking issue currently open for it.", detail: - 'Lobster documents only run/command, pipeline, and approval step types plus a boolean condition gate. A maintainer-filed proposal (openclaw/lobster issue #38) states plainly that "steps execute top to bottom. There\'s no way to jump back to a previous step" and lists step flow control/loops as a future addition, not a shipped feature.', - shortValue: 'No: Lobster steps run top to bottom, no loop construct shipped', + 'Lobster\'s own README and CHANGELOG document `run`/`command`, `pipeline`, `approval`, `parallel`, and `for_each` step types; the hosted docs page at docs.openclaw.ai/tools/lobster has not yet been updated to list `for_each` as of this check, but the feature is shipped on the `main` branch (PR #68, closing openclaw/lobster issue #76, "for_each step type for iterating over collections," as completed on 2026-04-11) and actively maintained (PR #160, merged 2026-09-08, added `timeout_ms`/`retry`/`on_error` handling and `cost_limit` interaction for the whole loop). A maintainer-filed umbrella proposal (openclaw/lobster issue #38) that separately stated "steps execute top to bottom. There\'s no way to jump back to a previous step" was closed as completed on 2026-04-11 after shipping structured input requests and richer conditions; its closing comment explicitly carves out `next`/backward-jump loop semantics as unshipped scope, inviting a separate follow-up issue that, as of this check, has not been filed.', + shortValue: 'Partial: for_each loop shipped in Lobster; no backward-jump construct', confidence: 'verified', sources: [ { url: 'https://docs.openclaw.ai/tools/lobster', label: 'OpenClaw Docs: Lobster', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/openclaw/lobster/issues/38', label: 'openclaw/lobster GitHub issue #38: Human-in-the-loop workflows: structured input requests, conditionals, and step flow control', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/openclaw/lobster/issues/76', + label: + 'openclaw/lobster GitHub issue #76: for_each step type for iterating over collections', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/openclaw/lobster/blob/main/CHANGELOG.md', + label: 'openclaw/lobster CHANGELOG', + asOf: '2026-09-15', }, ], }, @@ -801,14 +817,14 @@ export const openClawProfile: CompetitorProfile = { value: 'Yes, and mandatory: OpenClaw requires the operator to supply their own API credentials/OAuth login for whichever model provider(s) they configure (Anthropic, OpenAI, Google, or any OpenAI-compatible endpoint); there is no OpenClaw-hosted model access.', detail: - 'Onboarding documentation walks through provider-specific auth flows (e.g. `openclaw models auth paste-token --provider anthropic`, `openclaw models auth login --provider openai-codex`). BYOK is the only supported model-access model.', + 'Onboarding documentation walks through provider-specific auth flows (e.g. `openclaw models auth paste-token --provider anthropic`, `openclaw models auth login --provider openai --set-default` for ChatGPT/Codex OAuth — the older `openai-codex` provider id is legacy and is auto-migrated to `openai` by `openclaw doctor --fix`). BYOK is the only supported model-access model.', shortValue: 'Yes, mandatory; no OpenClaw-hosted model access', confidence: 'verified', sources: [ { url: 'https://docs.openclaw.ai/concepts/model-providers', label: 'OpenClaw Docs: Model providers', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -941,16 +957,16 @@ export const openClawProfile: CompetitorProfile = { }, piiRedaction: { value: - 'Partial: session logging redacts sensitive tool summaries and URLs by default (logging.redactSensitive: "tools"), but this is generic sensitive-data log redaction, not a dedicated, named PII-detection feature (e.g. SSNs, credit card numbers) applied to conversation content itself.', + 'Partial: sensitive-value redaction (tokens, bearer headers, PEM blocks, vendor token prefixes, payment-credential field names) is always on for console, file-log, OTLP, and transcript output and cannot be disabled; operators can only add custom patterns via `logging.redactPatterns`. This is generic secret/token redaction, not a dedicated PII-detection feature (e.g. SSNs) applied to conversation content itself.', detail: - 'Redaction applies to logging output only, not to what the agent itself sees or processes mid-conversation.', - shortValue: 'Partial: log redaction only, not conversation-content PII detection', + 'Redaction applies to logging/transcript output only (console, file-log, OTLP log records, and session transcript text), not to what the agent itself sees or processes mid-conversation; it targets secret-shaped values (keys, tokens, headers, PEM blocks, payment fields) via pattern matching, not semantic PII categories like names, SSNs, or addresses in ordinary conversation text.', + shortValue: 'Partial: mandatory secret/token redaction, not PII detection', confidence: 'estimated', sources: [ { url: 'https://docs.openclaw.ai/gateway/security', label: 'OpenClaw Docs: Security', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -983,8 +999,13 @@ export const openClawProfile: CompetitorProfile = { asOf: '2026-09-15', }, { - url: 'https://docs.openclaw.ai/gateway/authentication', - label: 'OpenClaw Docs: Authentication', + url: 'https://docs.openclaw.ai/gateway/security/trust-model', + label: 'OpenClaw Docs: Trust model', + asOf: '2026-09-15', + }, + { + url: 'https://docs.openclaw.ai/gateway/security/network-exposure', + label: 'OpenClaw Docs: Network exposure', asOf: '2026-09-15', }, ], @@ -1048,22 +1069,22 @@ export const openClawProfile: CompetitorProfile = { }, durabilityModel: { value: - 'Partial: cron-scheduled jobs run as isolated sessions with retention/pruning, and OpenClaw now provides automatic retry-with-backoff for both one-shot jobs (up to retry.maxAttempts, default 3 attempts, at 30s/60s/5m) and recurring jobs (an extended 30s/60s/5m/15m/60m backoff on consecutive errors), though there is still no checkpoint/replay-of-a-past-run feature for either scheduled jobs or interactive chat sessions.', + 'Partial: cron-scheduled jobs run as isolated sessions with retention/pruning, and OpenClaw provides automatic retry for one-shot jobs (a built-in retry schedule for transient errors — rate limit, overload, network, timeout, server error — with permanent errors disabling the job immediately; exact attempt count and intervals are not published) and recurring jobs (a documented extended backoff of 30s/60s/5m/15m/60m on consecutive errors, resetting after the next successful run), though there is still no checkpoint/replay-of-a-past-run feature for either scheduled jobs or interactive chat sessions.', detail: - 'The cron docs describe both delivery diagnostics (intended target, resolved target, fallback delivery used, final delivered state) for message delivery, and the retry/backoff schedule (cron.sessionRetention, runLog.keepLines, retry.maxAttempts) as configurable per job.', + 'The cron docs describe delivery diagnostics (intended target, resolved target, fallback delivery used, final delivered state) for message delivery, and document the recurring-job retry/backoff schedule numerically (30s/60s/5m/15m/60m, resetting after the next successful run); one-shot retry is described only qualitatively (transient-error categories trigger a built-in retry schedule, permanent errors disable the job immediately) with no published attempt count or interval schedule.', shortValue: 'Clean isolated cron runs with retry-with-backoff; no checkpoint/replay', confidence: 'estimated', sources: [ { url: 'https://docs.openclaw.ai/automation/cron-jobs', label: 'OpenClaw Docs: Scheduled tasks (cron jobs)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, failureAlerting: { value: - 'Partial: cron jobs support a dedicated failure-alerting path (a configurable cron.failureDestination global/per-job override, a webhook delivery mode, and --failure-alert-after/--failure-alert-cooldown tuning flags) in addition to normal chat delivery diagnostics, so failure alerting is a distinct feature rather than merely folded into chat delivery. There is still no email or cost/latency-threshold alerting.', + 'Partial: cron jobs support a dedicated failure-alerting path (a per-job `failureAlert`/`delivery.failureDestination` override layered over the global `cron.failureAlert` object (mode, channel, to, accountId) — the older `cron.failureDestination` key is legacy and is merged into `cron.failureAlert` by `openclaw doctor --fix` — plus a webhook delivery mode and `--failure-alert-after`/`--failure-alert-cooldown` tuning flags on `openclaw automations edit`) in addition to normal chat delivery diagnostics, so failure alerting is a distinct feature rather than merely folded into chat delivery. There is still no email or cost/latency-threshold alerting.', detail: 'Failure alerting is a dedicated, tunable path (webhook delivery mode plus alert-frequency flags), separate from the normal chat-delivery flow where the operator otherwise sees delivery outcomes in the channel where the job reports.', shortValue: @@ -1073,7 +1094,7 @@ export const openClawProfile: CompetitorProfile = { { url: 'https://docs.openclaw.ai/automation/cron-jobs', label: 'OpenClaw Docs: Scheduled tasks (cron jobs)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1108,17 +1129,17 @@ export const openClawProfile: CompetitorProfile = { }, executionLimits: { value: - 'No fixed platform-wide execution-time ceiling is published by default (runTimeoutSeconds defaults to 0/unlimited). Sub-agents cannot spawn their own children by default (maxSpawnDepth defaults to 1); setting maxSpawnDepth to 2 opts into one level of nesting (the documented "orchestrator pattern"), up to a configurable maximum of 5. agents.defaults.subagents.maxConcurrent caps concurrent sub-agent runs at 8 by default, with maxChildrenPerAgent capping children per orchestrator at 5 by default.', + "No fixed platform-wide execution-time ceiling is published by default (runTimeoutSeconds defaults to 0/unlimited). Sub-agent nesting depth defaults to 5 levels (maxSpawnDepth, range 1-5): a sub-agent at depth 1-4 defaults to the 'Orchestrator' role and can itself spawn children, while a depth-5 sub-agent is a 'Leaf' and cannot. Operators can lower maxSpawnDepth (e.g. to 1, disabling further nesting, or to 2) to force leaf workers sooner. agents.defaults.subagents.maxConcurrent caps concurrent sub-agent runs at 8 by default, with maxChildrenPerAgent capping children per orchestrator at 5 by default.", detail: "Because OpenClaw runs on infrastructure the operator controls, execution-time/concurrency limits beyond these published defaults (runTimeoutSeconds, maxSpawnDepth, maxConcurrent, maxChildrenPerAgent) are a function of that operator's own hardware and their model provider's API limits, not an OpenClaw-side ceiling.", shortValue: - 'No nesting by default (maxSpawnDepth 1, opt-in to 2+); maxConcurrent 8; no fixed time limit', + 'Nesting depth defaults to 5 (opt down to limit); maxConcurrent 8; no fixed time limit', confidence: 'verified', sources: [ { url: 'https://docs.openclaw.ai/tools/subagents', label: 'OpenClaw Docs: Sub-agents', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, @@ -1186,19 +1207,19 @@ export const openClawProfile: CompetitorProfile = { value: "Large and very fast-growing: the GitHub repository has roughly 382,000 stars, reported by multiple sources as the fastest-growing and, by some accounts, most-starred non-aggregator open-source project in GitHub's history, alongside an active ClawHub skill-sharing community.", detail: - 'Growth milestones include 9,000 stars in the first 24 hours after launch (as Clawdbot, November 2025) and 247,000+ stars by March 2, 2026. Star counts fluctuate and are best checked live on the GitHub repository.', + 'Growth milestones include 247,000 stars and 47,700 forks by March 2, 2026, per Wikipedia; the GitHub repository has since grown further (389,797 stars and 81,937 forks as of this check, 2026-09-15).', shortValue: '~382,000 GitHub stars, extremely rapid growth since Nov 2025', confidence: 'estimated', sources: [ { url: 'https://github.com/openclaw/openclaw', label: 'openclaw/openclaw (GitHub)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://en.wikipedia.org/wiki/OpenClaw', label: 'Wikipedia: OpenClaw', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/pipedream.ts b/apps/sim/lib/compare/data/competitors/pipedream.ts index 0a46e73e9f7..5ec32c0aaf3 100644 --- a/apps/sim/lib/compare/data/competitors/pipedream.ts +++ b/apps/sim/lib/compare/data/competitors/pipedream.ts @@ -36,7 +36,11 @@ export const pipedreamProfile: CompetitorProfile = { description: "Any step in a Pipedream workflow can be replaced with custom Node.js, Python, Bash, or Go code, and pre-built actions can be used as no-code building blocks or 'scaffolded' into code you customize.", shortDescription: 'Every workflow step can drop into custom code in four languages.', - source: { url: 'https://pipedream.com/docs', label: 'Pipedream Docs', asOf: '2026-07-02' }, + source: { + url: 'https://pipedream.com/docs/workflows/building-workflows', + label: 'Pipedream Docs: Building Workflows', + asOf: '2026-09-15', + }, }, { title: 'Source-available component registry on GitHub', @@ -105,7 +109,11 @@ export const pipedreamProfile: CompetitorProfile = { shortValue: 'Visual builder plus custom code steps', confidence: 'verified', sources: [ - { url: 'https://pipedream.com/docs', label: 'Pipedream Docs', asOf: '2026-07-02' }, + { + url: 'https://pipedream.com/docs/workflows/building-workflows', + label: 'Pipedream Docs: Building Workflows', + asOf: '2026-09-15', + }, ], }, learningCurve: { @@ -254,12 +262,7 @@ export const pipedreamProfile: CompetitorProfile = { { url: 'https://pipedream.com/docs/workflows/data-management/file-stores', label: 'File Stores docs', - asOf: '2026-07-02', - }, - { - url: 'https://pipedream.com/blog/filestores/', - label: 'File Stores blog announcement', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -287,9 +290,10 @@ export const pipedreamProfile: CompetitorProfile = { confidence: 'estimated', sources: [ { - url: 'https://pipedream.com/apps/helper-functions/actions/html-to-markdown', - label: 'HTML to Markdown action', - asOf: '2026-07-02', + url: 'https://github.com/PipedreamHQ/pipedream/tree/master/components/formatting/actions', + label: + 'GitHub: Formatting app actions (convert-html-to-markdown, convert-markdown-to-html)', + asOf: '2026-09-15', }, ], }, @@ -346,13 +350,18 @@ export const pipedreamProfile: CompetitorProfile = { ], }, agentReasoningBlocks: { - value: 'Yes: dedicated AI Agent Builder', + value: + "Yes, via 'String' (String.com), Pipedream's separately-branded, alpha-stage text-to-agent product built on Pipedream's automation engine: its landing page states 'Prompt, run, edit, and deploy AI agents in seconds,' distinct from plain data-routing workflow steps. It is not currently promoted on Pipedream's main homepage, which has been repositioned around Connect/MCP infrastructure for developer-built agents rather than a no-code agent builder.", detail: - "Pipedream markets an 'AI Agent Builder' to prompt, run, edit, and deploy AI agents, distinct from plain data-routing workflow steps.", - shortValue: 'Dedicated AI Agent Builder feature', - confidence: 'estimated', + "Pipedream's homepage no longer mentions an 'AI Agent Builder'; it now leads with 'The integration layer for AI agents' and sections for Connect, MCP, and Conduit (an enterprise agent-deployment offering, early access). The agent-building experience lives at a distinct product, String (also reachable at string.com), whose own page is tagged 'alpha' and carries the tagline 'Prompt, run, edit, and deploy AI agents in seconds,' with a prompt box ('How can String help you today?').", + shortValue: "Yes, via 'String' — a separate alpha-stage product", + confidence: 'verified', sources: [ - { url: 'https://pipedream.com/', label: 'Pipedream homepage', asOf: '2026-07-02' }, + { + url: 'https://pipedream.com/string', + label: 'Pipedream: String (alpha) landing page', + asOf: '2026-09-15', + }, ], }, naturalLanguageBuilding: { @@ -370,35 +379,31 @@ export const pipedreamProfile: CompetitorProfile = { ], }, knowledgeBaseRag: { - value: 'No dedicated customer-facing KB/RAG product feature', + value: + "Unknown: No dedicated customer-facing KB/RAG product feature is documented across Pipedream's current docs, but the specific detail that Pipedream built an internal Postgres+pgvector RAG system for its own support bot is no longer publicly documented — its sole source has gone dead.", detail: - 'Pipedream built an internal Postgres+pgvector RAG system to power its own documentation search/chat assistant, but it is not offered as a customer-usable knowledge-base/vector-store feature inside workflows.', - shortValue: 'No customer-facing KB/RAG feature', - confidence: 'estimated', - sources: [ - { - url: 'https://pipedream.com/blog/build-your-own-chat-bot-with-openai-and-pipedream/', - label: 'Pipedream Blog: Build your own chat bot with OpenAI and Pipedream', - asOf: '2026-07-04', - }, - ], + "Pipedream's blog previously described an internal Postgres+pgvector RAG system built to power its own documentation search/chat assistant, but that blog post now redirects (302) to /docs, and no independent source corroborates that implementation detail. Separately, a search of Pipedream's current documentation index turns up no page describing a customer-usable knowledge-base, vector-store, or RAG feature inside workflows, so the higher-level claim (no customer-facing KB/RAG product) still holds, even though the specific internal-architecture detail can no longer be sourced.", + shortValue: 'Unknown, no customer-facing KB/RAG feature found', + confidence: 'unknown', + sources: [], }, mcpSupport: { value: 'Yes: first-class, hosted MCP server', detail: - 'Pipedream runs a hosted MCP server (mcp.pipedream.com) exposing 3,000+ apps / 10,000+ tools to any MCP client, with managed OAuth and credential isolation. Its GitHub repo also includes a reference/self-hosted MCP server implementation, though Pipedream notes it is no longer actively maintained and recommends the hosted remote MCP server for production use.', + "Pipedream runs a hosted MCP server (mcp.pipedream.com) exposing 3,000+ apps / 10,000+ tools to any MCP client, with managed OAuth and credential isolation. Its GitHub repo formerly included a reference/self-hosted MCP server implementation; Pipedream removed that directory from the repository entirely in July 2026, with the removal commit noting the README had flagged it as a reference implementation only, superseded by Pipedream's hosted remote MCP server for production use.", shortValue: 'Hosted MCP server, 3,000+ apps as tools', confidence: 'verified', sources: [ { url: 'https://pipedream.com/docs/connect/mcp', label: 'Pipedream Docs: MCP Servers', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { - url: 'https://github.com/PipedreamHQ/pipedream/blob/master/modelcontextprotocol/README.md', - label: 'GitHub: Modelcontextprotocol README (reference implementation, unmaintained)', - asOf: '2026-07-08', + url: 'https://github.com/PipedreamHQ/pipedream/commit/22fe22c5e2eb88a93e7e4e228abed60936f79fc4', + label: + 'GitHub commit: "Remove deprecated modelcontextprotocol and docs-v2 directories"', + asOf: '2026-09-15', }, ], }, @@ -570,7 +575,11 @@ export const pipedreamProfile: CompetitorProfile = { shortValue: 'Node.js, Python, Bash, or Go steps', confidence: 'verified', sources: [ - { url: 'https://pipedream.com/docs', label: 'Pipedream Docs', asOf: '2026-07-02' }, + { + url: 'https://pipedream.com/docs/workflows/building-workflows', + label: 'Pipedream Docs: Building Workflows', + asOf: '2026-09-15', + }, ], }, codeSandboxRuntime: { @@ -610,15 +619,10 @@ export const pipedreamProfile: CompetitorProfile = { shortValue: 'Workflows hosted as REST endpoints', confidence: 'verified', sources: [ - { - url: 'https://pipedream.com/blog/creating-workflows-programmatically/', - label: 'Pipedream Blog: Creating Workflows with the REST API', - asOf: '2026-07-02', - }, { url: 'https://pipedream.com/docs/rest-api/examples/workflows', label: 'Pipedream Docs: REST API Example - Create a Workflow', - asOf: '2026-07-04', + asOf: '2026-09-15', }, ], }, @@ -696,22 +700,16 @@ export const pipedreamProfile: CompetitorProfile = { }, entryPaidPlan: { value: - 'Not publicly listed; third-party estimates range roughly $29–$45/mo for the entry paid tier', + "Publicly listed: the entry paid tier is 'Basic,' priced at $45/mo billed monthly or $29/mo ($348/yr) billed annually — a $192/yr discount for annual billing. It includes 2,000 credits/mo, 20M AI tokens/mo, 10 active workflows, and 5 connected accounts, sitting between the Free plan ($0/mo, 100 credits/mo, 3 workflows/3 accounts) and the 'Advanced' plan ($74/mo monthly or $49/mo annual, unlimited workflows/accounts, control-flow operators, GitHub Sync).", detail: - "Pipedream's own pricing page is JavaScript-rendered and not directly verifiable via static fetch. Third-party sources report conflicting numbers for the entry paid tier, roughly $29/mo to $45/mo for around 2,000 credits/month, but the exact current price is unconfirmed from a primary source.", - shortValue: '~$29–$45/mo (unconfirmed)', - confidence: 'estimated', + "Pipedream's pricing page renders its plan cards and prices client-side via JavaScript, but toggling between the 'Monthly' and 'Annual' billing views on the live page directly confirms the figures above: Basic shows '$45/mo' with 'Save $192 by switching to annual' on the Monthly view, and '$29/mo — $348 billed annually' on the Annual view. The page's plan lineup is Free / Basic / Advanced / Connect / Business (the last a custom-priced, contact-sales tier), so pricing for the entry paid tier is now clearly and precisely public rather than an unconfirmed third-party estimate.", + shortValue: 'Basic: $45/mo, or $29/mo billed annually', + confidence: 'verified', sources: [ { url: 'https://pipedream.com/pricing', - label: - 'Pipedream Pricing page (official, JS-rendered, not independently verifiable via fetch)', - asOf: '2026-07-02', - }, - { - url: 'https://automationatlas.io/answers/pipedream-pricing-explained-2026/', - label: 'Automation Atlas: Pipedream Pricing Explained 2026 (third-party)', - asOf: '2026-07-02', + label: 'Pipedream Pricing page (Basic plan, Monthly/Annual toggle)', + asOf: '2026-09-15', }, ], }, @@ -741,26 +739,26 @@ export const pipedreamProfile: CompetitorProfile = { security: { compliance: { value: - 'Yes: SOC 2 Type 2, with the report provided on request, plus HIPAA support (Pipedream acts as a Business Associate and signs BAAs, Enterprise) and GDPR handled through Standard Contractual Clauses. Sensitive data is encrypted at rest via AWS KMS, whose ISO 27001/27017/27018 coverage is inherited from the AWS infrastructure layer. No independent Pipedream-held ISO 27001, PCI, or FedRAMP certification appears on its trust page.', + 'Yes: SOC 2 Type 2, with the report provided on request, plus HIPAA support (Pipedream acts as a Business Associate and signs BAAs, on the Business plan) and GDPR handled through Standard Contractual Clauses. Sensitive data is encrypted at rest via AWS KMS, whose ISO 27001/27017/27018 coverage is inherited from the AWS infrastructure layer. No independent Pipedream-held ISO 27001, PCI, or FedRAMP certification appears on its trust page.', detail: - "Pipedream's Privacy and Security page states it provides a SOC 2 Type 2 report on request, undergoes annual third-party audits, and uses continuous-compliance monitoring tooling. It acts as a Business Associate and signs Business Associate Addendums (BAAs) for HIPAA/PHI use cases (Enterprise), and uses Standard Contractual Clauses (SCCs) for GDPR-related data transfers. Sensitive data (OAuth grants, key-based credentials, env vars) is encrypted at rest with AES-256-GCM via AWS KMS, which itself holds SOC 1/2/3 and ISO 27001/27017/27018 certifications. That ISO/PCI/FedRAMP coverage is inherited from the AWS infrastructure layer, not a certification Pipedream independently holds on its own trust page. Some third-party review sites describe Pipedream itself as directly PCI, FedRAMP, and CSA STAR compliant, but Pipedream's own security documentation does not corroborate this.", + "Pipedream's Privacy and Security page states it provides a SOC 2 Type 2 report on request, undergoes annual third-party audits, and uses continuous-compliance monitoring tooling. It acts as a Business Associate and signs Business Associate Addendums (BAAs) for HIPAA/PHI use cases — the pricing page's plan-comparison table checks 'HIPAA' only for the Business plan — and uses Standard Contractual Clauses (SCCs) for GDPR-related data transfers. Sensitive data (OAuth grants, key-based credentials, env vars) is encrypted at rest with AES-256-GCM via AWS KMS, which itself holds SOC 1/2/3 and ISO 27001/27017/27018 certifications. That ISO/PCI/FedRAMP coverage is inherited from the AWS infrastructure layer, not a certification Pipedream independently holds on its own trust page. Some third-party review sites describe Pipedream itself as directly PCI, FedRAMP, and CSA STAR compliant, but Pipedream's own security documentation does not corroborate this.", shortValue: 'SOC 2, HIPAA BAA, GDPR SCCs; ISO via AWS', - confidence: 'estimated', + confidence: 'verified', sources: [ { url: 'https://pipedream.com/docs/privacy-and-security', label: 'Pipedream Docs: Privacy and Security', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://pipedream.com/docs/privacy-and-security/hipaa', label: 'Pipedream Docs: HIPAA Compliance', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { - url: 'https://pipedream.com/blog/hippa/', - label: 'Pipedream Blog – Pipedream supports HIPAA compliance', - asOf: '2026-07-02', + url: 'https://pipedream.com/pricing', + label: 'Pipedream Pricing page (Security & Compliance table, HIPAA row)', + asOf: '2026-09-15', }, ], }, @@ -779,16 +777,22 @@ export const pipedreamProfile: CompetitorProfile = { ], }, rbac: { - value: 'Workspace-level access controls exist; granular per-plan RBAC not fully documented', + value: + "Documented, tiered access controls rather than full custom-role RBAC: Pipedream's plan-comparison page publishes 'Admin/editor roles' as included on every paid and free tier, 'Access controls for connected accounts' starting at the Advanced plan, and both 'Access controls for projects' and 'Require 2FA' (mandatory org-wide two-factor) reserved for the Business plan. This is coarser than a custom-role/permission-matrix RBAC system — there is no evidence of defining arbitrary named roles or granular per-resource permission sets — but the tiering itself is publicly documented, not undocumented.", detail: - 'OAuth clients and workspace administration are scoped to workspace admins, and internal staff access follows least-privilege principles, but no page enumerates a customer-facing RBAC feature (custom roles/permissions) or which plans include it.', - shortValue: 'Workspace-level controls; granular RBAC unclear', - confidence: 'estimated', + "Pipedream's pricing page Security & Compliance comparison table lists 'Admin/editor roles' checked for all five plans (Free, Basic, Advanced, Connect, Business); 'Access controls for connected accounts' checked from Advanced upward; and 'Access controls for projects' plus 'Require 2FA' checked only for Business. OAuth clients and workspace administration are otherwise scoped to workspace admins, and internal staff access follows least-privilege principles, but no page describes defining custom named roles or a granular per-resource permission matrix.", + shortValue: 'Tiered access controls documented; no custom-role RBAC', + confidence: 'verified', sources: [ + { + url: 'https://pipedream.com/pricing', + label: 'Pipedream Pricing page (Security & Compliance comparison table)', + asOf: '2026-09-15', + }, { url: 'https://pipedream.com/docs/privacy-and-security', label: 'Pipedream Docs: Privacy and Security', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -856,16 +860,21 @@ export const pipedreamProfile: CompetitorProfile = { }, dataRetention: { value: - 'Yes: Pipedream documents account-level retention rules for event/execution data, and states Enterprise customers can turn off all data retention, while internal application logs are deleted within about 30 days by default.', + 'Yes: Pipedream documents account-level retention rules for event/execution data, and states Business-plan customers can turn off all data retention, while internal application logs are deleted within about 30 days by default.', detail: - 'Documentation is thin on exact self-serve controls for standard workspaces; the clearest statement of org-configurable retention is tied to the Enterprise plan.', - shortValue: 'Yes, retention configurable on Enterprise', - confidence: 'estimated', + "Documentation is thin on exact self-serve controls for standard workspaces; the clearest statement of org-configurable retention is tied to the Business plan (Pipedream's pricing page checks 'Data retention controls' only for that tier).", + shortValue: 'Yes, retention configurable on Business plan', + confidence: 'verified', sources: [ { url: 'https://pipedream.com/docs/privacy-and-security', label: 'Privacy and Security at Pipedream', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://pipedream.com/pricing', + label: 'Pipedream Pricing page (Data retention controls row)', + asOf: '2026-09-15', }, ], }, @@ -1043,36 +1052,36 @@ export const pipedreamProfile: CompetitorProfile = { }, asyncExecution: { value: - "Yes: Pipedream's default HTTP-trigger behavior is asynchronous. A workflow returns an immediate 200 OK response to the caller while the rest of the workflow keeps running in the background, and developers can inspect the resulting event/execution afterward in the workflow's event history. A fully synchronous mode is also available via the `$.respond()` function, which can be called at the end of the workflow (blocking until completion) or mid-workflow with `immediate: true` to send a response early and continue processing after.", + "Partial: by default, a workflow's HTTP response (whether the built-in automatic 200 OK or an explicit `$.respond()` call) is not sent until the entire workflow finishes executing — Pipedream's docs state directly that '$.respond() is called at the end of your workflow, after all other code is done executing, so it may take some time to issue the response back.' To get an early response while the remaining steps keep running in the background, a step must explicitly call `$.respond({ immediate: true, ... })`; this is the opposite of a default-async model. No separate 'trigger now, poll status later' REST endpoint is documented, though the event/execution history UI lets you inspect completed runs afterward.", detail: - "Pipedream docs describe the default as an immediate 200 OK while processing continues in background; $.respond() gives synchronous or hybrid (immediate + continue) response patterns. No explicit API-based 'trigger now, poll status later' endpoint is documented, though the event inspector/history UI shows past execution results.", - shortValue: 'Yes, default is async with optional sync $.respond()', + "Pipedream's docs describe two response paths, both synchronous by default: the built-in automatic response (a canned '200 OK — Success!' payload, sent with no code required) and a manual `$.respond()` call in a code step. The docs' 'Timing of $.respond() execution' section is explicit that responses wait for the whole workflow to finish unless `immediate: true` is passed. The one documented exception is the no-code 'HTTP Response' action, which the docs say 'will always respond immediately when called in your workflow.' No explicit API-based 'trigger now, poll status later' endpoint is documented, though the event inspector/history UI shows past execution results.", + shortValue: 'No: response held until workflow completes by default', confidence: 'verified', sources: [ { url: 'https://pipedream.com/docs/workflows/triggers', - label: 'Pipedream Docs: HTTP-triggered workflows (default async response, $.respond)', - asOf: '2026-07-02', + label: 'Pipedream Docs: Triggers (default response timing, $.respond, immediate:true)', + asOf: '2026-09-15', }, { url: 'https://pipedream.com/docs/workflows/events/inspect/', label: 'Pipedream Docs: Inspect Events (viewing past execution results)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, executionLimits: { value: - 'Yes: Pipedream publishes hard execution limits. A single workflow execution times out at 300 seconds (5 minutes) by default on the free tier and can be raised to a maximum of 750 seconds (12.5 minutes) on paid plans; memory defaults to 256MB and can be raised up to 10GB. HTTP-triggered workflows are rate-limited to an average of 10 requests per second, with 429 Too Many Requests returned beyond that, and free workspaces additionally cap total test/dev runtime at 30 minutes per day.', + "Yes: Pipedream publishes hard execution limits. Workflow execution timeout defaults vary by trigger type — 30 seconds for HTTP- and Email-triggered workflows, 60 seconds for Cron-triggered workflows — and can be raised up to a plan-based ceiling: 300 seconds (5 minutes) on free tiers, 750 seconds (12.5 minutes) on paid tiers; memory defaults to 256MB and can be raised up to 10GB. HTTP-triggered workflows are rate-limited to an average of 10 requests per second, with 429 Too Many Requests returned beyond that. Free workspaces also have a daily builder-testing runtime cap that Pipedream's own limits page states as the bare number 750 with no time unit ('workspaces on the Free plan are limited to 750 of test runtime per day') — an apparent omission on Pipedream's own page, so the exact daily figure (750 seconds versus some other unit) is not clearly confirmed from that source.", detail: 'Additional published caps: HTTP request body 512KB, email payload including attachments 30MB, combined function logs/exports 6MB, /tmp scratch disk 2GB (fixed), event retention 7 days (free) with execution details expiring after 365 days.', - shortValue: '5-12.5 min timeout, 10 req/s HTTP cap', + shortValue: '30-60s default; 5-12.5min ceiling; 10 req/s cap', confidence: 'verified', sources: [ { url: 'https://pipedream.com/docs/workflows/limits', label: 'Pipedream Docs: Limits', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1120,36 +1129,41 @@ export const pipedreamProfile: CompetitorProfile = { support: { supportChannels: { value: - 'Community forum/Slack (free/lower tiers), email support and dedicated Slack channel (higher tiers), dedicated support on Business/Enterprise', + 'Community forum/public Slack (all tiers, including Free), email support starting at the Advanced plan, and a dedicated Slack Connect channel plus a dedicated Success Engineer reserved exclusively for the Business (top) plan.', detail: - 'Free tier gets community support (forum + public Slack) only; paid tiers add email support and a dedicated Slack channel; Business/Enterprise adds dedicated support resources.', - shortValue: 'Community free tier; email/Slack on paid', - confidence: 'estimated', + "Pipedream's pricing page Support & Expertise comparison table checks 'Community forums' and 'Public Slack' for every plan including Free; 'Email' is checked starting at Advanced (not Free or Basic); and 'Dedicated Slack Connect channel' plus 'Dedicated Success Engineer' are checked only for Business. Pipedream's Support page separately states 'Enterprise plan: Dedicated Pipedream Support Engineer, shared Slack Connect channel, and an SLA' and 'Advanced plan: Email support' — the same tiering as the pricing page, under the older 'Enterprise' label the Support page has not updated to 'Business.'", + shortValue: 'Community all tiers; email from Advanced; dedicated on Business', + confidence: 'verified', sources: [ { - url: 'https://pipedream.com/support', - label: 'Pipedream Support page', - asOf: '2026-07-02', + url: 'https://pipedream.com/pricing', + label: 'Pipedream Pricing page (Support & Expertise comparison table)', + asOf: '2026-09-15', }, { - url: 'https://pipedream.com/docs/pricing', - label: 'Pipedream Docs: Plans and Pricing', - asOf: '2026-07-02', + url: 'https://pipedream.com/support', + label: 'Pipedream Support page', + asOf: '2026-09-15', }, ], }, sla: { value: - 'Enterprise plan reportedly includes a dedicated Success Engineer and uptime guarantee; no published response-time SLA', + "Business plan (Pipedream's top self-serve tier, custom/contact-sales pricing) publishes a named SLA and a dedicated Support Engineer as included features — the pricing page's plan-comparison table has a checked 'SLA' row and an 'Uptime and availability SLAs' bullet for that plan — but Pipedream does not publish the specific numeric terms of that SLA (e.g., uptime percentage or response-time thresholds) on any public page.", detail: - 'No Pipedream page publishes a specific support response-time SLA for any tier; enterprise-level uptime/support arrangements appear to be negotiated directly with sales rather than published.', - shortValue: 'No published response-time SLA', - confidence: 'estimated', + "The plan-comparison matrix on Pipedream's pricing page has a row labeled 'SLA,' checked only for the Business plan; the Business plan's feature list also includes 'Uptime and availability SLAs.' Pipedream's support page separately states: 'Enterprise plan: Dedicated Pipedream Support Engineer, shared Slack Connect channel, and an SLA' — the same feature set as the pricing page's Business tier, just under Pipedream's older 'Enterprise' label, which the support page has not been updated to match. Neither page states an uptime percentage or a response-time commitment.", + shortValue: 'SLA named on Business plan; no numeric terms published', + confidence: 'verified', sources: [ { url: 'https://pipedream.com/pricing', - label: 'Pipedream Pricing page', - asOf: '2026-07-02', + label: 'Pipedream Pricing page (plan-comparison table, SLA row)', + asOf: '2026-09-15', + }, + { + url: 'https://pipedream.com/support', + label: "Pipedream Support page ('Enterprise plan' priority-support callout)", + asOf: '2026-09-15', }, ], }, @@ -1178,17 +1192,13 @@ export const pipedreamProfile: CompetitorProfile = { { url: 'https://newsroom.workday.com/2025-11-19-Workday-Signs-Definitive-Agreement-to-Acquire-Pipedream', label: 'Workday Newsroom – Workday Signs Definitive Agreement to Acquire Pipedream', - asOf: '2026-07-08', - }, - { - url: 'https://pipedream.com/blog/pipedream-to-be-acquired-by-workday/', - label: 'Pipedream Blog – Pipedream to be acquired by Workday', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { - url: 'https://pipedream.com/blog/series-a-financing/', - label: 'Pipedream Blog – Pipedream Closes $20M Series A Financing', - asOf: '2026-07-08', + url: 'https://www.prnewswire.com/news-releases/pipedream-closes-20-million-series-a-funding-round-led-by-true-ventures-301549167.html', + label: + 'PR Newswire – Pipedream Closes $20 Million Series A Funding Round Led by True Ventures', + asOf: '2026-09-15', }, { url: 'https://prospeo.io/c/pipedream', @@ -1201,14 +1211,19 @@ export const pipedreamProfile: CompetitorProfile = { value: 'Yes: Pipedream operates Pipedream University, a structured library of courses and video lessons that teaches workflow building, custom code steps, and platform concepts beyond ad hoc docs and blog posts.', detail: - 'No formal certification/exam program; it reads as structured video courses rather than a certification track.', + "No formal certification/exam program; it reads as structured video courses rather than a certification track. Pipedream's own site now links to this content inconsistently: pipedream.com/university, the URL Pipedream's own Support page still points to under 'Watch the University courses,' currently returns a genuine 404 ('404: Page not found'). The course content itself remains live as a 25-video 'Pipedream University' playlist on Pipedream's official YouTube channel, last updated September 2023, covering workflow building through custom component development.", shortValue: 'Yes, via Pipedream University courses', confidence: 'estimated', sources: [ { - url: 'https://pipedream.com/university', - label: 'Pipedream University', - asOf: '2026-07-02', + url: 'https://www.youtube.com/playlist?list=PL1t0lzi97kVxs0wBXesMmUNxkv8SvJHcG', + label: 'YouTube: Pipedream University playlist (official Pipedream channel)', + asOf: '2026-09-15', + }, + { + url: 'https://pipedream.com/support', + label: "Pipedream Support page ('Watch the University courses' link, target broken)", + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/power-automate.ts b/apps/sim/lib/compare/data/competitors/power-automate.ts index 6b226f779e9..76c12faddeb 100644 --- a/apps/sim/lib/compare/data/competitors/power-automate.ts +++ b/apps/sim/lib/compare/data/competitors/power-automate.ts @@ -64,12 +64,12 @@ export const powerAutomateProfile: CompetitorProfile = { { title: 'Built-in per-run analytics dashboard for cloud flows', description: - 'The Power Platform admin center ships a native Power Automate Analytics dashboard with Runs, Usage, Created, Errors, Shared, and Connectors reports for cloud flows, without needing a third-party observability tool.', - shortDescription: 'Native run analytics dashboard, no third-party tool needed.', + "The Power Platform admin center ships a native Power Automate Analytics dashboard with Runs, Usage, Created, Errors, Shared, and Connectors reports for cloud flows, without needing a third-party observability tool. This coverage excludes solution-aware cloud flows (flows created as part of a Dataverse solution), which Microsoft's own documentation states are not currently included in analytics reports, and the feature is not available in government or sovereign clouds.", + shortDescription: 'Native run analytics dashboard; excludes solution-aware flows', source: { url: 'https://learn.microsoft.com/en-us/power-platform/admin/analytics-flow', label: 'View analytics for Power Automate cloud flows - Power Platform | Microsoft Learn', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, ], @@ -260,10 +260,11 @@ export const powerAutomateProfile: CompetitorProfile = { }, versionControlDepth: { value: - 'Server-persisted version history with restore, for solution-aware cloud flows only; no native visual diff/compare between versions; no explicit undo/redo in the flow editor; no branching model', + 'Server-persisted version history with restore, for solution-aware cloud flows only; no native visual diff/compare between versions for cloud flows and no explicit undo/redo in the flow editor; no branching model for cloud flows. Desktop flows are the exception: Power Automate for desktop has a dedicated Version comparison view that diffs two saved versions side by side, with color-coded added/removed/edited indicators across subflows, actions, variables, UI elements, and images.', detail: 'The Version History panel lists timestamped snapshots and lets a user preview/restore a prior version as a new draft; desktop flows have a separate read-only version-comparison view. There is no branch-and-merge version control or in-editor undo/redo stack for cloud flows.', - shortValue: 'Version history with restore, no diff view, no branching', + shortValue: + 'Cloud flows: history + restore, no diff, no branching; desktop flows: full visual diff view', confidence: 'verified', sources: [ { @@ -279,7 +280,7 @@ export const powerAutomateProfile: CompetitorProfile = { { url: 'https://learn.microsoft.com/en-us/power-automate/desktop-flows/version-control', label: 'Version control in Power Automate for desktop - Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -350,7 +351,7 @@ export const powerAutomateProfile: CompetitorProfile = { detail: 'No built-in WYSIWYG document editor exists in Power Automate; document editing happens through separate connected apps like Word/SharePoint.', shortValue: 'No native document rich-text editor', - confidence: 'estimated', + confidence: 'unknown', sources: [], }, subWorkflows: { @@ -496,19 +497,19 @@ export const powerAutomateProfile: CompetitorProfile = { value: "Yes: a dedicated 'Start and wait for an approval' action pauses the flow run until a designated approver responds via the Power Automate mobile app, email, or Microsoft Teams notification, then resumes down Approve/Reject/custom-response branches", detail: - 'Supports first-to-respond or everybody-must-approve modes, custom response options beyond approve/reject, and timeout/escalation branches for production-grade approval chains.', + "Supports first-to-respond, everybody-must-approve, and sequential approval modes, plus custom response options beyond approve/reject (defined by the flow author). A production-grade approval chain can be built by adding a timeout branch manually (e.g., a parallel 'Delay' action feeding a Condition), but Power Automate does not document a built-in timeout or automatic escalation setting on the approval action itself.", shortValue: 'Built-in approval action with Teams/email/mobile response', confidence: 'verified', sources: [ { url: 'https://learn.microsoft.com/en-us/power-automate/get-started-approvals', label: 'Get started with Power Automate approvals - Power Automate | Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://learn.microsoft.com/en-us/power-automate/all-assigned-must-approve', label: 'Create an approval flow that requires everyone to approve - Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -906,17 +907,17 @@ export const powerAutomateProfile: CompetitorProfile = { security: { compliance: { value: - "Power Automate is SOC 2 Type 2 in-scope for Commercial and GCC environments only. It is not in-scope for GCC High or DoD in that attestation, separate from the product's general availability in those government clouds. The SOC 2 Type 2 report also incorporates the Cloud Security Alliance CCM and German BSI C5:2020 criteria. Beyond SOC 2 there is HIPAA/HITECH (Microsoft will sign a BAA as a business associate) and inclusion in the broader Office 365/Azure compliance program, which separately covers ISO 27001, FedRAMP, and other certifications at the Azure/Office 365 platform level.", + "Power Automate is SOC 2 Type 2 in-scope for Commercial, GCC, and GCC High environments per Microsoft's Office 365 SOC 2 Type 2 applicability table. It is not in-scope for the DoD environment in that attestation, separate from the product's general availability in that government cloud. The SOC 2 Type 2 report also incorporates the Cloud Security Alliance CCM and German BSI C5:2020 criteria. Beyond SOC 2 there is HIPAA/HITECH (Microsoft will sign a BAA as a business associate) and inclusion in the broader Office 365/Azure compliance program, which separately covers ISO 27001, FedRAMP, and other certifications at the Azure/Office 365 platform level.", detail: - "Microsoft's compliance documentation lists Power Automate among in-scope Commercial/GCC services. HIPAA/BAA support and CSA CCM/BSI C5:2020 coverage are documented directly in Microsoft's SOC 2 documentation. No Power Automate-specific ISO 27001/FedRAMP attestation page exists, so treat those two as platform-level coverage rather than product-specific certification.", - shortValue: 'SOC 2 (Commercial/GCC), HIPAA BAA, CSA CCM, BSI C5', + "Microsoft's compliance documentation lists Power Automate among in-scope Commercial, GCC, and GCC High services (not DoD). HIPAA/BAA support and CSA CCM/BSI C5:2020 coverage are documented directly in Microsoft's SOC 2 documentation. No Power Automate-specific ISO 27001/FedRAMP attestation page exists, so treat those two as platform-level coverage rather than product-specific certification.", + shortValue: 'SOC 2 (Commercial/GCC/GCC High, not DoD), HIPAA BAA, CSA CCM, BSI C5', confidence: 'estimated', sources: [ { url: 'https://learn.microsoft.com/en-us/compliance/regulatory/offering-soc-2', label: 'System and Organization Controls (SOC) 2 Type 2 - Microsoft Compliance | Microsoft Learn', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.keragon.com/hipaa/hipaa-compliant-checker/microsoft-powerautomate', @@ -1352,26 +1353,26 @@ export const powerAutomateProfile: CompetitorProfile = { }, companyMaturity: { value: - 'Microsoft Corporation. Founded April 4, 1975. Approximately 228,000 employees. Market capitalization approximately $2.8 trillion USD. Publicly traded (NASDAQ: MSFT) with quarterly revenue in the $80B+ range as of FY2026 SEC filings', + "Microsoft Corporation. Founded April 4, 1975. Approximately 223,000 employees (per Wikipedia's 2026 figure). Market capitalization approximately $3.69 trillion USD as of September 2026. Publicly traded (NASDAQ: MSFT) with quarterly revenue in the $80B+ range as of FY2026 SEC filings (Q3 FY2026 revenue was $82.9 billion).", detail: "Power Automate is a product line within Microsoft's Power Platform/Business Applications segment, backed by Microsoft's overall corporate scale rather than an independent startup.", - shortValue: 'Microsoft Corporation. Public, ~228,000 employees', + shortValue: 'Microsoft Corporation. Public, ~223,000 employees', confidence: 'verified', sources: [ { url: 'https://www.sec.gov/Archives/edgar/data/0000789019/000119312526191457/msft-ex99_1.htm', label: 'Microsoft Corp 8-K FY2026 filing', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://stockanalysis.com/stocks/msft/market-cap/', label: 'Microsoft (MSFT) Market Cap - StockAnalysis.com', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://en.wikipedia.org/wiki/Microsoft', label: 'Microsoft - Wikipedia', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/retool.ts b/apps/sim/lib/compare/data/competitors/retool.ts index 4af6688d829..332ec45816e 100644 --- a/apps/sim/lib/compare/data/competitors/retool.ts +++ b/apps/sim/lib/compare/data/competitors/retool.ts @@ -79,9 +79,9 @@ export const retoolProfile: CompetitorProfile = { 'Retool is proprietary and closed-source. The self-hosted deployment can be forked and customized and bundles open-source dependencies, but still requires a Retool-issued license key to run. No OSS license covers the product itself.', shortDescription: 'Closed-source product; self-hosted still requires a Retool license key.', source: { - url: 'https://docs.retool.com/self-hosted/tutorials/docker', - label: 'Deploy Self-hosted Retool with Docker | Retool Docs', - asOf: '2026-07-08', + url: 'https://docs.retool.com/legal/open-source-license-disclosure', + label: 'Open Source License Disclosure | Retool Docs', + asOf: '2026-09-15', }, }, { @@ -93,7 +93,7 @@ export const retoolProfile: CompetitorProfile = { source: { url: 'https://docs.retool.com/self-hosted/tutorials/docker', label: 'Deploy Self-hosted Retool with Docker | Retool Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -138,21 +138,26 @@ export const retoolProfile: CompetitorProfile = { }, selfHostOption: { value: - 'Yes: self-hosted deployment is available on Free, Team, and Business plans at the same pricing as cloud; Enterprise is required for unlimited users and advanced capabilities. A Retool-issued license key is required even when self-hosted.', + 'Yes, but Enterprise plan only: Retool\'s pricing page marks Free, Team, and Business as "Plan not available on Self-host," leaving Enterprise as the only tier that supports self-hosting (spanning managed cloud, blessed self-hosted, custom self-hosted, and air-gapped deployment). Retool\'s self-hosting marketing page likewise frames self-hosting as an Enterprise capability. A Retool-issued license key is required to run self-hosted Retool regardless of deployment method.', detail: - 'Self-hosted Retool is deployable via Docker (non-production/testing only) or Kubernetes/Helm (production).', - shortValue: 'Yes, on Free/Team/Business; license key required', + 'Self-hosted Retool is deployable via Docker Compose (non-production/testing only) or Kubernetes/Helm (production), both gated to the Enterprise plan.', + shortValue: 'Yes, Enterprise plan only; license key required', confidence: 'verified', sources: [ { url: 'https://retool.com/self-hosted', label: 'Retool Self Hosted', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.retool.com/self-hosted/tutorials/docker', label: 'Deploy Self-hosted Retool with Docker | Retool Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://retool.com/pricing', + label: 'Retool Pricing', + asOf: '2026-09-15', }, ], }, @@ -165,7 +170,7 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://docs.retool.com/self-hosted/tutorials/docker', label: 'Deploy Self-hosted Retool with Docker | Retool Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/tryretool/retool-onpremise', @@ -193,7 +198,7 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://docs.retool.com/legal/open-source-license-disclosure', label: 'Open Source License Disclosure | Retool Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -207,7 +212,7 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://retool.com/blog/git-branching-with-source-control', label: 'Introducing Source Control: Git-based branching and version control in Retool', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.retool.com/education/coe/customer-resources/environments', @@ -218,21 +223,21 @@ export const retoolProfile: CompetitorProfile = { }, versionControlDepth: { value: - 'Branch-based editing, pull-request review, and release history for controlling which version is live, plus rollback and blue/green deployments.', + 'Branch-based editing, pull-request review, and release history/versioning for controlling which version is live, plus rollback to a previous tagged release (described by third-party guides as a near-instant swap back to an earlier version, e.g. v1.1.9).', detail: - 'Source Control supports branch-based editing that isolates changes without overwriting teammates, pull-request review before merging into a live app, and Retool Releases to control which Git commit is live vs draft. No dedicated diff/compare view or client-vs-server undo/redo distinction exists.', - shortValue: 'Branching, PR review, and release history', + 'Source Control supports branch-based editing that isolates changes without overwriting teammates, pull-request review before merging into a live app, and Retool Releases to control which Git commit is live vs draft. Rollback restores a previous tagged release, described by a third-party delivery guide as a database-record swap that happens in milliseconds rather than a redeployed build. No dedicated diff/compare view, client-vs-server undo/redo distinction, or documented blue/green (parallel-environment traffic-switching) deployment mechanism exists in either cited source.', + shortValue: 'Branching, PR review, release history, and rollback', confidence: 'estimated', sources: [ { url: 'https://retool.com/blog/git-branching-with-source-control', label: 'Introducing Source Control: Git-based branching and version control in Retool', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://retoolers.io/blog-posts/staging-vs-production-in-retool-how-environments-and-versions-work', label: 'Staging vs Production in Retool: How Environments and Versions Work', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -292,7 +297,12 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://docs.retool.com/data-sources/guides/retool-database/link-tables', label: 'Link Retool Database tables (foreign keys) | Retool Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://community.retool.com/t/documentation-on-advanced-options-for-foreign-key-fields/15819', + label: 'Documentation on Advanced options for Foreign key fields (Retool Forum)', + asOf: '2026-09-15', }, { url: 'https://docs.retool.com/queries/guides/sql/writes', @@ -313,16 +323,16 @@ export const retoolProfile: CompetitorProfile = { }, richTextEditor: { value: - "Not true WYSIWYG editing: Retool's Rich Text Editor component lets users type HTML-formatted text, and a separate Text component displays Markdown, but neither is a full WYSIWYG Markdown editor. Community members have built custom components (based on the CKEditor library) to get true WYSIWYG Markdown editing.", + "Not true WYSIWYG editing in Retool's classic app builder (Retool's component reference for this control is explicitly scoped to classic apps, with a separate doc track for the newer app builder): Retool's Rich Text Editor component lets users type HTML-formatted text, and a separate Text component displays Markdown, but neither is a full WYSIWYG Markdown editor. Community members have built custom components (based on the CKEditor library) to get true WYSIWYG Markdown editing. Whether the new React-based app builder has an equivalent rich-text/Markdown component is not publicly documented.", detail: 'Multiple long-running Retool forum feature requests ask for WYSIWYG markdown editing, still unresolved.', - shortValue: 'No, native editor is HTML-input, not WYSIWYG markdown', + shortValue: 'No, classic-app editor is HTML-input, not WYSIWYG', confidence: 'verified', sources: [ { url: 'https://docs.retool.com/apps/reference/components/rich-text-editor', label: 'The Rich Text Editor component for classic apps', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://retool.com/blog/text-v2-app-documentation', @@ -480,14 +490,14 @@ export const retoolProfile: CompetitorProfile = { value: 'Native image generation only. No native video generation, text-to-speech, or speech-to-text block.', detail: - 'Retool\'s AI query block includes a native "Generate image" action (model options: GPT Image 1, GPT Image 1 Mini, and GPT Image 1.5, all via OpenAI) that returns a base64-encoded image. There is no native video-generation, text-to-speech, or speech-to-text block; users build these via third-party APIs.', + 'Retool\'s AI query block includes a native "Generate image" action (model options: GPT Image 1, GPT Image 1 Mini, GPT Image 1.5, and GPT Image 2, all via OpenAI) that returns a base64-encoded image. There is no native video-generation, text-to-speech, or speech-to-text block; users build these via third-party APIs.', shortValue: 'Image generation only, no video/TTS/STT', confidence: 'estimated', sources: [ { url: 'https://docs.retool.com/queries/guides/ai/image', label: 'Retool AI image actions (docs)', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://community.retool.com/t/speech-to-text-anybody/26774', @@ -530,12 +540,17 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://docs.retool.com/agents/guides/chat-with-agent', label: 'Retool Agents chat', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://retool.com/build-enterprise-apps/agents', label: 'Retool Agents: Create a custom-built agent team', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.retool.com/apps/guides/forms-inputs/agent-chat', + label: 'Getting started with Agent Chat | Retool Docs', + asOf: '2026-09-15', }, ], }, @@ -657,7 +672,7 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://docs.retool.com/workflows/guides/blocks/javascript', label: 'Execute JavaScript with the Code block | Retool Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, ], }, @@ -665,7 +680,7 @@ export const retoolProfile: CompetitorProfile = { value: 'Partial: the dependency set of a workflow Code block is user-configurable, but only at the package layer. In the workflow editor\'s Libraries tab, "Add Python library" picks from Retool\'s built-in library set, and "Modify requirements.txt" declares an arbitrary list of public PyPI packages with pinned versions; the JavaScript equivalent adds public npm packages via "Modify package.json". Package-level configuration only: there is no documented way to declare OS-level system packages or preinstalled CLI binaries for the runtime.', detail: - 'Beyond the preloaded set (Lodash, Moment.js, UUID, Numbro, and PapaParse are the JavaScript libraries Retool documents by name; the Python built-in set is not enumerated in the docs, which describe "built-in support for many popular libraries" and expose the list only through an interactive browser), builders add their own dependencies per workflow. Private npm/PyPI registries are self-hosted only and require a configured code-executor service, the container that runs user-defined JavaScript and Python with installed custom libraries; Retool sandboxes environment creation with NsJail, which needs privileged container access, and self-hosted operators can disable that sandboxing entirely with CONTAINER_UNPRIVILEGED_MODE.', + 'Retool\'s JavaScript Code blocks no longer preload any libraries by default: new workflows start with none configured, and Retool\'s docs say the editor no longer suggests Lodash (`_`), Moment.js (`moment`), Numbro (`numbro`), PapaParse (`Papa`), or UUID (`uuid`) in autocomplete, hover text, or AI-generated code. Workflows that already had these libraries configured keep them, but Retool recommends replacing them with custom per-workflow libraries added via "Modify package.json." The Python built-in set is not enumerated in the docs, which describe "built-in support for many popular libraries" and expose the list only through an interactive browser. Private npm/PyPI registries are self-hosted only and require a configured code-executor service, the container that runs user-defined JavaScript and Python with installed custom libraries; Retool sandboxes environment creation with NsJail, which needs privileged container access, and self-hosted operators can disable that sandboxing entirely with CONTAINER_UNPRIVILEGED_MODE.', shortValue: 'Packages only: per-workflow PyPI and npm libraries', confidence: 'verified', sources: [ @@ -677,7 +692,7 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://docs.retool.com/workflows/guides/blocks/javascript', label: 'Execute JavaScript with the Code block | Retool Docs', - asOf: '2026-08-10', + asOf: '2026-09-15', }, { url: 'https://docs.retool.com/self-hosted/reference/environment-variables', @@ -789,17 +804,17 @@ export const retoolProfile: CompetitorProfile = { security: { compliance: { value: - 'Yes: SOC 2 Type 2, plus ISO/IEC 27001:2022, GDPR, and CCPA certifications, and HIPAA via a signed BAA on Enterprise (self-hosted) plans. Reports and certificates are downloadable via the self-serve Trust Center (SafeBase-powered). PCI and FedRAMP are not confirmed.', + "Yes: SOC 2 Type 2, plus ISO/IEC 27001:2022, GDPR, and CCPA certifications, listed on and downloadable via the self-serve Trust Center (SafeBase-powered). HIPAA is not among the certifications Retool's Trust Center lists, and Retool's security-practices documentation does not mention HIPAA or a Business Associate Agreement; whether Retool will sign a BAA on any plan, including self-hosted Enterprise, is not publicly documented. PCI and FedRAMP are also not confirmed.", detail: - 'The Trust Center (SafeBase-powered) lists SOC 2 Type 2, ISO/IEC 27001:2022, GDPR, and CCPA certifications, and reports/certificates are downloadable from it self-serve. HIPAA compliance is available with a signed BAA on Enterprise (self-hosted) plans. PCI and FedRAMP are not confirmed.', - shortValue: 'SOC 2, ISO 27001, GDPR, CCPA; HIPAA via BAA', - confidence: 'estimated', + "The Trust Center (SafeBase-powered) Compliance section lists only SOC 2 Type 2, ISO/IEC 27001:2022, GDPR, and CCPA, and reports/certificates are downloadable from it self-serve. Neither the Trust Center nor Retool's Security Practices docs reference HIPAA or a Business Associate Agreement, so HIPAA/BAA support on any plan (including self-hosted Enterprise) is not publicly documented. PCI and FedRAMP are also not confirmed.", + shortValue: 'SOC 2, ISO 27001, GDPR, CCPA; no HIPAA documented', + confidence: 'verified', sources: [ - { url: 'https://trust.retool.com/', label: 'Retool Trust Center', asOf: '2026-07-02' }, + { url: 'https://trust.retool.com/', label: 'Retool Trust Center', asOf: '2026-09-15' }, { url: 'https://docs.retool.com/legal/security', label: 'Security Practices | Retool Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -812,7 +827,7 @@ export const retoolProfile: CompetitorProfile = { { url: 'https://docs.retool.com/legal/security', label: 'Security Practices | Retool Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/stackai.ts b/apps/sim/lib/compare/data/competitors/stackai.ts index 96cdae56443..01fdc928564 100644 --- a/apps/sim/lib/compare/data/competitors/stackai.ts +++ b/apps/sim/lib/compare/data/competitors/stackai.ts @@ -214,16 +214,16 @@ export const stackaiProfile: CompetitorProfile = { }, versionControlDepth: { value: - 'Version history with diff/compare and rollback via revert; no branching or client-side undo/redo', + "Version history with diff/compare and rollback via revert; branching and client-side undo/redo are not described anywhere in StackAI's version-control documentation", detail: 'Every save creates a full version snapshot; a compare tool diffs nodes, prompts/LLM config, and connections between versions. Any version can be reverted, which creates a new version and preserves history.', shortValue: 'Version history, diff, and rollback', - confidence: 'verified', + confidence: 'estimated', sources: [ { url: 'https://www.stackai.com/blog/the-agentic-development-life-cycle-how-to-manage-ai-agents-at-scale', label: 'The Agentic Development Life Cycle - StackAI blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -258,7 +258,7 @@ export const stackaiProfile: CompetitorProfile = { }, dataTables: { value: - "No: the Table node lets a workflow upload a CSV or XLSX file and query it with LLM-generated SQL, but only as a one-off input to that workflow run. That's different from a persistent, spreadsheet-like data table shared across a workspace, with defined row/column limits and spreadsheet-style keyboard navigation.", + "No: the Table node lets a workflow upload a CSV file and query it with LLM-generated SQL — the LLM turns a natural-language prompt into a SQL query and runs it against the uploaded CSV as a database table — but only as a one-off input to that workflow run. StackAI's documentation lists only CSV file upload as a Table node data source, with no mention of XLSX/Excel support. That's different from a persistent, spreadsheet-like data table shared across a workspace, with defined row/column limits and spreadsheet-style keyboard navigation.", detail: 'There is no standalone "Tables" product surface with persistent grid storage independent of a single workflow run.', shortValue: 'No, only per-workflow CSV analysis', @@ -267,7 +267,7 @@ export const stackaiProfile: CompetitorProfile = { { url: 'https://www.stackai.com/blog/how-to-build-spreadsheet-ai-agent', label: 'Build Spreadsheet AI Agent blog', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -373,14 +373,24 @@ export const stackaiProfile: CompetitorProfile = { }, evaluationGuardrails: { value: - 'Retrieval grounding, tool-call validation, and output enforcement are covered in vendor guidance, but there is no dedicated first-party evaluation or guardrails feature.', - shortValue: 'Guardrail guidance, no dedicated product', + 'Retrieval grounding, tool-call validation, and output enforcement are covered in vendor guidance rather than a dedicated first-party guardrails product, but StackAI does ship a dedicated first-party evaluation feature: the Evaluator View, which batch-tests an agent against CSV-uploaded test cases and grades each output with a separate LLM judge, either against a customizable evaluation prompt or by comparison to a gold-standard answer.', + shortValue: 'No guardrails product, but has Evaluator View', confidence: 'estimated', sources: [ { url: 'https://www.stackai.com/insights/how-to-design-ai-agent-guardrails-best-practices-for-input-validation-output-filtering-and-safety-controls', label: 'How to Design AI Agent Guardrails - StackAI insights', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.stackai.com/welcome-to-stackai/overview/platform-overview', + label: 'Platform Overview - StackAI Docs', + asOf: '2026-09-15', + }, + { + url: 'https://docs.stackai.com/agentic-adoption-and-security/observability/evaluator', + label: 'Evaluator View - StackAI Docs', + asOf: '2026-09-15', }, ], }, @@ -446,19 +456,24 @@ export const stackaiProfile: CompetitorProfile = { }, nativeChatDeployment: { value: - 'Yes: builders can publish a workflow or agent as a hosted Chat Assistant interface, alongside form, batch run, Slack, Teams, and API deployment targets. A chat widget can also be embedded on external sites via a copy-paste snippet.', + 'Yes: builders can publish a workflow or agent as a hosted Chat Assistant interface, alongside form, batch run, Slack, Teams, and API deployment targets. A chat widget can also be embedded on external sites as a Website Chatbot interface — StackAI\'s docs describe this as embedding "a chat widget on any webpage" without detailing the exact embed mechanism.', shortValue: 'Yes, native chat + embeddable widget', confidence: 'verified', sources: [ { url: 'https://docs.stackai.com/welcome-to-stackai/overview/platform-overview', label: 'Platform Overview', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.stackai.com/getting-started/start-here', label: 'Start Here', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.stackai.com/interface-and-deployment/end-user-interfaces', + label: 'End-User Interfaces - StackAI Docs', + asOf: '2026-09-15', }, ], }, @@ -542,14 +557,14 @@ export const stackaiProfile: CompetitorProfile = { integrationCount: { value: '70+ enterprise integrations', detail: - 'StackAI documentation states it connects to 70+ apps and services, including Notion, Airtable, AWS, BigQuery, GitHub, Google Workspace, HubSpot, MongoDB, and MCP. Some marketing pages cite a higher "100+" figure, but the documented apps list supports 70+.', + 'StackAI documentation states it connects to 70+ apps and services, including Notion, Airtable, BigQuery, GitHub, Gmail, Google Sheets, HubSpot, MongoDB, and MCP. AWS appears in StackAI\'s docs only as an LLM-hosting option (AWS Bedrock), not as a separate app-integration node, and there is no integration literally named "Google Workspace" — only individual nodes like Gmail, Google Sheets, and Google Docs. Some marketing pages cite a higher "100+" figure, but the documented apps list supports 70+.', shortValue: '70+ integrations', confidence: 'estimated', sources: [ { url: 'https://docs.stackai.com/workflow-builder/apps', label: 'StackAI Apps documentation (70+ apps and services)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1029,7 +1044,7 @@ export const stackaiProfile: CompetitorProfile = { value: 'Acquired by Asana in a deal worth approximately $75 million, announced May 28, 2026. StackAI is now a subsidiary of Asana rather than an independent company', detail: - 'Founders Antoni Rosinol and Bernardo Aceituno joined Asana as part of the acquisition. Prior to the acquisition, StackAI had raised just under $20M total: a ~$3M seed round in 2023 led by Gradient Ventures (with Y Combinator, Soma Capital, and others participating), and a $16M Series A in May 2025 led by Lobby Capital and LifeX Ventures, with Gradient Ventures and Epakon Capital returning.', + 'Founders Antoni Rosinol and Bernardo Aceituno joined Asana as part of the acquisition. Prior to the acquisition, StackAI had raised just under $20M total: a ~$3M seed round announced in May 2024 led by Gradient Ventures (with Y Combinator, Soma Capital, and others participating), and a $16M Series A in May 2025 led by Lobby VC and LifeX Ventures, with Gradient Ventures, Y Combinator, and Epakon Capital returning.', shortValue: 'Now a subsidiary of Asana (acquired 2026)', confidence: 'verified', sources: [ @@ -1041,12 +1056,17 @@ export const stackaiProfile: CompetitorProfile = { { url: 'https://www.stackai.com/blog/stack-ai-raises-16m-series-a-to-create-ai-agents-for-every-job', label: 'StackAI Raises $16M Series A - StackAI blog', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.stackai.com/blog/stack-ai-raises-3m-seed-round', + label: "StackAI's $3M Seed Round - StackAI blog", + asOf: '2026-09-15', }, { url: 'https://www.ycombinator.com/companies/stackai', label: 'StackAI - Y Combinator company page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/tines.ts b/apps/sim/lib/compare/data/competitors/tines.ts index b3d33ed2fe1..5598a2458db 100644 --- a/apps/sim/lib/compare/data/competitors/tines.ts +++ b/apps/sim/lib/compare/data/competitors/tines.ts @@ -574,14 +574,14 @@ export const tinesProfile: CompetitorProfile = { confidence: 'estimated', sources: [ { - url: 'https://www.tines.com/university/advanced/looping/', - label: 'Looping in Tines | Tines University', - asOf: '2026-07-02', + url: 'https://www.tines.com/docs/actions/types/event-transformation/message-only/', + label: 'Event Transformation: Message Only mode | Docs | Tines', + asOf: '2026-09-15', }, { url: 'https://www.tines.com/docs/actions/types/send-to-story/', label: 'Send to Story | Docs | Tines', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -855,7 +855,7 @@ export const tinesProfile: CompetitorProfile = { }, credentialGovernance: { value: - "Yes: credentials are scoped to Teams by default, and Team Admin/Editor roles control which teams a credential can be shared with. Sensitive settings like Access (where a credential can be used) and Domains (allowed outbound hosts/paths) are restricted to Team Admins or the credential's creator. Custom roles can extend the default viewer/builder/manager roles for finer-grained control.", + "Yes: credentials are scoped to Teams by default, and Team Admin/Editor roles control which teams a credential can be shared with. Sensitive settings like Access (where a credential can be used) are restricted to Team Admins (the 'Manage credentials' permission), and Domains (allowed outbound hosts/paths) can only be changed by the credential creator, users with the Team admin ('Manage credentials') role, or tenant owners. Enterprise Tenant Management customers can additionally create up to 25 custom roles that extend the default viewer/builder/manager roles for finer-grained, per-feature control; custom roles aren't available on lower plans and require contacting Tines to add them.", detail: "Governance operates at the team/role level with per-credential Access and Domain restrictions, not a credential-to-role assignment matrix like Sim's, but reaches a similar outcome.", shortValue: 'Yes: team-scoped credential access rules', @@ -864,12 +864,17 @@ export const tinesProfile: CompetitorProfile = { { url: 'https://www.tines.com/docs/credentials/credential-configuration/access/', label: 'Access | Docs | Tines', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.tines.com/docs/admin/user-administration/custom-roles/', label: 'Custom roles | Docs | Tines', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.tines.com/docs/credentials/credential-configuration/domain-restriction/', + label: 'Domain restriction | Docs | Tines', + asOf: '2026-09-15', }, ], }, @@ -890,16 +895,16 @@ export const tinesProfile: CompetitorProfile = { }, dataRetention: { value: - 'No: audit logs have a fixed two-year retention period, with no org-configurable retention window for logs or soft-deleted resources. Self-hosted deployments expose configurable event/rate limits via environment variables, but not data retention windows.', + 'Yes: Tines audit logs retain data for up to two years by default, and tenant admins can lower that window to as little as 30 days from the settings cog — a genuine org-configurable retention control for audit logs. Self-hosted deployments separately expose configurable event/rate limits via environment variables; retention of workflow/execution data beyond audit logs is not documented as separately configurable.', detail: - 'Org can extend retention indirectly by exporting audit logs to their own S3 bucket, but the in-product retention period itself is not shown as configurable.', - shortValue: 'No: fixed 2-year audit log retention', - confidence: 'estimated', + 'Org can also extend retention indirectly by exporting audit logs to their own S3 bucket, on top of the in-product configurable window.', + shortValue: 'Yes: audit log retention configurable, 30 days–2 years', + confidence: 'verified', sources: [ { url: 'https://www.tines.com/docs/admin/audit-logs/', label: 'Audit logs | Docs | Tines', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1158,16 +1163,16 @@ export const tinesProfile: CompetitorProfile = { support: { supportChannels: { value: - '"Dedicated support and training" for Business/Enterprise plans, per the pricing page; specific mechanisms (named CSM/CSE role, SLA terms) are not publicly itemized', + "Yes: Tines publishes a public Support Reference Guide detailing three base support tiers — Community/Explore (community support only, no SLA), Standard (email support, Monday–Friday 9:00–17:00 local time, 2h/4h/24h response times for Critical/Major/Minor severity), and Enterprise (email and Slack support available 24 hours a day Monday–Friday, with Critical-severity issues additionally covered 24x7 including weekends; 1h/2h/24h response times for Critical/Major/Minor severity). Every paying customer also gets a named Customer Success Manager, who oversees account success and leads business reviews, and a Customer Success Engineer, who handles onboarding and workflow-building guidance. Optional add-on 'Care Plans' (Growth, Enhanced, Total) tighten SLAs further, down to a 30-minute Critical response and 24x7 Slack support on the Total tier. Training is separate: free self-paced Tines University courses for all customers, plus paid instructor-led training arranged through your CSM.", detail: - 'The pricing page lists "Dedicated support and training" as a Business/Enterprise inclusion but does not name a specific role (e.g. Customer Success Manager/Engineer) or publish SLA terms.', - shortValue: 'Dedicated support and training for Business/Enterprise', - confidence: 'estimated', + "The pricing page no longer describes support inclusions after its 'Free edition / Paid editions' redesign; support tier and SLA specifics now live solely in the Support Reference Guide. Tines also publishes a quarterly SLA-adherence/CSAT scorecard (98.5-99% SLA adherence, 97-98% CSAT over the three months reported as of this check).", + shortValue: 'Named CSM/CSE roles; published SLA tables by plan and Care Plan tier', + confidence: 'verified', sources: [ { - url: 'https://www.tines.com/pricing/', - label: 'Pricing | Tines', - asOf: '2026-07-08', + url: 'https://www.tines.com/support-reference-guide/', + label: 'Support Reference Guide | Tines', + asOf: '2026-09-15', }, ], }, @@ -1200,19 +1205,19 @@ export const tinesProfile: CompetitorProfile = { confidence: 'estimated', sources: [ { - url: 'https://www.crunchbase.com/organization/tines', - label: 'Tines: Crunchbase Company Profile', - asOf: '2026-07-02', + url: 'https://am.gs.com/en-us/advisors/news/press-release/2025/growth-equity-tines', + label: 'Tines Secures $125M in Series C Financing Led by Goldman Sachs Alternatives', + asOf: '2026-09-15', }, { url: 'https://www.irishtimes.com/business/2026/05/28/tines-doubled-revenue-ahead-of-125m-funding-round/', label: 'Tines doubled revenue ahead of $125m funding round: Irish Times', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://tracxn.com/d/companies/tines/__vhdOz5rrILYCmI2TCvs_islx2OCpdITCseVJD-QhsR0', label: 'Tines: Tracxn Company Profile', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/vellum.ts b/apps/sim/lib/compare/data/competitors/vellum.ts index a27c480ed81..ddf052e1eb4 100644 --- a/apps/sim/lib/compare/data/competitors/vellum.ts +++ b/apps/sim/lib/compare/data/competitors/vellum.ts @@ -18,14 +18,15 @@ export const vellumProfile: CompetitorProfile = { 'Vellum is an enterprise AI development platform for building, evaluating, and deploying LLM prompts, workflows, and agents.', standoutFeatures: [ { - title: 'HIPAA compliance with a signable BAA', + title: 'HIPAA compliance, corroborated by a third-party audit', description: - 'Vellum is HIPAA compliant and enterprise customers can sign a Business Associate Agreement for handling protected health information, corroborated by a third-party Drata case study. Sim does not currently offer HIPAA compliance (both platforms hold SOC 2 Type 2).', - shortDescription: 'HIPAA compliant with a signable BAA; Sim does not offer HIPAA.', + "Vellum is HIPAA compliant, per both its own security documentation and a third-party Drata case study confirming Vellum achieved SOC 2 Type 1 and Type 2 attestations 'alongside HIPAA compliance.' Whether Vellum offers a signable Business Associate Agreement (BAA) for enterprise customers handling protected health information is not publicly documented on either source; enterprise customers should confirm BAA availability directly with Vellum's sales team. Sim does not currently offer HIPAA compliance (both platforms hold SOC 2 Type 2).", + shortDescription: + 'HIPAA compliant per a third-party audit; BAA availability not publicly documented. Sim does not offer HIPAA.', source: { url: 'https://drata.com/customers/vellum', label: 'Vellum Case Study: Drata', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -106,9 +107,14 @@ export const vellumProfile: CompetitorProfile = { asOf: '2026-07-02', }, { - url: 'https://skywork.ai/blog/vellum-ai-review-prompt-management-evaluations-orchestration/', - label: 'Vellum AI Review: Prompt Management, Evaluations & Orchestration', - asOf: '2026-07-02', + url: 'https://docs.vellum.ai/product/workflows/introduction', + label: 'Workflows Introduction - Vellum Documentation', + asOf: '2026-09-15', + }, + { + url: 'https://docs.vellum.ai/developers/workflows-sdk/introduction', + label: 'Workflows SDK Introduction - Vellum Documentation', + asOf: '2026-09-15', }, ], }, @@ -157,10 +163,19 @@ export const vellumProfile: CompetitorProfile = { ], }, templates: { - value: 'A templates page exists on vellum.ai; contents are not publicly detailed.', - shortValue: 'Exists; contents undocumented', + value: + 'Not publicly documented: vellum.ai/templates, previously referenced as a templates page, now redirects to the vellum.ai homepage rather than showing distinct template content. No dedicated templates page for the B2B workflow/agent platform could be located as of this check.', + detail: + "This mirrors the broader mid-2026 site pivot described elsewhere in this profile, where vellum.ai's marketing pages now serve the unrelated consumer 'Personal Intelligence' product. Whether the enterprise workflow platform still offers templates through docs.vellum.ai or the in-app product is not confirmed.", + shortValue: 'No longer found; URL now redirects to the consumer homepage.', confidence: 'unknown', - sources: [], + sources: [ + { + url: 'https://www.vellum.ai/templates', + label: 'Vellum Templates (redirects to homepage)', + asOf: '2026-09-15', + }, + ], }, license: { value: @@ -391,14 +406,14 @@ export const vellumProfile: CompetitorProfile = { confidence: 'verified', sources: [ { - url: 'https://skywork.ai/blog/vellum-ai-review-prompt-management-evaluations-orchestration/', - label: 'Vellum AI Review: Prompt Management, Evaluations & Orchestration', - asOf: '2026-07-02', + url: 'https://docs.vellum.ai/product/evaluation/online-evaluations', + label: 'Online Evaluations - Vellum Documentation', + asOf: '2026-09-15', }, { url: 'https://docs.vellum.ai/product/evaluation/quantitative-evaluation', label: 'Vellum Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -487,21 +502,22 @@ export const vellumProfile: CompetitorProfile = { }, kbChunkVisibility: { value: - "Yes: Vellum's Document Index search returns individual chunk-level results, and Advanced Chunking exposes per-chunk metadata (like source page range) alongside configurable chunk size and overlap settings, giving chunk-level visibility for debugging retrieval quality.", + "Yes: Vellum's Document Index search returns individual chunk-level results, and each search result includes per-chunk metadata (like the source page range where the chunk starts/ends), giving chunk-level visibility for debugging retrieval quality. Vellum's RAG-pipeline-evaluation guidance also recommends experimenting with different chunking sizes as a retrieval-tuning lever, though a dedicated 'Advanced Chunking' page with explicit overlap controls could not be located in current docs.", detail: 'Documented under the Document Indexes / Search API and RAG pipeline evaluation docs; each search result object represents one matching chunk, not a whole document.', - shortValue: 'Search returns per-chunk results with metadata', + shortValue: + 'Search returns per-chunk results with metadata; configurable overlap not confirmed.', confidence: 'verified', sources: [ { url: 'https://docs.vellum.ai/developers/client-sdk/document-indexes/search', label: 'Search - Vellum Documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.vellum.ai/product/evaluation/evaluating-rag-pipelines', label: 'Evaluating RAG Pipelines - Vellum Documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -596,14 +612,20 @@ export const vellumProfile: CompetitorProfile = { }, customCodeSteps: { value: - "Vellum 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.", - shortValue: 'Python/TypeScript code node with in-browser IDE', + "Vellum 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. A separate, newer 'Custom Nodes' feature also exists, but Vellum's own documentation does not state that Custom Nodes are intended to replace Code Execution Nodes; the two currently appear to be documented as parallel capabilities.", + shortValue: + 'Python/TypeScript code node with in-browser IDE; Custom Nodes exist separately, not documented as a replacement.', confidence: 'verified', sources: [ { url: 'https://docs.vellum.ai/product/workflows/nodes/code-execution-node', label: 'Vellum Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://www.vellum.ai/blog/introducing-custom-docker-images-custom-nodes', + label: 'Introducing Custom Docker Images & Custom Nodes - Vellum Blog', + asOf: '2026-09-15', }, ], }, @@ -697,7 +719,7 @@ export const vellumProfile: CompetitorProfile = { value: "Not publicly listed for the B2B enterprise platform: Vellum's current pricing page has been fully replaced by the unrelated consumer 'Personal Intelligence' product's plans. A September 2025 third-party pricing analysis, published before that switch, described the enterprise platform as execution-credit-based with per-tier seat caps (Free, Pro, Enterprise) rather than the prepaid-credit model now shown.", detail: - "Current pricing pages (vellum.ai/pricing, vellum.ai/docs/pricing) describe the consumer 'Personal Intelligence' product's plans (Base/Free and Pro $50/mo tiers with configurable vCPU/RAM/storage add-ons), not the enterprise workflow platform. The last third-party description of the enterprise platform's model itself states Vellum 'does not publicly list pricing details on its website,' so the figures below are third-party estimates, not Vellum-published prices.", + "Current pricing pages (vellum.ai/pricing) describe the consumer 'Personal Intelligence' product's plans, not the enterprise workflow platform: a free 'Start Free' tier, then three named paid tiers — Mighty ($30/month, 1 vCPU/2 GiB, 10 GB storage), Super ($100/month, 2.5 vCPU/5 GiB, 30 GB storage, plus a custom assistant email/subdomain), and Ultra ($200/month, 4 vCPU/8 GiB, 60 GB storage) — with a Custom Plan above that and self-hosting available at the cost of one's own infrastructure. The last third-party description of the enterprise platform's own pricing model states Vellum 'does not publicly list pricing details on its website,' so the enterprise-tier figures elsewhere in this profile are third-party estimates, not Vellum-published prices.", shortValue: 'Not publicly listed; third-party analysis describes credit-based tiers', confidence: 'unknown', sources: [ @@ -709,7 +731,7 @@ export const vellumProfile: CompetitorProfile = { { url: 'https://www.vellum.ai/pricing', label: 'Vellum Pricing (now shows the consumer product)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -762,35 +784,36 @@ export const vellumProfile: CompetitorProfile = { security: { compliance: { value: - 'SOC 2 Type 2 attested and HIPAA compliant, with a Business Associate Agreement (BAA) available for enterprise customers; no other certifications (ISO 27001, GDPR-specific attestation, PCI, FedRAMP) confirmed', + "SOC 2 Type 2 attested and HIPAA compliant; a Business Associate Agreement (BAA) is not publicly documented as available to enterprise customers on either Vellum's security docs or its third-party Drata case study; no other certifications (ISO 27001, GDPR-specific attestation, PCI, FedRAMP) confirmed", detail: - 'SOC 2 Type 2 is documented at docs.vellum.ai and corroborated by a third-party Drata customer case study noting Vellum achieved SOC 2 Type 1 and Type 2 attestations. Those same docs and case study state Vellum 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.', - shortValue: 'SOC 2 Type 2 and HIPAA; no other certs', - confidence: 'verified', + "SOC 2 Type 2 is documented at docs.vellum.ai/product/security/data-privacy-and-storage ('Vellum maintains SOC 2 Type 2 compliance and is HIPAA compliant') and corroborated by a third-party Drata customer case study noting Vellum achieved SOC 2 Type 1 and Type 2 attestations 'alongside HIPAA compliance.' Neither source mentions a Business Associate Agreement anywhere on the page, so BAA availability should be treated as unconfirmed rather than assumed. No mention of ISO 27001, PCI, or FedRAMP certification was found on either source.", + shortValue: + 'SOC 2 Type 2 and HIPAA confirmed; BAA availability unconfirmed; no other certs found.', + confidence: 'estimated', sources: [ { url: 'https://docs.vellum.ai/product/security/data-privacy-and-storage', label: 'Vellum Docs: Data Privacy and Storage', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://drata.com/customers/vellum', label: 'Vellum Case Study: Drata', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, dataResidency: { value: 'Unknown: no specific region/residency options documented', detail: - "Docs describe data being stored 'in Vellum's infrastructure, isolated in a dedicated, encrypted container' but do not specify selectable residency regions.", + "Vellum's Data Privacy and Storage docs state that 'All data stored in Vellum, including documents in Document Indexes, is encrypted using AES-256 GCM encryption,' and that this 'industry-standard encryption protocol ensures that your sensitive information remains secure both in transit and at rest,' but the page does not specify selectable residency regions or a customer choice of storage location.", shortValue: 'No selectable residency regions documented', confidence: 'unknown', sources: [ { url: 'https://docs.vellum.ai/product/security/data-privacy-and-storage', label: 'Vellum Docs: Data Privacy and Storage', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -862,9 +885,9 @@ export const vellumProfile: CompetitorProfile = { confidence: 'verified', sources: [ { - url: 'https://docs.vellum.ai/product/security/data-privacy-and-storage', - label: 'Data Privacy and Storage - Vellum Documentation', - asOf: '2026-07-02', + url: 'https://docs.vellum.ai/product/organizations/data-retention-policies', + label: 'Data Retention Policies - Vellum Documentation', + asOf: '2026-09-15', }, ], }, @@ -994,7 +1017,12 @@ export const vellumProfile: CompetitorProfile = { { url: 'https://docs.vellum.ai/product/monitoring/webhooks', label: 'Webhook Integration - Vellum Documentation', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://docs.vellum.ai/product/monitoring/datadog', + label: 'Datadog Integration - Vellum Documentation', + asOf: '2026-09-15', }, ], }, @@ -1071,10 +1099,10 @@ export const vellumProfile: CompetitorProfile = { support: { supportChannels: { value: - 'Email, an in-app chat, a shared Slack channel for active customers, and a Discord community', + "Email, an in-app chat, and a shared Slack channel for active customers are documented for the enterprise workflow platform; a Discord community exists on vellum.ai but is tied to Vellum's separate consumer product and its association with the workflow platform is unconfirmed", detail: - "Vellum's help center lists email (support@vellum.ai), in-app chat via the dashboard's 'Get Help' button, and a shared Slack channel for active customers; the enterprise page separately links a public Discord community. vellum.ai/pricing has since been repurposed for a different 'personal AI assistant' product, so its 'priority support' mention describes that product's paid add-on, not the workflow platform's support tiers — no priority-support or SLA claim is made here.", - shortValue: 'Email, in-app chat, Slack (customers), Discord community', + "Vellum's help center lists email (support@vellum.ai), in-app chat via the dashboard's 'Get Help' button, and a shared Slack channel for active customers. vellum.ai/enterprise has been repurposed for the consumer 'personal AI assistant' product and no longer links a Discord community; a Discord invite is still live from vellum.ai/community, but that page now serves the consumer product, so it can't be confirmed as the enterprise platform's channel. vellum.ai/pricing is likewise repurposed, so its 'priority support' mention describes that product's paid add-on, not the workflow platform's support tiers — no priority-support or SLA claim is made here.", + shortValue: "Email, in-app chat, Slack (customers); Discord's platform tie-in unconfirmed.", confidence: 'estimated', sources: [ { @@ -1085,7 +1113,12 @@ export const vellumProfile: CompetitorProfile = { { url: 'https://www.vellum.ai/enterprise', label: 'Vellum Enterprise', - asOf: '2026-07-08', + asOf: '2026-09-15', + }, + { + url: 'https://www.vellum.ai/community', + label: 'Vellum Community (Discord invite, now the consumer-product community page)', + asOf: '2026-09-15', }, ], }, @@ -1098,14 +1131,16 @@ export const vellumProfile: CompetitorProfile = { sources: [], }, community: { - value: 'Discord community exists', - shortValue: 'Discord community', - confidence: 'estimated', + value: + "Unconfirmed for the B2B workflow platform: a Discord invite link (discord.gg/ZABd9V2zM8) is live on vellum.ai/community, but that page and the rest of vellum.ai's marketing site now serve Vellum's separate consumer 'Personal Intelligence' product, so this Discord community can no longer be confirmed as associated with the enterprise workflow/agent platform compared here.", + shortValue: + 'Discord exists on the site, but is now tied to the consumer-product community page.', + confidence: 'unknown', sources: [ { - url: 'https://www.vellum.ai/enterprise', - label: 'Vellum Enterprise', - asOf: '2026-07-02', + url: 'https://www.vellum.ai/community', + label: 'Vellum Community (Discord invite, now the consumer-product community page)', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/workato.ts b/apps/sim/lib/compare/data/competitors/workato.ts index 3b941256c4c..9a00e33d7bc 100644 --- a/apps/sim/lib/compare/data/competitors/workato.ts +++ b/apps/sim/lib/compare/data/competitors/workato.ts @@ -49,9 +49,9 @@ export const workatoProfile: CompetitorProfile = { 'Agent Studio ships ready-made departmental agents (Genies) for IT, Sales, HR, Support, CX, and Marketing that customers can deploy and customize directly, alongside the option to build a custom agent from scratch.', shortDescription: 'Ready-made departmental agents (Genies) for IT, Sales, HR, and more.', source: { - url: 'https://docs.workato.com/agentic/agentic.html', - label: 'Agentic | Workato docs', - asOf: '2026-07-02', + url: 'https://www.workato.com/agentstudio', + label: 'Agent Studio | Workato', + asOf: '2026-09-15', }, }, { @@ -531,14 +531,14 @@ export const workatoProfile: CompetitorProfile = { value: "Text-only natively. Workato's own 'AI by Workato' utility connector has no generation actions, but a pre-built OpenAI connector adds a native 'Generate Images' (DALL-E) action for image generation. No native video or audio generation block exists.", detail: - "Workato's own 'AI by Workato' utility connector (built on Anthropic/OpenAI models) exposes only text/analysis actions: analyze image (vision/analysis, not generation), categorize text, draft email, parse text, summarize text, translate text. Generative-media capability beyond image generation would have to be assembled via generic HTTP/connector calls to third-party providers (e.g., ElevenLabs) rather than a first-party block.", + "Workato's own 'AI by Workato' utility connector (built on Anthropic/OpenAI models) exposes only text/analysis actions: analyze text, categorize text, draft email, parse text, summarize text, translate text. Generative-media capability beyond image generation would have to be assembled via generic HTTP/connector calls to third-party providers (e.g., ElevenLabs) rather than a first-party block.", shortValue: 'Image generation via OpenAI connector, no native video/audio', confidence: 'verified', sources: [ { url: 'https://docs.workato.com/connectors/ai-by-workato.html', label: 'AI by Workato | Workato docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.workato.com/platform/ai-by-workato', @@ -926,32 +926,32 @@ export const workatoProfile: CompetitorProfile = { }, dataResidency: { value: - "Yes, for enterprise customers: Workato enterprise customers can choose the region where their organization's automation data is stored and processed, from regional data centers (US, EU/Frankfurt, Japan, Singapore, Australia, Israel, China, South Korea). Once stored, data remains isolated in that region and is not shared or transferred across regions; there is no ongoing per-workspace or per-project residency toggle. Self-service (non-enterprise) users can't choose a region and are hosted in one of Workato's US data centers. Using more than one region requires signing up for and maintaining a separate Workato account in each desired region.", + "Yes, for enterprise customers: Workato enterprise customers can choose the region where their organization's automation data is stored and processed, from regional data centers (US, EU/Frankfurt, Japan, Singapore, Australia, Israel, China, South Korea, and the United Kingdom). Once stored, data remains isolated in that region and is not shared or transferred across regions; there is no ongoing per-workspace or per-project residency toggle. Self-service (non-enterprise) users can't choose a region and are hosted in one of Workato's US data centers. Using more than one region requires signing up for and maintaining a separate Workato account in each desired region.", shortValue: 'Enterprise customers pick a region; self-service defaults to US', confidence: 'verified', sources: [ { url: 'https://docs.workato.com/datacenter/datacenter-overview.html', label: 'Data center overview | Workato Docs', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, rbac: { value: - "Yes: RBAC 2.0 separates environment-level and project-level roles and permissions, and supports custom collaborator roles for granular access to projects, folders, and tools, following least-privilege principles. Availability of some custom-role features depends on the customer's pricing plan.", + 'Yes: RBAC 2.0 separates environment-level and project-level roles and permissions, and supports custom collaborator roles for granular access to projects, folders, and tools, following least-privilege principles.', shortValue: 'RBAC 2.0 with custom collaborator roles', confidence: 'verified', sources: [ { url: 'https://docs.workato.com/user-accounts-and-teams/role-based-access/access-control-v2.html', label: 'Manage workspace collaborators with role-based access control | Workato docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.workato.com/product-hub/changelog/rbac-2-0-enhanced-role-based-access-control/', label: 'RBAC 2.0: Enhanced Role-Based Access Control | Workato Product Hub', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1115,31 +1115,36 @@ export const workatoProfile: CompetitorProfile = { }, thirdPartyVetting: { value: - 'Partial: Workato has a large first-party catalog of native, Workato-built connectors, plus an open Community Library where any developer with Connector SDK access can build and publish a connector that other users install, alongside an invite-only Partner Connector tier that does get dedicated Workato code review. This is a genuine public marketplace for third-party executable connector code, unlike a vendor with no such marketplace at all.', + "Partial: Workato has a large first-party catalog of native, Workato-built connectors, plus an open Community Library where any developer with Connector SDK access can build and publish an open- or closed-source connector for others to install, subject to a Workato review before the listing goes live. This is a genuine public marketplace for third-party executable connector code, unlike a vendor with no such marketplace at all, but current docs do not describe a distinct, code-reviewed 'Partner Connector' tier separate from that community pipeline.", detail: - "Workato's docs distinguish three tiers: native connectors are built and maintained by Workato directly; Partner Connectors go through Workato's partnership program with dedicated developer accounts and code review by Workato engineers on the initial version and subsequent updates; and Community Connectors are built by any community member and published to the Community Library, reviewed within roughly one business day per Workato's own docs, but explicitly labeled 'intended as examples only.' Installing a community connector requires full Connector SDK privileges, and Workato tells users to independently evaluate and test a community connector's code before releasing it workspace-wide, since 'notwithstanding any Security Review conducted or any label provided by Workato, Workato does not certify, warrant or support any Community Listings, Partner Connectors or No Code Connectors.' Community connectors can also be published open-source (installable, viewable, and modifiable by anyone) or closed-source. This is structurally different from a vendor where every executable integration is first-party authored and code-reviewed through the vendor's own repository, with no public listing where an arbitrary third party can publish code for other users to install. No publicly documented incident (e.g., a malicious published community connector or a credential leak traced to one) exists; a Workato blog post on general AI/MCP security risk raises malicious lookalike marketplace tools as a theoretical, industry-wide concern rather than a Workato-specific incident.", - shortValue: 'Partial: first-party catalog plus an open, lightly-vetted marketplace', + "Workato's current docs describe two connector-contribution paths, not three formally reviewed tiers: native connectors are built and maintained by Workato directly, and Community Connectors are built by any community member with full Connector SDK privileges and published to the Community Library, where Workato notifies the developer by email once the connector has been reviewed — no stated turnaround time (e.g. a one-business-day SLA) is documented anywhere. Separately, a technology-partner program exists for ISVs building a connector to their own application: partners get a dedicated developer account plus tools and training, but current docs do not describe this as a distinct, code-reviewed 'Partner Connector' tier with its own review process or SLA. Workato's Acceptable Use Policy for the Community states that, 'notwithstanding any Security Review conducted or any label provided by Workato, Workato does not certify, warrant or support any Community Listings, Partner Connectors or No Code Connectors.' The Community Library's public asset listings also carry a blanket disclaimer that 'COMMUNITY ASSETS ARE INTENDED AS EXAMPLES ONLY,' describing shared library assets as 'a reusable set of templates, best practices and guidelines' rather than certified solutions. Installing a community connector requires full Connector SDK privileges, and community connectors can be published open-source (installable, viewable, and modifiable by anyone) or closed-source. This is still structurally different from a vendor where every executable integration is first-party authored and code-reviewed through the vendor's own repository, with no public listing where an arbitrary third party can publish code for other users to install. No publicly documented incident (e.g., a malicious published community connector or a credential leak traced to one) exists; a Workato blog post on general AI/MCP security risk raises malicious lookalike marketplace tools as a theoretical, industry-wide concern rather than a Workato-specific incident.", + shortValue: 'Partial: native catalog plus open marketplace, no reviewed Partner tier', confidence: 'verified', sources: [ { url: 'https://docs.workato.com/developing-connectors/community/community.html', label: 'Community connectors | Workato Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.workato.com/developing-connectors/community/community-listing.html', label: 'Contributing your connector | Workato Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.workato.com/product-hub/community-connectors/', label: 'Workato Community Connectors: What you need to know', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.workato.com/developing-connectors/sdk/quickstart/sharing.html', label: 'Workato Docs: Sharing a connector (open-source vs. closed-source)', - asOf: '2026-07-04', + asOf: '2026-09-15', + }, + { + url: 'https://assets.ctfassets.net/khy5qy7zbpmq/72IAM00Ydce3JM5EWjMJdu/9faed8b7e263383f48b8a7afc92e96ad/Workato_Community_Policy_2026-01-13.pdf', + label: 'Acceptable Use Policy for the Community | Workato', + asOf: '2026-09-15', }, ], }, @@ -1198,14 +1203,14 @@ export const workatoProfile: CompetitorProfile = { value: 'Yes: proactive email (and Slack/voice via Admin app) alerts on job failure, configurable and throttled', detail: - 'Workato sends error-notification emails automatically to the workspace owner by default, and admins can configure additional recipients under Workspace admin > Settings > Debug and logs > Error alerts. Notifications are throttled (default one minute per error type per recipe, with an optional one-hour throttle) to reduce noise. Beyond email, the Admin connector/Workbot integration can push failure notifications to Slack, or trigger a custom email or phone call/IVR (via Twilio) when a key recipe goes down, and Workbot lets teams watch for failures across all or specific recipes directly in Slack.', + 'Workato sends error-notification emails automatically to the workspace owner by default, and admins can configure additional recipients under Workspace admin > Settings > Error alerts. Notifications are throttled (default one minute per error type per recipe, with an optional one-hour throttle) to reduce noise. Beyond email, the Admin connector/Workbot integration can push failure notifications to Slack, or trigger a custom email or phone call/IVR (via Twilio) when a key recipe goes down, and Workbot lets teams watch for failures across all or specific recipes directly in Slack.', shortValue: 'Throttled email, Slack, and voice failure alerts', confidence: 'verified', sources: [ { url: 'https://docs.workato.com/recipes/error-notifications.html', label: 'Errors notifications emails | Workato Docs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://www.workato.com/the-connector/new-feature-manage-exceptions-with-workatos-admin-app/', @@ -1243,14 +1248,14 @@ export const workatoProfile: CompetitorProfile = { value: "Yes: Workato recipes can run as background jobs you check on later, rather than only blocking synchronously. A recipe run creates a job with an ID, and the Workato Jobs API lets you list jobs and fetch an individual job's status and details afterward. Workato also has explicit async patterns inside recipes: Callable Recipes support a 'fire-and-forget' async function call alongside a synchronous variant, a 'Wait for async calls' action to rejoin parallel async jobs, and a resume-token mechanism for jobs paused while awaiting external input.", detail: - 'The public Jobs API returns metadata/status only (job state, timestamps, step summaries) via job_id, not a rich step-by-step output payload; full run-time data is viewed on the job details page in the UI rather than returned by the API.', + "The public Jobs API returns full per-step run-time detail: the 'Get a job' endpoint's `lines` array includes each step's adapter, operation, and input/output data alongside job state and timestamps; the separate 'List jobs' endpoint returns metadata/status only, without run-time data.", shortValue: 'Yes: async job_id + pollable Jobs API', confidence: 'verified', sources: [ { url: 'https://docs.workato.com/workato-api/jobs.html', label: 'Workato API - Jobs', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://docs.workato.com/connectors/recipe-functions/actions/call-recipe-function-asynchronously.html', @@ -1338,14 +1343,14 @@ export const workatoProfile: CompetitorProfile = { support: { supportChannels: { value: - 'Email support (support@workato.com), an official documentation/help center, and a public community forum ("Systematic Community") for peer discussion; no dedicated live-chat channel is documented', + "Email support (support@workato.com), an official documentation/help center, and a public community forum ('Workato Builders Community,' rebranded from the earlier 'Systematic Community' and now also linking to a Slack community) for peer discussion; no dedicated live-chat channel is documented", shortValue: 'Email, docs, and community forum', confidence: 'estimated', sources: [ { - url: 'https://systematic.workato.com/', - label: 'Workato Systematic Community', - asOf: '2026-07-02', + url: 'https://community.workato.com', + label: 'Workato Builders Community', + asOf: '2026-09-15', }, ], }, @@ -1357,23 +1362,23 @@ export const workatoProfile: CompetitorProfile = { }, community: { value: - 'No published community size metrics. Workato operates a public forum ("Systematic Community") with active discussion, but no member count, Slack/Discord size, or GitHub star count is published, and the core product is closed source so no GitHub stars apply', + "No published community size metrics. Workato operates a public forum ('Workato Builders Community,' rebranded from the earlier 'Systematic Community,' with a linked Slack community) with active discussion, but no member count, Slack/Discord size, or GitHub star count is published, and the core product is closed source so no GitHub stars apply", shortValue: 'No published size metrics; closed-source', confidence: 'unknown', sources: [ { - url: 'https://systematic.workato.com/', - label: 'Workato Systematic Community', - asOf: '2026-07-02', + url: 'https://community.workato.com', + label: 'Workato Builders Community', + asOf: '2026-09-15', }, ], }, companyMaturity: { value: - 'Founded 2013; ~$421M total funding; last priced at $5.7B (2021), secondary markets ~$1.7B (mid-2025); ~1,400 employees', + 'Founded 2013; ~$421M total funding; last priced at $5.7B (Series E, Nov 2021); ~1,468 employees (as of Aug 2026)', detail: - 'Workato was founded in 2013 by Gautham Viswanathan and Vijay Tella (Palo Alto, CA). It has raised approximately $421M in total funding across rounds including a $200M Series E in late 2021 at a $5.7B valuation; secondary-market pricing as of mid-2025 implied a lower valuation near $1.7B. Employee count is approximately 1,414 as of May 2026, a mature, well-funded, late-stage private company with no IPO.', - shortValue: 'Founded 2013; ~$421M raised; ~1,400 employees', + 'Workato was founded in 2013 by Gautham Viswanathan and Vijay Tella (Palo Alto, CA). It has raised approximately $421M in total funding across rounds including a $200M Series E in November 2021 at a $5.7B valuation (an earlier January 2021 round was priced near $1.7B, a figure sometimes mistaken for a later secondary-market price). Employee count is approximately 1,468 as of August 2026, a mature, well-funded, late-stage private company with no IPO.', + shortValue: 'Founded 2013; ~$421M raised; ~1,468 employees', confidence: 'verified', sources: [ { @@ -1384,12 +1389,12 @@ export const workatoProfile: CompetitorProfile = { { url: 'https://techcrunch.com/2021/11/10/workato-storms-to-a-5-7b-valuation-after-raising-200m-for-its-enterprise-automation-platform/', label: 'Workato storms to a $5.7B valuation after raising $200M | TechCrunch', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://tracxn.com/d/companies/workato/__OtQBgvGNY2vOc7gmJydkZ3zQ6CHQGUY1_fzhOK4C3xU', label: 'Workato - 2026 Company Profile, Team, Funding & Competitors | Tracxn', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/competitors/zapier.ts b/apps/sim/lib/compare/data/competitors/zapier.ts index 57a34b24c60..c9f37b9d714 100644 --- a/apps/sim/lib/compare/data/competitors/zapier.ts +++ b/apps/sim/lib/compare/data/competitors/zapier.ts @@ -39,12 +39,12 @@ export const zapierProfile: CompetitorProfile = { { title: 'Hosted MCP server', description: - 'Zapier MCP exposes 9,000+ app connections and 30,000+ actions as Model Context Protocol tools over Streamable HTTP, letting any MCP-compatible AI client call Zapier actions. Each tool call costs 2 tasks on all plans.', - shortDescription: 'Exposes 9,000+ apps and 30,000+ actions as MCP tools for any AI client.', + 'Zapier MCP exposes 9,000+ app connections and 40,000+ actions as Model Context Protocol tools, letting any MCP-compatible AI client call Zapier actions. Each tool call costs 2 tasks on all plans.', + shortDescription: 'Exposes 9,000+ apps and 40,000+ actions as MCP tools for any AI client.', source: { url: 'https://zapier.com/blog/zapier-mcp-guide/', label: 'Zapier MCP: Perform 30,000+ actions in your AI tool', - asOf: '2026-07-02', + asOf: '2026-09-15', }, }, { @@ -211,14 +211,14 @@ export const zapierProfile: CompetitorProfile = { value: 'Server-persisted version history, rollback, and diff/compare; no branching; no native undo/redo', detail: - 'Zapier keeps a full Zap version history and lets you restore any prior version, creating a new draft from that version. A compare view shows the published version next to the in-progress draft, and drafts let you edit a live Zap without turning it off. There is no branching model with named branches merged back, and no dedicated undo/redo inside the draft editor.', - shortValue: 'Version history, rollback, and diff. No branching or undo', + 'Zapier keeps a full Zap version history and lets you restore any prior version, creating a new draft from that version. A compare view shows the published version next to the in-progress draft, and drafts let you edit a live Zap without turning it off. There is no branching model with named branches merged back, and no dedicated undo/redo inside the draft editor. Version history and rollback are available on paid plans only (Professional, Team, Enterprise) — the Free plan has neither.', + shortValue: 'Version history, rollback, diff; paid plans only', confidence: 'verified', sources: [ { url: 'https://help.zapier.com/hc/en-us/articles/14094586364941-Restore-your-Zap-to-a-prior-version-with-version-rollback', label: 'Restore your Zap to a prior version with version rollback', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://community.zapier.com/product-updates/we-ve-added-version-history-for-your-zaps-18362', @@ -233,7 +233,7 @@ export const zapierProfile: CompetitorProfile = { { url: 'https://help.zapier.com/hc/en-us/articles/9693520498445-Create-Zap-drafts-and-versions', label: 'Create Zap drafts and versions', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -260,7 +260,7 @@ export const zapierProfile: CompetitorProfile = { }, nativeFileStorage: { value: - "No: Zapier has no dedicated file-storage system with folder hierarchy, link-sharing, and recycle-bin recovery. 'Storage by Zapier' is a key-value data store (up to 25 KB per key, 500 keys per account) for small pieces of workflow data, not files. File handling happens per-step through connected apps like Google Drive or Dropbox.", + "No: Zapier has no dedicated file-storage system with folder hierarchy, link-sharing, and recycle-bin recovery. 'Storage by Zapier' is a key-value data store for small pieces of workflow data, not files — though Zapier's own docs disagree on the per-key size cap: the Storage by Zapier guide cites up to 25 KB per value, while the help center states values can be up to 1 MB (1,000,000 bytes); both sources agree on 500 keys per account. File handling happens per-step through connected apps like Google Drive or Dropbox.", detail: 'Zapier does offer folder-level permissions for organizing Zaps/Tables/Interfaces assets within the product, but that is asset organization, not a file-storage system for arbitrary documents.', shortValue: 'No: only a key-value store, not file storage', @@ -269,12 +269,12 @@ export const zapierProfile: CompetitorProfile = { { url: 'https://zapier.com/blog/storage-by-zapier-guide/', label: 'Storage by Zapier: A memory bank for your workflows', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.zapier.com/hc/en-us/articles/8496293271053-Save-and-retrieve-data-from-Zaps-using-Storage-by-Zapier', label: 'Save and retrieve data from Zaps using Storage by Zapier', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -363,14 +363,14 @@ export const zapierProfile: CompetitorProfile = { aiCapabilities: { multiLlmSupport: { value: - 'OpenAI (GPT family), Anthropic (Claude family), and Google (Gemini family), with BYOK for OpenAI and Anthropic only in Chatbots', - shortValue: 'OpenAI, Anthropic, and Google models; BYOK for OpenAI/Anthropic only', + 'OpenAI, Anthropic (Claude), Google (Gemini), Moonshot AI (Kimi), Z.ai (GLM), Amazon Bedrock, and Azure OpenAI built into AI by Zapier, plus direct app-integration access to Grok (xAI), DeepSeek, Mistral AI, OpenRouter, and Groq; BYOK is limited to OpenAI and Anthropic and only within Chatbots', + shortValue: 'OpenAI, Anthropic, Google, Kimi, GLM, and more; limited BYOK', confidence: 'verified', sources: [ { url: 'https://zapier.com/blog/ai-models-on-zapier/', label: 'Which AI models can you automate on Zapier?', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://help.zapier.com/hc/en-us/articles/21959873616013-Use-your-own-API-key-with-a-Zapier-Chatbot', @@ -767,12 +767,17 @@ export const zapierProfile: CompetitorProfile = { detail: "Includes unlimited Zaps, multi-step Zaps, and premium app access, beyond the free tier's 2-step limit.", shortValue: 'Professional plan from $19.99/mo for 750 tasks', - confidence: 'estimated', + confidence: 'verified', sources: [ { url: 'https://www.activepieces.com/blog/zapier-pricing', label: 'Zapier Pricing Breakdown (third-party)', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://zapier.com/pricing', + label: 'Zapier Pricing (official; $19.99/mo annual, $29.99/mo monthly for 750 tasks)', + asOf: '2026-09-15', }, ], }, @@ -806,32 +811,32 @@ export const zapierProfile: CompetitorProfile = { security: { compliance: { value: - "SOC 2 Type II and SOC 3 certified, plus GDPR and CCPA compliance. Reports are published and available via the Zapier Trust Center (trust.zapier.com). Not HIPAA-compliant (no BAAs, PHI unsupported). Some third-party sources also cite ISO 27001 and PCI DSS, though these aren't confirmed on Zapier's trust page.", + "SOC 2 Type II and SOC 3 certified, plus GDPR and CCPA compliance. The SOC 3 report is published for general distribution via the Zapier Trust Center (trust.zapier.com); the SOC 2 Type II report is available to existing and prospective customers only on request under NDA. HIPAA/BAA support and EU-US/UK/Swiss-US Data Privacy Framework certification are not addressed on Zapier's public security/trust pages. Some third-party sources also cite ISO 27001 and PCI DSS, though these aren't confirmed on Zapier's trust page.", detail: - "Zapier maintains SOC 2 Type II, SOC 3, GDPR, and CCPA compliance, with enterprise customers auto-opted-out of AI data training and full reports published and available via the Zapier Trust Center. Zapier does not support regulated healthcare or PHI data under HIPAA and will not sign BAAs. It also certifies to the EU-US/UK/Swiss-US Data Privacy Framework. ISO 27001 and PCI DSS are cited by secondary sources only and are not listed on Zapier's trust or security page.", - shortValue: 'SOC 2 Type II, SOC 3, GDPR, CCPA; no HIPAA', + "Zapier maintains SOC 2 Type II, SOC 3, GDPR, and CCPA compliance, with enterprise customers auto-opted-out of AI data training. The SOC 3 report is published for general distribution via the Zapier Trust Center, while the SOC 2 Type II report is available to existing and prospective customers only on request under NDA (per trust.zapier.com). Whether Zapier supports regulated healthcare/PHI data under HIPAA or will sign BAAs, and whether it certifies to the EU-US/UK/Swiss-US Data Privacy Framework, are not addressed by any of Zapier's public security, compliance, or trust pages checked here — treat both as undocumented rather than a confirmed 'no'. ISO 27001 and PCI DSS are cited by secondary sources only and are not listed on Zapier's trust or security page.", + shortValue: 'SOC 2, SOC 3, GDPR, CCPA; HIPAA/DPF undocumented', confidence: 'verified', sources: [ { url: 'https://zapier.com/blog/zapier-completes-soc-2-compliance-audit/', label: 'Zapier completes SOC 2 compliance audit', - asOf: '2026-07-02', + asOf: '2026-09-15', }, - { url: 'https://trust.zapier.com/', label: 'Zapier Trust Center', asOf: '2026-07-02' }, + { url: 'https://trust.zapier.com/', label: 'Zapier Trust Center', asOf: '2026-09-15' }, { url: 'https://zapier.com/security-compliance', label: 'Zapier | Secure and Compliant AI Orchestration at Scale', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.zapier.com/hc/en-us/articles/8496181993613-Security-and-Compliance', label: 'Security and Compliance – Zapier Help Center', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://zapier.com/legal/data-privacy', label: 'Data Privacy Overview | Zapier', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -963,14 +968,14 @@ export const zapierProfile: CompetitorProfile = { value: 'Yes: Zapier supports SAML 2.0 single sign-on (both Zapier-initiated and IdP-initiated), with Just-in-Time provisioning to auto-create user accounts on first login and optional Single Logout, on Team plans (SSO now included) and Enterprise plans.', detail: - 'Documented integration guides exist for Okta, Google Workspace, Microsoft Entra, JumpCloud, Duo, and OneLogin.', + 'Documented integration guides exist for Okta, Google Workspace, Microsoft Entra, JumpCloud, and OneLogin.', shortValue: 'Yes: SAML SSO with JIT auto-provisioning', confidence: 'verified', sources: [ { url: 'https://help.zapier.com/hc/en-us/articles/8496279747085-Set-up-single-sign-on-with-SAML', label: 'Set up single sign-on with SAML', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.zapier.com/hc/en-us/articles/33678718215309-Team-plan-updates-SSO-is-now-included-and-new-user-limits', @@ -1020,7 +1025,7 @@ export const zapierProfile: CompetitorProfile = { value: "Partial: Zapier's App Directory is an open developer ecosystem, not a closed first-party catalog. Any developer can build an integration on the Zapier Developer Platform and submit it for public listing. Zapier's review checks publishing/technical requirements (HTTPS-only endpoints, no hardcoded credentials, OAuth verification) rather than a deep security audit, and Zapier tells customers these apps are 'owned and operated by third parties' and that users are responsible for evaluating trust in the developer.", detail: - "Zapier's Partner Program docs describe review turnaround of up to 21 business days against publishing standards, and OAuth verification is framed as 'a helpful start' rather than a guarantee of an app's suitability. No security incident tied to a malicious third-party app published in the App Directory was found; separate publicly reported incidents (a February 2025 code-repository breach where customer data had been copied into repos for debugging, caused by a 2FA misconfiguration on an employee account, and a November 2025 npm supply-chain compromise of Zapier's own published developer-platform packages via the Shai-Hulud worm) involved Zapier's internal infrastructure and package registry, not the App Directory's third-party integration ecosystem.", + "Zapier's Partner Program docs describe review turnaround of up to 21 business days against publishing standards, and OAuth verification is framed as 'a helpful start' rather than a guarantee of an app's suitability. No security incident tied to a malicious third-party app published in the App Directory was found; separate publicly reported incidents (a February 2025 code-repository breach where customer data had been copied into repos for debugging, caused by a 2FA misconfiguration on an employee account, and a November 2025 npm supply-chain compromise of Zapier's own published developer-platform packages — Zapier's own incident report does not name the attacker or malware, describing it only as 'an apparent supply chain compromise') involved Zapier's internal infrastructure and package registry, not the App Directory's third-party integration ecosystem.", shortValue: 'Partial: open app directory, lighter technical review', confidence: 'verified', sources: [ @@ -1042,7 +1047,7 @@ export const zapierProfile: CompetitorProfile = { { url: 'https://docs.zapier.com/platform/build-cli/inc-547', label: 'Unauthorized Access to Zapier NPM Packages (official incident report)', - asOf: '2026-07-04', + asOf: '2026-09-15', }, { url: 'https://www.scworld.com/brief/cyber-incident-potentially-compromises-zapier-customer-data', @@ -1055,9 +1060,9 @@ export const zapierProfile: CompetitorProfile = { observability: { tracingDepth: { value: - 'Customer-facing per-run/per-step execution detail (Zap History) plus an account-level Analytics dashboard with success/error rate and task-usage metrics; no distributed-tracing spans or latency-percentile metrics', + 'Customer-facing per-run/per-step execution detail (Zap History) plus an account-level Analytics dashboard (Enterprise only) with success/error rate and task-usage metrics; no distributed-tracing spans or latency-percentile metrics', detail: - "Zap History logs every Zap run (up to 60 days / 10,000 runs) with per-step input/output detail and run status. The Analytics dashboard (Team/Enterprise) shows success-vs-error run percentages and task usage over time. Log Streams push real-time webhook events to a customer's own endpoint for external monitoring or SIEM dashboards. There is no latency-percentile view or distributed trace graph.", + "Zap History logs every Zap run (up to 60 days / 10,000 runs) with per-step input/output detail and run status. The Analytics dashboard (Enterprise only) shows success-vs-error run percentages and task usage over time. Log Streams push real-time webhook events to a customer's own endpoint for external monitoring or SIEM dashboards. There is no latency-percentile view or distributed trace graph.", shortValue: 'Per-run/step history and analytics, no distributed tracing', confidence: 'verified', sources: [ @@ -1074,7 +1079,7 @@ export const zapierProfile: CompetitorProfile = { { url: 'https://help.zapier.com/hc/en-us/articles/25444544607373-Review-your-account-usage-in-the-analytics-dashboard', label: 'Review your account usage in the analytics dashboard – Zapier', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://help.zapier.com/hc/en-us/articles/43732241361421-Set-up-log-streams-to-monitor-Zap-activity', @@ -1112,35 +1117,41 @@ export const zapierProfile: CompetitorProfile = { value: 'Yes: proactive default email alerts on Zap errors, configurable per-app frequency, plus auto-turn-off warnings and a dedicated "Zapier Manager" app for routing failure and pause events anywhere', detail: - 'By default, Zapier emails the account owner when a Zap errors, with per-app notification frequency configurable. If a Zap crosses a 95% error-rate threshold over 7 days, Zapier auto-turns it off, first sending a warning email with a grace period (24 hours on Team, 72 hours on Enterprise). The Zapier Manager app can trigger a Zap whenever any other Zap errors, is turned off, or is paused, so alerts route to Slack, SMS, PagerDuty, or elsewhere. While Autoreplay is retrying, no error email is sent until the final attempt fails.', + 'By default, Zapier emails the account owner when a Zap errors, with per-app notification frequency configurable. If a Zap crosses a 95% error-rate threshold over 7 days (and has run more than 20 times in that window), Zapier auto-turns it off, first sending a warning email with a grace period (24 hours on Team, 72 hours on Enterprise). The Zapier Manager app can trigger a Zap whenever any other Zap errors, is turned off, or is paused, so alerts route to Slack, SMS, PagerDuty, or elsewhere. While Autoreplay is retrying, no error email is sent until the final attempt fails.', shortValue: 'Default error emails, shutoff warnings, routable alerts', confidence: 'verified', sources: [ { url: 'https://help.zapier.com/hc/en-us/articles/8496289225229-Manage-notifications-when-errors-occur-in-Zap-workflows', label: 'Manage notifications when errors occur in Zap workflows – Zapier', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://zapier.com/apps/email/integrations/zapier-manager/60539/send-emails-with-new-zap-errors', label: 'Send emails with new Zap errors (Zapier Manager template)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://zapier.com/apps/email/integrations/zapier-manager/152952/send-notification-emails-for-new-zaps-turned-off', label: 'Send notification emails for new Zaps turned off (Zapier Manager template)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://zapier.com/help/autoreplay/', label: 'Autoreplay Tasks - Integration Help & Support | Zapier', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://help.zapier.com/hc/en-us/articles/8496216132621-Zap-is-not-running', + label: + 'Zap is not running – Zapier (95% error-rate/20-run threshold; 24h Team / 72h Enterprise grace period)', + asOf: '2026-09-15', }, ], }, dataDrains: { value: - "Yes: Zapier offers 'Log streams' (Enterprise) that continuously stream Zap configuration-change and run-outcome events to an external SIEM/monitoring destination such as Datadog or Splunk, in addition to an in-product account-wide audit log (Teams/Enterprise) for change and run-outcome history. (Note: a Zap Runs/Workflow API for programmatically pulling history exists only as an experimental, non-public feature, not generally available.)", + "Yes: Zapier offers 'Log streams' (Enterprise) that continuously stream Zap configuration-change and run-outcome events to an external SIEM/monitoring destination such as Datadog or Splunk, in addition to an in-product account-wide audit log (Teams/Enterprise) for asset and configuration change history (Zapier's Admin Center audit-log documentation does not describe run-outcome/execution-result logging in this in-product log). (Note: a Zap Runs/Workflow API for programmatically pulling history exists only as an experimental, non-public feature, not generally available.)", detail: "Log streams capture events only from when they're configured, not historical backfill.", shortValue: 'Yes: log streams to Datadog, Splunk, SIEM, plus in-product audit log', @@ -1154,7 +1165,7 @@ export const zapierProfile: CompetitorProfile = { { url: 'https://zapier.com/blog/mpe-admin-center-audit-logs/', label: 'Complete Control: Multi-Product Experience & Admin Center', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], }, diff --git a/apps/sim/lib/compare/data/sim.ts b/apps/sim/lib/compare/data/sim.ts index 8d53e616342..90bb3211a8f 100644 --- a/apps/sim/lib/compare/data/sim.ts +++ b/apps/sim/lib/compare/data/sim.ts @@ -18,13 +18,13 @@ export const simProfile: CompetitorProfile = { { title: 'AI Copilot / Chat agent-building surface', description: - 'A workspace-wide natural-language surface (Chat) that can build workflows, manage data, and take actions across integrations, plus an in-editor Copilot scoped to building and editing a single workflow directly.', + 'A workspace-wide natural-language surface (Chat) that can build workflows, manage data, and take actions across integrations, plus an in-editor Copilot (the `copilot` tab in the workflow panel) scoped to building and editing a single workflow directly — current public docs describe this workflow-scoped behavior under the Chat page without using the "Copilot" name.', shortDescription: 'Chat builds and manages work across the workspace; in-editor Copilot edits a single workflow.', source: { - url: 'https://docs.sim.ai/copilot', - label: 'Sim Docs: Copilot', - asOf: '2026-07-08', + url: 'https://docs.sim.ai/chat', + label: 'Sim Docs: Chat', + asOf: '2026-09-15', }, }, { @@ -101,13 +101,13 @@ export const simProfile: CompetitorProfile = { { title: 'Smaller integration catalog than the largest generalist automation platforms', description: - "Sim ships 266 first-party blocks and roughly 3,900 underlying tool actions. Platforms like Zapier (9,000+ apps) or Pipedream (3,000+ apps) list larger raw app counts. Sim's MCP support lets teams add custom integrations beyond the built-in catalog.", + "Sim ships 356 first-party blocks and roughly 5,500 underlying tool actions. Platforms like Zapier (9,000+ apps) or Pipedream (3,000+ apps) list larger raw app counts. Sim's MCP support lets teams add custom integrations beyond the built-in catalog.", shortDescription: - "266 blocks and ~3,900 tool actions, versus Zapier and Pipedream's larger raw app counts.", + "356 blocks and ~5,500 tool actions, versus Zapier and Pipedream's larger raw app counts.", source: { url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/blocks/registry-maps.ts', label: 'Sim codebase: BLOCK_REGISTRY count', - asOf: '2026-07-08', + asOf: '2026-09-15', }, }, { @@ -290,14 +290,14 @@ export const simProfile: CompetitorProfile = { value: 'Yes: a native spreadsheet-like Tables feature (typed columns, not an external DB connector) with full keyboard support (arrow keys, Tab, copy-paste bulk load, Cmd/Ctrl+Z undo) and atomic per-row writes from multiple workflows at once', detail: - 'No public fixed row-limit figure is documented (guidance says paginate reads past ~100k rows); a workflow can also be wired to run per row via a "workflow column."', + 'No public fixed row-limit figure is documented (a row may hold up to 400 KB of data, a table up to 1,000 columns, and query responses carry a 5 MB row-data budget, per the docs FAQ); a workflow can also be wired to run per row via a "workflow column."', shortValue: 'Spreadsheet-like tables with keyboard nav and undo', confidence: 'verified', sources: [ { url: 'https://docs.sim.ai/tables', label: 'Sim Docs: Tables', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -347,9 +347,10 @@ export const simProfile: CompetitorProfile = { asOf: '2026-07-08', }, { - url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/app/workspace/%5BworkspaceId%5D/settings/navigation.ts', - label: 'Sim codebase: Custom blocks nav entry (Enterprise/self-hosted gating)', - asOf: '2026-07-08', + url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/components/settings/navigation.ts', + label: + 'Sim codebase: Custom blocks nav entry gating (Enterprise/self-hosted entitlement)', + asOf: '2026-09-15', }, ], }, @@ -357,15 +358,15 @@ export const simProfile: CompetitorProfile = { aiCapabilities: { multiLlmSupport: { value: - '21 provider integrations (OpenAI, Anthropic, Google/Gemini, Azure OpenAI, Azure Anthropic, Groq, Cerebras, Mistral, xAI, Bedrock, Vertex, Ollama, OpenRouter, and more), with OpenRouter, LiteLLM, vLLM, and Ollama resolving models dynamically at runtime rather than from a fixed list, so effective model reach extends well beyond the 21 named providers', - detail: 'apps/sim/providers/models.ts defines 21 provider entries.', - shortValue: '21 providers plus dynamic-resolution aggregators (OpenRouter, LiteLLM, etc.)', + '25 provider integrations (OpenAI, Anthropic, Google/Gemini, Azure OpenAI, Azure Anthropic, Groq, Cerebras, Mistral, xAI, Bedrock, Vertex, Ollama, Ollama Cloud, OpenRouter, Sakana, Nvidia, Kimi, Z.ai, and more), with OpenRouter, LiteLLM, vLLM, and Ollama resolving models dynamically at runtime rather than from a fixed list, so effective model reach extends well beyond the 25 named providers', + detail: 'apps/sim/providers/models.ts defines 25 provider entries.', + shortValue: '25 providers plus dynamic-resolution aggregators (OpenRouter, LiteLLM, etc.)', confidence: 'verified', sources: [ { url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/providers/models.ts', label: 'Sim codebase: PROVIDER_DEFINITIONS', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -389,16 +390,21 @@ export const simProfile: CompetitorProfile = { confidence: 'verified', sources: [ { - url: 'https://docs.sim.ai/copilot', - label: 'Sim Docs: Copilot', - asOf: '2026-07-02', + url: 'https://docs.sim.ai/chat', + label: 'Sim Docs: Chat', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/simstudioai/sim/tree/main/apps/sim/app/workspace/%5BworkspaceId%5D/w/%5BworkflowId%5D/components/panel/components/copilot', + label: 'Sim codebase: in-editor Copilot panel component', + asOf: '2026-09-15', }, ], }, knowledgeBaseRag: { value: - 'Yes: hybrid vector (pgvector) plus full-text (tsvector) search knowledge base, 11 supported file formats (csv, doc, docx, html, json, md, pdf, pptx, txt, xlsx, yaml), configurable chunking, plus 51 connectors that continuously sync external sources (Google Drive, Confluence, Slack, Gmail, GitHub, HubSpot, Linear, Jira, and more) into the knowledge base rather than a one-shot upload', - shortValue: 'Hybrid vector + full-text search, 11 file formats, 51 connectors', + 'Yes: hybrid vector (pgvector) plus full-text (tsvector) search knowledge base, 11 supported file formats (csv, doc, docx, html, json, md, pdf, pptx, txt, xlsx, yaml), configurable chunking, plus 65 connectors that continuously sync external sources (Google Drive, Confluence, Slack, Gmail, GitHub, HubSpot, Linear, Jira, and more) into the knowledge base rather than a one-shot upload', + shortValue: 'Hybrid vector + full-text search, 11 file formats, 65 connectors', confidence: 'verified', sources: [ { @@ -413,8 +419,8 @@ export const simProfile: CompetitorProfile = { }, { url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/connectors/registry.ts', - label: 'Sim codebase: connector registry (51 connectors)', - asOf: '2026-07-08', + label: 'Sim codebase: connector registry (65 connectors)', + asOf: '2026-09-15', }, ], }, @@ -506,14 +512,15 @@ export const simProfile: CompetitorProfile = { value: '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', detail: - '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.', + 'Runtime MCP "discovery" resolves/refreshes the schema of an already-configured single tool in most configurations; an "MCP Server (Advanced)" tool entry is the exception — it hands the agent every tool the selected server currently exposes, though the server itself is still chosen by the workflow author at build time, not browsed at inference time.', shortValue: 'Tools pre-wired at build time; runtime discovery refreshes schemas', confidence: 'verified', sources: [ { url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/executor/handlers/agent/agent-handler.ts', - label: 'Sim codebase: agent tool resolution (pre-wired only)', - asOf: '2026-07-02', + label: + 'Sim codebase: agent tool resolution (pre-wired, Advanced mode exposes full server catalog)', + asOf: '2026-09-15', }, ], }, @@ -534,7 +541,7 @@ export const simProfile: CompetitorProfile = { }, agentSkills: { value: - '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', + '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 by uploading a `.md` file with YAML frontmatter or a `.zip` containing a SKILL.md, or by pasting SKILL.md content directly into the create form', detail: "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.", shortValue: 'Named, on-demand skills using the open SKILL.md format', @@ -543,7 +550,12 @@ export const simProfile: CompetitorProfile = { { url: 'https://docs.sim.ai/skills', label: 'Sim Docs: Agent skills', - asOf: '2026-07-02', + asOf: '2026-09-15', + }, + { + url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/app/workspace/%5BworkspaceId%5D/skills/components/skill-import/skill-import.tsx', + label: 'Sim codebase: skill import (file upload only, no GitHub URL)', + asOf: '2026-09-15', }, ], }, @@ -623,16 +635,16 @@ export const simProfile: CompetitorProfile = { integrations: { integrationCount: { value: - '1,000+ integrations counting individual API actions, built from 266 first-party blocks and roughly 3,900 underlying tool actions', + '1,000+ integrations counting individual API actions, built from 356 first-party blocks and roughly 5,500 underlying tool actions', detail: - 'Sim\'s landing page cites the "1,000+ integrations" figure; the block/tool-action counts are the same integration surface measured at a different level of granularity.', - shortValue: '1,000+ integrations (266 blocks, ~3,900 tool actions)', + 'Sim\'s landing page currently cites "hundreds of integrations"; the more granular block/tool-action counts below are the same integration surface measured at a different level of granularity.', + shortValue: '1,000+ integrations (356 blocks, ~5,500 tool actions)', confidence: 'verified', sources: [ { url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/blocks/registry-maps.ts', label: 'Sim codebase: BLOCK_REGISTRY', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.sim.ai/tools', @@ -642,21 +654,21 @@ export const simProfile: CompetitorProfile = { { url: 'https://sim.ai', label: 'Sim Landing Page', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, triggerTypes: { value: - 'Webhook, schedule/cron, chat, REST API, and event-based triggers for 61 apps (Slack, Gmail, GitHub, Stripe, etc.), plus a native row-level trigger on Sim Tables that fires on insert/update with an optional column watch-list and emits a before/after diff', + 'Webhook, schedule/cron, chat, REST API, and event-based triggers for 64 apps (Slack, Gmail, GitHub, Stripe, etc.), plus a native row-level trigger on Sim Tables that fires on insert/update with an optional column watch-list and emits a before/after diff', shortValue: - 'Webhook, cron, chat, REST API, 61 app triggers, plus a diff-aware Tables trigger', + 'Webhook, cron, chat, REST API, 64 app triggers, plus a diff-aware Tables trigger', confidence: 'verified', sources: [ { url: 'https://docs.sim.ai/triggers', label: 'Sim Docs: Triggers overview', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/triggers/table/poller.ts', @@ -704,22 +716,28 @@ export const simProfile: CompetitorProfile = { }, apiPublishing: { value: - 'Yes: a public REST API (mostly under /api/, with /api/v1 reserved for logs and audit-log endpoints) supporting API-triggered workflow execution and deployment rollback', + 'Yes: a public REST API under /api/v2/ (the documented API-reference surface), with a legacy /api/v1/** surface still live for backward compatibility (workflows, tables, knowledge, files, copilot, logs, audit-logs, admin) supporting API-triggered workflow execution and deployment rollback', detail: 'The API reference does not document SSE streaming, a resumable event buffer, a dedicated API-trigger block, or a chat-deployment surface as part of the REST API itself.', - shortValue: 'REST API (partially versioned) with rollback support', + shortValue: 'REST API (v2), with a legacy v1 surface still live', confidence: 'verified', sources: [ { url: 'https://docs.sim.ai/api-reference/getting-started', label: 'Sim Docs: API Reference - Getting Started', - asOf: '2026-07-08', + asOf: '2026-09-15', }, { url: 'https://docs.sim.ai/execution/api', label: 'Sim Docs: External API', asOf: '2026-07-08', }, + { + url: 'https://github.com/simstudioai/sim/tree/main/apps/sim/app/api/v1', + label: + 'Sim codebase: /api/v1 directory (workflows, tables, knowledge, files, copilot, logs, audit-logs, admin)', + asOf: '2026-09-15', + }, ], }, extensibilitySdk: { @@ -767,8 +785,8 @@ export const simProfile: CompetitorProfile = { pricing: { pricingModel: { value: - 'Credit-based usage billing (Stripe), with bring-your-own-key exemption from metered caps', - shortValue: 'Credit-based billing, BYOK exempt from caps', + "Credit-based usage billing (Stripe), with bring-your-own-key routing AI-model token costs directly to the provider and avoiding Sim's 1.1x hosted-model markup — the base run charge and any Sim-hosted tool usage still count against the plan's credit cap", + shortValue: 'Credit-based billing; BYOK avoids markup, not the credit cap', confidence: 'verified', sources: [ { @@ -776,6 +794,11 @@ export const simProfile: CompetitorProfile = { label: 'Sim Pricing', asOf: '2026-07-02', }, + { + url: 'https://docs.sim.ai/platform/costs', + label: 'Sim Docs: Costs (hosted multiplier and BYOK)', + asOf: '2026-09-15', + }, ], }, entryPaidPlan: { @@ -810,24 +833,24 @@ export const simProfile: CompetitorProfile = { }, byok: { value: - 'Yes: bring-your-own-key support exempts usage from metered credit caps, and multiple keys stored for the same provider are automatically round-robin rotated, with automatic fallback past any key that fails to decrypt', - shortValue: 'BYOK exempts credit caps; multi-key round-robin rotation', + "Yes: bring-your-own-key support routes AI-model usage costs directly to the provider (avoiding Sim's 1.1x hosted-model multiplier) rather than exempting all usage from the credit cap — the workflow base charge still applies — and multiple keys stored for the same provider are automatically round-robin rotated, with automatic fallback past any key that fails to decrypt", + shortValue: 'BYOK routes cost to provider, avoids markup; key rotation', confidence: 'verified', sources: [ { url: 'https://docs.sim.ai/platform/costs#bring-your-own-key-byok', label: 'Sim Docs: Bring Your Own Key (BYOK)', - asOf: '2026-07-02', + asOf: '2026-09-15', }, { - url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/lib/billing/calculations/usage-monitor.ts', - label: 'Sim codebase: BYOK usage-monitor logic', - asOf: '2026-07-02', + url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/providers/cost-policy.ts', + label: 'Sim codebase: BYOK billing policy (resolveModelCostPolicy)', + asOf: '2026-09-15', }, { url: 'https://github.com/simstudioai/sim/blob/main/apps/sim/lib/api-key/byok.ts', label: 'Sim codebase: BYOK key rotation', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -847,9 +870,9 @@ export const simProfile: CompetitorProfile = { asOf: '2026-09-15', }, { - url: 'https://sim.ai/enterprise', - label: 'Sim Enterprise Page', - asOf: '2026-07-02', + url: 'https://sim.ai', + label: 'Sim Landing Page (compliance badges)', + asOf: '2026-09-15', }, ], }, @@ -899,7 +922,7 @@ export const simProfile: CompetitorProfile = { }, auditLogging: { value: - 'Yes: dedicated audit_log table plus workflow execution logs, exposed via a public /v1/audit-logs API (Enterprise plan), plus continuous SIEM/warehouse export to Datadog, S3, GCS, Azure Blob, BigQuery, or Snowflake via a data-drains dispatcher', + 'Yes: dedicated audit_log table plus workflow execution logs, exposed via a public /v2/audit-logs API (Enterprise plan, GET /api/v2/audit-logs, requires organization admin/owner access), plus continuous SIEM/warehouse export to Datadog, S3, GCS, Azure Blob, BigQuery, or Snowflake via a data-drains dispatcher', shortValue: 'Audit log API plus SIEM/warehouse export', confidence: 'verified', sources: [ @@ -913,6 +936,11 @@ export const simProfile: CompetitorProfile = { label: 'Sim Docs: Data Drains', asOf: '2026-07-02', }, + { + url: 'https://docs.sim.ai/api-reference/audit-logs/listAuditLogs', + label: 'Sim Docs: List Audit Logs (GET /api/v2/audit-logs)', + asOf: '2026-09-15', + }, ], }, modelAndToolGovernance: { @@ -971,14 +999,14 @@ export const simProfile: CompetitorProfile = { }, dataRetention: { value: - 'Yes: Enterprise orgs can independently configure log retention, soft-deletion cleanup, and Chat/Copilot task cleanup (chats, runs, checkpoints, Inbox tasks) at 1 day to 5 years or Forever, applied org-wide with no per-workspace override', + 'Yes: Enterprise orgs can independently configure log retention, soft-deletion cleanup, and Chat/Copilot task cleanup (chats, runs, checkpoints, Inbox tasks) at 1 day to 5 years or Forever, applied org-wide by default with an optional per-workspace override for any workspace that needs different rules', shortValue: 'Configurable retention: 1 day to 5 years, or forever', confidence: 'verified', sources: [ { url: 'https://docs.sim.ai/platform/enterprise/data-retention', label: 'Sim Docs: Data Retention', - asOf: '2026-07-02', + asOf: '2026-09-15', }, ], }, @@ -1045,16 +1073,16 @@ export const simProfile: CompetitorProfile = { }, thirdPartyVetting: { value: - "Yes: every one of Sim's 266 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", + "Yes: every one of Sim's 356 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", detail: "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.", - shortValue: 'All 266 blocks are first-party authored and code-reviewed', + shortValue: 'All 356 blocks are first-party authored and code-reviewed', confidence: 'verified', sources: [ { url: 'https://github.com/simstudioai/sim/tree/main/apps/sim/blocks/blocks', label: 'Sim codebase: first-party block directory', - asOf: '2026-07-08', + asOf: '2026-09-15', }, ], },