Glossary
The terms these docs use, sorted A to Z. Each one links to the page that explains it properly.
| Term | Meaning | Read more |
|---|---|---|
| Account (network) | One member's attachment to a VPC. It gets an IPv6 address and a MAC, and an IPv4 address too if the VPC has IPv4. It is not the same thing as a billing account. | Guide |
| Activation | One run of a process, which starts when something wakes it, such as a frame. Memory and processor time are bounded per process. | Guide |
| API token | A bearer secret that authenticates a principal. You see it once, we store only its hash, and it expires. | Reference |
| Audit log | The record of successful changes and refusals in a project. It does not record reads or request contents. | Guide |
| Billing account | The object that says who pays. Whoever creates one becomes its owner, and each project is billed to exactly one. | Guide · Reference |
| Bucket | A container in a project for objects, which are named blobs of up to 32 MiB. Each bucket encrypts its objects with its own keys. | Guide · Reference |
| Canvas | The visual editor in the console where you draw infrastructure as blocks with typed ports. | Guide |
| Certificate | A TLS certificate resource that an ingress uses. The API never holds its private key. | Reference |
| Condition | One entry of status.conditions. It has a type, a true or false value, a reason and a message, and together the conditions explain the phase. | Guide |
| Console | The web interface at console.etorm.com, where you browse and edit resources. | Guide |
| Controller | The program that looks after a resource. It compares spec with what exists, fixes the difference and writes status. | Guide |
| Database | A PostgreSQL-compatible database on your VPC. Access is by invitation. | Guide · Reference |
| Device | There is one for each address the gateway sees on a VPC, whether that is a member or some other MAC. It shows the address's state and counters. | Reference · Guide |
| DHCPService | The resource that hands out IPv4 leases inside a VPC. | Guide · Reference |
| Diagram | A resource that describes other resources as blocks and links. A controller creates what it describes and removes what you delete from it. | Guide · Reference |
| DNSService | The resource that gives a VPC its names. It holds a zone, records and forwarders, and answers inside the VPC. | Guide · Reference |
| Gateway | The point where members tunnel into VPCs over WireGuard. It is also the host that runs the processes attached to it. | Guide · Reference |
| Group | A named set of principals that you can bind to a role in one step. | Reference |
| Ingress | Where traffic from outside comes in. It forwards by listener or, at L7, by host, path and header rules. Access is by invitation. | Guide · Reference |
| Invitation | A single-use link that grants a role when the person signs in. It never grants more than its creator holds. | Guide · Reference |
| Kind | The type of a resource, such as VPC or Bucket. Every kind has a reference page generated from its schema. | Guide |
| Load balancer | Spreads traffic over backends at L3, L4 or L7 and checks their health. Access is by invitation. | Guide · Reference |
| Logical cluster | An isolated slice of the API with its own objects, roles and audit log. Every project is one, and the platform has a root one of its own. | Guide |
| MessageBroker | A message broker for MQTT clients. Access is by invitation. | Guide · Reference |
| Object | A named blob of up to 32 MiB stored in a bucket. It is not an API resource. You read and write it over HTTPS. | Guide |
| Owner | The built-in role that allows everything, including granting roles. Whoever creates a billing account is its owner. | Guide |
| Personal token | An API token for your own identity, made by etorm login or the console. It has exactly your rights. | Guide |
| Phase | The one-word state in status.phase, such as Pending, Ready or Failed. | Guide |
| Principal | Whoever makes a request: a user, a service account or a member of a group. | Guide |
| Process | A program running with Ethernet interfaces on your VPCs. It runs only when something wakes it, and it keeps its state between wake-ups. | Guide · Reference |
| Program | A small WebAssembly module. It is checked when you register it and never changes after that. | Guide · Reference |
| Project | An isolated logical cluster with its own hostname. Everything you build lives in a project. | Guide · Reference |
| Ready | The phase that means the controller has made the object match its spec. Only Ready objects are metered. | Guide |
| Resource | An object the API serves, with a spec and a status. | Guide |
| Role | A list of permissions. A role can never grant more than its author holds. | Guide · Reference |
| RoleBinding | Grants a role to users, groups or service accounts, either in one project or across a billing account. | Guide · Reference |
| Service account | An identity for CI or an agent rather than a person. It lives in a project and has its own tokens. | Guide · Reference |
| SKU | An entry in the price list. It sets an hourly price in micro-units for one kind of resource. | Guide · Reference |
| Spec | The part of an object you write, saying what you want. | Guide |
| Status | The part of an object a controller writes. It holds the phase, the conditions and observed values. | Guide |
| Two-step verification | A code from an authenticator app that you enter after your password. It comes with recovery codes. | Guide |
| Usage | The record of metered resource time for one project, SKU and month. Only the metering controller writes it. | Guide · Reference |
| VPC | A private Ethernet segment with an IPv6 /64 and, if you want one, an IPv4 network. | Guide · Reference |
| WireGuard | The encrypted tunnel members use to reach a gateway. You bring the key, and Etorm only sees the public half. | Guide |