Never miss a package release.
The Package Feed gives every organization a live URL that delivers update notifications the moment a new version is published. Subscribe in any feed reader, pipe it into Teams or Slack, or use it as an automation trigger — RSS or JSON, your choice.
You publish an update. Who actually notices?
You push a new version of a package. Your customers and internal teams should update — but they only find out if they remember to check the portal. In practice, they don't. So they keep running old versions, miss security patches, and your release notes land nowhere.
A feed URL. For every package release.
IPMHub generates a signed, scoped feed URL for your organization. Every time you publish a new package version, an entry appears in the feed with the version number, release notes, and a link back to the package. Subscribe once, stay current forever.
One feed URL. A lot of ways to use it.
Scoped, signed, and time-limited.
Feed URLs are generated from a signed Access Signature. You define the scope (all packages or a single package) and the lifetime. When the signature expires, the URL stops returning updates — no manual revocation needed. For MSPs managing multiple customers, create one signature per customer and scope it to the packages they use.
Public packages have no setup required — the feed URL is openly accessible without an Access Signature.
The feed URL contains the access signature and grants read access to the feed. Treat it as a secret — do not share it publicly or commit it to source control.
Three steps to your first feed URL.
→ Full setup guide in the docs: docs.ipmhub.io/docs/organization/feed/feed
Know the moment
something ships.
Set up your first feed URL in under five minutes. No code required.