For the complete documentation index, see llms.txt. This page is also available as Markdown.

CatalyX Package Manager

CatalyX Package Manager (CPM) is a web-based package management platform for the Canton Network, designed to streamline the application distribution process with enterprise-grade reliability and control. CPM replaces ad-hoc file sharing with a standardised approach, ensuring Canton Network participants stay up to date with the latest application versions and reduce the operational risk that comes with deploying across a distributed network.


CatalyX Package Manager Overview

How It Works

CatalyX Package Manager provides an intuitive, user-friendly console where Canton Network participants can discover, distribute, and download application packages.

  1. Discover

Explore packages published by application providers on the Canton Network.

  1. Distribute

Publish your own packages, control who has access, and notify users when new versions are released.

  1. Download

Easily download and deploy application packages to your Canton node.

Key Features
  1. Streamlined Package Distribution Use CPM's central registry for publishing, distributing, and downloading application packages with full lifecycle visibility.

  2. Version & Lifecycle Management Manage multiple versions of a package, track updates, and guide safe upgrades using clear version history.

  3. Private Access Controls Support institutional requirements through package access controls, verified publisher credentials, deprecation warnings, and auditable access history.

  4. Managed Artifactory Hosting Host application artifacts directly within the CPM platform using a managed, highly available artifactory, no external repositories needed.

  5. Notifications and Subscriptions Notify your clients through email when new package versions are uploaded to CPM.

Security & Privacy

CPM is designed so that your credentials never leave your own infrastructure. The platform runs in your browser and communicates directly with your Canton node — IntellectEU's servers never receive or store your authentication tokens or node credentials. There are no user accounts on the CPM side; authentication is handled entirely by your organisation's own identity provider.

Learn More

Get Started

Explore the documentation and discover how you can use CatalyX Package Manager to streamline your package management lifecycle.


Frequently Asked Questions

Why do I need to install a DAR file on my Canton node to use CPM?

CPM uses the Canton ledger as its primary record of state, rather than a centralised database. Installing the CPM DAR file on your validator node lets every core platform action, such as registering a package, granting access to it, or approving a publish request, be recorded as a smart contract transaction on the ledger. This makes each action visible and independently verifiable by every relevant party: for example, the party ID shown as a package's publisher can always be checked on-ledger to confirm it is indeed the party ID that published that package.

How do I know a published package hasn't been tampered with, even if the registry itself were compromised?

Every package registered on CPM has its cryptographic hash recorded directly in its DAML contract on the Canton ledger. Before deploying a package, you can compute the hash of the DAR file you actually retrieve and compare it against the value recorded on-ledger. If the two match, you have cryptographic proof that the file is exactly what the publisher registered, independent of CPM's own infrastructure.

How does authentication work in CPM?

CPM is designed so that your credentials never leave your own infrastructure. The platform runs entirely in your browser and communicates directly with your own Canton node, so IntellectEU's servers never receive or store your authentication tokens or node credentials. There are no user accounts on the CPM side; authentication is handled entirely by your organisation's own identity provider.

What's the difference between a public and a private package?

When publishing a package, you choose its access model. Public packages can be downloaded by any registered CPM user. Private packages require a user to submit an access request, which the publisher can approve, deny, or revoke at any time from My Library.

Where are package DAR files actually hosted?

You choose the hosting when you publish a package: either upload the DAR file directly to CPM's managed artifactory, or host it yourself and provide an external artifactory link (public packages only).

How will I know when a package I use gets updated?

You're automatically subscribed to update notifications whenever you download a package or click its favourite ("star") icon. When the publisher releases a new version, you receive an email notification, and the package's full version history remains available on its detail page. Manage all your subscriptions from the Notifications & Subscriptions tab.


Last updated

Was this helpful?