A cloud engine is your own cluster of replica nodes that runs your apps, paid from its own balance and managed from the console.
- Nodes. Each replica node is a physical machine in a data center, run by an independent node provider. You pick the nodes when you create the engine. Every node runs the same software and keeps a full copy of your apps and their data.
- Fault tolerance. The nodes agree on every change by consensus, so the engine keeps running while some of them are offline. It takes at least 4 nodes to survive one failure: an engine with 3f + 1 nodes survives f failures.
- Node class. Every node of an engine shares one node class: Nano, Standard, Performance, High-Performance or Dense. A bigger class has more vCPU, RAM and storage per node, and costs more.
- Apps. Your apps run as canisters on the engine. The engine gets its own domain, and every app you deploy gets an address under it.
- Balance. Each engine has its own wallet. Node rent and usage draw on it day by day, in cycles. When the balance runs out the engine is deleted, so you add funds or leave automatic top-up on.
- Team. Whoever creates an engine is its Owner, and can add people as Admin or Developer.
Good to know
- Your engines are listed on My engines, the console's home page.
- You can add, replace or upgrade nodes after creation, from Replica nodes in the engine sidebar.