What platforms are supported by Applivery Custom Build Platforms?

Applivery Custom Build Platforms supports any platform, including game consoles (PlayStation, Xbox, Nintendo Switch), alternative storefronts, and web runtimes, in addition to Android, iOS, macOS, and Windows.

What file formats are supported for Custom Platforms?

Custom Platforms support .zip and .tar.gz as universal container formats. Platform-specific extensions like .pkg (PS4/PS5), .nsp (Switch), and others are also supported.

What metadata is required when uploading a Custom Platform build?

When uploading a Custom Platform build, you must manually provide the `packageName` and `packageVersion`. `packageIcon` is optional.

How do I enable Custom Build Platforms in Applivery?

Custom Build Platforms are not enabled by default. Contact Applivery Support at support@applivery.com to enable the feature for your workspace.

Can I use the Applivery Upload API with Custom Platforms?

Yes, Custom Platforms are fully supported through the Applivery Upload API. Specify the custom platform identifier in your request.

How do I upload a build for a Custom Platform?

Upload your build file, select the target Custom Platform, and provide the required metadata (packageName, packageVersion) in the Applivery dashboard.

Custom Build Platforms

Q: Where do I manage all my builds, including Custom Platforms?

All builds, regardless of platform, are managed in the same Applivery workspace and accessible through the same Upload API.

By default, Applivery natively supports Android, iOS, macOS, and Windows Builds. Custom Build Platforms extends this to cover any platform your team distributes to — including game consoles, alternative storefronts, web runtimes, and archive formats — all managed through the same Applivery workflow.

This is particularly useful for game studios, cross-platform development teams, and organisations distributing to Devices or environments outside the four major mobile and desktop operating systems.

Key capabilities

Extended platform support — upload and distribute Builds for platforms beyond iOS, Android, macOS, and Windows, including PlayStation, Xbox, Nintendo Switch, Steam, and more.

Manual metadata configuration — unlike native platforms, where Applivery extracts metadata automatically from the Build file, Custom Platforms require you to provide packageName, packageVersion, and optionally packageIcon manually at upload time.

Unified management — all Builds, regardless of platform, are managed in the same Applivery Workspace and accessible through the same Upload API, keeping your distribution workflow consistent across every target.

Raw file distribution — Custom Platforms distribute build files in their original format without automated processing, giving you full control over what gets delivered.

Supported platforms and file extensions

Every custom platform supports .zip and .tar.gz as universal container formats. Platform-specific supported extensions are listed below:

Platform identifier	Supported extensions
`android`	`.apk`, `.aab`
`amazon`	`.apk`, `.aab`
`flexion`	`.apk`, `.aab`
`ios`	`.ipa`
`macos`	`.pkg`, `.dmg`
`macos-archive`	`.zip`, `.tar.gz`
`windows`	`.msi`, `.exe`, `.msix`, `.appx`, `.msixbundle`, `.appxbundle`
`windows-archive`	`.zip`, `.tar.gz`
`ps4`	`.pkg`
`ps5`	`.pkg`
`switch`	`.nsp`
`xbox-one`	`.zip`, `.tar.gz`
`xbox-series`	`.zip`, `.tar.gz`
`steam`	`.zip`, `.tar.gz`
`steam-mac`	`.zip`, `.tar.gz`
`epic`	`.zip`, `.tar.gz`
`epic-mac`	`.zip`, `.tar.gz`
`web`	`.unityweb`, `.wasm`, `.js`, `.html`

Note

All platforms also accept .zip and .tar.gz as generic archive formats, regardless of the extensions listed above.

How to upload a Build for a Custom Platform

Upload your file

Follow the standard build upload process described in How to upload your first build. You can upload via the Dashboard or the Upload API.

If you are uploading a .zip or .tar.gz file that does not correspond to a native platform, Applivery will prompt you to select the target Custom Platform in the next step.

Select the Custom Platform

After uploading, select the platform the Build is intended for from the Custom Platform selector. This tells Applivery how to categorise and display the Build within your Workspace.

Provide build metadata

Because Custom Platforms do not undergo automated metadata extraction, you must supply the following information manually:

Field	Required	Description
`packageName`	Yes	The unique identifier for your App or build (e.g. `com.studio.mygame`).
`packageVersion`	Yes	The version string for this Build (e.g. `1.4.2`).
`packageIcon`	No	An icon image to represent the Build in the Applivery interface.

Once submitted, the Build will appear in your App's Builds section alongside any other Builds for that project.

How to enable Custom Platforms

Custom Build Platforms are not enabled by default and must be activated at the Workspace level.

To view your currently enabled platforms, go to the Applivery Dashboard, navigate to the Settings (1) section, and select Build Platforms (2) from the left-hand menu.

Note

To enable Custom Platforms for your Workspace, contact the Applivery Support team at [email protected].
We will enable the feature and help you configure the specific platforms you need.

Using the Upload API with Custom Platforms

Custom Platforms are fully supported through the Applivery Upload API, allowing you to integrate build uploads into your CI/CD pipeline just as you would for native platforms. The same endpoint is used — you simply specify the custom platform identifier in your request.

See the Upload API documentation for full details on request format, authentication, and required parameters, including packageName and packageVersion for custom platform Builds.