search

Packaging Requests

RealmJoin provides Packaging‑as‑a‑Service (PACKaaS) for applications not available in the RJ Store or for outdated packages. For details, contact your RealmJoin consultant, partner, or support team.

hashtag
Architecture (Win11 & macOS)

The RealmJoin Packaging Factory is currently optimized for Windows 11 application requests, delivering robust and reliable packaging services across the Windows ecosystem. Full macOS support is in active development and will add hundreds of ready‑to‑use macOS applications to the RealmJoin Store, enabling a more complete cross‑platform experience.

macOS packages are currently in preview as we continue refining the macOS packaging pipeline. We accept macOS application requests on a best‑effort basis, though processing times and availability may vary during this development phase. Our team will handle these requests as effectively as possible within the current framework.

We appreciate your patience as we work toward delivering the same level of excellence for macOS that our Windows 11 users currently enjoy.

hashtag
Private vs Generic Packaging

hashtag
Generic Packages in RealmJoin

We aim to create packages as generic as possible. This allows all settings to be configured via the RealmJoin portal post-app subscription. Our generic packages feature unmodified installers provided by vendors, without any customer-specific alterations. These packages are accessible to all customers in the RealmJoin store.

hashtag
Private Packages in RealmJoin

Custom packages are exclusively available for customers in their custom section of the RealmJoin Package Store. The custom namespaces are used for modified installers, including those customized by the vendor for the customer, such as SAP, or for customer-developed apps and similar cases.

We invite customers to share their evaluation on whether an application can be packaged as generic or requires a custom package, however, the final decision is made by the RealmJoin Packaging Factory. Note that private packages incur additional costs.

hashtag
Request Types

Three different PACKaaS requests are currently available: new package, update existing package and organic packages.

hashtag
New Packages

If an application is not available in the RealmJoin Store, it can be requested for packaging via the RealmJoin Packaging Factory. A valid PACKaaS request must include:

  • Application binaries, which must always be uploaded for regular packaging requests (a download URL may be added for reference but is not sufficient).

  • Documentation describing all required configuration switches as command‑line parameters, registry keys, configuration files, or similar (screenshots are not accepted; PACKaaS does not include Scripting‑as‑a‑Service).

  • Packaging type selection, specifying whether the application should be created as a generic package (when no customer‑specific data is included) or as a private/custom package (additional fees may apply). The Packaging Factory may change a request from generic to private if justified; for example, when customer‑specific details are identified during processing. Customers will be informed of such changes before the request is completed.

  • Contact email address, which may differ from the currently authenticated user’s email.

  • Installation parameters, which may be entered directly in the request instead of embedding them in the ZIP file.

  • Use of “skip upload”, which is allowed only when updating or adding parameters to an existing package—binaries must still be provided for all standard packaging requests.

RealmJoin packaging request form for new requests.

hashtag
Package Updates

If an application is required in a newer version than the one available in the RealmJoin Store, the same processes and requirements apply as new package requests. When the updated binary behaves identically to the existing version, command‑line parameters may be omitted from the request. A dropdown list is available showing all packages currently subscribed to within the tenant, and update requests can only be submitted for those subscribed packages.

RealmJoin package request form for package updates.
circle-info

Note: Additional switches, new parameters or configuration files for an existing package are considered updates and shall be requested the identical way.

circle-info

Tickets, Files and Setup

Please note that:

  • all update and new package requests necessitate the provision of both binaries and documentation detailing the required command line parameters.

  • if an update request does not entail changes from the previous version, the submission of new parameters is not required.

  • the request creates a ticket. All communication will be handled in this ticket, and it will only be sent to the account that created it. If this account does not have any active mailbox, the requester will not get any information.

  • the software requester role can be assigned to any user group in the tenant, therefore, an ADM account may not be required.

  • organic packages and PACKaaS might be not available right away, please get in touch with [email protected] if a feature is missing

Last updated

Was this helpful?