.svg)
Licensing options built for how you deploy
Vodia offers two licensing models designed for different deployment and commercial needs. Both provide access to the same production-ready PBX platform. The difference lies in how capacity is planned, how billing works, and how much operational flexibility you need.
Prepaid Licensing
Prepaid, single-tenant licensing
Prepaid licensing is delivered through predefined license bundles that combine capacity and feature levels into a fixed, predictable model.
This model is designed for dedicated PBX deployments where the system is installed for a single customer and capacity is known in advance.
This approach is commonly used for on-premise installations or dedicated cloud environments where the deployment is stable and well defined.
Once licensed, the system behaves like a fully owned PBX environment, regardless of where it is deployed.
When does this work best?
This approach works best for deployments that:
Deploy a dedicated PBX per customer.
Plan user or extension counts upfront.
Keep licensing costs stable and predictable.
Run on-prem or in a dedicated cloud.
Sell the deployment as a fixed package.
If these scenarios match your deployment, prepaid licensing is the right licensing model for you.
Choose the right feature level
Offered with multiple feature levels to match different operational needs.
Feature levels define what the system can do, not how it is deployed.
Standard
The essential PBX feature set for straightforward deployments.
Includes core functionality such as:
- User extensions
- SIP trunk connectivity
- Basic call routing and IVR
- Core PBX admin tools
Commonly used for smaller or fixed environments with simple call flows.
Pro
Extended functionality for environments with more flexibility.
Everything in Standard, plus:
- Advanced call handling
- Expanded routing and configuration capabilities
- Additional admin controls
Well suited for growing deployments or teams with more complex call logic.
Enterprise
The complete PBX feature set with no functional limitations.
Includes everything in Pro, plus:
- All available PBX features
- Advanced integrations
- Recording, monitoring, and enterprise-level controls
Designed for large or complex deployments with advanced operational requirements.
Understanding how prepaid licensing is structured...
How pricing, capacity, and upgrades work once a package is in place.
What’s included with this model
Prepaid licensing provides a complete, self-contained PBX deployment with predictable costs.
Each bundle includes:
- A single-tenant PBX instance dedicated to one customer
- A fixed extension capacity defined by the selected bundle
- A prepaid license term, billed annually or via monthly card charges
- Full access to all features included in the selected feature level
- A stable licensing cost for the duration of the license term
Once activated, the license cost does not change during the term, regardless of usage.
Extension capacity and scaling
Prepaid licenses are available in predefined sizes to support a wide range of deployments.
- Bundles are available from 5 extensions up to 1000 extensions
- The maximum number of extensions is fixed by the license bundle
- Billable extensions refer to user extensions only
If additional capacity is required, the license can be upgraded to a larger bundle.
Commercial model
With prepaid licensing, partners purchase the license from Vodia and resell it to end customers as part of their own commercial offering.
While Vodia primarily operates through partners, this licensing model is also available for direct sales. The licensing structure remains the same; only the commercial terms differ.
Licensing designed for hotel and accommodation environments
Vodia offers a dedicated hospitality licensing model designed specifically for hotels, resorts, and multi-room accommodation environments.
Unlike standard PBX licensing, hospitality licensing is structured around room count, with additional capacity for staff extensions and agent usage. This approach reflects how phone systems are typically deployed and operated in hospitality environments.
Hospitality licensing is available as predefined bundles, allowing deployments to be sized predictably without relying on per-user or per-extension billing.
How hospitality licensing is structured
Hospitality licenses are packaged in tiers that define:
- The number of hotel rooms
- The number of regular extensions for staff and services
- Agent capacity for front desk and operational use
Each bundle is designed to support a specific property size, from small hotels to large multi-site deployments.
Licensing is capacity-based and does not fluctuate month to month based on usage.
When hospitality licensing is the right fit
Hospitality licensing is typically the best choice when:
- The deployment is for a hotel or accommodation environment
- Phone endpoints are primarily associated with guest rooms
- Staff extensions and agent capacity are planned separately
- Predictable, room-based licensing is preferred
- A predefined bundle simplifies planning and deployment
Important note: Hospitality licensing follows a separate structure from both prepaid (single-tenant) and usage-based (multi-tenant) PBX licensing.
Frequently Asked Questions
Does the license cost change based on usage?
Are feature levels tied to extension count?
Can I upgrade my bundle later?
Can prepaid licensing be used for hosted deployments?
Is prepaid licensing available for hospitality deployments?
When should I choose usage-based licensing instead?
Usage-based licensing
Postpaid, multi-tenant licensing
Usage-based licensing is designed for hosted and multi-tenant PBX deployments where capacity changes over time and billing needs to reflect actual usage.
Instead of purchasing a fixed license upfront, usage is measured and billed monthly based on how the system was used during the previous billing period.
This model is commonly used by service providers and partners operating shared PBX platforms for multiple customers.
When does this work best?
This approach works best for deployments that:
Run a shared PBX for multiple tenants
Add or remove extensions month to month
Let billing follow actual usage automatically
Scale without resizing or upgrading licenses
Support changing tenant needs and setups
If these scenarios match your deployment, usage-based licensing provides the most operational flexibility.
What’s included
Usage-based licensing includes the full Vodia PBX feature set.
Full PBX capabilities
All PBX capabilities are available by default, with no feature tiers to manage.
No feature restrictions
Capabilities are not limited by a licensing tier. Configuration defines what’s enabled.
Usage-based billing
Billing is calculated based on actual usage, not on enabled features or predefined packages.
Understanding how usage is measured...
Usage-based licensing is billed monthly based on the number and type of extensions used during the previous month.
Common extension types
Common extension types include:
- Full extension
- Hotel room
- Classroom
- Mailbox-only
- No registration
- Collaboration (Microsoft Teams integration)
- Residential
- App-only
- Queue agent
- Hot desk
Different extension types are billed differently, allowing partners to align costs with how the system is actually used.
Scaling and flexibility
Usage-based licensing is built for environments where capacity is not static and change is expected.
Instead of committing to fixed limits upfront, the system scales naturally as tenants are added, removed, or modified over time. There are no predefined extension limits and no license resizing required as usage changes.
- Tenants can grow or shrink without license changes
- New extensions can be added at any time
- Unused capacity is not locked into a prepaid package
- Monthly costs automatically reflect actual usage
This model removes the need for long-term capacity planning and allows service providers to adapt quickly as customer requirements evolve.
Commercial model
With usage-based licensing, partners typically operate the PBX as a hosted service and bundle licensing into their own commercial offerings.
Customers are billed as part of a recurring service, while partners are charged monthly based on actual usage.
Direct sales follow the same licensing structure, with commercial terms adapted accordingly.
Frequently Asked Questions
Are there feature tiers or editions with usage-based licensing?
Does billing change if usage changes?
Do I need to plan capacity in advance?
Can different tenants have different configurations?
Is usage-based licensing suitable for large deployments?
Can I switch to prepaid licensing later?
When should I choose prepaid licensing instead?
Need help choosing the right licensing model for your environment?
Talk to our team to review your deployment model, usage patterns, and commercial requirements.
Prefer to explore on your own? Launch a prepaid instance on:
