Centralpoint's Remote Update Architecture
|It's a fact. All Content Management Systems or Portal technologies purchased today will be seriously outdated within 12 to 18
months of installation, except one: Centralpoint.
Centralpoint doesn't just consider change, it anticipates it. Here at Oxcyon, we like to say, "Let's stop being surprised by surprise and, instead, anticipate surprise." To successfully achieve that and end obsolescence forever, you need a sophisticated architecture "behind" your local installation. Centralpoint has been developed to remotely update its clients (similar to Microsoft Update) regardless of where they are hosted --even if it is a secure portal sitting behind a fire wall.
Clients have been conditioned to repurchase the
same software every few years, like SharePoint 2007, 2010,
and now 2013. We think it is rude to sell clients the same software they have already purchased. That's why our model of delivery ends obsolescence completely. This fact alone should be enough to cause you to pause when it comes to purchasing any software that does not offer a steady stream of enhancements, which can be updated remotely.
The diagram below illustrates Oxcyon's core development of Centralpoint: its ability to provide remote updates. New updates are made available to Centralpoint clients and may be PULLED from their servers, regardless of where they are hosted (even from behind a fire wall). New modules, database structures, or system enhancements are well documented in our Update Notes. These new features are "new options" on a menu, which you can elect to activate for any site that requires them. Our updates do not impact any local development or coding, allowing us all to develop in harmony.
I start where the last man left off. Thomas Edison