The Maestrano platform is composed of the following components:

1 - Frontend App(s)

The frontend applications are interfaces between the users - customers, staff, partners - and the actual Maestrano platform. While most implementations only include one frontend application - usually a customer portal/marketplace/dashboard - one could decide to create a different application for staff users such as support or administrator people. One could also decide to use the Maestrano platform in order to serve multiple business purposes - multiple business units - and create multiple frontend applications accordingly.

Maestrano supports multi-tenancy out of the box. This means that frontend applications can be setup with access to the same customer base or different customer bases (isolated frontend applications).

Frontend applications are lightweight, dependency-less Ruby on Rails (RoR) applications connecting via API to MnoHub (see section below). Frontend applications do not need a database such as MySQL or Oracle to function as all data are accessed via API from the hub. A database can always be added if application specific data or metadata need to be stored.

While Maestrano provides a RoR template to build frontend applications, one could easily choose another application stack to build their own frontend as the only hard dependency is to be able to consume the MnoHub JSON REST API.

2 - MnoHub

The Maestrano Hub acts as an orchestrator for the whole platform. It holds any data related to customer identification, billing and product purchase/subscription. The hub is also responsible for maintaining the Access Control Lists (ACL) for all platform users.

The hub contains customer related application logic exposed via two different APIs:

• The HUB API is used by frontend applications (see section 1) to retrieve and update customer data.
• The Developer API is used by third party applications to query data about their customer portfolio as well as submit bills for any subscription that users may have taken inside their app

The hub also acts as a Single Sign-On provider for accessing Cloud and Hosted application (= not "data only" or "connector" applications such as QuickBooks). Users coming from frontend applications and wishing to access an app are redirected to the hub wish then handle authorisation as well as single sign-on handshake with the applications.

Finally, the hub also contains an authorisation API called "IDM" (Identity Manager) that can be used by other services - such as Connec!™ - to authorise API queries. This is typically the case when users load their Impac!™ dashboard. A session token is enclosed in the query and transmitted through Impac!™ to Connec!™ which then contacts the hub to verify that the provided token (user) has access to the data. While Connec!™ is currently the only service to use the IDM, other services - such as Nex!™ for third party access to the apps - are expected to leverage the IDM in the near future.

3 - Nex!™

BLA - Overview Diagram

The diagram below show how all components interact together.

Image Removed

 section presents the platform and its different components

The following pages are available in this section