Skip to main content



This release lays the foundation for an easy-to-use and privacy-friendly alternative to Google Analytics within the Juno ecosystem, specifically on the IC.

While the feature is fully functional, it requires real-world testing, which will be conducted on the mainnet. Consequently, it won't be immediately visible through navigation links within Juno's console. Instead, we will initiate a trial phase during which it will be deployed and tested on Juno's website ( This approach allows us to iterate and refine the solution as needed before making it broadly available, hopefully in the next version.

That's why the mission control smart contract wasm code has been updated. These changes enable mission control to manage the new canisters related to the analytics, which we've named "Orbiters".


ModuleVersionBreaking changes
Console (Backend)v0.0.7
Console (UI)v0.0.17
Mission controlv0.0.7
Orbiter 🆕v0.0.1
LibraryVersionBreaking changes
@junobuild/analytics 🆕v0.0.1
CLIVersionBreaking changes


Here is a list of changes included in this release:



  • new analytics features (not yet available through the navigation)
  • support for creation and administration (login, upgrade, etc.) of the new canisters "Orbiter"


  • bump Juno's libraries
  • bump agent-js v0.19.2

Mission control

While their features are quite distinct, an "Orbiter" shares some similarities with a "Satellite."

The mission control will manage and provide a list of these new canisters, restrict their access according to the authorization scheme, and allow the administration of their controllers. Additionally, it will facilitate communication of their statuses for the cronjobs that monitor the cycles limit.


The observatory, the canister responsible for gathering information about cycle usage, has been extended to support the new orbiter's data.


Please refer to related release for details.


Please refer to related release for details.