HC10 presents a true hybrid model. It caters to the needs of providers desirous of offering a mix of both Cloud and on-premises services. To deliver on this promise, it integrates with various services such as Web, Mail, DNS, Database, Exchange, SharePoint etc. These services have been classified into three categories:
HC10 connects with all these products using their APIs. Each of these APIs have their own limitations and restrictions and therefore present multifarious challenges in connecting. The API limitations may manifest themselves in the form of security or other concerns. As a consequence some of the products can be managed while still on remote machines whereas for others it’s necessary to have an HC Agent on the machine to receive requests from HC Control Server and then forward to the product.

Because HC10 handles such diverse scenarios, its core architecture has purposely been designed to handle all possibilities. Its architecture consists of the following three components:
Portal refers to a site in IIS and serves as a place for the users to login into their respective management interfaces and administer their accounts. The Portal provides exclusive interfaces to Global Admin, Resellers, Sub-Resellers and Clients. Installation of HC creates a site for the Portal in IIS and names it Hosting Controller Portal. Portal consumes API.

The API component represents a collection of RESTful API. This component is the main brain of HC10, responsible for controlling all the system and database level operations. The entire HC10 business logic and workflows are implemented in this component.

HC Provisioning Services are responsible for all types of provisioning operations and system level tasks. Provisioning could be of resources such as system users, websites, mailboxes, virtual machines etc. As this Agent does the actual provisioning, it is the component available both with the Primary and Agent installations.
The Primary installer is the main HC10 installer and consists of all the three components discussed above. Primary installer can be downloaded here.
Where there is already a machine in the cluster with a Primary installation, already containing the Portal and API, there is usually less need for the full Primary installer again on subsequent servers. To handle this HC10 offers a lighter version of the installer. This Agent only installs the Provisioning Services and as such is much smaller in size than the Primary. Agent can be downloaded here.

On successful installation HC creates an installation folder by the name of “Hosting Controller”. Under this principal folder it creates the following folders:
