Перейти к основному содержимому

AACFlow против Retool

AACFlow — ИИ-рабочее пространство, где команды создают, развёртывают и сопровождают ИИ-агентов визуально, в диалоге или кодом. Вот как AACFlow соотносится с Retool по архитектуре платформы, возможностям ИИ, интеграциям, ценам, безопасности и поддержке. Каждый факт ниже подтверждён источником и датой, последняя проверка: .

AACFlow — ИИ-рабочее пространство для создания, развёртывания и сопровождения ИИ-агентов. На этой странице AACFlow сравнивается с Retool по архитектуре платформы, возможностям ИИ, интеграциям, ценам, безопасности и соответствию требованиям, наблюдаемости и поддержке; используются факты с источниками и датами для тех, кто выбирает между двумя платформами.

Что такое AACFlow?

AACFlow is the AI workspace where teams build, deploy, and manage AI agents, connecting 1,000+ integrations and every major LLM to automate real work visually, conversationally, or with code.

Что такое Retool?

Retool is a low-code platform for building, deploying, and managing internal software (apps, workflows, and AI agents) that connect to databases, APIs, and LLMs.

AACFlow и Retool: сравнение по возможностям

В разделах ниже AACFlow и Retool сравниваются по платформе и развёртыванию, ценам, безопасности и соответствию требованиям, возможностям ИИ, интеграциям, наблюдаемости и поддержке.

Платформа и развёртывание

