Zum Hauptinhalt springen

AACFlow vs. Tines

AACFlow ist der KI-Workspace, in dem Teams KI-Agenten visuell, im Dialog oder mit Code erstellen, bereitstellen und verwalten. So schneidet AACFlow im Vergleich zu Tines bei Plattformarchitektur, KI-Fähigkeiten, Integrationen, Preisen, Sicherheit und Support ab. Jeder Fakt unten ist belegt und datiert, zuletzt geprüft am .

AACFlow ist ein KI-Workspace zum Erstellen, Bereitstellen und Verwalten von KI-Agenten. Diese Seite vergleicht AACFlow mit Tines bei Plattformarchitektur, KI-Fähigkeiten, Integrationen, Preisen, Sicherheit und Compliance, Observability und Support – mit belegten, datierten Fakten für Entscheider, die beide Plattformen bewerten.

Was ist 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.

Was ist Tines?

Tines is a proprietary workflow automation platform, available cloud-hosted or self-hosted, originally built for security operations. Teams build event-driven "Stories" via a visual no/low-code canvas, natural language, or the API. It recently added native AI agent, MCP, and copilot capabilities.

AACFlow vs. Tines: Funktionsvergleich

Die folgenden Abschnitte vergleichen AACFlow und Tines bei Plattform und Bereitstellung, Preisen, Sicherheit und Compliance, KI-Fähigkeiten, Integrationen, Observability und Support.

Plattform und Bereitstellung

