Extension and Cloud Function Hosting
Emporix offers a built-in hosting model for custom extensions and cloud functions. Learn how the hosting works, what you can deploy, and how to manage the full deployment lifecycle.
Emporix provides a built-in, secure, and scalable hosting environment for custom extensions and cloud functions built on top of the Emporix Management Dashboard. Instead of maintaining your own cloud infrastructure, you can deploy and operate your custom code directly within the Emporix environment — with versioning, rollback, monitoring, and tenant isolation included out of the box.
Hosting of the extensions and cloud functions is not included in standard billing plans and is billed separately on a pay-as-you-go basis. If you're interested in getting access to the feature, contact the Sales Team.
How it works
The hosting model is project-based. It means that each tenant initializes a single hosting project as a one-time action. The project receives a unique Project ID and acts as the container for all hosted extensions and cloud functions on that tenant.
Emporix supports lazy hosting, which means no pre-configuration is required per tenant before the project is initialized. Once the project is set up, you can add any number of extensions and cloud functions to it.
Each hosted resource follows the same lifecycle:
You upload the code either from a GitHub repository or as a
zip/tar.gzarchive.The system automatically triggers a build process.
A successful build produces a versioned release that is immediately available for use.
For extensions hosting — all previous releases are retained, enabling rollback to any earlier version at any time.
What you can host
Extensions
Extensions are custom UI add-ons built on the MD Module Template, which is based on the module federation concept. A hosted extension integrates directly into the Emporix Management Dashboard and can be registered in one of two ways:
As a module — visible in the Extensions section of the Management Dashboard.
As a perspective — accessible with a dedicated URL path in the Dashboard navigation.
Each extension is identified by a unique Hosting ID, which becomes part of its hosting URL. Display names can be localized to support multiple languages.
The Emporix infrastructure supports up to 20 extensions per hosting project.
Cloud functions
Cloud functions are serverless units of custom logic that can be triggered by events, Emporix APIs, or other platform processes. Unlike extensions, they are not UI components; they operate in the background and can exposed in the Partner Library or consumed through custom API integrations.
Supported runtimes:
Node.js 24
Python 3.14
Cloud functions support environment variables, which can be defined as key-value pairs and used within the function code to securely decode credentials and configuration data.
Full invocation logs are available in the hosting details of each cloud function, showing when and how it was called and what the outcome was.
Example cloud function
Here is the example of a simple cloud function that returns a welcome message and the headers injected by Emporix.
Deployment and versioning
Every deployment — whether an initial upload or an update — triggers a build. The Build History tracks all builds with the following details: deployment ID, build ID, status, and timeline.
For extensions, all published versions are retained in the Releases panel. Each release shows its version ID, status, and timeline. If a new deployment introduces a regression, you can use the Rollback option to revert to any previous release — this results in the release of the selected version.
To set up hosting and deploy your first extension or cloud function, refer to the step-by-step instructions in the Management Dashboard: Hosting.
Invoking cloud functions
Once you have enabled a cloud function hosting in Emporix, you can call the cloud function within your integration through API.
HTTP Methods
To invoke a cloud function, send an HTTP request to the function endpoint. Standard HTTP methods are available, so depending on what you need, you can call one of the following: POST, GET, PUT, DELETE.
Endpoint path
The root endpoint path:
If your cloud function exposes internal endpoints in addition, you can extend the path. For example:
Authentication and authorization
All the requests are routed through the Emporix platform. This means that the platform validates the provided tokens (service, customer, or anonymous). You do not need to implement any additional token validation inside your cloud function.
Request headers
Emporix enriches each request with additional headers that can be used within your function:
emporix-scopes
Contains the list of scopes assigned to the requester. Use this header to verify whether the user has permission to trigger specific logic.
emporix-user-id
Available for customer tokens. Identifies the customer who triggered the function.
emporix-token
The token used for invocation. It can be reused to call Emporix APIs on behalf of the requester.
emporix-legal-entity-id
Present when the customer token is associated with a legal entity. Identifies the related legal entity.
Environment variables
If your cloud function uses environment variables, you can access them in your code as follows:
For example, process.env.client_id.
Example
See the example request calling a cloud function:
Last updated
Was this helpful?