AI-generated profiles
Claude proposes silent install/uninstall commands, install context, detection rules, display name, publisher, description and an icon — from the installer's metadata alone.
Wrappify packages your EXE, MSI or MSP installers into Microsoft Intune .intunewin Win32 apps. Upload an installer, let AI generate the silent install commands and detection rules, build the package, and deploy straight to Intune via Microsoft Graph — in minutes, not hours.
Free to use — just bring your own LLM API key.
No installers are ever executed · Metadata-only inspection · Multi-tenant & per-tenant isolated
From deterministic metadata extraction to one-click Graph deployment — Wrappify handles the whole packaging lifecycle.
Claude proposes silent install/uninstall commands, install context, detection rules, display name, publisher, description and an icon — from the installer's metadata alone.
MSI property tables, PE VersionInfo and installer-type heuristics — Inno, NSIS, InstallShield, WiX Burn, Squirrel, MSI-wrapped EXE and the new Teams bootstrapper.
Exactly one rule per app, in priority order: MSI Product Code, registry uninstall key, file presence, or a PowerShell script for the edge cases.
Builds the .intunewin and uploads it to Intune as a Win32LobApp — content version, Azure Blob upload, commit and optional supersedence, all automated.
Re-upload a newer version and Wrappify matches it to the previous app (MSI UpgradeCode or name/publisher) and sets up Intune supersedence for you.
Attach .reg, .xml, .json or .ini config files and Wrappify generates a reviewable PowerShell wrapper that runs the installer, then applies your settings at the right place on the endpoint.
Tell the localization composer which UI languages you need; Wrappify builds a reviewable plan — recipe-first, AI-fallback — then fetches the language packs, bundles them and rewrites the install command.
Optional virus scanning — ClamAV, or a VirusTotal hash lookup where only the SHA-256 leaves the host — checks every upload before it's stored. A confirmed detection hard-blocks the file.
Customer tenants onboard via Entra ID admin consent. Every upload, profile, build and LLM cache is strictly isolated per tenant — nothing leaks across customers.
Publish pre-built .intunewin packages once and let any tenant import and deploy them — with automatic supersedence and per-architecture variants.
A guided workflow that keeps you in control — review and edit every proposal before it ships.
Drop an .exe, .msi, .msp — or a .zip of a whole installer folder. Wrappify picks the right setup file automatically.
Metadata is extracted deterministically: publisher, product, version, MSI ProductCode, architecture and installer type.
AI proposes install commands, detection rules, requirements and display metadata — tuned by field-learned lessons.
Edit anything in the UI. Your corrections are cached, so re-uploading the same file returns your version.
Wrappify builds the .intunewin and deploys it to Intune via Microsoft Graph — with optional assignment groups.
Wrappify is free to use. You only bring your own LLM API key (Anthropic, OpenAI, xAI Grok or Google Gemini) and set it on the Settings page — you pay only your provider's usage directly, nothing to Wrappify.
Wrappify accepts .exe, .msi and .msp installers, plus a .zip of a whole installer folder. It can also create one Intune app per CPU architecture from a multi-architecture ZIP, so devices self-select the right build.
No. Wrappify reads metadata only — PE VersionInfo, MSI property tables and installer-type heuristics. Uploaded installers are never executed, not even for testing.
Wrappify builds the .intunewin with Microsoft's IntuneWinAppUtil (or the cross-platform ContentPrep module) and uploads it through the Microsoft Graph API as a Win32LobApp — content version, Azure Blob upload, commit and optional supersedence, all handled for you.
Exactly one rule per app, chosen in priority order: MSI Product Code, registry uninstall key with version comparison, file presence, or a custom PowerShell detection script for the cases the first three don't cover.
Yes. Attach config or registry companions (.reg, .xml, .json, .cfg, .ini) and Wrappify generates a reviewable PowerShell install wrapper that runs the original installer and then applies those files in the right location on the endpoint. You edit and confirm the script before anything is staged, and a one-click revert restores the original command.
Yes. The localization composer lets you describe the languages you need; Wrappify produces a reviewable plan — using a deterministic recipe where one exists (e.g. Firefox/Thunderbird language packs) and falling back to AI otherwise — then fetches the language artifacts, bundles them and rewrites the install command.
Optionally, yes. Operators can enable virus scanning — ClamAV, or a VirusTotal hash lookup where only the SHA-256 leaves the host. A confirmed detection blocks the upload before the file is ever stored, inspected or built.
Yes. Tenants onboard through Microsoft Entra ID admin consent, and tenant isolation is enforced at the database layer. Uploads, profiles, builds and LLM caches are scoped per tenant and never shared — even for identical files.
The default and recommended provider is Anthropic Claude. Tenants can switch to OpenAI, xAI Grok or Google Gemini with their own API key from the Settings page.
Free to use — bring your own LLM API key. Upload an installer and let Wrappify do the packaging, detection and deployment heavy lifting.
Open Wrappify