Directory
Every AI agent platform, reviewed honestly.
No-code builders, voice AI, and developer frameworks. What each one is best for, where it falls short, and the alternative worth trying.
No-code AI automation
15 toolsAutonoly
AI agents that automate any digital task for you.
Best for: Non-technical operators, analysts, and founders who want agents that actually do multi-step digital work, not just move data between two apps.
Read reviewn8n
Source-available workflow automation you can self-host.
Best for: Technical teams that want self-hosting, source access, and fine control over their workflows.
Read reviewMake
Visual automation with a detailed scenario builder.
Best for: People who want more logic and data handling than basic automation tools, with a visual canvas.
Read reviewZapier
The widely used app-to-app automation tool.
Best for: Teams that want the widest app coverage for straightforward automations.
Read reviewGumloop
AI-first automation on a drag-and-drop canvas.
Best for: Teams building AI-heavy workflows like scraping, summarizing, and enrichment on a visual canvas.
Read reviewStack AI
No-code builder for LLM apps and agents.
Best for: Teams building LLM apps, document assistants, and internal AI tools without heavy engineering.
Read reviewDify
Open-source platform for building LLM apps and agents.
Best for: Developers and teams building LLM apps and RAG assistants who want open-source and self-hosting.
Read reviewFlowise
Open-source visual builder for LLM flows and agents.
Best for: Developers who want a visual, open-source way to prototype LangChain-style LLM flows and agents.
Read reviewActivepieces
Open-source Zapier alternative with MCP built in.
Best for: Teams that want a Zapier-style builder they can self-host for free, with MCP and AI agents included.
Read reviewPipedream
Developer-friendly automation with code steps and a huge MCP catalog.
Best for: Developers who want managed integrations and auth but full code control inside workflows.
Read reviewWindmill
Code-first workflow engine that turns scripts into apps and jobs.
Best for: Engineering teams that want to turn their scripts into reliable scheduled jobs, workflows, and internal tools.
Read reviewMicrosoft Power Automate
Microsoft's automation layer for the 365 ecosystem, with RPA and Copilot.
Best for: Organizations already standardized on Microsoft 365 that want automation inside that ecosystem.
Read reviewWorkato
Enterprise iPaaS with agentic AI, priced for enterprises.
Best for: Mid-size and large enterprises integrating core business systems with governance and compliance requirements.
Read reviewLatenode
Low-code automation billed by execution time, with AI models built in.
Best for: Cost-conscious builders running high-volume automations who do not mind a rougher, newer platform.
Read reviewBardeen
AI browser automation living in a Chrome extension.
Best for: Sales, recruiting, and research workflows that live in the browser, especially LinkedIn scraping and CRM pushes.
Read reviewAI agent builder
11 toolsLindy
AI assistants that automate your busywork.
Best for: Individuals and small teams who want AI assistants for email, scheduling, and CRM busywork.
Read reviewBotpress
Build AI chatbots and agents with a visual builder.
Best for: Teams building customer-facing chatbots and support assistants across web and messaging channels.
Read reviewVoiceflow
Design, build, and deploy AI agents.
Best for: Product and design teams collaborating on customer-facing chat and voice agents.
Read reviewMicrosoft Copilot Studio
Build custom AI agents inside the Microsoft ecosystem.
Best for: Organizations already committed to Microsoft 365 that want agents grounded in their tenant data and deployed to Teams.
Read reviewSalesforce Agentforce
Autonomous AI agents built into Salesforce.
Best for: Companies already running Salesforce that want AI agents acting directly on CRM data for service and sales.
Read reviewIntercom Fin
AI customer service agent priced per resolution.
Best for: Support teams with solid help documentation that want to deflect a large share of tier-1 tickets and pay only for results.
Read reviewHubSpot Breeze
AI agents and copilots built into HubSpot.
Best for: HubSpot customers who want AI handling support conversations, prospecting, and content work inside the CRM they already use.
Read reviewZapier Agents
AI teammates that act across 7,000+ connected apps.
Best for: Teams already on Zapier who want AI handling fuzzy, judgment-based tasks their rigid Zaps cannot express.
Read reviewChatbase
Train AI support agents on your own content.
Best for: Small and mid-sized businesses that want a documentation-grounded support chatbot live on their site quickly.
Read reviewMindStudio
Visual builder for AI agents across any model.
Best for: Builders and small teams who want model flexibility and a visual editor for custom AI agents without writing code.
Read reviewDust
Company-wide AI agents connected to your internal data, sold per seat with a monthly credit allowance.
Best for: Teams of up to about 100 people that want shared, governed agents over company knowledge without building anything themselves.
Read reviewVoice AI
12 toolsVapi
Developer platform for building voice AI agents.
Best for: Developers who want fine-grained control over the voice stack and are comfortable working with an API and their own backend.
Read reviewRetell AI
Build and deploy conversational voice agents.
Best for: Teams that want a faster path to a working phone agent with a builder plus API, without assembling the whole voice stack themselves.
Read reviewBland AI
Automated phone calls with AI voice agents.
Best for: Businesses that want to automate outbound and inbound calling at scale with configurable conversation flows.
Read reviewElevenLabs Agents
Voice agents built on best-in-class speech synthesis.
Best for: Teams that want the most natural-sounding voice output available and are willing to manage credit-based usage costs.
Read reviewSynthflow
No-code AI voice agents for calls and appointments.
Best for: Non-technical teams and agencies that want working phone agents from templates without writing code.
Read reviewVocode
Open source library for voice-based LLM agents.
Best for: Developers who want a free, self-hosted starting point to learn the voice agent stack and do not mind maintaining the code themselves.
Read reviewLiveKit Agents
Open source framework for realtime voice AI agents.
Best for: Engineering teams building serious voice products at scale who want full stack control and are ready to write and operate code.
Read reviewPolyAI
Enterprise voice assistants for high-volume contact centers.
Best for: Large enterprises with heavy inbound call volume that want a managed, proven voice assistant rather than a build-it-yourself platform.
Read reviewPhonely
AI phone receptionist for small businesses.
Best for: Small businesses that miss calls today and want a low-lift AI receptionist without building anything.
Read reviewDeepgram Voice Agent API
One WebSocket that bundles speech to text, a language model and text to speech at a single per-minute rate.
Best for: Developers who want one bundled per-minute rate for the speech and model layers and are happy to write the telephony bridge themselves.
Read reviewTwilio ConversationRelay
Twilio handles speech to text and text to speech inside the call and hands your server plain text over a WebSocket.
Best for: Teams already on Twilio that want a voice agent on an existing number without running an audio pipeline.
Read reviewCartesia Line
Managed voice agents from the company behind Sonic text to speech, billed per call minute with prepaid dollars in every plan.
Best for: Developers who want their agent code hosted and scaled for them at a low published per-minute rate.
Read reviewDeveloper framework
15 toolsLangGraph
Build stateful, multi-step agents as graphs in code.
Best for: Engineers building complex, stateful, multi-step agents who want fine-grained control over the control flow.
Read reviewCrewAI
Orchestrate teams of role-playing AI agents in Python.
Best for: Python developers who want to compose multiple specialized agents that divide up and collaborate on a task.
Read reviewOpenAI Agents SDK
A lightweight SDK for building agents with tools and handoffs.
Best for: Developers who want a minimal, unopinionated way to build agents and multi-agent handoffs, especially on OpenAI models.
Read reviewMicrosoft AutoGen
A framework for multi-agent conversations and workflows.
Best for: Researchers and developers experimenting with multi-agent conversation patterns and code-executing agents.
Read reviewLangChain
The most widely used framework for building LLM applications.
Best for: Developers who want the largest ecosystem of LLM integrations and are willing to work within its abstractions.
Read reviewLlamaIndex
The data framework for connecting LLMs to your documents.
Best for: Developers building RAG and document-heavy applications where ingestion, parsing, and retrieval quality matter most.
Read reviewHaystack (deepset)
A production-focused pipeline framework for RAG and agents.
Best for: Engineering teams building production RAG and search systems who want explicit, testable pipelines over clever abstractions.
Read reviewPydantic AI
Type-safe, minimal agents from the team behind Pydantic.
Best for: Python developers who want structured, validated agent outputs with minimal abstraction and a FastAPI-like developer experience.
Read reviewMicrosoft Semantic Kernel
Microsoft's enterprise SDK for LLM apps in .NET, Python, and Java.
Best for: Enterprise .NET and Java teams, especially on Azure, who want a Microsoft-supported path for LLM features and agents.
Read reviewHugging Face smolagents
A tiny agent library where agents write their actions as code.
Best for: Developers and learners who want a small, readable agent library, and tasks where code-as-action beats JSON tool calling.
Read reviewGoogle Agent Development Kit (ADK)
Google's open-source framework for building multi-agent systems.
Best for: Teams building multi-agent systems, especially those already on Google Cloud and Gemini.
Read reviewTrigger.dev
Open-source background jobs and long-running agent tasks, billed by the compute second.
Best for: Developers who need agent runs or jobs that last minutes or hours and want to pay for seconds used rather than servers reserved.
Read reviewMastra
A TypeScript agent framework that is free to use, with a paid platform for hosting and observability.
Best for: TypeScript teams that want an agent framework in the language their product is already written in.
Read reviewAgno
An open-source Python agent framework whose runtime is free to serve, with a paid control plane.
Best for: Python teams that want to host agents in their own cloud and pay a flat fee, not a usage meter, for the management interface.
Read reviewAmazon Bedrock AgentCore
AWS's managed services for running agents built with any framework, each billed on its own meter.
Best for: Engineering teams already on AWS that want agent runtime, identity, memory and tool access as managed services.
Read reviewWhich category you are in
The four groups above are not marketing labels. They are four genuinely different products that happen to share the word agent, and picking the wrong one costs more than picking the wrong tool inside the right one. Two questions settle it almost every time. Does the problem involve a ringing phone? Will anyone on the team write code and keep owning it? A yes to the first puts you in voice AI whatever else is true. A no to the second rules out every developer framework in the directory, no matter how good it looks in a demo.
No-code AI automation: 15 tools
These are the descendants of iPaaS: a visual canvas where you wire a trigger to a sequence of steps across apps you already pay for, with an AI step available where judgement is needed. n8n, Make.com, Zapier and Autonoly are the recognisable names; Activepieces, Windmill and Pipedream sit closer to developers without requiring them. What distinguishes the category is that the logic is explicit: you can point at the step that failed. That is why it suits a business with an operations person and no engineer, and why it is the right home for the unglamorous work that actually pays back, moving a form submission into a CRM, chasing an unpaid invoice, reconciling two systems that were never meant to talk.
It suits you if your bottleneck is copy-and-paste between tools rather than reasoning. It does not suit you if the workflow branches differently on every run, because a canvas with forty conditional paths is harder to maintain than the code it replaced.
AI agent builders: 11 tools
An agent builder inverts the canvas. Instead of you specifying every step, you give the agent a goal, a system prompt, a set of tools it may call and some knowledge, and it decides the order at runtime. Lindy, Botpress, Voiceflow, Chatbase and MindStudio sell this directly. The other half of the category is different in kind: Copilot Studio, Agentforce, Intercom Fin and HubSpot Breeze are agents attached to a suite you are already buying, which makes them close to free to adopt and expensive to leave. Dust sits between the two: a per-seat workspace of agents over your own company knowledge.
This category suits businesses whose problem is conversational volume: an inbox that never empties, a support queue, a website that gets the same eleven questions. It suits a company already standardised on Microsoft or Salesforce even more, because the integration work is done. It does not suit a workflow that must be identical every time, where the non-determinism you are paying for is a liability rather than a feature.
Voice AI: 12 tools
Voice is the category that does not overlap with the others. A voice AI agent chains speech to text, a language model and text to speech inside a latency budget measured in hundreds of milliseconds, while also handling barge-in, DTMF and telephony. Vapi, Retell AI, Bland AI and Phonely sell it self-serve; LiveKit Agents and Vocode give you the plumbing to assemble your own. Below those sit the per-minute building blocks a developer wires in: the Deepgram Voice Agent API, Twilio ConversationRelay and Cartesia Line.
It suits any business where a missed call is a lost job: trades, clinics, lettings, anything with an out-of-hours problem. It does not suit a business whose calls are emotionally loaded or legally consequential without a human review point, and the honest limitation is that a voice agent which talks over the caller fails in a way a chat agent never can. Everything after the call, the booking, the CRM record, the follow-up text, still belongs to an automation platform.
Developer frameworks: 15 tools
A framework is a library, not a product. LangGraph, CrewAI, the OpenAI Agents SDK, Pydantic AI, Google ADK and Semantic Kernel are all free under MIT or Apache 2.0, and they charge nothing because there is nothing to charge for: you write the agent, you host it, you own the failures. What you get in exchange is control that no canvas offers, over retrieval, over evals, over observability, and over exactly what happens when a step fails at three in the morning. Mastra and Agno are free frameworks with a paid platform attached, and Trigger.dev and Amazon Bedrock AgentCore are the metered infrastructure that agent code runs on.
This suits a team that already employs developers and has a workflow whose logic no visual tool expresses cleanly. It does not suit a business hoping to avoid hiring one. The cost of a framework is not the licence, it is the person, and the thing that breaks first in a framework build is almost never the code. It is that the person who wrote it moved on and nobody else can read it.
Decide
The four categories compared
Prices are read from the individual reviews, each of which records the vendor page and the date it was checked. Vendors change them without notice, so treat the column as an order of magnitude and the review as the source.
| Category | Billing unit | Realistic monthly cost | Who it suits | What breaks first |
|---|---|---|---|---|
| No-code AI automation | A run, a task, a credit or a CPU second, depending on the vendor | $0 self-hosted; roughly $10 to $60 a month on a real self-serve tier. n8n Starter is EUR 20 a month for 2,500 executions, Make Core $9, Zapier Professional from $19.99 a month billed annually. | A business with an operations person and no developer, automating work that moves between apps it already pays for. | The billing unit. A workflow that loops over 400 rows is one execution on n8n and 400 credits on a per-row platform, and the bill only diverges once volume arrives. |
| AI agent builder | A conversation, an outcome or a credit | Free tiers are real but small. Botpress Plus is $150 a month billed annually, Chatbase Standard $120 a month billed annually, Intercom Fin $0.99 per resolved outcome with a 50-outcome monthly minimum. | Customer-facing chat, inbox and support work, and teams already standardised on a CRM or helpdesk that sells its own agent. | Volume. Outcome pricing is honest but linear, so success costs money, and the suite agents assume you keep paying for the suite underneath. |
| Voice AI | The minute, either bundled or itemised | Retell lands between $0.07 and $0.31 a minute all-in. Vapi charges $0.05 a minute for its own layer and you pay the model, transcription and speech vendors separately. Bland Start is $0.14 a minute bundled. Phonely Starter is $50 a month. | Anyone whose actual problem is the phone: missed calls, after-hours enquiries, appointment reminders, qualification before a human picks up. | Latency and interruption handling long before the invoice does. A voice agent that talks over the caller fails in a way a chat agent never can. |
| Developer framework | Nothing for the framework itself. You pay model tokens plus hosting. | The libraries are free under MIT or Apache 2.0. Hosting a small agent is roughly $5 to $20 a month, tokens are whatever your provider charges, and the commercial layers are optional: LangSmith Plus is $39 per seat a month, Pydantic Logfire Team $49 a month. | A team with at least one developer who will own the code, and a workflow whose logic no visual canvas expresses cleanly. | Ownership. There is no vendor to call, so the thing that breaks first is usually that the person who wrote it moved on. |
Takeaway: the phone question and the developer question pick your category, and the category picks your billing unit. Everything after that is a choice between two or three tools that already fit.
Start here by situation
Six shapes cover most of the people who land on this page. Find yours, read the two or three reviews named, and ignore the rest of the directory until you have a shortlist.
- No developer, and a phone problem. Start with Retell AI or Phonely, both of which publish rates you can model before signing anything, and read Vapi next if you want to swap the underlying voices and models yourself. Work out your monthly minutes first: at Retell's published range a business handling 1,500 minutes lands somewhere between roughly $105 and $465, and which end you sit at depends almost entirely on the model you choose. Pair it with missed-call text-back before you pair it with anything clever.
- No developer, and an inbox problem. Lindy if the inbox is the workflow, Chatbase if it is a website answering the same questions repeatedly, and Botpress if you need real control over the conversation and can live with per-conversation billing. Check the human in the loop design before you check the price: an agent that sends without review is a different risk profile from one that drafts.
- No developer, and a copy-and-paste problem. This is the most common case and the cheapest to solve. Make.com and Autonoly are the gentlest starts, Zapier has the widest connector list, and n8n is the one to pick if you expect volume, because whole-workflow execution billing is the friendliest unit at scale. The ROI calculator will tell you in two minutes whether the task is worth automating at all.
- One developer, or one technical person who likes this stuff. You have the widest choice and the most rope. n8n self-hosted covers an enormous amount of ground for the price of a server. If the workflow genuinely needs code, start with Pydantic AI or the OpenAI Agents SDK for a single agent and LangGraph when the control flow gets genuinely stateful. Budget for observability from day one rather than after the first silent failure.
- An existing Microsoft or Salesforce estate. The integration work is already done and that is worth a lot. Copilot Studio and Power Automate on the Microsoft side, Agentforce on the Salesforce side. Read the licensing sections carefully before you read the feature lists: Power Automate has three separate meters, and Agentforce now has four ways to buy that are not interchangeable. Both are the stickiest options in the directory, because leaving the agent means leaving the suite.
- A compliance regime to satisfy. Start from the constraint, not the tool. If data cannot leave your infrastructure, the shortlist is the self-hostable set: n8n, Activepieces, Windmill, Dify, Flowise and any of the frameworks. If the constraint is a signed agreement instead, you are looking for a DPA, data residency commitments and zero data retention, and those are priced items: Vapi publishes a HIPAA add-on at $2,000 a month and zero data retention at $1,000 a month. If you are phoning or texting US consumers, A2P 10DLC registration and STOP handling are not optional whichever platform you choose.
Takeaway: in five of these six situations the constraint picks the platform, not the feature list. Name the constraint first and the shortlist writes itself.
Billing units, decoded
This is the single most useful thing this directory can tell you, and it is the thing every vendor pricing page is quietly structured to obscure. Every platform here publishes a monthly price. Almost none of them are measuring the same thing, so the prices cannot be compared until you convert them into your own volume.
The glossary entry on execution versus task versus operation covers the vocabulary. The practical version is this. A run-based unit charges once per workflow however long it is, which rewards big workflows and punishes nothing. A step-based unit charges per action, so the same job costs more the more moving parts it has. A compute-based unit charges for time, which means a slow third-party API costs you money even though your workflow did nothing during the wait. A conversation unit charges for traffic, resolved or not. An outcome unit charges only for success, which is the most honest structure in the directory and also the one that scales most directly with how well the agent works. And a token unit charges for text, which means your bill depends on how verbose your prompts are, a variable most people never think to measure.
The failure mode is always the same. Someone models a workflow at 500 runs a month, picks the cheapest headline plan, and discovers that their 500 runs each loop over thirty rows. On n8n that is 500 executions. On a per-action platform it is 15,000 actions. On a per-row platform it is 15,000 credits. The workflow did not change; only the meter did. Before you commit, count three numbers: how many times the trigger fires, how many actions each run performs, and how long each run spends waiting on someone else's API.
Reference
What one unit actually buys, by platform
| Unit | Platform | Published rate | What it counts |
|---|---|---|---|
| Task | Zapier | Professional from $19.99/mo billed annually ($29.99 monthly) for 750 tasks | Each successful action a Zap completes. Triggers, polling and built-in tools such as Filter and Formatter are free; some AI actions consume more than one. |
| Execution | n8n | Starter EUR 20/mo for 2,500 executions | One full run of one workflow, whatever the step count or data volume. A 40-step workflow costs the same as a 2-step one. |
| Credit, by action complexity | Autonoly | Starter $29/mo for 10,000 credits | Simple actions cost 1 to 3 credits, advanced AI operations 5 to 15. Cost tracks what the steps do, not how many boxes are on the canvas. |
| Credit, per row of output | Bardeen | Basic $10/mo | One credit per row for scraping and web search. A 500-row scrape is 500 credits, not one run. |
| CPU second | Latenode | $0.00012 per CPU second in the 10,001 to 100,000 band; first 10,000 free each month | Processing time, calculated as runs multiplied by seconds. Step count does not multiply the bill on its own, but a slow API call does. |
| Conversation | Botpress | Plus $150/mo billed annually | Any exchange with at least two messages during the billing month. AI-only and human-assisted conversations count the same. |
| Outcome | Intercom Fin | $0.99 per outcome, $9.99 for a qualification, 50-outcome monthly minimum | A resolution, procedure handoff or disqualification. A conversation that fails to resolve is not billed, so the meter tracks success rather than traffic. |
| Resolution or lead | HubSpot Breeze | $0.50 per resolution, $1.00 per lead, $0.10 per data answer | Outcome pricing denominated in HubSpot Credits, on top of whatever Hub subscription you already carry. |
| Flex Credit | Salesforce Agentforce | $500 per 100,000 credits, or $2 per conversation | A standard Agentforce action costs 20 credits and a voice action 30, so 100,000 credits is 5,000 standard actions. |
| Copilot Credit | Microsoft Copilot Studio | $200 per prepaid pack per month | One credit for a classic answer, two for a generative one, with published action rates running from 1 to 100 credits and voice from 10 to 75 credits a minute. |
| Platform minute, unbundled | Vapi | $0.05 per minute | Vapi's own hosting and orchestration only. Transcription, language model and speech synthesis are billed by their own vendors, or cost nothing extra if you bring your own API keys. |
| Platform minute, bundled | Bland AI | Start $0.14 per minute | Language model, speech-to-text and speech synthesis in a single rate with no token charges. Higher tiers trade a monthly fee for a lower per-minute rate. |
| Token | Any developer framework | Provider rates, for example Gemini 3.5 Flash at $1.50 in and $9.00 out per million tokens | Fragments of text in and out of the model. The framework is free; the tokens are the whole bill, and they scale with how chatty your prompts are. |
Takeaway: convert every quote into your own monthly volume before you compare two of them. A plan price is a unit price multiplied by an assumption about you that the vendor has not shown you.
Two platforms in the directory publish nothing at all: Workato and PolyAI both route you to a sales conversation instead of a price, and Synthflow has withdrawn self-serve pricing in favour of contracts starting at $30,000 a year. That is not a gap in our research, it is the finding, and it tells you something real about who those products are sold to.
Category questions
- Which category should I start in if I have no idea?
- Answer two questions. Does the problem involve a ringing phone? If yes, you are in voice AI and nothing else in the directory solves it. Will anyone on the team write code and keep owning it? If no, you are in no-code automation or an agent builder, never a developer framework. Those two answers eliminate three quarters of the directory in about ten seconds, and almost every expensive mistake we see comes from someone who skipped them and picked on brand recognition instead.
- Why can I not just compare the monthly prices?
- Because the number in front of the slash is not the same thing on any two platforms. n8n bills a whole workflow run, Zapier bills each successful action inside it, Latenode bills the seconds of compute it consumed, Botpress bills a conversation, Intercom bills only the conversations that resolved, and a developer framework bills nothing at all until you count model tokens. Comparing the plan prices without converting to your own volume is how a $20 plan turns into a $400 invoice.
- Are the free tiers actually usable?
- Some are, and the difference matters. n8n, Activepieces, Windmill, Flowise, Dify and every developer framework in the directory can be self-hosted for the cost of a server, which is genuinely free software rather than a trial. Vendor free tiers are smaller: Zapier gives 100 tasks a month, Autonoly 1,000 credits, Latenode 10,000 CPU seconds. They are enough to prove a workflow works and not enough to run a business on.
- What does a platform actually cost once it is live?
- The subscription is rarely the largest line. Add the model tokens if the platform does not bundle them, telephony if it makes calls, the seats of anyone who needs to see the runs, and the hours someone spends fixing the workflow when an API changes. Our per-review real cost sections work through this for each tool, and the cost page models it against a salary rather than against a rival subscription, which is the comparison that actually decides things.
- Does an open-source framework work out cheaper?
- Cheaper in licence, not necessarily in total. The framework is free and hosting a small agent runs roughly $5 to $20 a month, so a low-volume agent can cost a few dollars. What you take on instead is the engineering: retries, logging, evaluation, upgrades and the person who understands it. If that person leaves, the saving evaporates. Frameworks pay off when you already employ developers, not when you are trying to avoid hiring one.
- Should I pick a platform before or after naming the workflow?
- After, always. Choosing a platform first is the most expensive mistake in this space because it silently rules out workflows the tool is bad at, and you never find out which ones. Name the trigger, the systems it touches and what a good outcome looks like, then read the reviews of the two or three platforms that handle exactly that. The playbooks and the build guides are written in that order for the same reason.
- Do I need a separate platform for voice?
- Usually yes. Voice is the one category that does not overlap: real-time speech needs a latency budget measured in hundreds of milliseconds, interruption handling, telephony and a per-minute economy that no task-based automation platform runs. Some agent builders bolt voice on, and Copilot Studio and Agentforce both publish voice rates, but a purpose-built voice platform will beat them on responsiveness. The usual shape is a voice platform for the call and an automation platform for what happens after it.
- How locked in am I once I have built something?
- It varies more than the marketing suggests. Self-hosted open-source tools and code frameworks are the easiest to leave because you already hold everything. Visual builders export a workflow file that only they can read, so a move is a rebuild. Suite agents such as Agentforce and Breeze are the stickiest, because the agent is not the thing you would be leaving, the CRM underneath it is. Each review has a migration section that says plainly how hard the exit is.
- Where does a8gent fit in all this?
- We build on whichever of these the workflow actually needs, and we say so before starting. The free audit maps your processes and tells you which ones are worth automating and which are not, and the automation services cover the build and the handover with documentation, so you own what we build rather than renting it. If you would rather build it yourself, the guides and courses cover the same ground without us.
Still undecided? Head-to-head comparisons break a tie between two named tools, the model directory covers the separate question of which LLM does the reasoning underneath, and what AI automation costs prices the whole thing against a salary rather than against a rival subscription. If you would rather hand the decision over, the free AI automation audit is where to start, and our automation services cover the build and the handover.
What this collection is for
This directory answers one question: what should the automation be built on? It is grouped into four categories - no-code automation platforms such as n8n, Zapier and Activepieces; agent builders such as Lindy, Botpress and Intercom Fin; voice platforms such as Vapi, Retell AI and ElevenLabs Agents; and developer frameworks such as LangGraph, CrewAI and the OpenAI Agents SDK. Each review covers what the tool is best at, where it falls short, roughly what it costs, and the alternative worth trying.
Do not start here if you have not yet decided what to automate. Choosing a platform before naming a workflow is the most common and most expensive mistake in this space, because the subscription then drives the design. Go to the free tools or the playbooks and come back with a workflow written down.
How to choose
Four questions, in this order. The first one eliminates most of the directory.
- Does it talk on the phone? Voice is its own category with its own physics - a latency budget, barge-in handling, telephony and, in most of North America, A2P 10DLC registration. If the answer is yes, read Vapi, Retell, Bland and Synthflow, settle it with Vapi vs Retell, and nothing else in this directory matters to you.
- Will anyone on the team write code? If no, you want a no-code platform or an agent builder: n8n if you want power and are willing to self-host, Make or Zapier if you want the integration to already exist, Power Automate if you live in Microsoft 365. If yes, a framework gives you control that no builder will: LangGraph for stateful multi-step work, CrewAI for role-based teams, Pydantic AI for typed outputs, and LlamaIndex when the job is really retrieval.
- Does it face a customer unedited? If it does, weight reliability, error handling and support response over feature count, and prefer the platforms with real observability into failed runs. Customer-facing support specifically is where the packaged answers - Intercom Fin, Chatbase - often beat anything you would assemble, and the comparison covers the trade.
- Who owns the data and the bill? If you need data residency or want to avoid vendor lock-in, the self-hostable options are the shortlist: n8n, Activepieces, Windmill, Dify and Flowise. Price it properly first - the true cost of self-hosted n8n is not the subscription you avoided.
- Is the thing you want already a product? A surprising share of automation requests are features somebody already sells. Support deflection, appointment booking and lead qualification all have packaged answers, and assembling your own is only worth it when the packaged one cannot reach your data or cannot be made to stay quiet on the topics you care about. Before you build, read Agentforce if you live in Salesforce, HubSpot Breeze if you live in HubSpot, and Copilot Studio in a Microsoft estate. The honest comparison is ChatGPT agents versus custom agents.
Two things not to weight heavily. Integration counts are marketing: what matters is whether the five systems you use are covered, which the integration checker settles in a minute. And benchmark leaderboards belong to the model rather than the platform - that is a separate directory and a separate decision.
Where this sits
Platforms is what you build on. Models is what does the reasoning - OpenAI, Anthropic, Gemini, DeepSeek and the rest, with pricing per million tokens and data-policy notes. The two are independent: you pick a platform and then point it at a model, and keeping that choice swappable is a deliberate design goal. Compare is where a two-way shortlist gets broken, and tools is upstream of all three, answering whether the workflow deserves automating in the first place.
What to do first
Run the stack picker to get to two or three candidates, then read those reviews in full rather than skimming ten. Check the running cost with the workflow cost calculator and the honest market ranges on what AI automation costs. Then build one small workflow on your first choice before committing to an annual plan - a build guide is a good test drive, and switching after one workflow is cheap while switching after twenty is not. If you would rather someone else made this call, the free audit includes the stack recommendation in writing.
A note on how this directory is put together, because directories are easy to pad. We cover the tools teams keep asking about and the ones we have shipped real work on, which means some well-known products are missing and some obscure ones are here. The reviews name weaknesses, and where a platform is a poor fit for a small business we say so rather than hedging. Pricing notes are what the vendor publishes; anything you would only learn on an enterprise sales call is marked unknown rather than guessed.
Whatever you pick, keep the exit cheap. Route model calls through one place, keep credentials and message copy out of the platform where you can, and write down what the workflow does in plain language so the knowledge does not live only inside a canvas. The workflow brief is the document for that, and vendor lock-in explains what you are guarding against. Most migrations are survivable; the painful ones are the workflows nobody had written down.
No single platform wins for every team
This directory covers the tools people actually build agents on: no-code builders, voice AI, and developer frameworks. Each review is honest about what a platform is best at and where it falls short.
If you are early, weight ease of use and price. If you are shipping something customer-facing, weight reliability and support. If you have engineers, a framework gives you more control than any builder. Match the platform to the stage you are at, not the one you aspire to.
Not sure where to start? Run the stack picker to narrow the field to two or three, then read those reviews in full.
Which platform is best for beginners?
A no-code builder. You get a working agent fastest and can move to code later if you outgrow it.
Do I need to pay to try these?
Most offer a free tier or trial. The pricing note on each review tells you what you get before paying.
Can I switch platforms later?
Usually yes, though the more custom your build, the more work the move is. Choosing well early saves that pain.
How do you pick which platforms to review?
We cover the ones teams keep asking about and the ones we have shipped real work on.
What is the difference between platforms and models?
A platform is what you build the automation on - n8n, Zapier, Vapi, LangGraph. A model is the LLM the platform calls to do the reasoning, priced per million tokens. You pick a platform, then point it at a model, and the model should stay swappable.
How is the directory organised?
Into four categories: no-code automation platforms, agent builders, voice AI, and developer frameworks. The category you belong in is usually settled by two questions - does it talk on the phone, and will anyone on the team write code.
