Quick summary
- Licence is only one line. Over five years, annual support, people and upgrades usually cost more than the licence itself.
- Proprietary costs grow with you. Subscriber-based licences and support fees calculated on them rise as your customer base grows.
- Open source moves cost to people. You pay for skills, implementation and support instead of a licence, and you choose who provides them.
- Neither is always cheaper. Scale, in-house skills and how much you need to change the system decide it.
What total cost of ownership means for a BSS
A business support system (BSS) runs everything between "the customer signed up" and "the money is in the bank": the product catalogue, customer accounts, orders, usage rating, invoicing and payments. It's also one of the longest-lived systems an operator owns. Billing platforms often stay in place for many years, because replacing one means moving every customer, balance and open invoice.
That long life is why the purchase price says so little. Total cost of ownership (TCO) is everything you spend to buy, run, change and eventually leave the system. For a BSS it falls into five groups:
- Licence or subscription: the right to use the software, paid once (perpetual) or every year (subscription or SaaS).
- Support and maintenance: patches, upgrades and access to the vendor's support team.
- Infrastructure: servers or cloud, the database and any other licensed software the BSS depends on.
- People: implementation, integration, data migration, day-to-day operations and new products or price plans.
- Change and exit: customisations, version upgrades, and what it costs to move off the system later.
Open source and proprietary BSS spread the money across these groups very differently. That's why comparing the first-year quote with "free" gives the wrong answer in both directions.
Open source vs. proprietary BSS: the cost line by line
| Cost line | Proprietary BSS | Open source BSS |
|---|---|---|
| Licence | Up-front licence or annual subscription, often tied to subscribers, transactions or revenue. | None. You can download, run and change the software. |
| Support | Annual fee, usually a percentage of the licence and rising each year. Hard to drop without losing upgrade rights. | Optional. Run it with your own team, or buy support from the project's maintainers or a partner. |
| Database and platform | Often requires a specific commercial database and middleware, licensed separately. | Usually runs on open source databases such as PostgreSQL or MySQL. |
| Infrastructure | Sized for the vendor's reference architecture, often several tiers from day one. | Varies by project; smaller platforms can start on one server and grow. |
| Implementation | Vendor or certified partner, priced by day or fixed scope. | Your team, the maintainers or any partner who knows the code. |
| Customisation | Through the vendor's extension points; deeper changes go back to the vendor. | Full source access; changes can be made by anyone with the skills. |
| Upgrades | Included in support, but the project to apply them is yours to fund. | Free to download, but you still fund the testing and rollout. |
| Exit | Data extraction and decommissioning can need vendor help; licences may need formal termination. | Easier, because the schema and code are open, but moving data to a new system is still a project to budget for. |
Where proprietary BSS costs pile up
The licence metric grows with your business
Most telecom BSS suites aren't priced per server. They're priced on what you bill. Oracle doesn't publish BRM pricing, but the licensing advisory firm Redress Compliance reports that BRM is licensed on a "Subscriber" metric that counts working telephone numbers and activated devices, not customer accounts, with a fallback of one subscriber per US$1,000 of annual revenue for businesses that don't fit those categories. Other vendors use transactions, accounts or a share of revenue. The effect is the same: as you add customers, the licence bill grows, even though the software hasn't changed.
For a growing MVNO or ISP, that turns success into a recurring licence negotiation. Check whether inactive, suspended or IoT lines count, and whether the price per subscriber drops as volume rises.
Support fees compound
Annual support is usually the biggest line over five years. Oracle's own price list shows support at 22% of the licence price: $10,450 a year on a $47,500 database licence. Licensing advisers such as SoftwareOne and Redress Compliance report the same 22% of the net licence fee across Oracle software, usually with an increase at each renewal. Simple arithmetic shows what that means: on a $1 million net licence, five years of support at 22% comes to $1.1 million before any increases. By year five, support alone has cost more than the original licence.
Support is also hard to cut. Oracle's support policies require every licence in a licence set to stay on the same support level. You can't keep support on only part of an estate, and any licences you stop supporting must be terminated. If support lapses and you want it back, Oracle charges a reinstatement fee of 150% of the last annual support fee, prorated back to the date support lapsed.
Platform licences you didn't plan for
Enterprise billing suites often need a specific commercial database, application server or analytics product. Oracle's own Technology Global Price List puts Database Enterprise Edition at $47,500 per processor licence, before options such as Real Application Clusters at $23,000 per processor. Ask every vendor whether the database and middleware licences are included, restricted-use, or extra.
Real-time charging can be a separate bill too. Redress Compliance notes that Oracle's Elastic Charging Engine (ECE) is licensed separately from BRM core, on a different metric such as concurrent transactions or peak throughput, so renewing your BRM subscriber band doesn't cap what you pay for charging.
Change goes through the vendor
New price plans are usually configuration, but deeper changes such as a new rating rule, a custom invoice, or an integration the product doesn't support often go back to the vendor's professional services team at their day rates. Version upgrades can turn into projects of their own, especially when years of customisation have to be re-tested.
Where open source BSS costs hide
Open source software does lower cost for most organisations. In the Linux Foundation's State of Global Open Source 2025 report, based on 851 survey responses, 84% of respondents said open source lowers the cost of software ownership. But "no licence fee" doesn't mean "no cost", and an honest open source BSS cost model includes these lines:
- Skills. Someone has to install, configure, monitor and patch the system. If that skill isn't in-house, budget for a support contract or an implementation partner.
- Security and patching. With no vendor support contract, applying security updates on time is your responsibility.
- Integration. Payment gateways, provisioning, CRM and mediation still need connecting. Check which integrations exist out of the box and which you'd build.
- Feature gaps. If the platform doesn't do something you need, you fund the development, though you then own the result.
- Project health. A platform with an active maintainer and regular releases costs less to run than one you'd have to maintain alone. Check the release history and who stands behind the code.
The difference is that these are costs you control. You can do the work yourself, buy it from the project's maintainers, or move to another partner, without losing the right to use the software.
A five-year BSS total cost of ownership model
Prices vary too much to publish one honest figure, so build the model with your own quotes. Use the same five years and the same assumptions for every option:
| Cost line | How to estimate it |
|---|---|
| Licence | Year-one quote, plus the extra licences you'd buy as subscribers grow each year. Zero for open source. |
| Support | Annual rate × licence value, with the vendor's yearly increase. For open source, the quoted support contract, or the internal staff time if you self-support. |
| Infrastructure | Servers or cloud for production, test and disaster recovery, plus any database or middleware licences. |
| Implementation | Fixed-scope quote for setup, data migration, integrations and a parallel bill run. |
| Operations | Staff or managed-service cost to run bill cycles, patch, monitor and add products, per year. |
| Change | An allowance for one major upgrade and for custom development over the period. |
| Exit | What it would take to move your data out at the end. Often left out, and often large. |
Then run the model at your expected subscriber count in year five, not today's. Subscriber-linked licences look affordable at launch and very different after three years of growth. That single change to the model often decides the comparison.
When a proprietary BSS is the cheaper choice
Open source doesn't win every comparison. A commercial suite can cost less overall when:
- You operate at tier-1 scale. Real-time converged charging for millions of 5G subscribers needs engineering that large vendors have already paid for.
- A tender demands certification. If certified TM Forum Open API conformance is mandatory, a certified product avoids building and proving it yourself. See what TMF Open API means for a billing platform.
- You already own the stack. If the database, middleware and skills are already in place and paid for, the extra cost of the billing module is smaller.
- You want a single point of accountability. If you have no technical team and won't build one, a fully managed SaaS BSS bundles hosting, support and upgrades into one fee.
Questions to ask before you compare quotes
- What is the licence metric, and what counts towards it: active, suspended, prepaid, IoT?
- What is the annual support rate, and how much can it rise each year?
- Which database, middleware and third-party licences are needed, and are they included?
- Is real-time charging part of the core licence, or a separate product on its own metric?
- What does a version upgrade involve, and who pays for the project?
- Who can change the system besides the vendor, and at what day rate?
- How would we export all our customer, balance and invoice data if we left?
- For open source: who maintains the code, how often are releases made, and what does a support contract cost?
The cost of running OpenBRM as your open source BSS
OpenBRM is an open source BSS covering rating, subscriptions, invoicing, payments, a built-in CRM, device inventory and a self-service storefront in one platform. On the cost lines above, here's where it sits:
- Licence: none, and no per-subscriber or per-transaction fee, so cost doesn't grow with your customer base. The full source is published.
- Database and platform: a Java application on Tomcat with PostgreSQL, so there's no commercial database licence. It can start on a single server. See the system requirements.
- Rating: the built-in OpenRate rating engine rates CDRs in batch or real time, so usage rating isn't a separate product to license on its own metric.
- People: run it with your own team, or have Saralam Technologies, the team that builds it, handle implementation and support. Our services are priced on the work, not on a licence.
- Change: custom behaviour goes into plug-ins and meta fields rather than a modified core, so it carries forward when you upgrade.
Where it isn't the cheaper choice: tier-1 real-time charging at very high volumes, or tenders that require certified TMF conformance. Moving from an older OpenBRM 2.x release to the current one is also a platform migration, not a file swap, so budget for it. If you're comparing against Oracle specifically, see OpenBRM vs Oracle BRM, or our guide to Oracle BRM alternatives for the wider shortlist.
The quickest way to check the numbers is to try it: download OpenBRM and bill a sample of your own customers, or ask us for a hosted trial and a scoped estimate.
Disclaimer: Oracle figures come from Oracle's published price list and support policies; BRM and ECE licensing details come from independent licensing advisers, as Oracle doesn't publish them. Actual terms vary by contract. Get written quotes from each vendor before you decide. Last reviewed: November 2026.
Open source BSS cost: common questions
The software is free to download and use, with no licence fee. You still pay for servers and for the people who implement, run and support it, whether that's your own team or a partner.
Usually annual support. Oracle, for example, charges 22% of the licence fee each year, so five years of support costs more than the original licence, even before yearly increases.
Add licence, support, infrastructure, implementation, operations, change and exit costs over the same period, usually five years. Model them at your expected subscriber count at the end of the period, not today's.
At tier-1 scale with real-time converged charging, when certified TM Forum conformance is mandatory, when you already own the vendor's stack, or when you have no technical team and want a fully managed service.
No. OpenBRM has no licence fee and no per-subscriber or per-transaction fee. If you use Saralam Technologies for implementation or support, that work is priced separately on its scope.
Sources
- Oracle: Technology Global Price List
- Oracle: Software Technical Support Policies
- SoftwareOne: Oracle technical support, understanding the facts
- Redress Compliance: Oracle BRM licensing and the Subscriber metric
- Redress Compliance: Oracle Communications BSS/OSS licensing buyer guide
- Linux Foundation Research: The State of Global Open Source 2025 (PDF)