Reader setup
Before you choose
List your constraints, required evidence and stop rules before you score options.
- Your current or planned agent count, since Five9's published seat minimum is the first filter, not the last.
- Read-only database access to your own VICIdial install if you want to measure your own concurrent agents and connected minutes — see vicidial-read-only-database-account if you do not have one yet.
- A named owner for telephony operations, since choosing self-hosted means someone owns patching, the carrier relationship and recovery.
- What you will prove
- You will know whether Five9's published plans are even purchasable at your seat count, and you will have a repeatable way to price a per-seat quote against your own infrastructure cost.
- Safety boundary
- This is a pricing and decision comparison, not a benchmark, a feature-parity claim or a vendor endorsement; reverify every figure directly with the vendor before budgeting.
Reader path
How to use this article
- Use it when: You are comparing options and need decision evidence before approval.
- Expected result: Turn options into explicit acceptance criteria and documented stop conditions.
- Start here: Score what is mandatory, keep unknowns visible, then decide only when risks are understood.
Start with the seat count, not the feature list
Fast answer: Five9 publishes a minimum of 50 seats on its own pricing page, current as of August 5, 2026. Below that seat count, Five9's published Digital and Core plans are not a more expensive option next to VICIdial: they are not purchasable at all. That single line decides this comparison for a large share of VICIdial operators before a single feature gets discussed, which is why it opens this article instead of sitting in a footnote.
The rest of this article compares what is actually comparable: the cost shape behind a per-seat quote versus owning a server, what a hosted contact-center-as-a-service (CCaaS) platform like Five9 operates on your behalf, what you give up in control and extensibility when someone else runs the platform, and what switching costs in either direction. It does not rank Five9 against VICIdial, assert feature parity, or hand you a total-cost figure for your own deployment; hosting, carrier rates and staffing vary too much between operators for a single number to be honest.
In plain language: an agent is the person logged into the dialer screen taking calls; a campaign is one outbound or inbound calling project with its own dialing rules; a carrier is the phone company that carries a call onto the public telephone network; a DID (direct inward dial number) is a phone number that routes calls into your system; the dial level, or dial ratio, is how many outbound calls the system places for each agent who is free to take one; and a disposition is the outcome code an agent saves after a call, such as SALE or NOT INTERESTED.
- Know your current or planned agent count before you read a per-seat quote; it is the first thing that matters here.
- This is a pricing and decision comparison, not a benchmark, a ranking or a recommendation.
- Every dollar figure attached to Five9 in this article is dated August 5, 2026 and should be reverified before purchase.
Visual walkthrough
Follow three real demo screens
Captured on an isolated VICIdial demo: Administration screens on September 24, 2026, and the idle Agent screen on August 11, 2026. Each caption states its own capture time, and every sanitized image helps you recognize a related screen; none proves that this article's call, command, or result occurred.Start at Administration home

Use the Administration menu as a map

Confirm version and system-wide context