CompareAACFlow vs Tines
AACFlow
Tines
Builder-Typ
Tines
Visual Stories canvas plus Workbench AI copilot (Quelle: Tines Platform overview, öffnet in neuem Tab)Visual event-driven builder ('Stories') plus 'Workbench,' a natural-language AI copilot for building and editing stories. Workbench absorbed the former 'Story Copilot,' which was renamed 'Workbench for Storyboard' on June 2, 2026.
Lernkurve
AACFlow
Low, plus natural-language Chat for non-technical users (Quelle: AACFlow Docs: Introduction (visual, natural-language, and API/SDK building), öffnet in neuem Tab)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.
Tines
Moderate. API-centric, more setup than typical no-code (Quelle: Solving the integrations problem (API-centric approach), öffnet in neuem Tab)Moderate. Tines favors direct HTTP/API actions over pre-built app connectors, giving flexibility but requiring more configuration knowledge than typical no-code tools
Bereitstellungsoptionen
AACFlow
Managed cloud, no single-tenant VPC option (Quelle: AACFlow Pricing Page, öffnet in neuem Tab)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.
Tines
Cloud-hosted or self-hosted (Business/Enterprise) (Quelle: Security at Tines, öffnet in neuem Tab)Tines-hosted cloud, and self-hosted (customer's own data center/cloud) for Business/Enterprise
Vorlagen
AACFlow
(Quelle: AACFlow codebase: templates gallery and APIs removed, öffnet in neuem Tab)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.
Tines
Large public library across security, IT, HR (Quelle: Tines Library, öffnet in neuem Tab)Large public "Tines library" of pre-built Story and Action templates across security, IT, HR, and other use cases
Übernahme zwischen Umgebungen
AACFlow
(Quelle: AACFlow Docs: Workspace Forks, öffnet in neuem Tab)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.
Tines
(Quelle: Change Control docs, öffnet in neuem Tab)No dev/qa/prod environment-promotion feature. Tines provides in-place "Change Control" (approval gating on edits to a single Story) and multi-team separation instead of cross-environment promotion of a whole project
Versionskontrolle
AACFlow
Deployment rollback plus Copilot edit diff/revert (Quelle: AACFlow codebase: WorkflowDiffEngine, öffnet in neuem Tab)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.
Tines
Per-Story auto-save, diff preview, one-click rollback (Quelle: Story versions docs, öffnet in neuem Tab)Per-Story version history with auto-saved versions (every 5 min of inactivity or manual snapshot), diff preview between versions, and one-click restore. Scoped to a single Story, not a whole-project branch model
Echtzeit-Zusammenarbeit
AACFlow
(Quelle: AACFlow codebase: realtime presence handler (cursor/selection broadcast), öffnet in neuem Tab)Yes: live multiplayer editing of the same workflow canvas, with real-time cursors, selection broadcasting, and synced concurrent edits over a dedicated realtime backend
Tines
(Quelle: Cases | Docs | Tines, öffnet in neuem Tab)No: Tines has no live, concurrent multi-user editing of the same Story canvas (shared cursors, selections, synced changes in real time). Its collaboration model centers on Cases (async, ticket-like collaboration on top of Records) and Send to Story (passing execution between stories), not simultaneous canvas co-editing.. Story editing follows a draft/versioning model rather than Figma/Google-Docs-style live co-editing. No evidence found of a lock-based alternative.
Nativer Dateispeicher
AACFlow
(Quelle: AACFlow codebase: file share modal (password/email/SSO modes), öffnet in neuem Tab)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.
Tines
(Quelle: Workbench | Docs | Tines, öffnet in neuem Tab)No: Tines has no native, standalone file storage system with folder hierarchy, link-based sharing with auth options, or deleted-item recovery. File handling is per-feature: any action/tool can return a file to a Workbench user, and Pages can display file-related content, but there is no dedicated file-storage product.. Workbench file returns are scoped to a single user's chat session, not a shared workspace file store with folders/trash.
Native Datentabellen
AACFlow
(Quelle: AACFlow Docs: Tables, öffnet in neuem Tab)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."
Tines
(Quelle: Records | Docs | Tines, öffnet in neuem Tab)No: Records and Cases is a structured-data feature where record types define fields (text, number, boolean, timestamp, fixed values). Its table view lets you rearrange or filter columns and export to CSV, but lacks spreadsheet-style keyboard navigation (arrow keys, copy-paste across cells) and the row/column limits of a true spreadsheet grid.. The closest analog, Records/Cases, is a data table by record type with customizable row counts (e.g. up to 50 rows shown), not a general-purpose spreadsheet.
Rich-Text-Dokumenteditor
AACFlow
(Quelle: AACFlow codebase: rich markdown editor, öffnet in neuem Tab)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
Tines
(Quelle: Rich text in pages with Markdown | What's New at Tines, öffnet in neuem Tab)Yes: Tines Pages has a rich text page element (renamed from 'paragraph') that supports Markdown formatting, and Markdown is also supported inline within Pages table cells.. Markdown-based rich text, not a full WYSIWYG document editor, but a genuine inline formatted-text authoring feature within the platform.
Sub-Workflows (Komposition)
AACFlow
(Quelle: AACFlow Docs: Workflow block, öffnet in neuem Tab)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.
Tines
(Quelle: Send to Story | Docs | Tines, öffnet in neuem Tab)Yes: Tines' Send to Story action lets a parent Story call a separate sub-Story as a reusable step. The sub-story is configured with a webhook input action and a message-only output action; the parent's Send to Story action passes a payload, execution blocks until the sub-story finishes, and the sub-story's output event is returned to the calling action.. This is synchronous parent-waits-for-child composition with data passed in and returned, distinct from firing an independent story asynchronously via a plain webhook.
Eigene Blöcke (organisationsweite Wiederverwendung)
AACFlow
(Quelle: AACFlow codebase: custom-blocks publish API (admin gate), öffnet in neuem Tab)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.
Tines
(Quelle: Private Templates | Docs | Tines, öffnet in neuem Tab)No: Tines has no feature that lets a builder publish a Story as its own named, iconed entry in a shared block toolbar. The closest features are (1) Private/Public Templates, which are scoped to configuring a single action (e.g. a pre-built HTTP Request) with parameterized 'Action inputs' that hide that one action's underlying config, and can be shared team-wide or org-wide; and (2) Send to Story, one generic action type used to call any sub-story via a picker — the caller selects the target sub-story and enters its defined parameters, without needing view/edit access to the sub-story's own actions. Neither meets the bar: templates wrap one action, not a multi-step Story, and Send to Story is a single generic action a builder configures per call site, not a distinct block appearing in the toolbar for each published Story.. Public docs describe template edits as letting a builder 'optionally replace storyboard actions that use the template in one step,' confirming propagation is a manual, opt-in action rather than always running the source's latest deployed version automatically. Send to Story does genuinely hide a sub-story's internals from a caller without permission on it ('will not be able to view or modify the contents of the story unless you have the relevant permissions'), but it is one generic action configured with a target-story picker each time, not a separate published block per Story.

Preise

CompareAACFlow vs Tines
AACFlow
Tines
Preismodell
AACFlow
Credit-based billing, BYOK exempt from caps (Quelle: AACFlow Pricing, öffnet in neuem Tab)Credit-based usage billing (Stripe), with bring-your-own-key exemption from metered caps
Tines
Tiered platform fee; Business/Enterprise are quote-only (Quelle: Pricing | Tines, öffnet in neuem Tab)Tiered platform-fee model (Community / Business / Enterprise) with add-ons to expand capacity (flows, teams, apps, AI credits, tunnels). No self-serve published dollar pricing; Business/Enterprise are "Contact Tines"
Günstigster kostenpflichtiger Tarif
Tines
Business Edition, price on request (Quelle: Understanding Tines pricing and packaging, öffnet in neuem Tab)Business Edition. No public price; starts around 30 flows / 1 team / 100 users / 1.5M daily events per the pricing explainer, with self-hosting available
Kostenloser Tarif
AACFlow
(Quelle: AACFlow Pricing, öffnet in neuem Tab)No free tier: usage is paid for with prepaid wallet credits or a paid plan
Tines
Community Edition free forever, limited usage (Quelle: Understanding Tines pricing and packaging, öffnet in neuem Tab)Community Edition is free forever: 1 builder, 3 flows/apps, 1 team, 25,000 monthly events, 50 AI runtime credits/month, unlimited viewers, SSO included
Eigener Schlüssel (BYOK)
AACFlow
(Quelle: AACFlow Docs: Bring Your Own Key (BYOK), öffnet in neuem Tab)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
Tines
(Quelle: Use a preferred AI provider in Tines, öffnet in neuem Tab)Yes, for AI/LLM keys. Customers can bring their own AI provider (OpenAI, Anthropic, or a custom AWS Bedrock account) instead of Tines' default Bedrock-hosted Claude, though the pricing page doesn't use the term BYOK

Sicherheit und Compliance

CompareAACFlow vs Tines
AACFlow
Tines
SOC 2
AACFlow
(Quelle: AACFlow Landing Page, öffnet in neuem Tab)No third-party SOC 2 report is claimed
Tines
(Quelle: Security at Tines, öffnet in neuem Tab)Yes: SOC 2 Type II, audited annually
Datenspeicherort
AACFlow
Cloud region toggle is global, not per-customer (Quelle: AACFlow codebase: async job region resolution, öffnet in neuem Tab)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
Tines
Cloud or self-hosted for residency, retention controls (Quelle: Security at Tines, öffnet in neuem Tab)Cloud-hosted (Tines-managed, AWS-based) or self-hosted in the customer's own data center/region for data-residency requirements; granular data retention controls provided
Rollenbasierte Zugriffskontrolle
AACFlow
(Quelle: AACFlow Docs: Roles and Permissions, öffnet in neuem Tab)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.
Tines
(Quelle: Security at Tines, öffnet in neuem Tab)Yes: Teams-based separation lets admins logically separate users, credentials, resources, and Stories; role-based permissions across the tenant
Audit-Protokollierung
AACFlow
(Quelle: AACFlow codebase: auditLog table, öffnet in neuem Tab)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
Tines
(Quelle: Security at Tines, öffnet in neuem Tab)Yes: automatic audit log capturing any data/configuration change in the tenant, accessible via UI and API
Zusätzliche Compliance
AACFlow
None claimed (Quelle: AACFlow Enterprise Page, öffnet in neuem Tab)None claimed. No additional third-party certification is claimed.
Tines
ISO 27001, 27701, and 42001 certified (Quelle: Tines achieves the ISO trifecta (27001, 27701, 42001), öffnet in neuem Tab)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
Modell- und Tool-Governance
AACFlow
(Quelle: AACFlow codebase: PermissionGroupConfig (allowedModelProviders, deniedModels, deniedTools), öffnet in neuem Tab)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.
Tines
Not publicly documentedUnknown. Not publicly documented.
Governance für Anmeldedaten
AACFlow
(Quelle: AACFlow Docs: Roles and Permissions, öffnet in neuem Tab)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.
Tines
(Quelle: Access | Docs | Tines, öffnet in neuem Tab)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.. Governance operates at the team/role level with per-credential Access and Domain restrictions, not a credential-to-role assignment matrix like AACFlow's, but reaches a similar outcome.
Single Sign-on (SSO)
AACFlow
(Quelle: AACFlow Docs: Single Sign-On (SSO), öffnet in neuem Tab)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
Tines
(Quelle: Single sign-on | Docs | Tines, öffnet in neuem Tab)Yes: SSO via SAML or OIDC, configured at the tenant Authentication settings, with certified integrations for Okta, Duo, and CyberArk among others. Docs describe validating the IdP connection and redirecting users to the identity provider on sign-in.. Public docs describe the IdP handshake and setup steps but do not explicitly detail 'organization auto-provisioning on first login' (JIT provisioning) as a named capability.
Individuelle Sitzungsrichtlinie
AACFlow
(Quelle: AACFlow Docs: Session Policies, öffnet in neuem Tab)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.
Tines
(Quelle: Security at Tines, öffnet in neuem Tab)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.. The documented control is an inactivity timeout with an admin-set length; Tines does not publish a separate absolute session lifetime cap measured from sign-in, nor the permitted range of timeout values or any plan gating on the setting.
Geprüfte native Integrationen
AACFlow
(Quelle: AACFlow codebase: first-party block directory, öffnet in neuem Tab)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.
Tines
(Quelle: Story Library | Tines, öffnet in neuem Tab)Yes: Tines' executable actions (HTTP Request, webhooks, email, Send to Story, AI Agent, etc.) are a fixed, first-party set built and maintained by Tines, not a plugin/node marketplace. Third-party integrations go through the generic HTTP Request action against that tool's API, or by importing a pre-built 'Story' (a workflow template/JSON config, not installable code) from the community Story Library. No mechanism lets a third party publish executable custom actions/nodes that other tenants install.. The public Story Library has a 'Community selection' of user-submitted Story templates alongside Tines-authored ones, but these are shareable workflow configurations built from the same fixed first-party action set, not third-party executable plugins with their own code/dependencies (unlike n8n community nodes or a skill/plugin registry). No public vetting process for community Story submissions is documented, and no public security incident involving Tines' Story Library or action set was found.
Schwärzung personenbezogener Daten (PII)
AACFlow
(Quelle: AACFlow Docs: Guardrails Block, öffnet in neuem Tab)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
Tines
Unknown: no documented PII redactionUnknown: no documented built-in detection or redaction of PII (emails, SSNs, etc.) in workflow content or retained logs. Tines markets credential/secret protection and access controls, but not a dedicated PII-scanning/redaction capability.
Individuelle Datenaufbewahrung
AACFlow
(Quelle: AACFlow Docs: Data Retention, öffnet in neuem Tab)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
Tines
(Quelle: Audit logs | Docs | Tines, öffnet in neuem Tab)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.. 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.
White-Labeling
AACFlow
(Quelle: AACFlow Docs: Whitelabeling, öffnet in neuem Tab)Yes: Enterprise orgs can replace the logo, wordmark, brand name, and primary/accent theme colors across the workspace UI with their own
Tines
(Quelle: Branding and style | Docs | Tines, öffnet in neuem Tab)No: branding customization is scoped to Pages (custom logo, background/action colors, light/dark mode, saved Page themes), not the whole workspace or product UI. No evidence of full white-labeling (removing the Tines name/logo tenant-wide) was found.. Page themes let you brand individual deployed pages differently per audience, which is narrower than workspace-wide white-labeling.

KI-Fähigkeiten

CompareAACFlow vs Tines
AACFlow
Tines
Multi-LLM-Unterstützung
AACFlow
21 providers plus dynamic-resolution aggregators (OpenRouter, LiteLLM, etc.) (Quelle: AACFlow codebase: PROVIDER_DEFINITIONS, öffnet in neuem Tab)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.
Tines
(Quelle: AI docs, öffnet in neuem Tab)Yes: default AI runs on Anthropic Claude via AWS Bedrock (Tines-hosted), and customers can bring their own AI provider/key: OpenAI, Anthropic direct, or a custom AWS Bedrock account with any enabled model
Agent-Reasoning-Blöcke
AACFlow
(Quelle: AACFlow codebase: block registry, öffnet in neuem Tab)Yes: dedicated agent, function-calling, RAG, code-execution, and evaluation blocks, not just data routing
Tines
(Quelle: Agents | Tines, öffnet in neuem Tab)Yes: dedicated "Agents" capability for building autonomous/semi-autonomous AI agents and multi-agent orchestration inside workflows (e.g., multi-agent security investigation), separate from the core deterministic Story/Action model
Erstellung in natürlicher Sprache
AACFlow
(Quelle: AACFlow Docs: Copilot, öffnet in neuem Tab)Yes: Chat + in-editor AI Copilot can build and modify workflows from natural-language requests
Tines
Workbench assistant builds and edits Stories from chat (Quelle: AI Agents, Copilots & MCP | Tines, öffnet in neuem Tab)Story Copilot and Workbench are now one product. Story Copilot was rebranded 'Workbench for Storyboard' on June 2, 2026, and the same Workbench assistant covers both general chat and in-story building/editing.
Wissensdatenbank / RAG
AACFlow
(Quelle: AACFlow codebase: KB schema (pgvector + tsvector), öffnet in neuem Tab)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
Tines
Connects to Notion, Glean, Confluence for context (Quelle: AI Agents, Copilots & MCP | Tines, öffnet in neuem Tab)Supports connecting to external knowledge sources (e.g. Notion, Glean, Confluence) for enterprise knowledge/RAG-style context in workflows, rather than a built-in vector database product
MCP-Unterstützung
AACFlow
(Quelle: AACFlow Docs: Using MCP Tools, öffnet in neuem Tab)Yes: both MCP client (call external MCP servers) and MCP server (expose AACFlow workflows as MCP tools)
Tines
(Quelle: AI Agents, Copilots & MCP | Tines, öffnet in neuem Tab)Yes: native support for both MCP servers and MCP clients, positioned as a governed way to expose Tines actions to AI and to consume external MCP tools
Evaluierung und Guardrails
AACFlow
LLM-judge Evaluator plus Guardrails validation block (Quelle: AACFlow Docs: Evaluator Block, öffnet in neuem Tab)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.
Tines
Governance controls, no dedicated eval/guardrail product (Quelle: AI Agents, Copilots & MCP | Tines, öffnet in neuem Tab)Governance-oriented controls (policy-aligned MCP access, approvals, oversight), not a dedicated LLM-output evaluation/testing framework. No eval/guardrail product (output scoring, red-teaming) is documented
Human-in-the-Loop
AACFlow
(Quelle: AACFlow Docs: Human in the Loop Block, öffnet in neuem Tab)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
Tines
"Pages" collect mid-run input from people (Quelle: Pages docs, öffnet in neuem Tab)"Pages" let a running Story present a web form to a person for input mid-run, used for requester/approver flows. Exact pause/resume and notification mechanics are not publicly documented.
Generative Medien
AACFlow
(Quelle: AACFlow codebase: Image Generator V2, öffnet in neuem Tab)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
Tines
(Quelle: AI docs, öffnet in neuem Tab)No built-in image, video, or TTS/STT generation blocks. Tines' AI surface is text-oriented (AI Action, Agents, Workbench) via LLM providers; media generation requires the generic HTTP Request action against a third-party API.
Dynamische Tool-Nutzung
AACFlow
(Quelle: AACFlow codebase: agent tool resolution (pre-wired only), öffnet in neuem Tab)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.
Tines
Not publicly documentedUnknown. Not publicly documented.
Automatischer Modell-Fallback
AACFlow
(Quelle: AACFlow codebase: executeProviderRequest (no retry/fallback), öffnet in neuem Tab)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.
Tines
Not publicly documentedUnknown. Not publicly documented.
Agent-Skills
AACFlow
(Quelle: AACFlow Docs: Agent skills, öffnet in neuem Tab)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.
Tines
(Quelle: Workbench skills | What's New at Tines, öffnet in neuem Tab)Yes: Tines Workbench supports Agent Skills, an open standard for packaging specialized knowledge or workflows as a SKILL.md file (name, description, instructions) that the AI loads on demand. Skills are created and managed in a team's Skills section alongside credentials and templates, are team-scoped, and toggle per preset for reuse across the team.. Distinct from Presets (which bundle templates/stories/instructions); Skills specifically are reusable named knowledge snippets loaded on demand.
Native Chat-Bereitstellung
AACFlow
(Quelle: AACFlow Docs: Chat Deployment, öffnet in neuem Tab)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
Tines
(Quelle: "Anyone with the link" access for AI agent chat | What's New at Tines, öffnet in neuem Tab)Yes: Tines' AI Agent action supports a Chat mode that can be deployed as a public-facing page with an 'Anyone with the link' access option, requiring no Tines login for external users; it supports a configurable URL, theming, an initial message, and idle timeout.. This is a deployable chat surface built on the AI Agent action rather than a separate 'Chat' module, but it meets the bar of a publicly deployable conversational surface.
Parallele Ausführung
AACFlow
(Quelle: AACFlow Docs: Parallel block, öffnet in neuem Tab)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.
Tines
(Quelle: Do events passed from an explode action run in parallel or sequentially? | Tines Explained, öffnet in neuem Tab)Yes: Tines supports native fan-out/fan-in via its Explode and Implode actions. Explode splits an array into individual events that flow through the rest of the story concurrently while sharing the same story run GUID; Implode recombines those parallel branches back into a single event using that shared GUID plus an item count.. Explode/Implode is Tines’ dedicated split-and-rejoin mechanism, distinct from a single sequential loop over an array.
Agent2Agent-Protokoll (A2A)
AACFlow
(Quelle: AACFlow Docs: A2A integration, öffnet in neuem Tab)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
Tines
(Quelle: AI Agent | Docs | Tines, öffnet in neuem Tab)No documented support. Tines' AI Agent action integrates with the Model Context Protocol (MCP) for connecting to remote tool servers, but no Tines documentation, changelog, or help center article describes support for the Agent2Agent (A2A) protocol or an Agent Card-based peer-to-peer agent discovery mechanism.. Tines documents MCP tool-calling explicitly. A2A is a distinct, newer standard for agent-to-agent (not agent-to-tool) communication and isn’t mentioned anywhere in Tines’ public docs.
Schleifen-/Iterationsblock
AACFlow
(Quelle: AACFlow Docs: Loop block, öffnet in neuem Tab)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
Tines
(Quelle: Looping in Tines | Tines University, öffnet in neuem Tab)Yes: Tines actions (including Event Transform in message-only mode and Send to Story) support a Loop attribute that points at a list or object field on the incoming event and invokes the action once per element, exposing a LOOP object for the current item on each pass. This is a per-action for-each attribute rather than a visual loop container block, and runs one item at a time rather than concurrently, distinct from the Explode/Implode parallel fan-out mechanism.. Tines caps a single loop at fewer than 20,000 elements. The dedicated concurrent-fan-out counterpart is Explode/Implode, documented separately as parallelExecution.

Integrationen

CompareAACFlow vs Tines
AACFlow
Tines
Integrationen
AACFlow
1,000+ integrations (266 blocks, ~3,900 tool actions) (Quelle: AACFlow codebase: BLOCK_REGISTRY, öffnet in neuem Tab)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.
Tines
API-centric; 1000s of preconfigured Action templates (Quelle: Solving the integrations problem, öffnet in neuem Tab)Tines does not market a fixed integration count. It is deliberately API-centric (the "HTTP Request" action can call any API) while also offering "1000s of preconfigured Action templates" for tools like Jira, Slack, and CrowdStrike
Trigger-Typen
AACFlow
Webhook, cron, chat, REST API, 61 app triggers, plus a diff-aware Tables trigger (Quelle: AACFlow Docs: Triggers overview, öffnet in neuem Tab)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
Tines
Webhook, schedule, email, and Send-to-Story (Quelle: Webhook action docs, öffnet in neuem Tab)Webhook actions (unique inbound URL), scheduled/interval runs, Receive Email (IMAP or generated address), and Send-to-Story (synchronous inbound API call)
Eigene Code-Schritte
AACFlow
(Quelle: AACFlow Docs: Function block, öffnet in neuem Tab)Yes: code-execution block for custom logic
Tines
(Quelle: Run script | Docs | Tines, öffnet in neuem Tab)Yes: the Run Script action executes builder-authored code inline in a workflow (the script must define a `main` function), running in AWS Lambda in the same region as the tenant. It is currently limited to the `python3.13` runtime, so there is no JavaScript or other-language option. Lighter-weight logic is also expressible via built-in "Formulas"/functions without a code action.
Konfigurierbare Code-Sandboxes
AACFlow
(Quelle: AACFlow Docs: Function block - Sandboxes, öffnet in neuem Tab)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.
Tines
(Quelle: Run script | Docs | Tines, öffnet in neuem Tab)Yes: the Run Script action exposes a Requirements field where builders declare PyPI dependencies "in the format of a requirements.txt file with each requirement separated by a new line" (e.g. numpy==1.25), built at runtime as AWS Lambda layers with a 250MB unzipped package limit. Tines also supports custom runtimes, user-built runtime archives that bundle specific package versions, system libraries, custom Python builds, and extra files such as certificates or config files.. The runtime is limited to Python (python3.13 on the managed Lambda path); there is no Node/other-language option. Custom runtimes must be built on Amazon Linux 2023 to match Lambda, and are scoped either to Cloud (Lambda) or to Docker, meaning the Tines command runner reached over a tunnel for self-hosted execution. Timeout (10s default, 110s max) and networking mode (Standard, Dedicated, or No networking) are configurable per action.
API-Veröffentlichung
AACFlow
(Quelle: AACFlow Docs: API Reference - Getting Started, öffnet in neuem Tab)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.
Tines
(Quelle: Workflows as APIs docs, öffnet in neuem Tab)Yes: "Workflows as APIs": a Story can be exposed via Send-to-Story so external callers can invoke it synchronously and optionally wait for a response
SDKs und Erweiterbarkeit
AACFlow
Official Python and TypeScript SDKs, plus MCP, code block, and A2A protocol (Quelle: AACFlow Docs: Python SDK, öffnet in neuem Tab)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
Tines
Full REST API; no client SDK or marketplace (Quelle: API welcome docs, öffnet in neuem Tab)Full REST API (https://<tenant>/api/v1/...) covering Stories, Actions, Cases, audit logs, and more, but no dedicated client SDK or third-party integration marketplace. Extensibility runs through the generic HTTP Request action rather than an SDK/plugin marketplace
Als MCP-Server veröffentlichen
AACFlow
(Quelle: AACFlow Docs: MCP Deployment, öffnet in neuem Tab)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
Tines
(Quelle: MCP server | Docs | Tines, öffnet in neuem Tab)Yes: Tines lets you build an MCP server action directly on the storyboard, turning a Story into a callable MCP endpoint for external AI clients (e.g. Claude Desktop). The MCP server action configures which Tools (Public Templates, Private Templates, Send to Story) are exposed, supports HTTP Authorization header or URL-based secret auth, and the build panel provides ready-to-copy configuration for popular MCP clients.. Confirms the prior signal: any Story can be exposed as an MCP endpoint with configurable access/auth, the reverse direction of ordinary MCP client consumption.

Observability und Ausfallsicherheit

CompareAACFlow vs Tines
AACFlow
Tines
Tracing und Observability
AACFlow
(Quelle: AACFlow codebase: TraceSpan tree builder, öffnet in neuem Tab)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.
Tines
Per-run GUID trace; no built-in OpenTelemetry dashboards (Quelle: Story runs docs, öffnet in neuem Tab)Each workflow run ("Story run") gets a unique ID and a full, action-by-action event chain viewable in the UI or API. A Tenant Health dashboard (self-hosted) and Story/Action status views surface errors, run volume, and worker capacity, but this isn't OpenTelemetry-style distributed tracing by default; Tines' own documentation includes an official guide showing customers how to wire up their own OpenTelemetry dashboard
Ausfallsicherheit und Wiederholungen
AACFlow
Tool-call retries (up to 10x); single-attempt job orchestration (Quelle: AACFlow codebase: ToolRetryConfig (exponential backoff), öffnet in neuem Tab)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.
Tines
Configurable HTTP retries; no confirmed execution replay (Quelle: HTTP Request action retries without notification, öffnet in neuem Tab)HTTP Request actions support configurable automatic retries with "retry on status" behavior, notifying only if the final retry fails. Story version history lets you restore a prior configuration, but no explicit feature to replay a past execution with its original captured inputs is confirmed
Fehlerbenachrichtigung
AACFlow
(Quelle: AACFlow Docs: AACFlow Workspace Events trigger, öffnet in neuem Tab)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
Tines
(Quelle: New 'log error if' option, öffnet in neuem Tab)Yes: per-action "log error if" / status-based error conditions can emit events, and action monitoring can notify on errors; retry notifications only fire on final failure (not every retry), reducing noise
Data Drains
AACFlow
(Quelle: AACFlow Docs: Data Drains, öffnet in neuem Tab)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.
Tines
(Quelle: Audit logs | Docs | Tines, öffnet in neuem Tab)No: Tines documents scheduled export of audit logs to Amazon S3 every 15 minutes, but no general-purpose, continuous data-drain feature for execution/workflow data to destinations like BigQuery, Datadog, or generic webhooks.. The audit-log-to-S3 export is the only continuous export destination found; broader execution-data drains are not documented.
Asynchrone Ausführung
AACFlow
(Quelle: AACFlow codebase: async execution handler, öffnet in neuem Tab)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.
Tines
(Quelle: Tines Docs: Workflows as APIs, öffnet in neuem Tab)Yes: Tines supports asynchronous execution for Workflows as APIs. Triggering a story via an API request runs it in the background. If an Exit Action produces an event within 30 seconds, the response returns that data immediately. If it takes longer, the API returns an HTTP 504 with a response_url (also given in the X-Tines-Response-Location header) that can be polled later to fetch the eventual result, while the story keeps running regardless of the timeout.. The 30-second window only affects whether the HTTP response can return data immediately; the underlying story execution is not bound by it and continues in the background.
Ausführungslimits
AACFlow
5-50 min sync; async defaults to 90 min, Enterprise up to 7 days (Quelle: AACFlow Docs: Concurrent Executions, öffnet in neuem Tab)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.
Tines
30s per-action timeouts; concurrency capped, unpublished number (Quelle: Tines Docs: HTTP Request action (30s default timeout, retry_on_status), öffnet in neuem Tab)Tines publishes per-action timeout figures rather than one global run timeout: HTTP Request and AI Agent (LLM) actions default to a 30-second timeout, Run Script actions default to 10 seconds with a 110-second maximum, and MCP server tool responses cannot exceed 30 seconds before the client sees a timeout error. For Workflows as APIs, an Exit Action must emit an event within 30 seconds of the API request or the call returns a 504 Gateway Timeout (story execution continues regardless). Tines also caps the number of simultaneous API requests to a story; when exceeded it returns HTTP 201 Created instead of 200, signaled via the X-Tines-Status and X-Tines-Limit-Reached headers, without publishing an exact numeric concurrency ceiling.. No single 'max execution time per run' number is published; limits are per action-type. The exact numeric concurrency ceiling for simultaneous story API requests isn't disclosed in public docs, only that exceeding it changes the response status code.
Behandlung von Teilausfällen
AACFlow
(Quelle: AACFlow codebase: error-output edge routing, öffnet in neuem Tab)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
Tines
(Quelle: Tines What's New: Failure path for actions, öffnet in neuem Tab)Yes: Tines lets you connect a dedicated failure path from an action, so any action that errors emits its event down that path to a separate error-handling action instead of halting the whole story. This is configured via the action's context menu ('set failure path') and pairs with retry logic (e.g. HTTP Request actions retry on configured status codes, up to 25 retries with exponential backoff plus jitter) and an emit_failure_event option that fires once retries are exhausted, so downstream actions can react while the rest of the run proceeds.. Historically a failed HTTP Request action after exhausted retries would stop the story; Tines added error-event emission plus explicit 'failure path' routing so the rest of the story is not forced to halt.
Unbeaufsichtigte Ausführung
AACFlow
(Quelle: AACFlow codebase: trigger.dev background job backend, öffnet in neuem Tab)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.
Tines
(Quelle: Webhook | Docs | Tines, öffnet in neuem Tab)Yes: standard Stories (webhook, scheduled HTTP Request actions, Receive Email) run entirely server-side on Tines infrastructure, cloud-hosted or self-hosted, with no dependency on a browser tab or desktop client staying open. The one documented exception is a Story explicitly set to 'Workbench' mode, which can only be invoked interactively through Workbench chat and will not fire on its own schedule or accept external webhook events unless switched to a standard or 'Workbench and Send to Story' mode.. Workbench-only stories are intentionally excluded from license story limits precisely because they cannot run autonomously, confirming that autonomous (non-Workbench) stories are the default, unattended execution model.

Support

CompareAACFlow vs Tines
AACFlow
Tines
Support-Kanäle
AACFlow
Community support plus Enterprise 'Dedicated Support' (Quelle: AACFlow Pricing Page, öffnet in neuem Tab)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.
Tines
Dedicated support and training for Business/Enterprise (Quelle: Pricing | Tines, öffnet in neuem Tab)"Dedicated support and training" for Business/Enterprise plans, per the pricing page; specific mechanisms (named CSM/CSE role, SLA terms) are not publicly itemized. 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.
SLA
AACFlow
(Quelle: AACFlow Pricing Page, öffnet in neuem Tab)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
Tines
Not publicly disclosedUnknown
Community
AACFlow
Tines
Public library, university/bootcamp, community Slack (Quelle: Tines Library, öffnet in neuem Tab)Public "Tines Library" of shared Story/Action templates, a "Tines University"/bootcamp learning program, and a community Slack referenced in documentation
Academy / Schulungen
AACFlow
(Quelle: AACFlow Docs: Academy, öffnet in neuem Tab)Yes: AACFlow Academy is a dedicated structured-learning section of the docs site, separate from reference documentation and the API reference
Tines
(Quelle: Tines University, öffnet in neuem Tab)Yes: Tines offers a structured learning program, Tines University, with free foundational courses (about 30 minutes each), instructor-led and self-paced Bootcamps (fundamentals and advanced), and two certification tiers (Core and Advanced) that builders can share on LinkedIn.. Available free even on Community Edition; Advanced certification is hands-on labs, roughly 3 hours.

Herausragende Funktionen von AACFlow

AI Copilot / Chat agent-building surface (Quelle: AACFlow Docs: Copilot, öffnet in neuem Tab)

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 (Quelle: AACFlow codebase: KB schema + file-parsers, öffnet in neuem Tab)

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 (Quelle: AACFlow Docs: MCP Deployment, öffnet in neuem Tab)

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 (Quelle: AACFlow Docs: Workspace Forks, öffnet in neuem Tab)

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 (Quelle: AACFlow Docs: Human in the Loop Block, öffnet in neuem Tab)

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 (Quelle: AACFlow codebase: realtime presence handler, öffnet in neuem Tab)

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.

Dokumentierte Einschränkungen von Tines

No public pricing above the free tier (Quelle: Understanding Tines pricing and packaging, öffnet in neuem Tab)

Business and Enterprise pricing requires contacting sales.

Business and Enterprise plans have no published dollar pricing. Buyers must contact sales to get a quote, making self-serve cost comparison impossible.

No cross-environment (dev/qa/prod) promotion model (Quelle: Change Control docs, öffnet in neuem Tab)

No dev/qa/prod promotion model, only in-place change approval.

Version control is scoped to a single Story (auto-saved versions, diff, restore), not a fork/branch model for promoting a whole project between environments. The closest analog is in-place "Change Control" approval gating on edits.

No documented built-in generative media blocks (Quelle: AI docs, öffnet in neuem Tab)

No built-in image, video, or speech generation blocks.

Public docs show text-oriented AI features (AI Action, Agents, Workbench) via LLM providers, but no dedicated image, video, or text-to-speech/speech-to-text generation blocks. Those calls would need to go through the generic HTTP Request action against a third-party API.

Not open source (Quelle: Understanding Tines pricing and packaging, öffnet in neuem Tab)

Closed-source SaaS with a limited free tier, not an open-source license.

Tines is a closed-source commercial SaaS/self-hosted product; the free "Community Edition" is a limited product tier (1 builder, 3 flows, 25,000 monthly events), not an open-source license.

Fazit

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 Tines if you specifically need ISO 42001 AI-governance certification: Tines announced the "ISO trifecta" on April 14, 2026: ISO 27001, ISO 27701, and ISO 42001, the international standard for AI management systems.

Häufig gestellte Fragen

AACFlow is an AI workspace where teams build, deploy, and manage AI agents visually, conversationally, or with code. Tines is a proprietary workflow automation platform, available cloud-hosted or self-hosted, originally built for security operations. Teams build event-driven "Stories" via a visual no/low-code canvas, natural language, or the API. It recently added native AI agent, MCP, and copilot capabilities. Teams considering a switch typically weigh pricing model, and how AI-native the platform's agent-building experience is.

Jeder Agent Ihres Unternehmens. Alles an einem Ort.