A8gent
AI Agent PlatformsAI agent builder

Salesforce Agentforce Pricing and Review (2026)

Autonomous AI agents built into Salesforce.

Reviewed by A8gent
Contents
  1. Verdict
  2. What is Salesforce Agentforce?
  3. Best for, and not for
  4. Strengths and limits
  5. Pricing
  6. What people actually build with it
  7. What Agentforce actually costs at small-business volume
  8. The gotcha: two prices for the same work, and no advice on which to pick
  9. What breaks in production, and how you find out
  10. What it connects to that you already run
  11. Agentforce alternatives: what to pick instead, and when
  12. Migration and lock-in: can you get your work out?
  13. FAQ
VerdictIs Salesforce Agentforce worth it?

Agentforce is the most powerful agent in this batch and the one where the buying decision matters most, because Salesforce sells the same capability two ways at a threefold price difference. Flex Credits cost $500 per 100,000, an action is 20 credits, so a three-action conversation is $0.30. Conversation pricing is $2 flat and bills every chat including the ones the agent fails. At our reference workload that is $300 against $2,000 for identical work. Neither is standalone: you need Salesforce licences first, and Service Cloud Enterprise is $175 per user per month billed annually. For a committed Salesforce shop this is excellent. For anyone else it is the most expensive way to answer a support ticket.

What is Salesforce Agentforce?

Agentforce is Salesforce's platform for building autonomous AI agents that work inside your CRM, handling customer service, sales development, and employee-facing tasks. Agents are configured with Agent Builder and Prompt Builder, grounded in Salesforce data through Data 360, and can take actions like updating records, answering cases, and qualifying leads. It is deeply tied to the Salesforce platform, which is both its biggest strength and its biggest constraint.

Best for

Companies already running Salesforce that want AI agents acting directly on CRM data for service and sales.

Not for

Any business that is not already on Salesforce. The prerequisite licence costs more than most of the agents in this directory cost in total, and you get nothing back for it unless your data genuinely lives in the CRM.

Strengths

  • Flex Credits are published at a real unit price, $500 per 100,000, with per-action rates of 20 credits for actions and 30 for voice, so consumption is forecastable
  • Agents act on the Salesforce data model with the permissions your users already have, which no third-party agent can replicate
  • Salesforce publishes five worked billing examples with the arithmetic shown, which is more transparency than most vendors in this batch offer
  • Digital Wallet gives near real-time consumption tracking with threshold alerts, included free on any Digital Wallet enabled product
  • No overage penalty: exceeding your entitlement bills at the contracted rate in arrears rather than cutting the agent off, unlike Copilot Studio's hard cliff
  • Three buying models - Pre-Purchase, Pre-Commit and PayGo - so you can start without an upfront commitment
  • The $125 per user per month add-on makes internal employee usage unmetered, which removes consumption anxiety for staff-facing agents entirely

Limitations

  • It is not standalone: Salesforce licences come first, and Service Cloud Enterprise alone is $175 per user per month billed annually
  • Conversation pricing at $2 bills every conversation including the ones the agent fails to resolve, unlike Intercom Fin's outcome model
  • Flex Credits and Conversations cannot coexist in one org, so switching means swapping every existing Agentforce SKU through your account executive
  • Unused Flex Credits do not roll over into subsequent subscription terms, so over-committing is a straight loss
  • Agentforce 1 Editions start at $550 per user per month, which is more than most businesses spend on their entire software stack
  • The Agentforce Rate Card that governs voice multipliers is not published on the pricing page, so voice cannot be fully modelled from public information
  • Pre-Commit was still described as widely available later this year when we checked in August 2026, so one of the three buying models is not yet fully available

Salesforce Agentforce pricing

There are now four ways to buy Agentforce and they are not interchangeable. Flex Credits are the consumption currency at $500 per 100,000 credits, with a standard Agentforce action costing 20 credits and an Agentforce Voice action 30, which works out at $0.10 and $0.15 respectively. Conversations are the flat alternative at $2 per conversation, optimised for customer-facing agents, and Salesforce states Flex Credits and Conversations cannot coexist in the same org. Separately, the Agentforce User License is $5 per user per month and still requires Flex Credits, the Agentforce add-on for Sales, Service and Field Service is $125 per user per month for unmetered employee usage, the Industries add-on is $150, and Agentforce 1 Editions start at $550 per user per month including 2.5 million Flex Credits per org per year. Unused Flex Credits do not roll over into a subsequent term, and there is no overage penalty: exceeding your entitlement bills at your contracted rate monthly in arrears.

Salesforce Agentforce pricing tiers
PlanPriceWhat you get
Salesforce Foundations$0Free entry point with Agentforce Builder, Prompt Builder, Agent Script and Agentforce Vibes
Flex Credits$500 per 100k credits$0.005 a credit. An Agentforce action is 20 credits ($0.10), a Voice action 30 credits ($0.15). Fungible across actions, prompts, translations and voice
Conversations$2 per conversationFlat per-conversation pricing for customer-facing agents. Cannot be used in the same org as Flex Credits
Agentforce User License$5/user/moCompany-wide employee access with limited CRM object access. Still requires Flex Credits for the metered usage
Agentforce add-on$125/user/moUnmetered employee Agentforce usage for Sales, Service and Field Service. Industries add-on is $150
Agentforce 1 Editionsfrom $550/user/moAdd-on included plus 2.5 million Flex Credits per org per year, billed annually
Prerequisite: Service Cloud$175/user/moService Cloud Enterprise, billed annually. Starter Suite is $25 and Pro Suite $100, both with transaction fees and Pro Suite requiring a contract

Pricing reflects public plans as of August 6, 2026 and can change. Check Salesforce Agentforce for the latest.

What people actually build with it

Agentforce's distinguishing feature is that an action is a real operation against the Salesforce data model, executed with the permissions of the identity running it. That makes the useful builds the ones where answering the question requires touching a record, not just retrieving a document. Salesforce publishes five worked examples with the arithmetic shown, and they are the best guide to what the platform is actually for.

The builds Salesforce prices out itself

Customer self-service order status. The agent authenticates the customer from their email address, retrieves order details from the order management system, and returns a real-time status and delivery estimate. Two actions, 40 Flex Credits, $0.20 a request. At 20 requests a day Salesforce puts this at $120 a month, and it is the cleanest example of why credits beat conversations: the same exchange on Conversation pricing would be $2.

Internal case management for service agents. The agent identifies the customer by email, pulls all cases for that contact, and adds a case comment. Three actions, 60 credits, $0.30 per case. Salesforce models 100 users handling three cases a day over 20 days at $1,800 a month, which is the number that shows how quickly employee-facing metered usage argues for the $125 per user unmetered add-on instead.

Field service appointment scheduling. Identify the customer, fetch work types, pull appointment slots twice, answer a knowledge question. Five actions, 100 credits, $0.50 per appointment. This is the shape where Agentforce earns its keep, because scheduling against real availability is not something a retrieval chatbot can fake.

IT support and new-employee onboarding, answering from a knowledge base at one action, 20 credits, ten cents a question. Salesforce models 20 new starters asking five questions each at $10 a month. Note how cheap purely conversational work is on credits, and how badly it would be served by $2 conversations.

Voice reservation management, at four actions per call and 30 credits per voice action, which Salesforce prices at $180 a month for 300 calls. Voice actions cost half again what standard actions do, and the full multiplier detail sits in the Agentforce Rate Card rather than on the pricing page.

Where Agentforce is the wrong choice

Anything whose data does not live in Salesforce. This sounds obvious and gets ignored constantly. An agent grounded in a CRM that holds a third of the relevant context will give confidently partial answers, and you will have paid Service Cloud Enterprise prices for the privilege. If your operational truth is in a scheduling system, an ERP or a spreadsheet, connect an automation platform to those systems instead.

Simple FAQ deflection on a marketing site. Salesforce's own numbers put a knowledge answer at ten cents, which is competitive, but you cannot get to that ten cents without the licences underneath it. Chatbase or Botpress will do this job for a flat monthly fee that is less than a single Service Cloud seat.

Cross-system back-office workflow. Agentforce actions are Salesforce-shaped. For a nightly job that reconciles three systems none of which is Salesforce, you want n8n, Make.com or Workato, and using an agent at all may be the wrong instinct.

Bottom line: Agentforce is worth its price when the agent must read and write real CRM records with real permissions, and is poor value for anything that is fundamentally retrieval over documents.

What Agentforce actually costs at small-business volume

