Operating a Neutron
| Page | Covers |
|---|---|
| Provisioning | Operator-owned PocketIC fleets and paid IC creation, adoption, reinstall, and recovery |
| Dispenser | Hosted ICP-funded creation and one-time ownership activation |
| Repositories | Certified third-party setup links, owner review, and interrupted-install recovery |
| Updates | Update-source trust, publishing, owner-triggered checks, and atomic upgrades |
The distinction worth holding
Operator provisioning creates or adopts whole canisters, installs a complete configured package set, reinstalls destructively, and records recovery evidence. The Dispenser is the separate hosted browser path: it funds and creates one new canister, then transfers Kernel authorization through a one-time activation code.
Installing is a product feature: an owner reviewing and accepting one package or a batch into their running Neutron while preserving compatible state. Repository setup installs absent apps; update sources advertise newer versions of installed apps.
These paths share package, compiler, and deployment machinery, but they are not substitutes. There is no per-app local CLI install. The browser Dispenser creates a new canister; the browser package flows mutate an already running Neutron only after owner review.