Pricing structure
Kolmisoft pricing is not one-size-fits-all because VoIP businesses vary in size, traffic volume, and infrastructure.
Instead of fixed packages, pricing mainly depends on four factors:
- product (MOR or M4)
- add-ons you choose to use
- hosting model (your server or hosted)
- system implementation and capacity requirements
The sections below explain how each factor affects the final cost.
Product
The first factor is which product best fits your business model.
Kolmisoft offers two main softswitch platforms:
Designed for businesses serving end users or enterprises, such as:
- Retail VoIP providers
- SIP trunking providers
- Virtual PBX providers
- Call centers
- Mixed retail and wholesale VoIP businesses
Designed for high-volume voice routing environments such as:
- Wholesale VoIP transit
- Carrier-to-carrier traffic
- Call center traffic termination
- High-performance routing setups
You can compare both platforms here: MOR vs M4 SBC comparison table
Add-ons (Optional Modules)
Both MOR and M4 can be extended with add-ons that provide additional functionality.
Add-ons only affect pricing if you choose to use them.
See available add-ons:
Hosting: Hosted vs Your Own Server
You can choose where your softswitch will run.
Option 1 – Your own server (on-premise)
Best if you:
- already manage servers or infrastructure
- want full control over your environment
- plan to host the system in your own data center or cloud provider
See recommended hardware.
Option 2 – Hosted Softswitch
Kolmisoft manages the infrastructure and server environment for you.
This option is suitable if you want to:
- avoid server management
- focus on running your VoIP business
- deploy faster without infrastructure setup
System Implementation and Capacity
Pricing also depends on the system implementation required to support your expected traffic volume and reliability requirements.
The recommended architecture depends on:
- expected number of concurrent calls
- calls per second (CPS)
- system architecture (single-server or multi-server)
- redundancy and high-availability requirements
Smaller VoIP deployments can run on a single server, while larger operations typically use multi-server architectures to improve scalability and reliability.
Typical deployment scenarios include:
MOR single-server implementation
- Up to ~500 concurrent calls
- Up to ~50 CPS (commonly closer to ~20 CPS)
- Suitable for smaller VoIP providers or early-stage deployments
MOR multi-server implementation with full redundancy
- Up to ~2000 concurrent calls
- Up to ~100 CPS
- Includes SIP load balancer and distributed services across multiple servers
- Designed for scalable and high-availability environments
M4 scalable multi-server implementation
- Up to ~10 000 concurrent calls
- Up to ~1000 CPS
- Built for large wholesale and carrier-grade traffic
Redundancy and High Availability
For production environments, redundancy can be implemented by adding standby servers, database replicas, or load-balanced nodes.
Redundancy increases reliability and fault tolerance but also increases infrastructure and implementation costs.
More details:
What Does NOT Affect the Price
For transparency, the price does not depend on:
- number of customers
- number of SIP accounts
- number of DID numbers
- number of carriers
- number of routes
These elements are not artificially limited.
Pricing mainly depends on the selected product, infrastructure, expected traffic capacity, and optional add-ons.
Get Pricing
Want to see approximate pricing? Request pricing here.
Want an exact price based on your setup? Please contact us and we will help estimate the most efficient configuration for your business.