The reference workload is 1,000 support conversations a month with 700 resolved without a human. On Flex Credits, assume a realistic three actions per conversation - identify the customer, look something up, answer or update. That is 60 credits, or $0.30, per conversation. All 1,000 conversations consume credits whether they resolve or not, because credits bill on actions taken rather than outcomes reached, giving 60,000 credits and $300 a month.

On Conversation pricing the same workload is 1,000 times $2, or $2,000 a month, for identical work. That is not a typo and it is not an edge case. Conversation pricing only becomes competitive above 20 actions per conversation, which is far beyond a normal support exchange. Salesforce sells both models and its FAQ describes the choice in terms of flexibility and flat pricing rather than in terms of the number.

Then add the prerequisite. Agentforce cannot be bought alone, and a customer service deployment sits on Service Cloud. At Enterprise, $175 per user per month billed annually, three agent seats is $525. That is the number no vendor page in this batch puts next to the agent price, so here it is next to all five.

The prerequisite licence nobody prints. Same workload throughout: 1,000 conversations a month, 700 resolved without a human. Vendor rates read 2026-08-06.
PlatformAgent add-on priceLicence required firstAll-in monthly total
Agentforce, Flex Credits$300 at 3 actions per conversationService Cloud Enterprise, $175/user/mo annual~$825 with three seats
Agentforce, Conversations$2,000 at $2 per conversationService Cloud Enterprise, $175/user/mo annual~$2,525 with three seats
Agentforce 1 ServiceIncluded, 2.5M credits per org per yearNone extra - it is the licence$1,650 for three seats at $550 each
Intercom Fin$693 at $0.99 per outcomeNone, Fin sells standalone$693, or ~$780 with three Intercom seats
HubSpot Breeze$320 in credits after the included 3,000HubSpot Professional, from $90/seat/mo~$590 plus $1,500 one-time onboarding
Copilot Studio$200 for one 25,000-credit packMicrosoft 365 tenant plus the pack itself$200 at 8 credits per conversation

Where the money actually goes

Read that table and notice that on the Flex Credits row the licence is nearly double the agent. This is the central fact about incumbent-suite agents and the reason the marketing focuses relentlessly on the per-action price. The agent is cheap; the ticket of entry is not.

Notice also that Agentforce 1 Service at $550 per user per month is not obviously bad value once you have decided to be a Salesforce shop, because it bundles the unmetered add-on and 2.5 million Flex Credits per org per year. At our reference workload, 720,000 credits a year, the bundled allocation is three times what you need. The trap is buying it per user for a team where only two people need it.

None of these totals include Data 360 credits or other consumption services, which Salesforce explicitly excludes from its own worked examples. Treat every figure here as a floor.

Bottom line: At 1,000 conversations a month Agentforce costs about $300 on Flex Credits or $2,000 on Conversations for identical work, and the Service Cloud licences underneath add roughly $525 either way.

The gotcha: two prices for the same work, and no advice on which to pick

Salesforce sells Agentforce consumption two ways. Flex Credits bill per action at 20 credits, or $0.10, each. Conversations bill $2 flat regardless of what happens inside. Both are on the pricing page, both are presented as equally valid choices, and the FAQ that addresses the decision talks about flexibility, scalability and granular usage data rather than about the fact that one is frequently six times the price of the other for the same work.

The break-even is 20 actions in a single conversation. Salesforce's own five worked examples use one, two, three, four and five actions respectively. Not one of them comes close to 20. On the platform vendor's own numbers, Flex Credits win every published scenario, and the margin is not narrow: the order-status example is $0.20 on credits and would be $2 on conversations.

There are two further traps around this choice. First, Flex Credits and Conversations cannot coexist in the same org, so this is not a decision you can hedge by running both and comparing. Second, switching from Conversations to Flex Credits requires swapping every existing Agentforce Conversation SKU through your account executive, which is a commercial negotiation rather than a settings change. You are choosing once, under-informed, and the wrong choice is expensive for the length of your term.

The mitigation is to instrument before you commit. Build the agent under Salesforce Foundations, run it against real conversations, and count actions per conversation in Digital Wallet. If the median is under ten, Flex Credits are correct and it is not close. Also remember that unused Flex Credits do not roll over into a subsequent subscription term, so the PayGo model is the safer starting point even though Pre-Purchase saves the most.

