Custom Billing & Support..?

siforek

New member
Alright, so I'm starting this topic because you really don't see very many "in house" systems anymore, and even less from smaller operations(which I guess I'd consider myself). Nothing against all the great solutions like WHMCS, ClientEx, Blesta, etc..

I'd like to see how many here use custom solutions, and perhaps get some feedback on how to further develop mine. So far the plan has been working out pretty well: I add features to my system as I need them, maybe a few things a week. This way I'm not going down a huge list of popular features spending countless hours, and I'm also able to ensure everything is working perfectly before I move on to the next thing.

If there's some serious developers here, I'm totally willing to share source in an effort to further expand things. Ultimately I'd like to offer the first 100% open source host billing/support system with a great deal of support.

I know there's a demand for it. I can't count the number of threads I've seen started at WHT looking for Free & Good host systems. We all know there's not any at the moment compared to the paid solutions.
 
So, you want to make it easier to start a web hosting company?

No. Make it better to run one. First mine, then others. An open source system comparable to many popular paid/encoded ones would have great advantages. Imagine if I needed a special feature I could simply add it and contribute to the community. Yes, I know some current systems allow "modules", but it's just not the same.
 
The idea is there, and there are a few that are about although the only problem I can see with open source is security and support, even though many applications such as joomla pull it off well, the addition of community modules can be very “dangerous” although it does depend on how open you intend the project to be, for example community development vs closed development.

That would be my only reservation over say choosing whmcs or another system that is already well rounded. Although that said there will always be security holes in any piece of code/software/script just really depends on how determined someone is to gain access.
 
The idea is there, and there are a few that are about although the only problem I can see with open source is security and support, even though many applications such as joomla pull it off well, the addition of community modules can be very “dangerous” although it does depend on how open you intend the project to be, for example community development vs closed development.

That would be my only reservation over say choosing whmcs or another system that is already well rounded. Although that said there will always be security holes in any piece of code/software/script just really depends on how determined someone is to gain access.

If you've ever stopped by the WHMCS forums and noticed all the contributions, and members willing to advance feature development you'll understand the outcome if they were actually given access to the source.

There's just the licensing/security issues, which CAN be sorted out.
 
Back
Top