Custom Applications

Deploy and manage your own Custom Applications to Pckgr.

The Custom Applications feature allows customers to upload, validate, and deploy applications that sit outside of Pckgr’s automated private repository, through a simple drag-and-drop tool. This solution is ideal for internal apps, applications behind vendor authentication portals, or software that Pckgr cannot automatically monitor for updates.

Business Plan Required Custom Applications is only available to customers on the Business Plan.

When to Use Custom Applications

Use Custom Applications for:

Internal business applications.
Applications with installers behind authentication or paywalls.
- For example, design packages such as AutoDesk DWG TrueView - read our blog post here for insight into packaging applications such as this.
Commercial applications where Pckgr cannot programmatically access installer files for automation.

Tip: If your installer is publicly accessible for Pckgr to download, submit it through Request an Application. Pckgr will then fully automate patching and version management using its Private Repository.

Packaging Workflow

1. Access Custom Applications

Log in to the Pckgr Dashboard.
Select the Custom Application tool.
Click Create New Application to begin.

2. Upload Installer File

Upload your installer file.
- EXE or MSI only - this is a Windows Application tool.
- For complex application with extra files, upload these as a ZIP file.
Upload the full release version you intend to deploy.

3. Set Application Name

Enter a clear name (for example: FileZilla instead of FileZilla_3.67.1_win64-setup.exe).
The name is critical for downstream detection accuracy.

4. Configure Detection Logic

Auto Detection Enabled (default): Pckgr will automatically extract detection information:
- For MSI files: MSI Product Code will be used for detection.
- For EXE files: Product Name is extracted from registry entries post-install.
Auto Detection Disabled: Pckgr will default to using your provided Application Name for detection.

5. Provide Install String (Highly Recommended)

Supply any known silent install parameters.
Avoid including tokens, license keys, or tenant-specific data.
- This can be added in the 'Install String' section when performing the actual deployment of the Custom Application from the Application Library.
Install strings dramatically improve test validation accuracy.
If you disable this setting, Pckgr will search for and create an install string for you.

6. (Optional) Select Pre-Requisite Application

If your installer depends on another app being installed to validate:
- Select the Pre-Requisite Application from the drop down list.
- Pckgr will use this application during the installation validation test.
- The pre-requisite is only used for verification — it is not included in your package nor deployed automatically.

Verification Process (Automated)

Once the above steps are configured, click Verify. Pckgr performs a fully automated validation process, which includes:

Downloading and isolating the installer file inside a secure container.
Scanning for malware or known malicious content.
Identifying the installer type (EXE or MSI).
Parsing and applying the install string.
Executing the installation silently in a test container.
Scanning the registry to detect installation markers:
- For MSI: Product Code is captured.
- For EXE: Product Name from registry or Application Name (if auto detection is disabled).
Generating a detection script based on registry entries.
Testing detection script accuracy against install results.
Generating application description metadata.
Returning the package back to you for final confirmation.

If verification fails, you may:

Reattempt verification with a different install string.
Contact Pckgr Support to investigate complex installer behavior, following the prompt to create a Support Ticket.

7. Edit Metadata and Set Logo

After successful verification:
- Edit any metadata as required.
- Upload a logo for the application (optional but recommended).

8. Save Package

Click Save to finalize the application packaging.
The validated Custom Application is now ready for deployment from your own Custom Apps repository - these applications are private to your company, you are not adding applications to the library for other Pckgr users.

Deployment Workflow

Navigate to your App Library.
Select Add New App.
Choose Custom App as the app type.
Select your tenant and proceed with deployment.

Deployment of Custom Applications follows the same process as standard applications within Pckgr.

Updating Custom Applications

Custom Applications operate on a static update model.
Each time a new version is available:
- Upload the new installer.
- Repeat the packaging and validation process.
- Save and deploy.

Automation roadmap in development: Pckgr is considering dynamic update automation options for Custom Applications, including dynamic URL integration and API creation.

Pckgr is always looking at ways to improve this tool to ensure all our users' packaging needs can be managed from our Dashboard - please feel free to contact us with any feedback you have!

Known Limitations

Portable apps (without registry entries) are not supported.
ARM architecture currently unsupported.
Silent install string detection may occasionally require manual input.

Troubleshooting Failures

Review any error messages provided after validation or deployment failures.
If needed, provide support with:
- Application Name
- Installer file link
- Any captured error messages or screenshots.

Pckgr Support will conduct internal testing and assist in resolution.

Summary Table: Private Repository vs Custom Applications

Use Case