Bottom line: Conversation pricing only beats Flex Credits above 20 actions in a single conversation, and none of Salesforce's own five published examples exceeds five.

What breaks in production, and how you find out

Agentforce fails in ways that are specific to acting on a live CRM rather than answering from documents, which makes its failure modes more consequential than a chatbot's and easier to catch if you look in the right place.

Permission-shaped blind spots

The strength is that agents run with the permissions of an identity. The failure is the same fact viewed from below: an agent running as a restricted user cannot see records that would have changed its answer, and it does not know that. It answers from what it can see, confidently, and the omission is invisible in the transcript because nothing errored.

Find it by testing the agent under several real permission profiles rather than as an administrator. An agent that works perfectly in testing and poorly in production is very often an agent that was tested with a system administrator profile and deployed against a service user with narrower access.

Action count drift and the invoice that follows

Flex Credits bill per action, and action counts are not fixed by you - they emerge from the orchestration. Adding a knowledge source, enabling deep reasoning or changing a topic transition can quietly move a conversation from three actions to six, doubling the cost per conversation with no change in the conversation volume. Because there is no overage cliff, nothing stops it. The first symptom is the invoice.

Digital Wallet is the control and it is free on Digital Wallet enabled products, with near real-time consumption data and threshold alerts. Set alerts on credits per conversation, not just on total credits, because total credits move with volume and hide a per-conversation regression.

Writes that succeed when they should not

The most serious Agentforce incidents are not wrong answers, they are wrong writes. An agent with a case-update action and a plausible-sounding instruction will update the case. Validation rules on the object are your last line of defence, and they are far more reliable than prompt instructions. Put a human in the loop on any action that changes financial state, entitlement or contractual data, and treat prompt-level restrictions as guidance rather than as guardrails, because prompt injection through customer-supplied text is a real vector on a customer-facing agent.

Bottom line: Test Agentforce under the permission profile it will actually run as, and alert on credits per conversation rather than total credits, because orchestration changes can double the unit cost without changing volume.

What it connects to that you already run

Inside the Salesforce estate, Agentforce's reach is unmatched by anything else in this directory. Cases, accounts, contacts, entitlements, knowledge, Field Service work types and appointment slots, Data 360, Slack and Tableau Next are all first-class, and an action against any of them respects your existing sharing model rather than a bolted-on permission layer. That is a real engineering advantage and it is why Salesforce shops buy it.

Outside the estate it is a different story. Agentforce reaches external systems through the same integration machinery as the rest of the platform - MuleSoft, external services, Flow, and the connectors on AgentExchange - and every one of those is a project rather than a checkbox. There is no equivalent of a 6,000-app connector directory. If your operation spans a booking system, an accounting package and a CRM, expect the non-Salesforce two thirds to cost more to connect than the agent costs to run.

The honest comparison is with the platforms built for breadth. Zapier, Make.com and n8n connect to thousands of applications and know almost nothing about your data model. Agentforce knows your data model intimately and connects to comparatively little. Neither is better; they solve opposite problems, and the most common architectural mistake we see is choosing on agent quality rather than on where the data actually is.

Agentforce's reach, honestly split.
SystemHow Agentforce reaches itEffort
Salesforce objectsNative actions with your existing sharing modelConfiguration
Salesforce KnowledgeGrounded answers as a one-action retrieval, 20 creditsConfiguration
Slack and Tableau NextFirst-party surfaces, bundled in Agentforce 1 EditionsConfiguration
Third-party SaaSMuleSoft, external services, Flow or an AgentExchange partner actionIntegration project
Bespoke internal systemsCustom API-backed actionsEngineering, plus the API if it does not exist

Bottom line: Agentforce is unbeatable on Salesforce data and unremarkable on everything else, so the deciding question is what proportion of the answer lives inside the CRM.

Agentforce alternatives: what to pick instead, and when

Almost every Agentforce alternative is cheaper. The question is what you give up, and the answer is nearly always the same thing: depth of integration with the system that holds your customer truth. Pick the alternative when that system is not Salesforce, or when the agent's job does not require touching records at all.

