chore: merge main

Signed-off-by: David Dal Busco <[email protected]>

Author: peterpeterparker

.llms-snapshots/llms-full.txt

@@ -0,0 +1,93 @@
+---
+slug: architecture-changes-for-better-developer-experience
+title: Architecture Changes for a Better Developer Experience
+authors: [peterpeterparker]
+tags: [architecture, dx, platform]
+date: 2026-01-08
+---
+
+Happy New Year 🥳
+
+We're kicking off 2026 with a major [release](https://github.com/junobuild/juno/releases/tag/v0.0.63) that ships significant changes in the architecture and design of the Juno Console with a single goal: making the DX more straightforward and comprehensive.
+
+---
+
+## Mission Control and Monitoring merged
+
+Mission Control was originally designed as a dedicated control center for developers — a place to create and manage projects (Satellites) and analytics (Orbiters). Over time, it was also extended to include Monitoring.
+
+The original idea was simple: the Console would only know a developer's identity and their Mission Control ID — nothing else.
+
+While this approach had advantages, it also introduced significant drawbacks.
+
+On every new sign-up, the Console had to automatically create a Mission Control. This meant that when a developer signed in and created their first (free) project, Juno had to provision **two containers instead of one**, increasing infrastructure costs.
+
+It also led to a confusing user experience. Mission Control could not be hidden from the UI because modules must be provisioned with resources (cycles) to avoid being decommissioned. As a result, it was always visible, and many developers were unsure what Mission Control was or why it existed.
+
+For these reasons, Mission Control and Monitoring have now been merged:
+
+- A Mission Control is created **only when a developer explicitly enables Monitoring**
+- Monitoring is now treated as a dedicated microservice
+
+This architectural change brings clear benefits:
+
+- **For developers:** a clearer, more straightforward experience and simpler long-term maintenance
+- **For Juno:** acquisition costs for new developers are effectively cut in half
+
+There are a few trade-offs to note:
+
+- The Juno Console now keeps track of all containers created by developers (Satellites, Orbiters, and Mission Controls), whereas previously it only knew the Mission Control ID.
+- When Monitoring is enabled, module metadata must be duplicated inside the Mission Control so it knows what to monitor. This introduces a risk of inconsistencies if a bug causes a mismatch between the Console and Monitoring data. To mitigate this, a Console feature is planned to compare and verify this information.
+
+---
+
+## Deprecate ICP, use only Cycles
+
+Over the past year, I've been refining both the platform and its communication to reinforce Juno's vision: a platform to build, deploy, and run applications in WASM containers, with ownership and zero DevOps.
+
+As part of this effort, I've aimed to remove all blockchain and crypto-slangs.
+
+While merging Mission Control and Monitoring, a new wallet ID - derived from the developer's sign-in - had to be introduced.
+
+During this work, it became really clear again that the onboarding for new developers was just confusing:
+
+> Why do I need ICP to get cycles?
+
+Since this release already introduced breaking changes, it felt like the right moment to simplify the model further.
+
+As a result, **ICP is now deprecated in favor of using cycles only**.
+
+This significantly simplifies the user journey:
+
+- You start using Juno for free
+- You learn about cycles as the resource that powers your containers and services
+- When you need more resources or want to spin up additional modules, you acquire cycles
+
+To support this, the primary call to action for acquiring cycles now points to [cycle.express](https://cycle.express), which allows developers to convert dollars directly into cycles. Third-party wallets like [OISY](https://oisy.com) remain supported, but are now positioned as secondary options for users already familiar with them.
+
+Together with the other changes in this release, this should make both the developer experience and the mental model of how Juno works much more approachable.
+
+![](cycles-everywhere.png)
+
+---
+
+## Price increase
+
+Previously, creating new Satellites or Orbiters cost 0.4 ICP. In practice, this was undervalued: each module is provisioned with 1.5 T cycles, while 0.4 ICP corresponds to roughly 0.93 T cycles—effectively a significant bonus.
+
+Going forward:
+
+- Additional Satellites and Orbiters cost 3 T cycles (roughly $4).
+- Enabling Monitoring (which spins up a Mission Control) requires the same fee.
+
+:::note
+
+See the [Pricing](/docs/pricing) documentation for more details.
+
+:::
+
+---
+
+I believe these changes represent a significant step forward in making Juno more accessible and easier to understand. Whether you're just getting started or have been with us for a while, I hope these improvements make your development experience that much better.
+
+To infinity and beyond<br />David

blog/2026-01-08-architecture-changes-for-better-developer-experience/cycles-everywhere.png

@@ -81,7 +81,7 @@ You have the capability to delete all collected data within your Analytics at an
 
 ## How does it work?
 
-To gather analytics for your dapps, you need to create an [orbiter]. Creating an Orbiter requires Cycles, and its price is defined in the [transaction costs](../../pricing#transaction-costs).
+To gather analytics for your dapps, you need to create a module called [orbiter]. Creating an Orbiter requires Cycles, and its price is defined in the [transaction costs](../../pricing#transaction-costs).
 
 Each Orbiter is used to collect analytics for one or multiple [satellites].
 

blog/2026-01-08-architecture-changes-for-better-developer-experience/index.md

@@ -2,32 +2,43 @@
 description: "A quick guide to creating a Satellite on Juno in production — the container that powers your app."
 keywords:
   [
-    create a Satellite,
+    create a satellite,
     deploy with Juno,
     Juno Satellite,
     Juno container,
-    Internet Identity,
     Juno production guide,
     Juno app deployment,
-    launch Satellite,
+    launch satellite,
     Juno hosting
   ]
 ---
 
 # Create a Satellite
 
-When you're ready to deploy your project to production, you'll need to create a [satellite].
+When you're ready to deploy your project to production, you'll need to create a [Satellite].
 
-1. To get started, sign-in to the Juno [console](https://console.juno.build). If you are a new developer on Juno and the Internet Computer, you may be prompted to create your first anonymous [Internet Identity].
-2. Click **Launch a new Satellite**.
+1. To get started, sign-in to the Juno [Console](https://console.juno.build).
+2. Click **Launch your first Satellite**.
 3. Enter a name for your Satellite (note: this is for display purposes only and does not need to be unique).
-4. Confirm with **Create a Satellite.**
-5. The platform will then create your Satellite and provision its resources.
-6. Once the process is complete, click **Continue** to access the overview page.
+4. Select whether you're deploying a **Website** or **Application**.
+5. Confirm with **Create a Satellite.**
+6. The platform will then create your Satellite and provision its resources.
+7. Once the process is complete, click **Continue** to access the service page.
 
 🎉 You’re all set! You can now deploy your frontend app, static website, or publish your serverless functions to production.
 
 ➡️ Continue with the [deployment](/docs/category/deployment) guides to take the next step.
 
+---
+
+:::note
+
+Choose **Website** if you're deploying a static site, blog, portfolio, etc.
+
+Choose **Application** if your project needs user sign-in, data management, or serverless functions.
+
+You can change this later in your Satellite "Hosting" settings.
+
+:::
+
 [satellite]: terminology.mdx#satellite
-[Internet Identity]: terminology.mdx#internet-identity

docs/build/analytics/index.md

@@ -37,7 +37,7 @@ For reproducibility, developers can run the official Docker build for Juno and i
 
 ### What happens if Juno disappears?
 
-In the unlikely event of Juno's disappearance, you, as the sole controller of your [mission control] and [satellites], would retain full control over your creations. They would continue to function independently without any reliance on Juno.
+In the unlikely event of Juno's disappearance, you retain full control over your creations. They would continue to function independently without any reliance on Juno.
 
 ### Can I just deploy my website on the Internet Computer?
 
@@ -51,7 +51,7 @@ No, Juno is an independent project. In 2024, we received a [Developer Grant](htt
 
 No, Juno does not exert any control over developers' work. Juno is designed to provide developers with true control and autonomy over their projects.
 
-Developers have full ownership and control over their [mission control], [satellites], and the applications they build on the platform.
+Developers have full ownership and control over their modules, and the applications they build on the platform.
 
 Juno's philosophy aligns with the principles of Web3, empowering developers with transparency, decentralization, and the freedom to create and innovate without external interference.
 

docs/create-a-satellite.mdx

@@ -14,7 +14,7 @@ keywords:
 
 # Monitoring
 
-Keeping your modules running smoothly is essential for any application. The monitoring feature ensures your [Mission Control] (your wallet) and modules — Satellites and Orbiter (Analytics) — stay operational by automatically refilling cycles when they run low. This helps prevent unexpected downtime, allowing you to focus on building and growing your product without worrying about cycle balances.
+Keeping your modules running smoothly is essential for any application. The monitoring feature ensures your modules — Satellites and Orbiter (Analytics) — stay operational by automatically refilling cycles when they run low. This helps prevent unexpected downtime, allowing you to focus on building and growing your product without worrying about cycle balances.
 
 ![A screenshot of the monitoring overview within Juno Console](../img/monitoring/monitoring-dashboard.webp)
 
@@ -23,23 +23,23 @@ Keeping your modules running smoothly is essential for any application. The moni
 ## Features
 
 - **Cycle refilling**: Monitored modules are automatically topped up when their balance falls below what's needed to stay active.
-- **Self-Monitoring**: Your Mission Control ensures that both your wallet and modules maintain sufficient cycles, with full control remaining in your hands at all times.
+- **Self-Monitoring**: The monitoring monitors itself to maintain sufficient cycles, with full control remaining in your hands at all times.
 - **Hourly Checks**: The system evaluates balances once an hour.
 - **Automatic ICP Conversion**: Can mint new cycles from the ICP in your wallet, ensuring your modules stay adequately funded.
 
 ---
 
 ## Why Enable Monitoring?
 
-When a smart contract runs out of [cycles] on the [Internet Computer](https://internetcomputer.org), it stops functioning, which can disrupt your application or service. Enabling monitoring provides peace of mind by automating the management of cycles, ensuring your modules are always ready to perform. It also saves a little time by eliminating the need for manual top-ups.
+When a container runs out of [cycles] on the [Internet Computer](https://internetcomputer.org), it stops functioning, which can disrupt your application or service. Enabling monitoring provides peace of mind by automating the management of cycles, ensuring your modules are always ready to perform. It also saves a little time by eliminating the need for manual top-ups.
 
-It's important to note that if your wallet or a module run out of cycles, they will enter a grace period. During this time, the module stops working but can still be restored. If no action is taken, the module eventually gets deleted, resulting in the permanent loss of its data and functionality.
+It's important to note that if your modules run out of cycles, they will enter a grace period. During this time, the module stops working but can still be restored. If no action is taken, the module eventually gets deleted, resulting in the permanent loss of its data and functionality.
 
 ---
 
 ## How does it work?
 
-Monitoring runs hourly within your Mission Control, which acts as the central hub for managing all monitored modules. The process follows these steps:
+Monitoring runs hourly within a dedicated service called Mission Control, which acts as the central hub for managing all monitored modules. The process follows these steps:
 
 ---
 
@@ -130,9 +130,14 @@ In the case of failed attempts (e.g., when Mission Control or a module could not
 
 ## Configuration
 
-To enable monitoring, go to the [Monitoring Section](https://console.juno.build/monitoring) in the Juno Console. Start the wizard by clicking **Enable Auto-Refill** and follow the prompts to select the modules you want to monitor, choose a pre-defined strategy or create a custom one, and enable the feature.
+To enable monitoring, go to the [Monitoring Section](https://console.juno.build/monitoring) in the Juno Console. Start the wizard by clicking **Get started** and follow the prompts to:
 
-The wizard simplifies the setup process, making it easy to configure monitoring according to your needs.
+- Create the Mission Control service
+- Select the modules you want to monitor
+- Choose a pre-defined strategy or create a custom one
+- Enable the feature
+
+The wizard guides you through the setup process, making it easy to configure monitoring according to your needs.
 
 [Analytics]: ../build/analytics/index.md
 [Satellites]: ../terminology.mdx#satellite

docs/faq.md

@@ -4,14 +4,12 @@ description: Learn how to manage access keys in Juno, their roles, and how to ge
 
 # Access Keys
 
-Access keys play a crucial role in granting permissions to Mission Controls, Satellites or Analytics within Juno.
+Access keys play a crucial role in granting permissions to Mission Controls, Satellites or Orbiters within Juno.
 
-When you sign in to Juno's [Console] using [Internet Identity](https://internetcomputer.org/internet-identity), you — and no one else (including not Juno) — become the owner of your [mission control]. This information is then sent back to your browser, where you can manage your modules.
+When you sign in to Juno's [Console] (for example, with Internet Identity) and create modules, you — and no one else, not even Juno — become their owner.
 
 ![Juno's console flow](../img/console.png)
 
-When you create a [satellite], you and your Mission Control become its owners. Per extension, you — and no one else (including not Juno) — own your satellite.
-
 :::note
 
 - What was previously referred to as _controllers_ in earlier versions of the documentation is now called _administrative access keys_. The concept remains the same — only the terminology has been updated for clarity and consistency.
@@ -31,7 +29,7 @@ Each access key is assigned a **role** that defines what it can do:
 | **Write**       | Editor        | ✅         | ✅               | ✅                     | ❌                      |
 | **Submit**      | Submitter     | ✅         | ❌               | ❌                     | ❌                      |
 
-An **administrator** can perform tasks such as configuring or deploying an app, topping up a Mission Control or satellite, creating a new collection in the [datastore](../build/datastore/index.mdx) or [storage](../build/storage/index.mdx), or configuring a custom domain in the [hosting](../build/hosting/index.md).
+An **administrator** can perform tasks such as configuring or deploying an app, topping up a module, creating a new collection in the [datastore](../build/datastore/index.mdx) or [storage](../build/storage/index.mdx), or configuring a custom domain in the [hosting](../build/hosting/index.md).
 
 An **editor** can publish new serverless function versions to a Satellite’s CDN, deploy your frontend application, and read data from a collection. However, it cannot directly upgrade a Satellite or start/stop a module.
 
@@ -101,7 +99,7 @@ When you run the command, the CLI checks if an access key is already present on
 
 ### Generate a new access key
 
-To **generate a new access key** and attach it to your desired Mission Controls and Satellites, you can run:
+To **generate a new access key** and attach it to your desired module, you can run:
 
 ```bash
 juno login

docs/management/monitoring.md

@@ -51,10 +51,6 @@ Juno provides supporting services to manage your projects, while keeping everyth
 
 The Console is a platform for managing your projects. It runs as its own container, combining a user interface with orchestration logic.
 
-It only holds one piece of data: a keypair linking each developer's anonymous ID to their Mission Control ID.
-
-When you sign in, the Console returns your Mission Control ID. From there, all project management happens under your control. The Console does not have access to your apps, your data, or your infrastructure.
-
 It provides services such as:
 
 - Creating, upgrading, and deleting Satellites.
@@ -91,13 +87,7 @@ While it functions as a CDN, technically it's not a traditional content delivery
 
 ## Developer-Owned Spaces
 
-### Mission Control
-
-Mission Control is your personal management container. It tracks your Satellites and Orbiters, and it acts as your wallet.
-
-You use it for example to spin up new containers or provide [cycles](../terminology.mdx#cycles) to keep your modules running. It serves as your central hub for managing projects and resources.
-
-Mission Control belongs to you. No one else can access it — not Juno, not the Console, not any other service.
+Juno's architecture is built on a microservices approach, where each component runs independently as its own WASM container, giving you modular control over your infrastructure.
 
 ### Satellites
 
@@ -113,6 +103,12 @@ Satellites are your applications. Each one is a self-contained unit that bundles
 
 Orbiters provide analytics — a decentralized alternative to services like Google Analytics. Orbiters collect traffic, page views, and device information, under your ownership and without exposing user data to third parties.
 
+### Mission Control
+
+Mission Control is an optional monitoring service that automatically tracks and maintains your Satellites and Orbiters.
+
+When enabled, it monitors [cycles](../terminology.mdx#cycles) balances across your modules and automatically tops them up when needed, ensuring your applications stay running without manual intervention.
+
 ---
 
 ## CI/CD and Deployment

docs/miscellaneous/access-keys.md

@@ -40,13 +40,9 @@ It is free and passwordless. It integrates WebAuthn for maximum compatibility an
 
 ## Mission control
 
-Mission control is the command center for your project. It is under your exclusive control, allowing it, for example, to hold ICP and perform various operations such as topping up your modules.
+Mission Control is an optional monitoring service. When enabled, it automatically monitors and tops up your Satellites and Orbiters to keep them running smoothly.
 
-Think of it like the command center for a space mission. Just as NASA's Mission Control coordinates spacecraft and Satellites, your Mission Control manages all your [satellites] or [orbiters](#orbiter).
-
-Because it can hold ICP and is only controlled by you, your Mission Control also functions as your [wallet](#wallet).
-
-For a schematic representation, refer to the [Architecture](miscellaneous/architecture.md) documentation page.
+Think of it like the command center for a space mission. Just as NASA's Mission Control monitors spacecraft and Satellites, your Mission Control watches over all your modules and ensures they have the resources they need.
 
 ## Modules