> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/application-management/packages/packaging-requests.md).
# 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.
## Architecture (Win11 & macOS)
The RealmJoin Packaging Factory packages applications for Windows 11.
macOS packaging is in preview. macOS requests are accepted on a best‑effort basis; processing times and availability may vary.
### Custom vs Generic Packaging
We aim to create packages as **generic** as possible: unmodified vendor installers without customer-specific alterations, available to all customers in the Package Store. All settings are then configured in the RealmJoin Portal after subscribing.
**Custom** packages 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. They are only visible in the *Custom* section of your Package Store. See [Package kinds](/application-management/packages.md#package-kinds).
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. Custom packaging is an add-on and incurs additional costs; if it is not part of your plan, the *Custom* option in the request form is disabled.
## Request Types
Requests are submitted on the **New Packaging Request** tab of *Request Package* in the RealmJoin Portal. Your previous requests are listed on the **Request History** tab.
Three request types are available: **New Package**, **Update Package** and **New Organic Package** (see [Organic Packages](/application-management/packages/packaging-requests/organic-packages.md)). New Package and Update Package require the `CanRequestSoftwarePaas` [permission](/administration-and-settings/permission/custom-roles/available-permissions.md#software-requests), New Organic Package requires `CanRequestSoftwareOrganic`. Before submitting, confirm that you have reviewed this documentation.
{% hint style="warning" %}
**Plan ahead:** We highly recommend raising new package and update requests at least **14 days before the planned rollout** of the application or update. This leaves time for packaging and for your [testing](/application-management/packages/packaging-requests/application-package-testing.md). There is no priority line for packaging requests, see [Packaging Delivery Time](/legal/support.md#packaging-delivery-time).
{% endhint %}
### 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:
* **Package Type** - *Generic* (when no customer‑specific data is included) or *Custom* (additional fees apply). The Packaging Factory may change a request from generic to custom if justified, for example when customer‑specific details are identified during processing. Customers will be informed of such changes before the request is completed.
* **Package Name**, **Vendor** and **Version**.
* **Override Reply Address** - The email address that receives all communication about the request. It may differ from the signed-in user's address and is required if your account has no mailbox.
* **Installation Parameters and Configurations** - All required configuration switches as command‑line parameters, registry keys, configuration files, or similar (up to 2047 characters; longer instructions can be added as files to the upload). Silent/unattended installation commands are always required. Screenshots are not accepted; PACKaaS does not include Scripting‑as‑a‑Service.
* **Description** (optional) - Any additional context you want to pass to the Packaging Factory.
* **Application binaries** - After clicking **Open Request**, upload the binaries and click **Upload all files**. Binaries must always be uploaded for new packages; a download URL may be added for reference but is **not** sufficient. If there are multiple files, please use a zip container.
{% hint style="info" %}
When you enter a package name, the form lists existing Package Store packages that match it, so you can check whether the software is already available before requesting it.
{% endhint %}
RealmJoin packaging request form for new requests.
### 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 for new package requests. Select the package from the dropdown, which lists the packages subscribed in your tenant; update requests can only be submitted for those packages. Enter the **New Version** and the **Installation Parameters and Configurations**. If the parameters have not changed, refer to the previous version's parameters.
**Skip Upload** is only available for update requests, e.g. when you only add parameters to an existing package.
RealmJoin package request form for package updates.
{% hint style="info" %}
Note: Additional switches, new parameters or configuration files for an existing package are considered updates and shall be requested the identical way.
{% endhint %}
{% hint style="danger" icon="exclamation" %}
**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. Silent/unattended installation parameters are not optional and **must** be provided.
* the request creates a ticket. All communication will be handled in this ticket and is only sent to the reply address. If your account has no mailbox, the form asks for a reply address with an active mailbox. Once the ticket is created, the reply address can not and will not be changed.
* the [Software Requester](/administration-and-settings/permission/pre-defined-roles.md#software-requester-permissions) 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 if a feature is missing
* any incomplete request will be rejected.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.realmjoin.com/application-management/packages/packaging-requests.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
