Glossary

Glossary: what the console's terms mean

All help topics

The words the console uses, as it uses them.

  • Cloud engine (engine): your own Internet Computer subnet, run by nodes you pick, that hosts your apps and their canisters.
  • Subnet: a group of Internet Computer nodes that run the same canisters together. Each engine is one dedicated subnet. Its subnet id is what the ICP CLI needs to deploy to the engine; a new engine gets one once it's ready.
  • Node (replica node, replica): one physical machine of an engine, in a data center, run by a node provider. Every node runs the same canisters and keeps an identical copy of their state, and the nodes agree on every change. Replica nodes lists an engine's nodes.
  • Node class: a hardware tier (Nano, Standard, Performance, High-Performance, Dense) that sets a node's minimum CPU, memory, storage and network. All nodes of an engine share one class; an engine can move to another class later.
  • Node provider: an independent company that owns and runs nodes and sets their prices. Nodes of one provider share its failures, so spreading across providers makes an engine sturdier.
  • Data center (also written datacenter): the facility a node sits in. Nodes in one data center, country or continent share its risks.
  • Canister: a program on the Internet Computer, WebAssembly code with its own stored data. Software canisters lists every canister on an engine.
  • App: one application on an engine, one or more canisters grouped together, with its own web address. Your apps and services lists them.
  • Custom domain: any domain an app serves besides its canister address, the address its frontend canister is served at, which can't be renamed or removed. It's a subdomain of your engine's domain, live as soon as that domain is, with no DNS setup, or a domain you own, like app.example.com, pointed at the app with DNS records.
  • Cycles and T: cycles pay for everything canisters do (computing, storage, messages) and are used up as they go. An engine's balance is held in cycles, shown in T, trillions of cycles. 1 T is worth 1 XDR, a currency unit defined by the IMF. Your USD payments become cycles for the engine.
  • Engine operator: a canister on every engine that keeps track of what runs on it and who is on its team. Until it is installed, some pages say "Setting up your engine's operator".
  • Proxy canister: a canister that makes calls to features on other subnets for your canisters (threshold signatures, VetKeys, the exchange-rate canister), paid from the engine balance. The engine owner deploys one on Integrations.
  • Principal: the id of an identity on the Internet Computer. Yours is the User ID in Settings; engines and team roles are tied to it.
  • Internet Identity: the sign-in service the console uses: a passkey, or one click with Google, Apple or Microsoft, instead of a password. It gives you a different principal on each website.
  • Fault tolerance (BFT): how many nodes, F, can be offline or faulty at once while the engine keeps running. With n nodes, 3F + 1 ≤ n: 4 nodes tolerate 1, 7 tolerate 2, 10 tolerate 3. With more nodes down, the engine stops answering until enough come back; apps and data stay.
  • Halted: an engine whose balance came within its halt line, a set number of days before the balance runs out. It answers no requests but is still billed, and runs again once a payment takes it past the line. If the balance runs out, the engine is deleted.
  • Roles on an engine: Owner, set when the engine is created, the only one who can delete it, change its nodes, deploy proxy canisters and add or remove admins. Admin runs the engine and manages developers, and can delete apps and manage members and domains. Developer deploys canisters and installs apps. An organization has its own roles: Org owner and Org admin manage it and its billing; other members get engine access as roles are assigned.
Still stuck? Contact support