Now you have an enterprise open source billing system as an alternative for your billing solution.
| |
In-House Development |
Proprietary Vendor |
jBilling |
| Source code available |
Yes |
No |
Yes |
| Complex business rules |
No. The norm is to develop only those strictly necessary for today's requirements and development never ends. |
Yes |
Yes, with a dedicated- rules engine |
| Licensing costs |
No |
Yes. It can amount to $100,000s per year. |
No |
| Development cost |
Very High. Assigning internal resources to build a billing system is the most expensive option, and often underestimated. |
Included in license |
No |
| Custom Features |
Yes |
No |
Yes |
| Billing domain know-how |
No. You need to go through a steep learning curve. |
Yes |
Yes |
| Maintenance & Support Costs |
High |
Medium to high |
Medium |
| Bottom Line |
Focus your business on what it does best. Do not build infrastructure that is already built and available without cost. |
Avoid being locked-in with a vendor with high licensing costs |
A choice where your retain full control of your billing solution, based on a proven billing framework. |