Bronson is a rapid deployment framework for LAMP enabling buildling of scaleable highly customized robust membership, content, community and media sites.
There are a few templating systems in the world, a few content management systems in the world, and a few forum systems in the world, and many messaging systems in the world and a few video-media systems in the world, why is Bronson better?
Seamlessness You can put together a video system and a blogging system and a forum system and a content management system and a rating system and a friending system and a messaging system and .... By the time you're done, that's a lot of integration to do. Wouldn't it be better if there was something that did all of them right? That's what we think too. The day will come when you want to show a list of your most prolific users in your remote-video's end-placard, even though you don't want it now. And when that day comes, having an integrated system is critical. Integrating your applications late in the game is too-late and also hurts consumer experience, causing drop-off and affecting the top-line revenues, costs and therefore the bottom-line of any online business from the start to the end.
The Shoe Fits But not all data is alike. Not every business has the same needs, not all brands want to interact with their consumers in the same way. On the web there are a million words for "friend" including enemy, date, appointment, cohort, team-member, acquaintance, etc. Each relations indicates a different kind of media and personal interaction - that's what makes communities unique and brings people to join them. The ability to correctly communicate those relationships in a compelling and custom way for a given brand is an engineering challenge for our competitors which force everyone into a similar data-model, similar relationships model and similar interactions model. Creating customizations of even those open-source packages can cause engineering challenges beyond the ken of even advanced programmers leading to short-term development costs and long-term support nightmares.
Open-Source software is the foundation of most modern technologies, from Linux to Perl to XVID Video. Open source software is critical to the success for every enterprise. At the same time, interacting with those specific technologies is an engineering challenge and finding the right talent to correctly enhance those products can be simultaneously expensive and troublesome. Meanwhile, interacting directly at low-levels with those software pieces can leave consumers of technology in a lurch - what happens when the engineer who rewrote drupal for you gets a better job?
At the same time, because of the distributed nature of open-source development, strict quality controls and programming methods are not enforced in the same manner as a controlled environment leading to the need for ongoing upgrades and revisions based on constant new releases of those pieces. This also presents an engineering challenge - which parts of a given application can be trusted to scale beyond 10,000 users? And who do you call when it fails? What happens when a new version of PHP is released that's not compatible with your community engine but required for your content-management system?
Both of these questions are support problems. In most open-source frameworks, responsibility for supporting the platform is left to the engineers who deployed it, creating the need for constant engagement with that company which may or may not be organized effectively to deliver the needed support.
Bronson, on the other hand, is built to be supported, both by internal resources and by Bronson's Guarantee which is unparalleled in the software industry. By accepting the support issue as a management challenge to be solved up-front, Bronson is able to ensure the ongoing success of an enterprise-critical web presence because it's our core business.
Installing a script to handle uploads or a forum is one thing. It's quite another to handle 10,000 simultaneous transcodes and uploads and voting and display just the right records of a friends' forum postings. We know, we've been there. Take our word for it, it's not the same thing. Delivering dynamic content accurately and consistently during load is an immense technical challenge and if it's not your core business now, the question is whether or not you want to make it into your core business. We've done the heavy lifting, scaling our services across geographically distributed server farms seamlessly and with better performance than any comparable system - including the Mega-Communities. Many open-source community systems are adequate for small-to-medium sized communities, but what happens when they reach 10,000,000 messages, 20,000 videos and 100,000 user comments?
We believe that your time is better spent creating your content and developing your community than worrying whether or not your software will scale.
Of course there are other enterprise-class content management portals. There may even be other enterprise class custom-media-community software with world-class support. (Not that we're awareof.) But the question is how much does it cost to deploy and maintain. Our model is simple. Our license is available as a monthly fee to reduce initial costs and has a buy-out clause for those who want to "take it home". We support and host systems we deploy if desired, obviating the need for in-house headcount and hardward costs and associated management problems. Lastly, because our system is built for rapid deployment, we can demonstrate rapid deployment while other systems are still being installed.
Finally, did we mention our features!?
And our Services