Uploading and releasing packages
Creating & Managing your projects
The very first step to activate a project for streaming is to upload and release an Unreal Engine packaged app!
To do so, you have to navigate to the Packages page.
Uploading packages
After preparing the package by enabling the Pixel Streaming plugin, you can start the uploading process.
Drag + drop or browse Once inside the 'Packages' section, Drag and drop your zipped package into the upload box (manual browsing to your package is also possible). The upload will start immediately.
Auto-release This option enables uploaded packages to be automatically released after a successful upload.ion enables the uploaded packages to automaticaly being released after a succesfull upload.
Upload servers Thor & Loki This option allows you to choose between two different locations to upload your packages. - Thor (EU) - Loki (USA)
Now that you know the basics, start by uploading your first project. Simply drag and drop your zipped package in the Drag + drop or browse section for the upload to start.
Uploading in progress!
Important notice Refreshing or leaving the Packages page will interupt the upload. Arcware Cloud has a resume upload function in place to resume the upload from where it stopped.
How to Resume Upload
After the upload is finished the package will pass through the Virus Scanner and the Gauging phase.
Virus Scanner - In this phase the application will be unzipped and scanned for threats.
Gauging - Here the system checks if the pixel streaming plugin is enabled and if the package is starting properly without any issues.
Releasing packages
After the package has succesfully passed through the upload pipeline, we can click the release button with the Rocket symbol.
After pressing the release button, it will still take some time to download your package to our system and staged for distribution. It depends on the package size. The Arcware Cloud template project with 500MB, takes around 5 mins to be released.
Enabling projects
Now that we have uploaded your first package to your project, you will be able to 'Enable' your project, to allow it to be streamed.
After enabling the project the released project will start the rolling out phase, in this step the package is being distributed to the GPU servers for streaming.
Lastly, when the upload status is in Active state, you are ready to stream the project
Upload Cleanup Rules !
🧹 Upload Cleanup Rules (Automatic Deletion Policy)
To keep storage clean and predictable, old uploads are automatically deleted based on these simple rules:
Released uploads are never deleted. Any upload that’s currently marked as Released is permanently kept — even if the tenant is unsubscribed or the project is disabled. You can always return to us and enable your project(s) and continue streaming with your latest released package(s).
Keep the most recent uploads. For each project, the system keeps up to 5 of the most recent uploads (based on their Last Update time) - including the released package.
Delete uploads older than 90 days. Regardless of how many uploads a project has, anything older than 90 days is automatically marked for deletion — except released uploads, which are always kept.
Keep a few recent failed uploads. The system keeps up to 3 failed uploads from the last 7 days. These are kept in addition to the uploads mentioned above, so you can review recent failures and for debugging.
⚠️ Important: If a project is deleted by the client, all uploads belonging to that project are permanently removed immediately. This is handled by a separate deletion process and is not part of the regular cleanup cycle.
You nailed it! Next we will cover the Resume package upload feature.
Last updated