Agentforce against four alternatives at 1,000 conversations a month, 700 resolved without a human.
PlatformBilling unitCost at the reference workloadWho it suitsDoes better than Agentforce
Agentforce20 Flex Credits per action, or $2 per conversation~$825 to ~$2,525 all-inBusinesses whose operation genuinely runs on SalesforceReads and writes CRM records with your real permission model
Intercom Fin$0.99 per outcome$693, no prerequisite licenceSupport teams on any helpdeskCharges nothing when the agent fails, and needs no suite licence
HubSpot Breeze$0.50 per resolution~$590 all-in on HubSpot ProfessionalCompanies on HubSpot rather than SalesforceA fifth of the licence cost for comparable CRM grounding
Copilot StudioCopilot Credits, $200 per 25,000$200 at 8 credits per conversationMicrosoft 365 estatesFar cheaper per conversation, and free for employee-facing use
WorkatoNot published; custom annual quoteQuoted, typically enterprise-scaleMulti-system integration without a CRM centre of gravityConnects a heterogeneous estate rather than one vendor's

When to pick the alternative

Pick Intercom Fin if support deflection is the goal and Salesforce depth is not. Fin runs on top of Salesforce as a helpdesk anyway, bills only on outcomes, and costs less than Agentforce on Conversation pricing by a factor of three. If your Salesforce usage is really just case management, this is the honest recommendation.

Pick HubSpot Breeze if you are choosing a CRM rather than already locked into one. Breeze gives you CRM-grounded agents at $0.50 a resolution on a Professional licence from $90 a seat, against Service Cloud Enterprise at $175. The capability gap is real but it is not a $1,000-a-month gap for a team of three.

Pick Copilot Studio for employee-facing agents, full stop. Agentforce charges $125 per user per month for unmetered employee usage; Microsoft zero-rates employee usage entirely for Microsoft 365 Copilot licensed users. If your staff already have those licences, paying Salesforce for internal agents is difficult to justify.

Pick Workato or n8n when the work spans many systems and no single one is the centre of gravity. Agentforce actions are Salesforce-shaped by design, and forcing a cross-system reconciliation job through them is more expensive and more fragile than using an integration platform built for it.

Bottom line: Every alternative here is cheaper than Agentforce, so the only defensible reason to choose it is that your answers genuinely require reading and writing Salesforce records.

Migration and lock-in: can you get your work out?

Agentforce is the most locked-in product in this batch and it is not close. The agent is defined in terms of Salesforce objects, executed against Salesforce permissions, billed in a Salesforce currency and surfaced through Salesforce channels. There is no export format that another platform can read, because there is nothing coherent to export: an Agentforce agent is a configuration of a system, not an artefact.

That is a rational position if Salesforce is a decade-long commitment, which for many businesses it genuinely is. The cost of the lock-in is not the agent, it is that the agent raises the switching cost of the CRM itself. Every action, prompt and topic you build is additional work that would have to be redone if the CRM ever moved, and the whole point of building them is that they encode operational knowledge.

There are two softer dependencies worth naming. Flex Credits do not roll over into a subsequent subscription term, so an unused balance at renewal is simply lost, which pushes buyers toward under-committing and then paying in arrears. And the Conversations-to-Flex-Credits switch requires swapping every existing SKU through an account executive, so even moving between Salesforce's own pricing models is a negotiation.

The hedge is documentation rather than technology. Write down what each agent is meant to achieve in plain business language, separately from how it is implemented: which decision it makes, what data it needs, what it is forbidden to do, and what the escalation path is. Keep a set of real conversations with correct answers as an evaluation set. If Salesforce ever stops being the answer, a rebuild that starts from documented intent takes weeks; one that starts from reverse-engineering a live org takes months.

Bottom line: An Agentforce agent cannot be exported in any usable form, so the practical hedge is documenting each agent's intent in plain language so a future rebuild starts from requirements rather than archaeology.

Salesforce Agentforce FAQ

How much does Agentforce cost?

It depends which of the two consumption models you buy. Flex Credits are $500 per 100,000 credits, or half a cent each, and a standard Agentforce action costs 20 credits, so an action is $0.10 and a typical three-action conversation is $0.30. Conversation pricing is a flat $2 per conversation. Both sit on top of Salesforce licences you must already hold: Service Cloud Enterprise is $175 per user per month billed annually. At 1,000 conversations a month that is roughly $300 in credits or $2,000 in conversations, plus the licences.

What are Agentforce Flex Credits?

