IntuneGet: One-Click Winget App Deployment to Microsoft Intune

TL;DR

• IntuneGet is an open-source tool by Ugur Koc that lets IT admins deploy Winget apps to Microsoft Intune with a single click.
• It covers a catalog of 10,000+ apps, handles packaging automatically, and ships pre-configured detection rules.
• v0.7.1 improves self-hosting by making Discovered Apps work in SQLite mode without Supabase, fixes Auto-update and Pin version toggles, and cleans up Docker builds.
• Deployment options include a hosted version at intuneget.com, Docker Compose, or Vercel.
• Licensed under AGPL-3.0 and free to self-host for internal use.

A note on this page: IntuneGet is an independent open-source project created and maintained by Ugur Koc. It is not built by, affiliated with, or endorsed by Navanem. This page is an editorial spotlight published by Navanem to highlight useful open-source tooling for IT professionals.

What is IntuneGet?

IntuneGet is a Next.js web application that sits between IT admins and Microsoft Intune, eliminating the tedious manual packaging workflow normally required to get a Winget application into Intune. Instead of downloading installers, running the IntuneWinAppUtil packager locally, and filling in detection rules by hand, admins browse a curated catalog of over 10,000 apps and hit deploy. The tool handles packaging via GitHub Actions and pushes the result directly to the tenant through the Intune Graph API.

What's new in v0.7.1?

Version 0.7.1 is a patch release on top of v0.7.0 with a focus on self-hosting reliability and several targeted bug fixes. The headline change is that Discovered Apps now works in SQLite mode - previously it would error when Supabase was absent; it now performs a live scan against Microsoft Graph with local catalog matching instead. Two long-standing update-management bugs are also resolved: the Auto-update and Pin version options in the bell menu now correctly apply their deployment config, whereas before only Ignore and Notify had any effect. The uploads activity list no longer imposes a 7-day cutoff and is properly scoped to the signed-in user. A locale-pinning fix stops the brief German-to-English language flip in the Uploads section. On the build side, the gt translation CLI was removed from bundled dependencies in favour of on-demand npx invocation, cutting a heavy native module and making multi-arch Docker builds faster. The multi-arch image is published to ghcr.io/ugurkocde/intuneget:0.7.1.

How does it work?

Authentication is handled through MSAL against Microsoft Entra ID, supporting multi-tenant scenarios out of the box. When an admin triggers a deployment, IntuneGet kicks off a GitHub Actions workflow on a Windows runner that downloads the app, packages it into a .intunewin file using the official IntuneWin tool, and uploads it to Intune via the Graph API - all without the admin touching a Windows machine. For air-gapped environments a local packager is available as an alternative to the cloud runner. The database layer is flexible: Supabase (cloud or self-hosted) for full feature parity, or SQLite for lightweight deployments.

Who is it for?

IntuneGet targets two main audiences. Individual IT admins managing a single tenant benefit most from the one-click catalog and automated packaging. Managed Service Providers gain additional value from MSP Mode, which allows managing multiple client tenants from one interface with batch deployments, role-based team management (Owner, Admin, Operator, Viewer), webhook integrations for Slack, Teams, and Discord, audit logging with IP and user-agent tracking, and cross-tenant reporting exportable to CSV, JSON, or PDF.

FAQ

Is IntuneGet made by Navanem?

No. IntuneGet is an open-source project created and maintained by Ugur Koc. The repository is hosted at github.com/ugurkocde/IntuneGet. Navanem has no involvement in its development and publishes this page solely as an independent editorial spotlight.

What database do I need to self-host?

You have three options: Supabase Cloud (quickest setup), self-hosted Supabase (for compliance or enterprise requirements), or SQLite (for development and small deployments). Note that some features - dashboard history, notifications, and MSP Mode - still require Supabase; SQLite support covers core deployment and, as of v0.7.1, Discovered Apps.

Does it store my app binaries or tenant credentials?

No. According to the project's documentation, IntuneGet does not store application binaries or tenant credentials. Access tokens are never persisted and expire after use. All packaging workflow callbacks are verified with HMAC-SHA256 signatures, and tenant IDs are masked in logs.

What license does IntuneGet use?

IntuneGet is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0). You may self-host it for internal business use and modify it for personal or internal purposes. If you run a modified version as a network service, the AGPL requires you to make your modifications available as open source.

Where do I get started?

The fastest path is the hosted version at intuneget.com, which requires no infrastructure. For self-hosting, the project provides a Docker Compose setup and a one-click Vercel deploy option. Full documentation, including an environment variable reference and self-hosting guide, lives in the docs/ folder of the repository.