My dilemma: Custom CMS or Open Source?

I prefer Joomla. Because Joomla contains advance features like ACL ( different user groop access,easy to modified). It will also easy to handle the site safe and secure.

Expensive lesson to learn.

Ok, the main benefit of using an opensource solution - presuming it has a large community supporting it, is that upgrades and addons are usually widely available, and a lot of times for free - or very little cost.

Using your custom CMS solution would likely incur a fee every time you want to add features, or require updates.

If it were me - I'd have thoroughly researched first - but, if I found myself in your position now...

I'd continue the development of the custom CMS version (assuming you own full rights to sell it), and then package it up and sell it (assuming it's the type of script that users can easily install and use).

You'd be responsible for providing support etc, though.

With the money from the script sales - I'd then invest in the opensource customisation, and potentially be in profit.

Kindest regards,
Karl.

I think, building software is an iterative process. It always evolves. Even if you have already paid for your custom CMS in all likelihood there will be a lot of continual changes that you will have to make because complex Pinterest-like social sites need to always add features to stay relevant and expand. And, of course, they have to roll out updates in response to inevitable security threats. So you’re looking at continual financial outlay to do all that.

Yep, ideally, it would be specific to your needs which means fast, less redundant code and a completely customisable layout but as it grows if it is not based on a solid modular design (which is hard to nail on the first iteration of the product) it might become increasingly difficult to maintain and expand in the future resulting in more bugs and increased development times meaning you’ll have to spend more money.

An open source CMS on the other hand has been through many iterations already (Joomla is a good example) since there’s a large community of developers that has perfected it in the last several years. Its design is very well understood and tested. So there’s much less re-inventing the wheel, even if you need to customise it for your specific needs.

There are advantages in “rolling your own” CMS but, I think, if you are not a well-rounded developer yourself then you’re better off basing your new system on an Open Source CMS.

Of course as always your mileage may vary,

All the best

PS. it's unfortunate that you're already half way through with developing your custom system at this point it may be hard to just bite the bullet and "cut the losses". Only you can decide what's best

Going the custom route is going to cost you time and more money.

Drupal is a highly powerful CMS platform. You can do anything with Drupal. We have made marketplaces, ecommerce sites, membership sites - the sky is the limit. It has lots of develop support, tons of years behind in, and is packed with features. The right developer can make it happen.

Goodluck.

I always suggest open source. Open source CMSs are so powerful now there's rarely a reason to build a custom one. They will save you a lot of time and money. I've also seen twice this year where someone knew had a custom CMS and it was infected with malware. A custom CMS can end up having some major security holes. Don't get me wrong open source can have it's share of problems too but I find it less likely and it's typically easier to find answers to such problems.

The catch with either is support costs...
You spend at most 10% on development, compared to 90% for support & maintenance over the life of your site.

This is why open source is embraced by so many because that 90% is now almost completely free...

I don't use Joomla, but I'd also definitely prefer to go opensource (I'm a python aficionado). Obviously it helps "a lot" to be coding-literate, so you can get yourself out of the occasional holes and not be forced to reach for the purse at every road bump.
Still, it's a tough call: would I "cut my losses" or stick with my initial decision/strategy. I think you should consider not your past, but the future of your project: which road will bring your project the best outcome in the future ...
best of luck!