When an account wants to host Maglr content on their local server, there are two options. The first option is for accounts with an annual license to manually export the content to an HTML-zip file. This is a static download that can then be uploaded to their local server. The second option is for Enterprise accounts to automate this process with a direct (FTP/SFTP) synchronisation to a local server. In this update, we will tell you more about the reasons why users would host a Maglr publication on their local server.
IMPORTANT: The first functionality is only available for users with a 1) annual Business license, 2) Pro or 3) Enterprise license. The FTP/SFTP connection is only available for users with an Enterprise license.
Publications hosted on Maglr servers
Our platform and the publications that are created with Maglr are hosted at Amazon Web Services (AWS) Frankfurt. Using a Content Delivery Network (CDN), live publications are (temporarily) stored on various CDN servers that are geographically dispersed. This way, your content is available worldwide quickly and without delay.
Publications hosted on local servers
There can be several reasons for our users to host publications on their own server:
Search Engine Optimization
Publications created with Maglr are being indexed by search engines. But in order to fully complement the domain authority of a corporate website, you can either embed content with an HTML inject or host Maglr publications on the local server. By doing the latter, you can publish the content on the main domain where it will be indexed and contribute to its domain authority, instead of hosting it on a (Maglr) subdomain.
Because of some companies' regulations, it is mandatory for them that all content created with Maglr is under their own control when published. Therefore, a synchronisation would mean that all the published code is hosted on their own server. And when changes or updates are made to a live publication, all newly published code is directly synchronized from the Maglr platform.
Another reason is the companies’ desire to secure the published content for employees or to deny access without authorisation. By hosting and sharing gated content on a local server, companies can fully secure content by company regulations with additional security gates.
The synchronized version that is running on the local servers of the client is completely static. Meaning, in the case when the AWS servers would (potentially) go down, the local version will still work and is not affected. Published projects would still be accessible for visitors. With a direct FTP/SFTP synchronization via the Maglr platform, projects are immediately synchronized on the local server during 'Publishing'. Users are thus not dependent on another FTP program to transfer content to their own primary domain.
Important: the published synced content on a local server is a static minimized version of the original source material uploaded in Maglr. To make edits to these publications, you would still need the Maglr platform to make changes. Updates of our code (that changes every month) are only pushed when you are making new updates or synchronisations to these projects.
To learn more about synchronising publications to local servers, please visit our Help Center or contact us for more inquiries.