> 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.md).

# Packages

RealmJoin's catalogue of ready-to-use Windows and macOS application packages deployable via RealmJoin Client or Microsoft Intune, and the concepts behind subscribing, assigning and updating them.

RealmJoin Packages are software packages for Windows and macOS that RealmJoin builds and maintains. You subscribe to them in the RealmJoin Portal and deploy them via the **RealmJoin Agent** or **Microsoft Intune**. Android apps from Managed Google Play are managed on the same pages.

This page explains the terms used throughout this section. The pages below follow the lifecycle of a package: find it in the store, subscribe to it, assign it, and keep it up to date.

## Package lifecycle

<table data-view="cards"><thead><tr><th></th><th></th><th data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>1. Find</strong></td><td>Browse and search the Package Store.</td><td><a href="https://docs.realmjoin.com/application-management/packages/package-store.md">Package Store</a></td></tr><tr><td><strong>2. Subscribe</strong></td><td>Add a package to your tenant for RealmJoin or Intune deployment.</td><td><a href="https://docs.realmjoin.com/application-management/packages/package-store/package-store-details.md">Subscribing to a Package</a></td></tr><tr><td><strong>3. Assign</strong></td><td>Assign the package to users and devices through managed groups.</td><td><a href="https://docs.realmjoin.com/application-management/packages/package-deployment.md">Package Assignments</a></td></tr><tr><td><strong>4. Update</strong></td><td>Roll out new versions manually or automatically, with a preview stage.</td><td><a href="https://docs.realmjoin.com/application-management/packages/package-updates.md">Package Updates and Automation</a></td></tr></tbody></table>

## Key concepts

### Package kinds

Every package in the [Package Store](https://docs.realmjoin.com/application-management/packages/package-store.md) belongs to one of these kinds:

* **Generic** - Built without any customer-specific configuration and available to all customers. Settings such as arguments are configured after subscribing.
* **Custom** - Built specifically for your organization, for example from a vendor-customized installer or an in-house application. Only your tenant sees it. Custom packages are created through a [packaging request](https://docs.realmjoin.com/application-management/packages/packaging-requests.md) and are an add-on.
* **Organic** - Built automatically from a `.zip` file you upload, without involvement of the Packaging Factory. Only your tenant sees it. See [Organic Packages](https://docs.realmjoin.com/application-management/packages/packaging-requests/organic-packages.md).

Independent of the kind, packages exist for **Windows** and **macOS**. Android apps are not part of the RealmJoin catalogue; they are added from [Managed Google Play](https://docs.realmjoin.com/application-management/packages/android-apps-managed-google-play.md).

### Maintained and unmaintained packages

**Maintained** packages are updated by the RealmJoin Packaging Factory whenever the vendor releases a new version, so you can keep them up to date [automatically](https://docs.realmjoin.com/application-management/packages/package-updates.md#automation). For **unmaintained** packages, you request updates yourself. See [Packaging Roles & Responsibilities](https://docs.realmjoin.com/application-management/packages/packaging-requests/packaging-roles-and-responsibilities.md).

### Deployment method

You choose per package whether it is delivered by the **RealmJoin Agent** (recommended) or pushed to **Intune** as an `intunewin` app. See [Deployment Methods: RealmJoin Agent vs. Intune](https://docs.realmjoin.com/application-management/deployment-methods.md) for how the two differ.

### Managed and basic subscriptions

* **Managed** (recommended) - RealmJoin creates and manages a fixed set of Entra ID groups for the package (Main, Preview, Available, Uninstall and optionally Update). You assign users and devices by adding them to these groups, and you can use the Preview stage and update automation.
* **Basic** (legacy) - No groups are created. You assign groups, users or devices directly. Basic subscriptions can be [converted to managed](https://docs.realmjoin.com/application-management/packages/package-deployment.md#migrating-from-basic-to-managed).

See [Package Assignments](https://docs.realmjoin.com/application-management/packages/package-deployment.md) for details.

### Package badges

The Package Store and the details page of a subscribed package show badges below the package name:

* **Generic / Custom** - The package kind, see above. Organic packages additionally show **Organic**.
* **Maintained / Unmaintained** - Whether RealmJoin provides new versions on a regular basis.
* **Billable / Not billable** - Whether provisioning this package counts towards your package usage quota, if you have one.
* **Free to use / Needs license** - Whether the software needs a commercial license to be used.

On a subscribed package, an additional badge shows the deployment method and subscription type, e.g. **RealmJoinManaged** or **IntuneBasic**.

![Package Name and Status](https://2868468309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkrcM7cKOpXKri1kVrh%2Fuploads%2FJp40BrolzwVT0gsOLp6V%2Fimage.png?alt=media\&token=49a3f4dc-fca6-407d-8ef1-5187e0878f5a)

## Full and limited catalogue

If you recently self-onboarded into RealmJoin or do not have a subscription/licensing agreement yet, the Package Store is limited to a free-to-use subset of packages. Please [contact us](https://docs.realmjoin.com/legal/support.md) to enable the full catalogue for your organization.


---

# 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.md?ask=<question>&goal=<user_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.
