Software packaging
From the WinGet catalogue to a finished Intune package
AppCloud365 mirrors the Microsoft WinGet catalogue locally, searches applications, versions and installers and builds packages from them that go straight into Intune, Configuration Manager or a classic software distribution: as a PSAppDeployToolkit package, as .intunewin or as a verified original installer.
- Around 14,600 applications in the catalogue (as of August 2026)
- PSAppDeployToolkit v4
- .intunewin via the Microsoft Win32 Content Prep Tool
- SHA-256 check on every download
- User interface in English and German, more languages to follow
The products are currently available in German and English; further languages will follow soon.
How AppCloud365 works
Four steps from search to download. All images show the real application.
-
Synchronise the catalogue
A separate sync process clones the Microsoft WinGet repository and imports every manifest into a local database. Subsequent runs only process the changes since the last run, typically every few hours via Windows Task Scheduler. Removed packages are marked inactive rather than deleted.
-
Find the application
Search covers name, identifier, publisher, moniker and tags, with filters for installer type and architecture. The detail page lists every installer per version with type, architecture, scope and silent capability; the best match is preselected, and SHA-256, ProductCode and silent switches are visible at once.
-
Build the package
A three-step wizard takes vendor, name, version and architecture from the catalogue, derives install and uninstall commands from the manifest data and shows a summary with output name and commands before the build starts.
-
Download and deploy
Packages are built as background jobs in isolated work directories. The job list shows status, duration and result and offers the finished artefact for download. After a configurable retention period it is cleaned up automatically.
Four packaging options
Depending on the distribution path and the packaging team’s preferences, the same application becomes the artefact you need.
-
setup fileOriginal installer
Downloads the original file and verifies it server-side against the SHA-256 recorded in the WinGet manifest. A mismatch fails the job.
-
.zipPSADT package
PSAppDeployToolkit v4 package with the installer and a fully configured deployment script: vendor, name, version, install and uninstall commands.
-
.intunewinPSADT IntuneWin
The PSADT package, additionally wrapped with the Microsoft Win32 Content Prep Tool for Intune.
-
.intunewinNative IntuneWin
Lightweight Install.ps1/Uninstall.ps1 wrapper without PSADT for environments that do not use the toolkit. Exit codes are passed to the deployment unchanged.
For installer types without reliable manifest data, such as portable applications or ZIP archives, only the original download is available. The interface explains why in that case.
Delivery straight into the target system
Besides downloading the finished packages, we can set up a direct hand-over into your distribution system on request: packages built in AppCloud365 then land in Microsoft Intune or Configuration Manager without a manual step in between.
- Microsoft Intune and Microsoft Configuration Manager (SCCM / Endpoint Configuration Manager)
- Other systems, provided the interfaces are known or made available by you
- Set-up and scope by arrangement, as part of the managed service
What AppCloud365 deliberately does not do
A package that fails silently in deployment costs more time than one that is never built. Hence a few firm rules.
-
No invented commands
Install and uninstall commands come exclusively from manifest data and known installer families. If no reliable uninstall command exists, the wizard says so; it has to be added or explicitly confirmed as “no uninstall”.
-
No unverified download
Every installer is checked against the SHA-256 from the WinGet manifest while it is downloaded. If the hash does not match, the file is discarded and the job fails with a clear message.
-
No tool downloads by the website
PSAppDeployToolkit and IntuneWinAppUtil are obtained by a separate bootstrap from the official sources. If the tooling is missing, the affected packaging options are visibly disabled.
-
No silent success
Failed runs never produce a package. In the native wrapper only exit codes 0, 3010 and 1641 count as success; every other code is reported as a failure, unchanged.
Outlook
Microsoft Store: planned extension
PlannedThe current version works with the WinGet community catalogue (microsoft/winget-pkgs). Support for applications from the Microsoft Store is planned as an extension but is not yet part of AppCloud365. We will not name a date before the scope and the conditions are settled.
Built on PSAppDeployToolkit
The PSADT options use the official v4 template. AppCloud365 sets the session variables for vendor, name, version and architecture and inserts the install and uninstall calls at the designated markers of the script. If the expected markers are missing from the template, the build stops instead of altering the structure.
Technical basis
Web application on .NET 10 (Blazor Server) with an open architecture and data access through Entity Framework Core. Runs on Windows; the catalogue sync is a separate process scheduled with Windows Task Scheduler. Automated unit, integration and UI tests are part of the project.
Working together with OpsCloud365
AppCloud365 and OpsCloud365 are separate products with separate data. If you use both, the packages built with AppCloud365 can be offered as orderable items in the OpsCloud365 service catalogue: staff order an application, approval runs in the service desk, and provisioning uses the finished package.
OpsCloud365Offer and collaboration
No off-the-shelf price, no off-the-shelf configuration
Every enquiry starts with a conversation. We clarify your requirements for hosting, data security and scope and turn them into an offer that fits you.
All enquiries go by email or phone. A person will get back to you.
-
Individual offer instead of list price
You will not find standard prices on this website. Every offer reflects platform, data security, number of users and the level of support you want.
-
No self-registration
There is no online account to create. Access to our products is set up by arrangement, so that operations and data protection are settled from the start.
-
Demo and demo installation by arrangement
We demonstrate the products using your workflows and set up a demo installation on request. Platform and scope are agreed beforehand.
-
Configuration to fit
Roles, fields, catalogues, policies and operating parameters are tailored to your organisation, not copied from a template.
-
Operation and maintenance as a managed service
We maintain your installation on any agreed platform as a managed service: updates, monitoring, adjustments and a named contact.
See AppCloud365 in action
We show you the path from catalogue search to a package in Intune, ideally with applications from your own portfolio, and set up a demo installation by arrangement. Send us an email or give us a call.