Flex Credits are Salesforce's consumption currency for Agentforce, priced at $500 per 100,000 credits. Each action an agent takes draws from the pool: a standard Agentforce action is 20 credits and an Agentforce Voice action is 30. Credits are fungible across actions, prompts, translations and voice actions, so you are not forecasting separate budgets per feature. Unused credits do not roll over into subsequent subscription terms. Salesforce publishes worked examples, including a self-service order-status agent at two actions per request costing $120 a month at 20 requests a day.

Flex Credits or Conversations: which should we pick?

Flex Credits, in almost every case where your conversations are not enormously complex. At $0.10 an action, a conversation breaks even against the $2 flat rate at 20 actions, which is far more than a normal support exchange uses. Salesforce's own worked example of a customer self-service order lookup uses two actions, or $0.20. Conversations only make sense if your agents routinely run very long, action-heavy interactions and you value the predictability of a flat rate. Note that the two cannot coexist in one org, and switching means swapping every existing SKU.

Do we need Salesforce to use Agentforce?

Yes. Agentforce is an add-on to the Salesforce platform, not a standalone product. Salesforce Foundations gives you Agentforce Builder, Prompt Builder and Agentforce Vibes at no cost as an entry point, but a production customer service agent sits on Service Cloud licences, and Service Cloud Enterprise is $175 per user per month billed annually. Compare that with Intercom Fin, which works with any helpdesk and needs no prerequisite licence at all. The licence is usually the larger number.

Agentforce vs Copilot Studio: which is cheaper?

Copilot Studio, decisively, at ordinary support volumes. A Microsoft prepaid pack is $200 a month for 25,000 Copilot Credits, and Microsoft's own worked support-agent example consumes 8 credits per conversation, so 1,000 conversations fits inside a single pack. The same 1,000 conversations on Agentforce is about $300 in Flex Credits or $2,000 in Conversations, before Salesforce licences. The real question is not price though, it is which platform holds your data. Neither agent is worth anything grounded in a system it cannot see.

What happens if we run out of Flex Credits?

Nothing dramatic, and this is a genuine advantage over Microsoft. Salesforce states there is no overage penalty: if you exceed your entitlement, usage bills at your contracted rate monthly in arrears. Compare Copilot Studio, which disables custom agents outright at 125 percent of prepaid capacity and shows end users a billing-issue message. The risk with Agentforce is therefore a surprise invoice rather than an outage. Digital Wallet threshold alerts are the control, and they are included free.

Is Agentforce worth it?

For a business whose operation genuinely runs on Salesforce, yes, because the agent reads and writes your real data model with your existing permissions and no bolt-on can match that. For anyone else it is the most expensive way to answer a support ticket in this directory once the licence is counted. The test is simple: if removing Salesforce would stop your business, Agentforce is the right agent for you. If Salesforce is one system among several, an agent that connects to all of them will serve you better for less.

Does Agentforce have a free plan?

Salesforce Foundations is listed at $0 and includes Agentforce Builder, Prompt Builder, Agent Script and Agentforce Vibes, which is enough to build and try an agent. It is not enough to run a customer-facing agent in production, because that consumes Flex Credits or Conversations and sits on licensed Salesforce clouds. Treat Foundations as an evaluation environment rather than a free tier. The PayGo buying model is the honest starting point: no upfront commitment, billed monthly in arrears for what you use.

Can you help us size and build an Agentforce deployment?

Yes, and the sizing decision is worth more than the build on this platform, because picking Conversations over Flex Credits can multiply your bill threefold for identical work. We map your real conversation shapes to action counts, model both pricing models against your actual volumes, and identify which workflows genuinely need CRM-native depth and which would be cheaper elsewhere. That starts with a free automation audit, and the handover includes documentation you own plus a recurring plain-language report of what ran and what it consumed.

Looking at alternatives? We will say the thing Salesforce's own page will not: if your agent is customer-facing and you have a choice, Flex Credits beat Conversations by a factor of three at ordinary conversation complexity, and Salesforce sells both without telling you that. Where Agentforce genuinely beats us and everyone else is depth of CRM integration. An agent that reads and writes your case, account and entitlement objects with your existing permission model is doing something a bolt-on cannot, and for a business whose operation truly runs on Salesforce that is worth the money. Where it loses is everywhere else. Autonoly builds fixed-scope automations against whatever systems you actually run, and you own the result rather than renting it per action forever. See the Autonoly review.