The fact that decides this before you compare features
Five9's own pricing page, accessed August 5, 2026, publishes two flat per-seat rates: Digital at $119 per seat per month (USD) and Core at $159 per seat per month (USD). The higher Plus, Pro and Enterprise tiers carry no published number at all; the page says only to contact sales for flexible pricing. Every tier, published or quote-only, sits behind the same line: a minimum of 50 seats. The page also notes that usage-based pricing may apply for certain features, and that 24/7 support is included across all tiers.
VICIdial has no seat license and no seat minimum, because there is no seat to buy. You install open-source software on infrastructure you provision yourself, and the role Five9 fills as a subscription line item becomes engineering time your team either already has or needs to add. That is a real cost. It just never shows up as a quote with a number attached to it.
The published field is not uniformly seat-based across every hosted alternative, either. Amazon Connect's own pricing page, also accessed August 5, 2026, states plainly that there are 'no seat-based licensing requirements': voice runs $0.038 per minute plus standard telephony rates, chat $0.010 per message, email $0.080 per message, and SMS or third-party messaging $0.014 per message, with no minimum commitment. That usage-based shape is structurally the closest published match to VICIdial's own economics, paying for calls rather than for chairs, even though the product, support model and everything else about the two differ.
- Reverify Five9's published seat minimum and per-seat prices directly before budgeting anything; pricing pages change without much notice.
- Quote-only tiers (Plus, Pro, Enterprise) have no public number to compare against yet.
- A usage-based model like Amazon Connect's removes the seat-minimum question entirely, at the cost of a very different bill shape.
Two different cost shapes: per seat versus own-the-server
A per-seat quote scales with headcount: fifty agents cost fifty times the per-seat rate whether every seat is busy all shift or idle half of it. A self-hosted VICIdial bill scales differently, with concurrent capacity, connected minutes and the infrastructure sized to carry them, not with how many people are logged in. Those are two different cost shapes, and comparing a per-seat number to a server bill without converting both to the same units is how this comparison goes wrong.
“VICIdial VPS requirements and cost: separate a lab floor from production capacity” walks through building that self-hosted number line by line: compute, storage, backup snapshots, outbound transfer, monitoring, and carrier or compliance services, and it deliberately avoids publishing a single dollar figure, because provider catalogs, regions and taxes move too much for one number to stay honest. The same discipline applies here: price your own infrastructure from a dated quote, not from an average.
The two numbers that decide whether a per-seat plan is cheaper than a server are your own peak concurrent agents and your own monthly connected minutes. Both are measurable on infrastructure you already run, and neither one requires guessing at what a typical business looks like when the business is not yours.
- Convert both sides to the same units, cost per agent per month, before comparing a quote to a server bill.
- Include carrier minutes, recording storage and staffing time on the self-hosted side; they are real costs even without a line-item quote.
- Re-run the comparison after your first billing cycle on either side, not only at signup.
SELECT COUNT(DISTINCT user) AS agents_logged_in_nowFROM vicidial_live_agentsWHERE campaign_id = '<CAMPAIGN_ID>' AND status IN ('READY','INCALL','QUEUE','PAUSED'); SELECT ROUND(SUM(length_in_sec) / 60, 1) AS connected_minutes_last_30_daysFROM vicidial_logWHERE campaign_id = '<CAMPAIGN_ID>' AND call_date >= DATE_SUB(NOW(), INTERVAL 30 DAY) AND length_in_sec > 0;Captured demo response · 2026-09-24 22:25 UTC. The displayed command is the command that ran; a safe subset label means it was filtered, redacted, or fixture-scoped. Replays only after you select Replay transcript.
- Before you run it
- Run both statements with a read-only account, for example mysql --defaults-extra-file=/etc/vicidial-readonly.cnf. READY, INCALL, QUEUE and PAUSED count as logged in because those are the states an agent occupies while still on shift. This lab scopes both statements to one fixture campaign for a safe capture; on your own single-campaign install, drop that filter for an org-wide total.
- Success looks like
- You have your own peak concurrent-agent count and a 30-day connected-minutes total to put against any per-seat quote, instead of an industry average.
- Stop if
- If agents_logged_in_now or connected_minutes_last_30_days looks implausible, check the status list, the campaign scope and the call_date range against your own schema before trusting the comparison.
What a hosted platform operates for you, and what stays yours
Five9 is a hosted CCaaS platform: the per-seat price buys access to infrastructure Five9 operates, not a license you install. In exchange for that price, Five9's own pricing page states 24/7 support is included in all tiers, and the platform itself, the servers and the underlying telephony, plus patching and upgrades to that platform, is Five9's responsibility rather than yours.
Self-hosted VICIdial moves every one of those items onto your own side of the line. “Managed VICIdial hosting vs self-hosting: a decision framework, not a vendor ranking” maps that shared-responsibility split in detail: who owns operating-system patching, VICIdial and Asterisk changes, certificates, firewall rules, database care, recordings, access review, monitoring and incident response, and the same mapping exercise applies here even though Five9 sells software and infrastructure together rather than infrastructure alone.
The practical question is not whether Five9 operates more than a plain hosting provider does; it clearly does, since it also owns the application. The question is whether the list of things you would otherwise staff yourself is worth the per-seat price at your seat count, once you can actually see that list written down instead of assumed.
- Write down who currently owns operating-system patching, telephony changes, certificate renewal, monitoring and incident response for your dialer today.
- A hosted platform the size of Five9 moves most of that list to the vendor's side of the contract.
- Ask for the contract language on each item; a sales conversation is not a commitment.
What you give up in control and extensibility
Self-hosted VICIdial gives you direct database access, direct Asterisk access, and the ability to write a custom report, a custom script or a custom integration against your own schema without asking a vendor's roadmap to move first. A hosted platform exposes what its API and admin console expose, and a change that is not on that surface is not a change you can make.
“Scaling VICIdial: designing a multi-server cluster for 500+ agents” documents the real ceilings that come with keeping that control yourselves at scale: a database that hurts first because every role reads and writes the same tables, per-box audio-channel capacity, and the operational cost of running four split roles instead of one box. That is the actual trade for extensibility: you can change anything, and you also own every ceiling above.
“VICIdial alternatives: an operator test matrix, not a ranking” places Five9 in the commercial contact-center-suite group of alternatives and argues for testing the exact workflow you depend on, login, call handling, disposition and callback scheduling, transfers, scripts, supervisor controls, reporting, against a trial account rather than accepting a features table. That test is what actually tells you how much control a hosted platform costs; a marketing comparison does not.
- Test the specific workflow you depend on today against a trial account, not a features table.
- Confirm whether a custom report, a custom script or a specific integration is possible on the hosted platform before assuming it, one way or the other.
- Self-hosting keeps every extensibility option open; it also keeps every scaling ceiling yours to solve.
The switching cost runs in both directions
Moving onto Five9, or any hosted CCaaS platform, means re-platforming campaigns, scripts and integrations, retraining agents on a new screen, and porting phone numbers (DIDs) and carrier relationships across, on the vendor's contract timeline rather than your own. None of that is priced on the pricing page; all of it is real.
Moving off Five9 later is the same category of work in reverse, plus whatever the contract says about exporting configuration, recordings and data, and however long that export actually takes once you need it. Self-hosted VICIdial has the opposite shape: nothing to export from a vendor, but nowhere else to point when a change breaks something, either.
Before committing budget in either direction, know your own numbers first. Five9's 50-seat floor is a headcount threshold, not a snapshot of who is logged in this second, so the figure that tells you whether you clear it is how many distinct agents actually worked your installation over the last month, measured directly rather than estimated from a badge count or an org chart.
- Budget a migration in either direction as a project with a defined cutover and rollback, not a weekend task.
- Get the contract's data, recording and configuration export terms in writing before you need them.
- Test the destination platform with your own real campaign shapes before retiring the source.
SELECT COUNT(DISTINCT user) AS distinct_agents_last_30_daysFROM vicidial_logWHERE campaign_id = '<CAMPAIGN_ID>' AND call_date >= DATE_SUB(NOW(), INTERVAL 30 DAY);Captured demo response · 2026-09-24 22:25 UTC. The displayed command is the command that ran; a safe subset label means it was filtered, redacted, or fixture-scoped. Replays only after you select Replay transcript.
- Before you run it
- Run this with a read-only account, mysql --defaults-extra-file=/etc/vicidial-readonly.cnf, over a full 30-day window so a single quiet day does not understate your roster. This lab scopes the query to one fixture campaign for a safe capture; run it against your own real campaign to get your own roster.
- Success looks like
- distinct_agents_last_30_days gives you a defensible headcount to test against Five9's 50-seat floor, instead of assuming your business is above or below it.
- Stop if
- If the number looks off, check for shared logins or a campaign filter narrower than your real operation before treating the count as final.
A decision rule instead of a verdict
This article does not pick a side, because the right side depends on numbers only you have: your seat count against the 50-seat floor, your own infrastructure cost against a dated per-seat quote, and how much of the operating list from earlier you actually want to own.
Below 50 seats, Five9's published Digital and Core plans are not purchasable, full stop, as of August 5, 2026. The practical choices are a direct quote conversation with Five9's sales team for an exception, a usage-based hosted option such as Amazon Connect, or self-hosted VICIdial. At 50 seats or more, the comparison becomes real arithmetic: seats multiplied by the published per-seat rate, against your own measured infrastructure and staffing cost.
Run the rule below on your own numbers rather than a hypothetical one. A blank line in it is a sign to go measure something, not a sign to guess.
- Re-run this rule whenever Five9's published price or your own agent count changes materially.
- Treat a quote-only tier as an unknown until you have a dated number in hand, not as a number you can estimate.
- This rule produces an input to your decision; it does not make the decision for you.
agent_count = [your current or planned seat count] if agent_count < 50: five9_published_plans = not purchasable (minimum of 50 seats, as published 5 Aug 2026) next_step = self-hosted VICIdial, a usage-based hosted option, or a direct sales conversation if agent_count >= 50: five9_monthly = agent_count x per_seat_price ($119 Digital or $159 Core, as published 5 Aug 2026) self_hosted_monthly = compute + storage + backup + carrier_minutes + staffing_time compare five9_monthly against self_hosted_monthly using your own dated quote ownership_appetite = can your team patch, monitor and recover the telephony stack itself?switching_tolerance = cost and time you can absorb if you change platforms in two years decision_is_yours = weigh the three lines above together; no single number wins aloneThis sample is a template or reading aid, not a terminal command. There is no output to show.
- Before you run it
- Fill every bracket and blank with your own numbers before treating this as a decision; a placeholder left in place is not an answer.
- Success looks like
- Every line has a real number or a clear yes/no, and the comparison uses your own dated quotes on both sides.
- Stop if
- Stop and gather the missing number rather than picking a side with a blank line still in the rule.
Evidence ledger
Verification basis
- Five9's per-seat prices, tier names and the 50-seat minimum are quoted verbatim from Five9's own pricing page, accessed August 5, 2026, not from a reseller or aggregator site.
- No feature-parity claim is made for either product beyond what the cited pages state.
- No total-cost-of-ownership figure is stated for a VICIdial deployment; it depends on hosting, carrier rates and staffing that vary by operator.
- No vendor is declared better anywhere in this article. It ends with a decision rule, not a verdict.
Primary references
Sources
- Five9 pricingFive9 · accessed August 5, 2026
- Amazon Connect pricingAmazon Web Services · accessed August 5, 2026