CompareAACFlow vs Retool
AACFlow
Retool
Тип конструктора
Retool
Low-code builder with AI-generated starting points (источник: Retool homepage, откроется в новой вкладке)Low-code/no-code visual app and workflow builder with an underlying React-based app runtime; supports AI-generated ("AppGen") starting points that users then refine visually or by editing generated queries/code.. Retool offers a React-based app builder where you can generate pages, components, and queries from a natural-language description and then edit the underlying logic directly.
Порог входа
AACFlow
Low, plus natural-language Chat for non-technical users (источник: AACFlow Docs: Introduction (visual, natural-language, and API/SDK building), откроется в новой вкладке)Low for visual building; natural-language Chat surface (with a workflow-scoped Copilot) for non-technical builders. Chat lets users describe a workflow in plain language and have AACFlow scaffold or edit it; the visual canvas requires no code to connect blocks.
Retool
Not publicly documentedUnknown. Retool has not published a learning-curve claim.
Варианты развёртывания
AACFlow
Managed cloud, no single-tenant VPC option (источник: AACFlow Pricing Page, откроется в новой вкладке)Cloud-hosted (managed, multi-tenant SaaS) operated by AACFlow. No documented managed single-tenant/VPC hosting tier. AACFlow is sold as a managed cloud service; there is no dedicated-instance/VPC offering.
Retool
Cloud, or self-hosted via Docker/Kubernetes (источник: Deploy Self-hosted Retool with Docker | Retool Docs, откроется в новой вкладке)Retool Cloud (multi-tenant SaaS), or self-hosted via Docker Compose (non-prod/testing) or Kubernetes with Helm chart (production).
Шаблоны
AACFlow
(источник: AACFlow codebase: templates gallery and APIs removed, откроется в новой вкладке)No: the pre-built workflow template gallery (landing and in-workspace) was removed platform-wide. AACFlow now surfaces per-integration starter prompts instead of a template library.
Retool
(источник: Retool Templates, откроется в новой вкладке)Yes: a public template gallery of ready-made, one-click apps/workflows/dashboards (e.g. inventory alerts, abandoned-cart recovery, ticket routing, DB admin panels, SLA/HR/sales dashboards) usable as-is or as a starting point.
Продвижение между средами
AACFlow
(источник: AACFlow Docs: Workspace Forks, откроется в новой вкладке)Yes: fork a whole workspace into a dev/qa/prod-style child, diff it, and promote or roll back changes in either direction. Credential and env-var remapping is required before every promote, so secrets are never silently copied across environments. Gated to the Enterprise plan.
Retool
(источник: Introducing Source Control: Git-based branching and version control in Retool, откроется в новой вкладке)Yes: via Retool Source Control (Git-based) across separate instances/spaces. Source Control lets teams branch an app, open pull requests, and merge changes across dev, staging/QA, and production, running on separate Retool instances (self-hosted Enterprise) or Retool Spaces (Cloud) with per-app control over what syncs. It targets Enterprise/self-hosted customers and requires connecting an external Git provider (GitHub, GitLab, or CodeCommit).
Контроль версий
AACFlow
Deployment rollback plus Copilot edit diff/revert (источник: AACFlow codebase: WorkflowDiffEngine, откроется в новой вкладке)Deployed-version history with rollback for every workflow; server-persisted checkpoint/revert and visual diff (accept/reject) specifically for Copilot AI edits. Manual drag-and-drop undo/redo is client-side/localStorage only (capped at 100 ops, 5 stacks), not server-synced across devices. Deployment history does not include an arbitrary version-to-version diff tool, and knowledge base documents have no version history.
Retool
Branching, PR review, and release history (источник: Introducing Source Control: Git-based branching and version control in Retool, откроется в новой вкладке)Branch-based editing, pull-request review, and release history for controlling which version is live, plus rollback and blue/green deployments.. 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.
Совместная работа в реальном времени
AACFlow
(источник: AACFlow codebase: realtime presence handler (cursor/selection broadcast), откроется в новой вкладке)Yes: live multiplayer editing of the same workflow canvas, with real-time cursors, selection broadcasting, and synced concurrent edits over a dedicated realtime backend
Retool
(источник: Multiplayer: Collaborative app building, откроется в новой вкладке)Yes: Retool Multiplayer lets multiple people edit the same app at once, with live avatars and highlights showing where each teammate is working. It is generally available on Cloud and in beta for self-hosted. Under the hood it uses conflict-free replicated data types (CRDTs) over WebSockets so simultaneous edits merge automatically instead of overwriting each other.. Self-hosted customers must sign up for beta access.
Встроенное файловое хранилище
AACFlow
(источник: AACFlow codebase: file share modal (password/email/SSO modes), откроется в новой вкладке)Yes: a native Files area with folder hierarchy, link-based sharing (public, password, email OTP, or SSO auth), and a workspace-level Recently Deleted view covering workflows, tables, knowledge bases, files, and folders. Admins can restrict which share-auth modes (public/password/email/SSO) a permission group is allowed to use.
Retool
Partial, folders and links yes, no trash/recovery or password links found (источник: Retool Storage quickstart, откроется в новой вкладке)Partial: Retool Storage is a native Retool-hosted file store (cloud orgs) supporting folder creation/rename/delete, file rename/move, and link-based access (public URLs or app-scoped private URLs). No password-protected/SSO-gated sharing links or deleted-item/trash recovery mechanism is documented.. Storage caps at a fixed capacity and lacks more advanced sharing and recovery controls.
Встроенные таблицы данных
AACFlow
(источник: AACFlow Docs: Tables, откроется в новой вкладке)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. 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."
Retool
(источник: Retool Database | Power apps with a built-in Postgres database, откроется в новой вкладке)Yes: Retool Database is a real, built-in Postgres-backed database (not a spreadsheet-like store). Tables support foreign-key fields that link rows between tables, and any query can be written in raw SQL (Retool's SQL mode supports arbitrary SELECT/UPDATE/DELETE and other statements, including joins), in addition to a spreadsheet-style Edit Table view for inline editing. Retool's Table UI component separately renders and scrolls through 100,000+ rows and hundreds of columns without slowing down.. Because it's genuine Postgres under the hood, Retool Database supports foreign-key relationships (with configurable on-delete/on-update behavior) and hand-written SQL queries that a typed-column grid like AACFlow's Tables does not expose; Retool does not publish hard row/column caps for Retool Database itself (forum threads mention plan-dependent limits like 50,000 records, unconfirmed as current). The Table UI component is documented to handle 100K+ rows.
Редактор документов с форматированием
AACFlow
(источник: AACFlow codebase: rich markdown editor, откроется в новой вкладке)Yes: markdown files opened in the Files viewer render in an inline WYSIWYG-style rich markdown editor, with inline @-mention links to other AACFlow resources
Retool
No, native editor is HTML-input, not WYSIWYG markdown (источник: The Rich Text Editor component for classic apps, откроется в новой вкладке)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.. Multiple long-running Retool forum feature requests ask for WYSIWYG markdown editing, still unresolved.
Подворкфлоу (композиция)
AACFlow
(источник: AACFlow Docs: Workflow block, откроется в новой вкладке)Yes: a Workflow block calls another saved workflow as a step, waits for it to finish, runs its latest deployed version, and maps parent variables into the child's input form. Self-references are blocked to prevent infinite recursion.
Retool
(источник: Run another workflow with the Workflow block | Retool Docs, откроется в новой вкладке)Yes: the Workflow block runs another saved workflow as a step, passing data to it and receiving its returned data back, so the parent workflow can compose child workflows rather than duplicating logic.. The Workflow block supports two execution modes: Finished, where the calling workflow pauses until the triggered workflow run completes, and Queued, where the calling workflow continues immediately while the triggered run is queued.
Собственные блоки (повторное использование в организации)
AACFlow
(источник: AACFlow codebase: custom-blocks publish API (admin gate), откроется в новой вкладке)Yes: a user with admin access on a workflow's workspace can publish its deployed version as a named, iconed custom block that appears in the block toolbar for the whole organization. Inputs are read live from the source workflow's Start block; the publisher picks which outputs to expose. The block always runs the source workflow's latest deployed version, and its internal steps and intermediate values are never exposed to consumers. Enterprise-gated. Distinct from the Workflow (sub-workflow) block, which composes a workflow the same author controls, and from custom code/tool blocks, which run inline code rather than a full deployed workflow.
Retool
(источник: Workflow Block Library (Feature Request) - Retool Forum, откроется в новой вкладке)No: Retool has no way to publish a deployed workflow as a named, encapsulated block that shows up in a shared block library for other builders to drop into their own workflows. The closest primitive is the generic Workflow block (see subWorkflows), which requires manually selecting which saved workflow to call each time it is added, rather than appearing as its own distinct, iconed, org-wide toolbar entry. A public forum feature request asking for exactly this ("Workflow Block Library," save a block once and reuse it across workflows) is still open, with a Retool team member confirming only an internal, unshipped feature request exists for it.. The Workflow block abstracts away the called workflow's internal steps, but it is one generic block type, not a per-source-workflow custom block, and Retool's docs do not document automatic org-wide distribution or live-sync-to-latest-deploy behavior the way a dedicated published-block feature would.

Тарифы

CompareAACFlow vs Retool
AACFlow
Retool
Модель ценообразования
AACFlow
Credit-based billing, BYOK exempt from caps (источник: AACFlow Pricing, откроется в новой вкладке)Credit-based usage billing (Stripe), with bring-your-own-key exemption from metered caps
Retool
Seat-based plus AI credits and hourly Agents billing (источник: Retool Pricing, откроется в новой вкладке)Seat-based (separate builder vs. end-user/internal-user seat prices) plus pooled monthly AI-credit allocations and separately metered hourly billing for Agents usage.
Начальный платный тариф
Retool
$10/builder + $5/user per month (Team plan) (источник: Retool Pricing, откроется в новой вкладке)Team plan: $10/builder/month and $5/internal-user/month (annual billing; $12/$7 monthly), including 5,000 workflow runs/month, staging environment, app release versions, and 1,000 AI credits/month.
Бесплатный уровень
AACFlow
(источник: AACFlow Pricing, откроется в новой вкладке)No free tier: usage is paid for with prepaid wallet credits or a paid plan
Retool
(источник: Retool Pricing, откроется в новой вкладке)Yes: Free plan: unlimited web/mobile apps, 500 workflow runs/month, 5GB database capacity, 5GB file storage, up to 5 users, 20 hours/month of Agents, 250 AI credits/month.
Собственный ключ (BYOK)
AACFlow
(источник: AACFlow Docs: Bring Your Own Key (BYOK), откроется в новой вкладке)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
Retool
BYO chat model, but embeddings always use OpenAI (источник: Retool AI, откроется в новой вкладке)Partial: Retool AI supports "bring your own" model connections for chat/completion models (OpenAI, Anthropic, Google, AWS, Azure, or custom), but Retool Vectors' embedding calls always go through OpenAI's API regardless of the chosen chat model.

Безопасность и соответствие требованиям

CompareAACFlow vs Retool
AACFlow
Retool
SOC 2
Retool
(источник: Retool Trust Center, откроется в новой вкладке)Yes: SOC 2 Type 2, plus ISO/IEC 27001:2022, GDPR, and CCPA.. Reports/certificates are downloadable via the self-serve Trust Center (SafeBase-powered).
Резидентность данных
AACFlow
Cloud region toggle is global, not per-customer (источник: AACFlow codebase: async job region resolution, откроется в новой вкладке)On AACFlow Cloud, async job execution has an internal US/EU region toggle, but it is deployment-wide, not a customer-selectable per-workspace residency option
Retool
AWS-hosted (cloud); no data stored self-hosted (источник: Security Practices | Retool Docs, откроется в новой вкладке)Cloud: customer data stored redundantly across multiple AWS data center locations (no customer-selectable region specified). Self-hosted: no Retool systems store customer data and no Retool personnel have technical/logical access to it.
Ролевой контроль доступа
AACFlow
(источник: AACFlow Docs: Roles and Permissions, откроется в новой вкладке)Yes: admin/write/read workspace permissions, org-level admin/member roles, plus Enterprise-tier permission groups that allow/deny-list specific models, tools, and integrations per group on top of those base roles. See modelAndToolGovernance and credentialGovernance for the finer-grained permission-groups layer.
Retool
(источник: Configure role-based access control | Retool Docs, откроется в новой вкладке)Yes: role-based access control with organization-level and resource-level permissions; Business plan gets a limited set of assignable permissions, Enterprise plan gets the full range of organization-level permissions.
Журнал аудита
AACFlow
(источник: AACFlow codebase: auditLog table, откроется в новой вкладке)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
Retool
(источник: Retool Pricing, откроется в новой вкладке)Yes: available starting on the Business plan (audit logging listed as a Business-tier feature), with expanded audit logging on Enterprise; Enterprise orgs can also continuously stream audit log events to Datadog, or output them to stdout for ingestion by any external pipeline on self-hosted deployments.. Cloud Business/Enterprise can additionally download audit logs from the UI in batch. No direct S3/BigQuery/generic-webhook drain is documented; Datadog streaming and self-hosted stdout are the only continuous-export mechanisms Retool publishes.
Дополнительное соответствие требованиям
AACFlow
Retool
SOC 2, ISO 27001, GDPR, CCPA; HIPAA via BAA (источник: Retool Trust Center (SafeBase), откроется в новой вкладке)SOC 2 Type II, ISO/IEC 27001:2022, GDPR, and CCPA certifications, plus HIPAA via BAA on Enterprise.. 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.
Управление моделями и инструментами
AACFlow
(источник: AACFlow codebase: PermissionGroupConfig (allowedModelProviders, deniedModels, deniedTools), откроется в новой вкладке)Yes: enterprise "permission groups" let an admin allow-list/deny-list specific LLM providers and models, and separately deny specific tools/integrations (or disable all MCP or custom tools) per group, layered on top of workspace admin/write/read roles. This does not control whether an LLM provider retains prompts. AACFlow offers no "zero data retention" mode or governed AI gateway. A separate, Enterprise-gated feature lets orgs set a log-retention window and redact PII, but that only controls how long AACFlow itself keeps execution logs.
Retool
Not publicly documentedUnknown. Not publicly documented.
Управление учётными данными
AACFlow
(источник: AACFlow Docs: Roles and Permissions, откроется в новой вкладке)Yes: shared credentials (connected accounts, service accounts, workspace secrets) are their own nested permission level (Member/Admin) below organization and workspace roles, and enterprise permission groups can further allow-list specific integrations and restrict which file-share auth modes (public/password/email/SSO) a group may use. A user's personal environment variables/secrets are never shared or inherited by anyone, including org owners/admins.
Retool
(источник: Configure resource environments, откроется в новой вкладке)Yes: Retool (Business/Enterprise plans) supports resource-level permissions with Use, Edit, and Own tiers. Enterprise orgs can go further and set per-environment permissions on the same resource (for example, allow Use on staging credentials but deny production credentials), independent of feature-level RBAC.. Permission control for Resources (Use/Edit/Own tiers) is available starting on the Business plan; per-environment override, selecting 'Define specific resource access' on a resource, is an Enterprise-only capability.
Единый вход (SSO)
AACFlow
(источник: AACFlow Docs: Single Sign-On (SSO), откроется в новой вкладке)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
Retool
(источник: Provision users with SCIM, откроется в новой вкладке)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+.. 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.
Настраиваемая политика сессий
AACFlow
(источник: AACFlow Docs: Session Policies, откроется в новой вкладке)Yes: Enterprise organization owners and admins can set a max session lifetime (1 to 8,760 hours from sign-in, regardless of activity) and an idle timeout (48 to 8,760 hours without activity), applied to every member on every device. Both limits are optional; leaving them empty keeps the default of 30-day sessions that extend automatically while a member stays active. A separate "Sign out all members" action immediately revokes every member session in the organization except the admin's own, for use after a security incident or an offboarding wave. The 48-hour idle floor exists because session activity is recorded at most once per day, so a shorter window could sign out members who are actively working.
Retool
Absolute cap only, coarse on cloud; no idle timeout (источник: Configure SSO session duration | Retool Docs, откроется в новой вкладке)Partial: an absolute session lifetime cap is configurable, but the cloud control is coarse and lives inside SSO settings. Toggling "Use short session" in the organization's Single Sign On settings drops the session length from one week to 12 hours. Self-hosted deployments get finer control through SESSION_DURATION_MINUTES, which sets an arbitrary custom session duration in minutes (default 10080, or 720 when USE_SHORT_SESSIONS is true). No inactivity or idle timeout is documented.. The documented policy is an absolute cap measured from sign-in, not an idle timer, so an active or idle browser session persists until the cap expires. Cloud orgs choose between the two fixed values (one week or 12 hours); only self-hosted operators can specify a duration of their own. Retool's pricing page lists Custom SSO (SAML/OpenID) under Enterprise and does not list Google SSO at any tier, and Retool's documentation does not state which plans can reach the short-session toggle. A Retool staff member states on the community forum that configuring Google SSO, which exposes the same short-session control, does not require the Enterprise plan; that is not confirmed in Retool's official documentation.
Проверенные собственные интеграции
AACFlow
(источник: AACFlow codebase: first-party block directory, откроется в новой вкладке)Yes: every one of AACFlow's 266 blocks is first-party authored and code-reviewed through the standard pull-request process in the main AACFlow repository; there is no public marketplace where an arbitrary third party can publish and have other users install executable tool code without going through AACFlow's own review. Custom code steps run inside AACFlow's own isolated-vm sandbox rather than as an installable third-party skill package, so the supply-chain trust boundary is AACFlow's codebase review, not an open registry.
Retool
(источник: Retool Integrations, откроется в новой вкладке)Yes: Retool's built-in integrations (Resources) are a first-party catalog of roughly 90+ databases, APIs, AI services, and cloud tools built and maintained by Retool, not an open marketplace of third-party-submitted connectors. Custom Component Libraries let a customer's own developers pull in npm packages to build custom UI components, but these are private to the authoring organization by default, not a shared registry of code from unrelated third parties.. A custom component loads into a sandboxed iframe, and Retool's custom-component-guide plus a community forum thread ('Custom Component Vulnerabilities') flag that developers should run npm audit on dependencies pulled into their own component libraries. This is a supply-chain caution for self-authored code, not an incident involving a shared marketplace, since no public component marketplace exists.
Скрытие персональных данных
AACFlow
(источник: AACFlow Docs: Guardrails Block, откроется в новой вкладке)Yes: a Guardrails workflow block detects and blocks or masks PII (30+ entity types across the US, UK, and several other countries) via Microsoft Presidio, in addition to the org-level data-retention PII policy applied to stored data
Retool
(источник: Security Checklist, откроется в новой вкладке)No: Retool has no automated PII-detection or redaction system for workflow content or logs. The closest control is the manual, per-query 'Remove parameters from logs' option in Advanced Options, which lets a builder exclude specific named parameters (which could include PII) from being written to audit logs. This is manual exclusion, not automatic PII detection or redaction.
Настраиваемое хранение данных
AACFlow
(источник: AACFlow Docs: Data Retention, откроется в новой вкладке)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
Retool
(источник: View user audit logs, откроется в новой вкладке)No: Retool Cloud has a fixed one-year audit log retention with only the most recent three months browsable in the UI; there is no documented org-configurable retention window on Cloud. Self-hosted orgs manage retention themselves via their own infrastructure, but that is operator-managed, not a Retool-provided configurable setting.. No configurable retention windows exist for other resources, like soft-deleted items, either.
White-label (собственный бренд)
AACFlow
(источник: AACFlow Docs: Whitelabeling, откроется в новой вкладке)Yes: Enterprise orgs can replace the logo, wordmark, brand name, and primary/accent theme colors across the workspace UI with their own
Retool
(источник: Retool Pricing, откроется в новой вкладке)Yes: Retool's Enterprise plan includes full white-labeling, letting orgs replace the Retool logo/favicon and remove references to the Retool name across login pages, headers, invite/password-reset emails, and app presentation mode. The Business plan gets custom branding with fewer white-label controls. Separately, white-labeled Retool Mobile apps can be requested for the iOS/Android app stores.. Custom domain (Business/Enterprise) is required alongside white-labeling for a fully de-branded experience.

Возможности ИИ

CompareAACFlow vs Retool
AACFlow
Retool
Поддержка нескольких LLM
AACFlow
21 providers plus dynamic-resolution aggregators (OpenRouter, LiteLLM, etc.) (источник: AACFlow codebase: PROVIDER_DEFINITIONS, откроется в новой вкладке)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. apps/sim/providers/models.ts defines 21 provider entries.
Retool
OpenAI, Anthropic, Google, Bedrock, Azure, or BYO model (источник: Retool AI, откроется в новой вкладке)Direct providers OpenAI, Anthropic, and Google; cloud service providers AWS (Bedrock) and Azure (OpenAI); plus a "bring your own model" option.. Retool lists these categories without enumerating specific model versions.
Блоки рассуждений агента
AACFlow
(источник: AACFlow codebase: block registry, откроется в новой вкладке)Yes: dedicated agent, function-calling, RAG, code-execution, and evaluation blocks, not just data routing
Retool
(источник: Retool Agents docs, откроется в новой вкладке)Yes: Retool Agents is a dedicated product for encoding business processes that mixes deterministic code-based decisions with non-deterministic LLM-based decisions and human-in-the-loop steps, separate from the classic data-routing Workflows product.
Создание на естественном языке
AACFlow
(источник: AACFlow Docs: Copilot, откроется в новой вкладке)Yes: Chat + in-editor AI Copilot can build and modify workflows from natural-language requests
Retool
(источник: Retool AI App Generation, откроется в новой вкладке)Yes: "Generate with AI" / AppGen lets users describe an app in plain English and iterate via prompts; Retool generates pages, queries, components, and event handlers wired to live data and existing security policies.
База знаний / RAG
AACFlow
(источник: AACFlow codebase: KB schema (pgvector + tsvector), откроется в новой вкладке)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
Retool
(источник: Retool-managed Vectors tutorial | Retool Docs, откроется в новой вкладке)Yes: Retool Vectors is a Retool-managed vector database that stores and indexes text, PDF, or web-page content, so AI apps and agents can retrieve relevant context in one click. Embedding calls go through OpenAI's API (default model text-embedding-ada-002).
Поддержка MCP
AACFlow
(источник: AACFlow Docs: Using MCP Tools, откроется в новой вкладке)Yes: both MCP client (call external MCP servers) and MCP server (expose AACFlow workflows as MCP tools)
Retool
(источник: How to use MCP in Retool, откроется в новой вкладке)Yes, bidirectional. Retool Agents can connect to external remote-hosted MCP servers (Streamable HTTP/SSE; basic, bearer-token, or OAuth 2.0 auth) as tool sources, and Retool itself can act as an MCP server so external AI tools (Claude, Cursor, Codex, Kiro) can manage Retool apps/workflows/users.
Оценка и ограничители
AACFlow
LLM-judge Evaluator plus Guardrails validation block (источник: AACFlow Docs: Evaluator Block, откроется в новой вкладке)Evaluator block (LLM-judge scoring against user-defined named metrics) and Guardrails block (JSON validity, regex, RAG/hallucination scoring, PII detection/masking). These are per-call scoring/validation primitives, not a batch golden-dataset eval-suite runner or A/B prompt-testing harness.
Retool
Access/audit controls only, no eval framework (источник: Retool AI, откроется в новой вкладке)Partial: Retool provides governance-style guardrails, enterprise access controls, monitoring, and audit trails for agent and workflow actions, but no dedicated evaluation or test-suite framework for validating AI output quality.. Retool's guardrails are access and observability controls (enterprise access controls, monitoring, and audit trails), not a dedicated evals product.
Участие человека (human-in-the-loop)
AACFlow
(источник: AACFlow Docs: Human in the Loop Block, откроется в новой вкладке)Yes: dedicated approval block that pauses a run and waits for a human-submitted "Resume Form," with durable pause/resume via persisted execution snapshots and notification hooks (e.g. Slack, email) carrying the resume link
Retool
(источник: Human + AI collaboration: Beyond the automation anxiety (Retool Blog), откроется в новой вкладке)Yes: dedicated human-in-the-loop approval tasks distinct from a delay/wait step. Retool Agents and Workflows support an auditable, permissionable approval task that must be approved by one or more people in a designated permission group before a run proceeds (for example, reviewing an agent's proposed tool call or action). Approvers can be notified via Retool app/task assignment or Slack/email through workflow blocks. The run resumes automatically once the decision is recorded, and every step is logged to the audit trail.
Генеративные медиа
AACFlow
(источник: AACFlow codebase: Image Generator V2, откроется в новой вкладке)Yes: dedicated image (3 provider families incl. OpenAI, Gemini, Fal.ai proxy), video (5 provider families incl. Runway, Veo, Luma, Hailuo, Fal.ai proxy), text-to-speech (7 providers), and speech-to-text (5 providers) blocks
Retool
Image generation only, no video/TTS/STT (источник: Retool AI image actions (docs), откроется в новой вкладке)Native image generation only. No native video generation, text-to-speech, or speech-to-text block.. 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.
Динамическое использование инструментов
AACFlow
(источник: AACFlow codebase: agent tool resolution (pre-wired only), откроется в новой вкладке)No: an Agent block calls tools the workflow author explicitly added to it at build time, rather than browsing and picking from a broader pool (e.g. an entire MCP server catalog) at inference time. Runtime MCP "discovery" exists to resolve/refresh the schema of an already-configured tool. The model does not browse or choose from the server's full tool list.
Retool
Not publicly documentedUnknown. Not publicly documented.
Автоматическая замена модели
AACFlow
(источник: AACFlow codebase: executeProviderRequest (no retry/fallback), откроется в новой вкладке)No: a failed or rate-limited LLM call is retried using AACFlow's own hosted API keys for the same model, rather than automatically switching to a different model or provider. A "fallback" comment in the provider layer refers to rotating among AACFlow's own hosted API keys for the same model, not switching models.
Retool
Not publicly documentedUnknown. Not publicly documented.
Навыки агентов
AACFlow
(источник: AACFlow Docs: Agent skills, откроется в новой вкладке)Yes: named, reusable "Agent Skills" (built on the open Agent Skills / SKILL.md format) that agents load on demand via progressive disclosure, editable in-app or imported from a SKILL.md file or GitHub URL. Only the skill name and description sit in the agent's system prompt (~50-100 tokens each); the full instructions load into context only when the agent calls load_skill.
Retool
Unknown, no shared skills-library feature foundUnknown: Retool has no feature for defining a reusable, named prompt or knowledge snippet once and reusing it across multiple agents by reference. Retool's agent docs describe per-agent instructions and system prompts, plus connecting Resources, Vectors, and MCP servers as tools, but not a shared 'skills library' construct.. Retool has reusable components and shared primitives for apps and workflows generally, but nothing matches a cross-agent named prompt-snippet system, the kind Anthropic and Replit call 'Agent Skills'.
Встроенное развёртывание чата
AACFlow
(источник: AACFlow Docs: Chat Deployment, откроется в новой вкладке)Yes: a workflow can be deployed as a public, shareable Chat interface with selectable auth (public, password, email OTP, or SSO), in addition to API and MCP deployment targets
Retool
Estimated yes, via Agent Chat component embedded in apps (источник: Retool Agents chat, откроется в новой вкладке)Estimated yes: Retool Agents include a chat interface for testing and interacting with an agent, and can be embedded into deployed Retool apps via an Agent Chat component, giving end users a conversational surface, alongside other deployment targets like email and workflows/API. A public 'share thread' replay link also exists for individual conversations.. Chat is delivered by embedding the Agent Chat component in a publicly-shared app rather than a single-click standalone public chat deployment; there is no dedicated one-click public chat endpoint.
Параллельное выполнение
AACFlow
(источник: AACFlow Docs: Parallel block, откроется в новой вкладке)Yes: a native Parallel block fans a run out into concurrent branches (fixed count or one per list item) and joins their results back into the workflow automatically. Contained blocks run concurrently instead of sequentially, either a fixed number of times or once per item in a list/collection, and each branch's output aggregates for downstream blocks.
Retool
(источник: Retool Workflows quickstart, откроется в новой вкладке)Yes: Retool Workflows has a Branch block that outputs to multiple downstream blocks, creating separate paths that run at the same time, and a Loop block with a dedicated parallel execution mode for concurrent iteration. A block with multiple incoming connections waits for all of them to finish before running, which is how parallel paths join back together. Some older community forum reports describe blocks executing sequentially rather than concurrently in certain cases, so real-world concurrency may vary from the documented behavior.. Official docs describe multi-output blocks and a Loop block parallel mode; a small number of community forum threads report inconsistent concurrent execution in practice.
Протокол Agent2Agent (A2A)
AACFlow
(источник: AACFlow Docs: A2A integration, откроется в новой вкладке)Yes: a dedicated A2A block sends messages to, tracks and cancels tasks on, and discovers the capabilities of any Agent2Agent (A2A)-compliant external agent via its Agent Card
Retool
(источник: Agent-to-agent communication (A2A), откроется в новой вкладке)Yes: Retool documents native Agent2Agent (A2A) protocol support for Retool-built agents, including agent cards, sending messages, polling for task updates, and streaming updates over Server-Sent Events. Support is ingress-only (external agents can call a Retool agent, not the reverse), limited to the HTTP+REST and JSON-RPC transports, and authenticates callers with an API key header rather than delegated auth.. Retool docs describe this as "the core set of A2A functionality" and explicitly note the input-required and auth-required task states are not supported, so tools requiring delegated authentication or approval will fail over A2A.
Блок цикла / итерации
AACFlow
(источник: AACFlow Docs: Loop block, откроется в новой вкладке)Yes: a Loop container block runs the blocks inside it repeatedly (For a fixed count, ForEach over a collection, While a condition holds, or Do-While), running iterations one after another; concurrent fan-out is a separate Parallel block
Retool
(источник: Loop block | Retool Docs, откроется в новой вкладке)Yes: a dedicated Loop block runs an embedded set of blocks once per item in an array, referencing each item and its index via value and index.. The Loop block supports Sequential mode (each iteration completes before the next starts, with an optional delay to avoid rate limits), Parallel mode (all iterations run simultaneously), and Batch mode (a configurable number of iterations run in parallel per batch, default batch size 10) before moving to the next batch.

Интеграции

CompareAACFlow vs Retool
AACFlow
Retool
Интеграции
AACFlow
1,000+ integrations (266 blocks, ~3,900 tool actions) (источник: AACFlow codebase: BLOCK_REGISTRY, откроется в новой вкладке)1,000+ integrations counting individual API actions, built from 266 first-party blocks and roughly 3,900 underlying tool actions. AACFlow'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.
Retool
90+ connectors plus REST/GraphQL/gRPC (источник: Retool Integrations, откроется в новой вкладке)90+ listed integrations/connectors on the public integrations page, plus generic REST API, GraphQL, and gRPC connectivity for anything without a native connector.. Categories include databases, cloud platforms, CRMs, messaging, and AI services (OpenAI, Anthropic, Google Gemini, etc.).
Типы триггеров
AACFlow
Webhook, cron, chat, REST API, 61 app triggers, plus a diff-aware Tables trigger (источник: AACFlow Docs: Triggers overview, откроется в новой вкладке)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 AACFlow Tables that fires on insert/update with an optional column watch-list and emits a before/after diff
Retool
Not publicly documentedUnknown. Not documented in a single consolidated reference.
Шаги с собственным кодом
Retool
(источник: Execute Python with the Code block | Retool Docs, откроется в новой вкладке)Yes: a workflow Code block runs custom Python or JavaScript as a step, with the language chosen per block
Настраиваемые песочницы для кода
AACFlow
(источник: AACFlow Docs: Function block - Sandboxes, откроется в новой вкладке)Yes: named sandboxes a workspace maintains and a Function block selects, each declaring a language, its pip or npm dependencies, optional Debian/APT system packages, and optional managed CLI tools from a catalog grouped by cloud, Kubernetes, infrastructure, deployment, data and storage, and security tools; on aacflow.io they require an active Max or Enterprise plan. Only workspace admins can create or edit sandboxes, in Settings → Sandboxes. On aacflow.io each specification is prebuilt into a reusable image so runs pay no install cost. Two sandboxes with the same language, dependency list, system packages, and managed CLI tools share one build. Every managed CLI entry uses a pinned, integrity-checked vendor artifact. With no sandbox selected, remote code runs on the dedicated Function base; import-free JavaScript stays in the local isolated runtime and ignores the sandbox selection either way.
Retool
Packages only: per-workflow PyPI and npm libraries (источник: Execute Python with the Code block | Retool Docs, откроется в новой вкладке)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.. 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.
Развёртывание через API
AACFlow
(источник: AACFlow Docs: API Reference - Getting Started, откроется в новой вкладке)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. 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.
Retool
Enterprise platform APIs plus MCP server access (источник: Retool Pricing, откроется в новой вкладке)Enterprise plan includes "platform APIs" for managing/orchestrating Retool resources; Retool itself can also be exposed as an MCP server for programmatic/agent access.. Platform APIs are an Enterprise-tier pricing feature. Retool has not published whether individual apps or workflows can be published as standalone REST endpoints.
SDK и расширяемость
AACFlow
Official Python and TypeScript SDKs, plus MCP, code block, and A2A protocol (источник: AACFlow Docs: Python SDK, откроется в новой вкладке)Official client SDKs exist for Python (aacflow-sdk, pip install aacflow-sdk) and TypeScript/JavaScript (aacflow-sdk, npm install aacflow-sdk), both wrapping the REST API (x-api-key header) with methods like execute_workflow / executeWorkflow, retry-with-backoff, and usage-limit lookups. Extensibility is further extended by MCP (client + server), a sandboxed code-execution block (JS/Python), custom tools, and an Agent-to-Agent (A2A) protocol block for external agent interop
Retool
Custom Component React/TS kit, no multi-language SDK (источник: Build custom React components (Retool Docs), откроется в новой вкладке)Custom Component dev kit (React/TypeScript) + CLI, plus a community Custom Component Gallery; no general-purpose client SDK for multiple languages found. Retool provides a TypeScript API for building custom React components locally (using standard npm packages and Retool's `retool-ccl` CLI tool) that adds new properties and events to the app editor. Finished components can be published to the community Custom Component Gallery or shared privately as component libraries. There is no multi-language client SDK, such as Python, Node, or Go REST client libraries, beyond this TypeScript toolkit and workflow webhook/REST triggers.
Публикация как MCP-сервер
AACFlow
(источник: AACFlow Docs: MCP Deployment, откроется в новой вкладке)Yes: any deployed workflow can be published as a tool on an MCP server (private, API-key protected, or public/no-auth), with ready-to-paste client config generated for Codex, Cursor, Claude Code, Claude Desktop, and VS Code
Retool
(источник: How to use MCP in Retool: Two setup options for AI agents, откроется в новой вкладке)No, not in the sense of turning one specific app into its own callable tool: Retool's MCP server (public beta) exposes Retool's own build and management actions (create/edit apps, run queries, manage users, inspect resources) so external AI tools like Claude or Cursor can operate the Retool platform itself. It does not let you publish a single deployed app or workflow as its own standalone MCP tool for outside consumption.. Retool agents can call external MCP servers as tools, and Retool itself is an MCP server for managing the workspace, but no documentation confirms publishing an individual workflow or app as its own MCP endpoint for external tool-calling.

Наблюдаемость и надёжность

CompareAACFlow vs Retool
AACFlow
Retool
Трассировка и наблюдаемость
AACFlow
(источник: AACFlow codebase: TraceSpan tree builder, откроется в новой вкладке)Yes: execution logs include a per-block/per-span trace view (duration, cost, token counts, and latency stats like TTFT/TPS) with expandable nested iteration groups, plus a "View Snapshot" frozen copy of the workflow structure and block states at run time for debugging. This trace view is built directly into AACFlow rather than a raw export browsable in an external tool like Jaeger, and does not expose aggregate latency-percentile charts (p50/p95/p99). The run snapshot serves as a log-detail/debugging artifact rather than a resumable mid-run checkpoint.
Retool
Block-level run logs; tracing via Datadog/Sentry (источник: Configure workflow error handlers (Retool Docs), откроется в новой вкладке)Per-run/per-block execution logs and status in Run History; no native distributed tracing with spans. Latency percentile and error-rate dashboards require connecting Datadog or Sentry.. Run History lists every workflow run with date/time/status and lets you drill into each block to find where a failure occurred, filterable by error/success/info. This is block-level status logging, not distributed tracing with spans. For latency percentile or error-rate dashboards, Retool points to connecting an external tool like Datadog or Sentry rather than offering a built-in metrics dashboard.
Надёжность и повторные попытки
AACFlow
Tool-call retries (up to 10x); single-attempt job orchestration (источник: AACFlow codebase: ToolRetryConfig (exponential backoff), откроется в новой вкладке)Individual tool/API calls have configurable exponential-backoff retry (up to 10 attempts). The background job-orchestration layer itself retries only once by design. Durability instead comes from consecutive-failure tracking on schedules and the human-in-the-loop snapshot pause/resume mechanism. AACFlow does not offer guaranteed-once-only block execution, a failed-run holding queue for manual recovery, or a "replay a past execution with its original inputs" feature. The per-execution debugging snapshot serves as a log-detail artifact rather than a resumable mid-run checkpoint.
Retool
Configurable retries with backoff; no checkpointing (источник: Configure workflow error handlers (Retool Docs), откроется в новой вкладке)Automatic retries with configurable schedules and exponential backoff. No durable checkpointing or one-click replay of a past execution with its original inputs.. Workflows can configure error handlers to automatically retry failed blocks on a schedule, including exponential backoff for rate-limited APIs/data sources, plus block-level and global error handlers for unhandled errors. There is no durable checkpointing of workflow state or one-click replay of a past execution with its original inputs beyond re-running/retrying.
Оповещения о сбоях
AACFlow
(источник: AACFlow Docs: AACFlow Workspace Events trigger, откроется в новой вкладке)Yes: a sim_workspace_event trigger fires on run success/failure, deployments, and cost/latency spikes, wired to any notification block (Slack, email, webhook) for real-time alerting
Retool
DIY via error handlers, no built-in alerting (источник: Configure workflow error handlers (Retool Docs), откроется в новой вкладке)Alerting is DIY. Built via error-handler blocks wired to Slack/email/notification actions. No built-in proactive alert or cost/latency-threshold subscription system.. Retool Workflows exposes `workflowContext.currentRun.error` inside an error handler block, which builders commonly wire to a Slack or email notification action to be proactively notified of a failed run. There is no native cost/latency-threshold alerting feature (e.g., an admin setting an alert for runs exceeding a cost or duration threshold); this is typically DIY via error handlers.
Выгрузка данных (data drains)
AACFlow
(источник: AACFlow Docs: Data Drains, откроется в новой вкладке)Yes: Enterprise orgs can continuously export workflow logs, job logs, or audit logs on a schedule to a customer-owned S3 bucket, GCS bucket, Azure Blob container, BigQuery table, Snowflake table, Datadog logs intake, or an HTTPS webhook. Each drain exports exactly one data source; multiple drains are created to export multiple sources. Viewing drain config/run history is restricted to org owners/admins.
Retool
(источник: Send audit log events to Datadog, откроется в новой вкладке)Yes: Retool Enterprise orgs (Cloud or self-hosted 3.38 Edge+) can continuously stream audit log events to Datadog, and self-hosted deployments can set LOG_AUDIT_EVENTS=true to output all audit events to stdout for ingestion by any external log pipeline.. Cloud Business/Enterprise can also download audit logs from the UI (batch, not a live drain). No direct S3/BigQuery/generic-webhook drains are documented; Datadog and self-hosted stdout are the documented mechanisms.
Асинхронное выполнение
AACFlow
(источник: AACFlow codebase: async execution handler, откроется в новой вкладке)Yes: a workflow can be triggered in fire-and-forget async mode, returning HTTP 202 with an execution ID immediately, then polled through the canonical execution resource across queued/running/terminal states. Async runs are tracked by execution ID through the same execution status endpoint used for durable logs rather than a separate queue-job resource.
Retool
(источник: Retool Docs: Workflow limits (sync vs async execution modes), откроется в новой вкладке)Yes: Retool workflows triggered via their webhook URL (the same api.retool.com/v1/workflows/{id}/startTrigger endpoint used for classic-app and API triggers) can run asynchronously. If the workflow has no Response block, it is enqueued for asynchronous execution and responds immediately; if it has a Response block, it responds synchronously up to that block and the rest of the run continues asynchronously afterward. Retool's own docs define a 30-hour timeout for 'asynchronous workflow runs' versus 15 minutes for 'synchronous workflow runs' (bound to the first Response block). Run status can optionally be checked via the Get Workflow Run Details endpoint, currently in private beta (Retool 3.122+, requires a 'Workflows > Read' API token scope, access by request).. The enqueue-and-respond-immediately behavior for Response-block-less runs is documented specifically for classic-app-triggered workflows, which fire through the same webhook/startTrigger mechanism as API-triggered ones. The Get Workflow Run Details API to fetch a run status/result after triggering is gated behind a private-beta signup, not generally available.
Лимиты выполнения
AACFlow
5-50 min sync; async defaults to 90 min, Enterprise up to 7 days (источник: AACFlow Docs: Concurrent Executions, откроется в новой вкладке)Plan-gated: synchronous runs time out at 5 minutes on accounts without a plan and 50 minutes on paid plans; async runs default to 90 minutes, while Enterprise policy can be configured up to 7 days; concurrency ranges from 10 to 1,000 executions per billing account depending on plan. A direct async API request can shorten the account policy for that request, but cannot extend it. Concurrency limits are published in the platform cost docs, where the Enterprise limit is 1,000 by default and customizable. A run that exceeds its time limit is terminated and marked failed with a timeout error.
Retool
(источник: Retool Docs: Workflow limits, откроется в новой вкладке)Yes: Retool publishes concrete execution limits. Synchronous workflow runs (blocking until the first webhook Response block) time out after 15 minutes; asynchronous runs time out after 30 hours, though workflows with a User Task or Wait block can run indefinitely (individual Wait blocks still cap at 60 days). Resource and query blocks can run up to 2 minutes in sync mode or up to 10 minutes in async mode (Cloud). Concurrency is capped at 50 in-flight outbound requests per workflow and 100 concurrent workflow runs on Retool Cloud, with a burst allowance of 200 runs in a 10-second window, and each run can use up to 2.5GB of memory.. Self-hosted customers can raise the 50 in-flight request cap via the WORKFLOW_REQUEST_CONCURRENCY_LIMIT env var, and memory enforcement (2,500 MB default) is opt-in via WORKFLOW_MONITOR_PROCESS_ENABLED.
Обработка частичных сбоев
AACFlow
(источник: AACFlow codebase: error-output edge routing, откроется в новой вкладке)Yes: any block can be wired to a dedicated error-output edge, so a failing step routes execution down an error-handling branch instead of always halting the entire run
Retool
(источник: Retool Docs: Configure workflow error handlers, откроется в новой вкладке)Yes: Retool Workflows let a failing block route to a dedicated error-handling path while the rest of the run continues, rather than always halting the whole execution. Each block has a red 'On Error' connector you can wire to a downstream handler block, and workflow-level (global) error handlers catch any unhandled errors from blocks that don't have their own On Error connection.. Global error handlers only fire for blocks lacking a block-level On Error connection, avoiding double handling; error details are exposed at workflowContext.currentRun.error for logging.
Выполнение без присмотра
AACFlow
(источник: AACFlow codebase: trigger.dev background job backend, откроется в новой вкладке)Yes: scheduled, webhook, and chat-triggered runs execute as background jobs on trigger.dev workers, entirely on AACFlow's servers. No client device needs to be open, awake, or connected for a run to fire or complete; closing the browser tab or shutting down a laptop has no effect on a scheduled or triggered workflow.
Retool
(источник: Retool Docs: Workflow limits (sync vs async execution modes), откроется в новой вкладке)Yes: scheduled and webhook-triggered Retool Workflow runs execute entirely on Retool's servers (Cloud) or the self-hosted deployment's own infrastructure, not on a builder's browser or device.. A triggered run continues executing after the initial request returns and can be polled later via the Get Workflow Run Details API, exactly as documented for asynchronous runs. No client device needs to stay open, awake, or connected for a scheduled or webhook-triggered run to fire or complete.

Поддержка

CompareAACFlow vs Retool
AACFlow
Retool
Каналы поддержки
AACFlow
Community support plus Enterprise 'Dedicated Support' (источник: AACFlow Pricing Page, откроется в новой вкладке)Community plus an unquantified "Dedicated Support" flag on the Enterprise plan. Enterprise and pricing pages do not include CSM, onboarding/enablement, or professional-services details beyond a plan-comparison-table "Dedicated Support" flag.
Retool
Breakage form/forum/office hours for all; dedicated portal on Enterprise (источник: Contact Retool support | Retool Docs, откроется в новой вкладке)A 'Report a Breakage' form and billing/account email support (all customers, 2-business-day response), a Developer Forum and weekly office-hours Zoom calls with Community Engineers, and a Reddit community; a dedicated Enterprise Support Portal with response times per the Enterprise Support Policy is available for Enterprise customers.. No Team-tier email+chat or Business-tier dedicated support, and no Slack group for 'Power Users', is currently documented.
SLA
AACFlow
(источник: AACFlow Pricing Page, откроется в новой вкладке)Yes: the Enterprise plan includes a "Dedicated Support" feature per the pricing plan-comparison table; no SLA terminology, response-time, or uptime figures are published on the enterprise or pricing pages
Retool
Support Engineering + technical advisor on Enterprise (источник: Retool Pricing, откроется в новой вкладке)Enterprise plan includes Retool's Support Engineering team for technical support and access to a dedicated technical advisor for onboarding, training, and guidance.. The pricing page does not explicitly reference a named 'custom SLA' or 'account management' service.
Сообщество
Retool
Active Discourse forum (190K+ posts), no public star/member count (источник: Retool Forum stats (community.retool.com/about.json), откроется в новой вкладке)Community Discourse forum with 190,000+ posts across 22,900+ topics and 17,000+ registered users. No GitHub star count or Slack member count is publicly disclosed.. Aggregate forum stats come from Retool's public Discourse instance stats endpoint rather than a published Retool metrics page.
Академия / обучение
AACFlow
(источник: AACFlow Docs: Academy, откроется в новой вкладке)Yes: AACFlow Academy is a dedicated structured-learning section of the docs site, separate from reference documentation and the API reference
Retool
(источник: Retool University docs, откроется в новой вкладке)Yes: Retool University (university.retool.com) launched with five course paths (Fundamentals, Platform Developer, Platform Admin, Platform Architect, Platform Advanced Developer), with most courses awarding a digital badge on completion, and a live Retool Platform Developer badge is issued via Credly.. Retool's education docs (docs.retool.com/education) have since been reframed around AI Apps, Workflows, and Agents rather than these named course paths, though the original five-path structure and Credly badges remain live via university.retool.com and the announcement blog post.

Сильные стороны AACFlow

AI Copilot / Chat agent-building surface (источник: AACFlow Docs: Copilot, откроется в новой вкладке)

Chat builds and manages work across the workspace; in-editor Copilot edits a single workflow.

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.

Hybrid semantic + keyword knowledge base (источник: AACFlow codebase: KB schema + file-parsers, откроется в новой вкладке)

Combines vector and full-text search with configurable chunking across 11 file formats.

Built-in RAG with pgvector embeddings and a generated tsvector column for combined vector + full-text search, plus a token-based chunker with configurable chunk size/overlap and 11 supported file formats (csv, doc, docx, html, json, md, pdf, pptx, txt, xlsx, yaml).

Native MCP client and server (источник: AACFlow Docs: MCP Deployment, откроется в новой вкладке)

Call external MCP servers as tools, or expose AACFlow workflows as an MCP server.

A dedicated MCP block lets any workflow call external MCP servers as a tool, and a serve/workflow-servers API surface lets AACFlow expose its own workflows as MCP servers.

Fork a workspace into dev, qa, and prod environments (источник: AACFlow Docs: Workspace Forks, откроется в новой вкладке)

Fork, diff, and promote environments with mandatory credential remapping.

Fork a whole workspace into a dev/qa/prod-style child environment, preview a diff, and promote changes bidirectionally. Credential and env-var remapping is required on every promote, so secrets never cross environments silently.

Human-in-the-loop approvals with durable resume (источник: AACFlow Docs: Human in the Loop Block, откроется в новой вкладке)

Pause a run for human approval and resume later via a durable snapshot link.

A dedicated block pauses a run and waits for a human-submitted approval form, backed by persisted execution snapshots so the run can resume later via a link, even after a server restart.

Live multiplayer canvas editing (источник: AACFlow codebase: realtime presence handler, откроется в новой вкладке)

Real-time cursors, selections, and synced edits on the same canvas.

Real-time cursors, selection broadcasting, and synced concurrent edits over a dedicated realtime backend, so a team can build the same workflow together at the same time.

Задокументированные ограничения Retool

Proprietary, closed-source core (источник: Deploy Self-hosted Retool with Docker | Retool Docs, откроется в новой вкладке)

Closed-source product; self-hosted still requires a Retool license key.

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.

Docker self-hosted deployment explicitly not production-ready (источник: Deploy Self-hosted Retool with Docker | Retool Docs, откроется в новой вкладке)

Docker Compose setup is for testing only; production needs Kubernetes/Helm.

The Docker Compose self-hosted setup (bundled Postgres container, no SSL configured) is for local and non-production testing only. Production self-hosting requires a Kubernetes/Helm deployment.

No dedicated built-in eval/guardrail framework documented (источник: Retool AI, откроется в новой вкладке)

No dedicated evaluation or guardrail framework for AI output quality.

Retool documents governance controls (audit logs, RBAC, enterprise access controls) but no dedicated evaluation, testing, or guardrail framework for validating AI agent behavior or outputs before production use.

Agents billed separately by the hour, outside the AI-credit pool (источник: Retool Pricing, откроется в новой вкладке)

Agents usage is billed hourly, separate from the AI-credit pool.

Retool Agents usage is metered and billed hourly, separate from the monthly AI-credit allocation used for app-building and AI actions. This adds a second, less predictable usage-based cost on top of seat pricing.

Итог

Choose AACFlow if you want an AI workspace that treats AI agents as first-class citizens: native multi-LLM support, real-time multiplayer editing, environment promotion (dev/qa/prod), human-in-the-loop approvals, and enterprise governance (SSO, credential-level permissions, audit logs) built in rather than bolted on.

Choose Retool if you specifically need full internal business applications, not just agent workflows: Retool builds full internal business applications, not just agent workflows: apps are now written in React on the frontend and TypeScript on the backend, giving teams a real app runtime instead of a proprietary component tree. AppGen lets users describe an app in plain English; Retool's agent generates the UI, data queries, and bindings from that prompt, wired to production data, with every generated app automatically inheriting the org's existing centralized authentication, role-based access controls, and data-access policies rather than having auth logic baked into the app code.

Часто задаваемые вопросы

AACFlow is an AI workspace where teams build, deploy, and manage AI agents visually, conversationally, or with code. Retool is a low-code platform for building, deploying, and managing internal software (apps, workflows, and AI agents) that connect to databases, APIs, and LLMs. Teams considering a switch typically weigh pricing model, and how AI-native the platform's agent-building experience is.

Каждый агент вашей компании. Всё в одном месте.