Abstract: Systems, methods, and computer program products are disclosed for customized segmentation operations in a serverless environment. An intermediate platform receives a signal from an entity requesting application hosting for use with a SaaS platform. The signal conveys personalized configuration information and a unique identifier. The personalized configuration information is used to construct a metadata configuration file. A request is transmitted to the serverless environment for a segmented storage location and a request for a related signed URL containing permission for writing data. The metadata configuration file is sent to the segmented storage location. The signed URL is provided to the entity requesting application hosting for enabling secure transmission of a code to the segmented storage location directly by the entity requesting application hosting.

Abstract: Systems, methods, and computer program products allow usage of shared software resources. A first application to be run as a first image includes first code and first metadata information including a first set of functionalities, and first specific settings for a first set of functionalities. A mapping of the first set of functionalities to a first list of shared software resources enables the first application to accomplish the first set of functionalities. A second application to be run as a second image includes a second code and second metadata information including a second set of functionalities and second specific settings for a second set of functionalities. A mapping of the second set of functionalities to a second list of shared software resources enables the second application to accomplish the second set of functionalities. The first and second lists of shared software resources have at least one shared resource in common.

Abstract: Systems, methods, and computer program products are disclosed perform data access operations in association with a multi-tenant SaaS application within a Multi-tenant SaaS Platform. Code for a multi-tenant SaaS application includes a call to a token associated with retrieving tenant-specific data. A first request is received for first data access using a first token associated with a first tenant associated with a first storage location, the first request lacking an identification of the first storage location. Tenant-specific data associated with the first tenant is retrieved and provided to the multi-tenant SaaS application. A second request is received for second data access using a second token associated with a second storage location associated with a second tenant. The second token is mapped to the second storage location. The second tenant tenant-specific data is retrieved from the second storage location and provided to the multi-tenant SaaS application.