Infrastructure Package Manager
The infrastructure layer your MSP practice actually needs.
Package and distribute Bicep, Terraform, and PowerShell across your team, your clients, and your clients' own engineers — with full visibility into what's running where.
✓ No credit card required
✓ Setup in minutes
✓ Cancel anytime
➜ client-a ipm add --package acme-msp/landing-zone --version 2.0.3 IPMHub Cli v0.14.0 Adding package acme-msp/landing-zone to the workspace... Package 🛡 acme-msp/landing-zone version 2.0.3 was added to the workspace and is synchronized. ➜ client-a ipm status -p acme-msp/landing-zone └── Package acme-msp/landing-zone └── Version 2.0.3 Hub: 🔼 New version available: 2.1.0 Local: ✔ In Sync
75%
Faster feature development across client portfolios
4hr → 1hr
Average upgrade time per client environment
100%
Visibility into which version is running at every customer
0
Shared Git repos or credentials needed to share packages
Three ways to use IPMHub
One platform. Three distinct problems solved.
Whether you're an MSP sharing code with customers, managing a client fleet, or a platform team distributing to internal engineers — IPMHub handles the distribution and visibility layer.
New
Co-Managed Infrastructure
Let customers deploy their own Azure resources using your vetted packages. You control what they get access to and track every workspace, so you always know what's running where.
1 cmd
Customer gets all packages
Live
Workspace visibility
For MSPs
MSP Fleet Management
Manage infrastructure packages across 50+ client environments from one place. Version-pin individual clients, roll back in under a minute, and prove compliance without repo archaeology.
75%
Faster feature dev
<1 min
Per-client rollback
For Enterprise
Enterprise Cloud Center of Excellence
Distribute approved IaC patterns to 50+ internal teams. Self-service infrastructure with built-in guardrails. Track which teams are on which versions and surface drift before it breaks anything.
90%
Fewer support tickets
3×
Deploy frequency
How IPMHub works
Publish once. Distribute anywhere.
Track everything.
01 — Build
Package your infrastructure
Bundle Bicep, Terraform, PowerShell, and pipeline definitions into a single versioned artifact. Language-agnostic — everything in one package.
➜ ipm publish -p acme-msp/landing-zone -f ./ -v 2.1.0Publishing version 2.1.0 for package acme-msp/landing-zone completed successfully.
02 — Distribute
Teams and customers pull what they need
Internal teams, client environments, and co-managed customers all use the same IPM CLI. One command gets the right version with the right authorization.
➜ ipm add --package acme-msp/landing-zonePackage 🛡 acme-msp/landing-zone version 2.1.0 was added to the workspace and is synchronized.
03 — Track
See what's running where, always
Tracked Workspaces give you a live view of every environment. Which version, last sync, full revision history. No more guessing what's deployed.
➜ ipm status -p acme-msp/landing-zone└── Version 2.0.3 Hub: 🔼 New version available: 2.1.0
What goes in a single IPM package
[Complete Infrastructure Solution] ├── Infrastructure Code (Bicep / Terraform) ├── CI/CD Pipelines (Azure DevOps / GitHub Actions) ├── Deployment Scripts (PowerShell / Bash) ├── Configuration Files ├── Documentation & Examples ├── Nested Dependencies (Optional) └── Everything else that makes the solution work
Platform capabilities
Built for real infrastructure teams,
not just developers.
Language-agnostic packages
Bicep, Terraform, PowerShell, Python, YAML — all in one versioned artifact. No more juggling multiple registries for one solution.
Tracked Workspaces
Real-time visibility into what's deployed where. Every sync creates a revision. Know which version is running before your customer calls you.
Cross-org package sharing
Share specific packages with customer organizations. They authenticate with their own credentials — you define the scope and revoke it when the contract ends.
Malware scanning
Every package version is scanned before it's available for download. Customers get code you can stand behind. The audit trail proves it.
Nested dependencies
Packages can depend on other packages. IPMHub resolves and downloads the full dependency tree automatically — no manual wiring.
No vendor lock-in
Packages download directly into your Git repo. Your infrastructure runs without IPMHub being online. You own the code, not us.
In production
Used by MSPs managing
real client portfolios.
InSpark · Dutch Azure MSP
Faster onboarding, full visibility
InSpark uses IPMHub to distribute verified infrastructure packages to clients and track deployment state across their entire portfolio.
75%
Faster client onboarding
4×
Faster per-client upgrades
"We can now onboard new clients significantly faster. They get working infrastructure from day one, built on code we've already tested and verified."
— Technical Lead, InSpark
Major Dutch Azure MSP · 50+ clients
50 clients, one codebase
Separated Bicep and PowerShell into versioned IPM packages. Individual clients can be pinned or rolled back without touching the others.
<1 min
Per-client rollback
1 day
Audit prep (was 2 weeks)
"By separating Bicep and PowerShell into IPM packages, we iterate 75% faster on our monitoring solution and can roll back an individual client in under a minute."
— Technical Lead, Major Dutch Azure MSP
Common questions
Straightforward answers.
How is this different from storing files in Git?
Git stores your files. IPMHub tracks what's actually running across all your environments and customers. Git shows history — IPMHub shows you which version is live right now, where, and what needs updating.
What happens to packages if IPMHub goes offline?
Packages download directly into your repository. Your deployments have no runtime dependency on IPMHub. The code is yours and it runs without us.
How does customer access work for co-managed infrastructure?
You create a relationship with the customer's IPMHub organization and define which packages they get access to. They authenticate with their own credentials. You control the scope and can revoke access when the contract ends.
Does it work with Azure DevOps and GitHub Actions?
Yes. IPM integrates natively with Azure DevOps and GitHub Actions and all other major CI/CD platforms. You can reference IPMHub packages in pipelines and package your pipeline definitions alongside your infrastructure code.
Ready to distribute infrastructure
like software packages?
Free trial, no credit card, full access. Set up your first package in under 30 minutes — we'll help if you need it.
➜ winget install ipmhub.ipm➜ ipm login ➜ ipm publish -p acme-msp/landing-zone -f ./ -v 2.1.0Publishing version 2.1.0 for package acme-msp/landing-zone completed successfully.