Can I submit apps to WinGet, and why are updates sometimes delayed?

There is also a separate option for organizations: WinGet supports custom REST-based sources, so a company can host its own repository if it follows the required source API. That is different from contributing an application to the public catalog and can be useful for approved internal software.

Yes. WinGet accepts community contributions through package manifests. A manifest describes details such as the application name, version, installer download URL, installer type, and silent-install options. The installer needs to be publicly downloadable and support unattended installation, and the submission is reviewed and tested before it is accepted. You can contribute manifests even if you are not the software's developer.

WinGet is mainly a catalog and installer source, not a service that automatically tracks every vendor release in real time. Paid application-management products generally have staff who monitor vendors, package releases, and perform additional testing, so their updates may arrive sooner. WinGet is closer to a community-maintained package repository, with some validation but no guarantee of immediate updates.

New versions can take a while to appear because WinGet's public catalog is maintained by Microsoft and community contributors. Someone has to notice the release, update the manifest, submit it, and get it reviewed. The application's built-in updater can therefore find a release before the WinGet catalog has been updated. If you notice a missing version, you can submit the updated manifest yourself.