Home | Private Catalog

Private Catalog

A Private Catalog allow ahasa users to onboard a choice of preferred containerised applications on to an owned (private) product space which is not visible to external parties.

Watch the video on Product Catalogs >>

The Value of Private Catalogs 


Reduced cost for integrations

With Private Catalog apps, developers do not need to invest in expensive siloed integrations and deployment tools.

Version Management

The Private Catalog makes product creation and versioning a much easier process. It allows your created solutions to be deployed on the platforms of your choice of Cloud service provider such as Google or AWS.  

Efficient design

The digital design studio using the Private Catalog allows you to visually design, integrate multiple products and own a solidity of crafted solutions and deployments delievring efficient design effort. 

Speed-up onboarding

ahasa comes with a single graphical interface to onboard products onto the Private Catalog

Compliance & governance

With the product versioning feature, and the process of internally approved products (trustworthy third-party products which are onboarded), it is easier for organisations to maintain corporate compliance and good governance while using up-to-date products to craft solutions. 

Ensuring Good Governance with Private Catalogs 


As best practice and good governance, it is recommended that the admin user or the ‘super user’ of the ahasa account reviews all app design requests generated from any individual user account or any third-party product onboarding requirement.

This should also include an initiation process to prepare a standardised evaluation process with approvals from the relevant authorised personnel inside the organisation. For new app requests, the user will be first requested to check the existing Catalog for the same or a similar product before onboarding the new product. 

The administrator or the super user can then share the products created inside the Private Catalog with other users of the organization for use. 

When onboarding products, it is critical that the authenticity and trust of all onboarded products are validated before proceeding to a published state.