Getting Started

Your first infrastructure package
deployed in 30 minutes.

Follow a proven 4-step journey — account setup, package your IaC, deploy to your team, and start tracking versions. No manual coordination. No scattered scripts. Just a working distribution pipeline from day one.

✓ Account → Package → Deploy → Track ✓ Free trial, no credit card ✓ Done in 30 minutes
zsh — your workspace
➜  first-stack ipm publish -p my-org/first-stack -f ./ -v 1.0.0
IPMHub Cli v0.14.0
Preparing a new package from local folder '/src/first-stack/'...
Publishing package my-org/first-stack version 1.0.0 to the hub...
Publishing version 1.0.0 for package my-org/first-stack completed successfully.

➜  my-app ipm add --package my-org/first-stack
IPMHub Cli v0.14.0
Adding package my-org/first-stack to the workspace...
Package 🛡 my-org/first-stack version 1.0.0 was added to the workspace and is synchronized.
Before you start

Pre-flight checklist.

✓
Infrastructure code ready
Bicep, Terraform, or PowerShell — have your IaC folder structure prepared before publishing.
✓
IPM CLI installed
Install on Windows via winget install ipmhub.ipm, macOS via Homebrew, or Linux via the install script.
✓
IPMHub account
Sign up at portal.ipmhub.io using GitHub or Microsoft authentication. Your organization is created during sign-up.
✓
Team members to invite
Have the email addresses of colleagues ready — you'll invite them in Step 3 so they can install and verify your package.
How it works

Set up. Publish. Deploy.
Track from day one.

01 — Account Setup
Sign up, install the CLI, authenticate
Create your IPMHub organization at portal.ipmhub.io using GitHub or Microsoft authentication. Install the IPM CLI with a single command, then authenticate so the CLI can publish and manage packages on your behalf.
➜ winget install ipmhub.ipm➜ ipm login➜ ipm accountIdentity 'Jane Doe - (My Org) (jdoe)' is detected, which is still valid for 7 hour(s) and 59 minute(s).
02 — Create Your First Package
Structure your IaC folder, define ipm.json, publish
Organise your Bicep, Terraform, or PowerShell files into a folder. Add an ipm.json manifest with your package name and metadata. Then publish version 1.0.0 — IPMHub validates, scans, and makes it available to your team immediately.
➜ ipm publish -p my-org/first-stack -f ./ -v 1.0.0Publishing version 1.0.0 for package my-org/first-stack completed successfully.
03 — Deploy & Track
Team installs in one command, you track every workspace
Team members run a single command to install your package into their workspace. Enable Tracked Workspaces to see who's running what version in real time. Verify the deployment state at any time with ipm status.
➜ ipm add --package my-org/first-stackPackage 🛡 my-org/first-stack version 1.0.0 was added to the workspace and is synchronized.

Ready to go beyond
your first package?

Unlock advanced IPMHub features — Tracked Workspaces for real-time version visibility across your entire team, nested packages to compose complex solutions from reusable building blocks, and CI/CD client secrets for fully automated pipelines.

# 14-day trial · no card · cancel anytime
➜ ipm publish -p my-org/first-stack -f ./ -v 2.0.0 --non-interactivePublishing version 2.0.0 for package my-org/first-stack completed successfully. ➜ ipm status -p my-org/first-stack└── Package my-org/first-stack └── Version 1.0.0 Hub: 🔼 New version available: 2.0.0