Service access

Use this page to see how you get each service and which limits apply to it. We bring teams on by invitation. To ask for access, write to us and say which services you need. For live health and current incidents, see status.etorm.com.

By service

ServiceAccessWhat it isLimits
Networking: VPC and AccountBy invitationVPCs with an IPv6 /64 and optional IPv4. Linux machines join through a gateway with WireGuard and a VXLAN or Geneve tunnel, over an IPv6 underlay. See the guide.Connecting a machine needs a gateway that is running and reachable. A VPC is served by one gateway.
Networking: DHCP and DNSBy invitationDHCP leases and DNS records, forwarders and automatic member names inside a VPC. See the guide.None listed.
Networking: GatewayBy invitationA Gateway and the agent that builds its tunnels. See the guide.The agent is a Linux program you run yourself.
ComputeBy invitationWebAssembly programs run as processes with Ethernet interfaces on your VPCs, woken by frames. Resident processes keep memory between wake-ups, bind buckets, and hibernate and resume with their memory and TCP connections intact. A program written with the Rust SDK serves TCP over IPv6. See the guide, hibernation and TCP services.Programs up to 256 KiB, core WebAssembly modules only. At most 256 MiB of memory per process. A process runs on the gateway agent that serves its VPC and stays Pending until one is attached. A failure, suspension or restart of the machine begins a new life for a resident process. Hibernation keeps a process on one machine.
StorageBy invitationBuckets of objects written, read, listed and deleted over HTTPS with a token, encrypted per bucket. See the guide.Objects up to 32 MiB, keys up to 1 024 bytes, at most 200 keys per list page in the store's own order.
DatabaseBy invitationPostgreSQL-compatible databases (psql 16) on your VPC, run by Compute with every byte in a bucket of your project. See the reference.One primary. No client TLS. Created with the platform team.
Queues (MessageBroker)By invitationA message broker for MQTT 5.0 and 3.1.1 clients, with sessions and queued messages kept in Storage. See the reference.QoS 0 and 1. One serving node. Created with the platform team.
Identity and accessBy invitationRoles, bindings, service accounts, API tokens and personal tokens, invitation links, members, an audit log, two-step verification. Deny by default. See the guide.Access tokens already issued stay valid until they expire. Personal tokens last 90 days by default and 365 at most, 20 per person. Per cluster: 20 invitations, 100 roles, 500 bindings. The audit log keeps the last 5 000 changes and 1 000 refusals per cluster for 90 days.
Billing and projectsBy invitationBilling accounts, projects, SKUs and usage records. See the guide.Usage is recorded; nothing is invoiced.
Control plane and consoleBy invitationOne Kubernetes-compatible API for every service, and the console at console.etorm.com to browse, create and edit every resource through wizards, share access, read the audit log and manage tokens.Process interfaces show no byte counters in the console.
OpenTofu providerBy invitationBilling accounts, projects, VPCs, accounts, DHCP and DNS. See the guide.Built from source. Covers the kinds listed here.
Canvas and diagramsBy invitationResources as blocks with typed ports, drawn on the canvas or written as YAML, with live status. Modules, loops and logic blocks. See the guide.A block of a service that is not enabled for your project creates its resource, which stays Pending until the engine is enabled for your project.
Load balancing and ingressBy invitationLoad balancers and ingress at L3, L4 and L7 with health probes and TLS termination, run as processes on your VPC. See the guide.Until the engine is enabled for your project, a new load balancer or ingress stays Pending with reason EngineNotAvailable.
Graph databaseBy invitationDistributed openCypher databases on your VPC, kept in Storage. See the guide.Until the engine is enabled for your project, a new GraphDatabase stays Pending with reason EngineNotAvailable.
WorkflowsBy invitationDurable workflows written in Rust and compiled to WebAssembly, with activities, timers and schedules kept in Storage. See the reference.Until the engine is enabled for your project, a namespace stays Pending with reason EngineNotAvailable.
Agents (agents, memory, inference endpoints)By invitationAgents that act through your API with their own service account and exactly the role you name, with memories and inference endpoints. Deletes wait for a person's AgentApproval. See the guide.None listed.
MCP endpoints and the GraphQL APIBy invitationA GraphQL API per project, generated from its kinds and authorized like the REST API, and MCP endpoints that give an AI client two tools (search the API, run one GraphQL document) as a service account you choose. See the guide.Static credentials. No subscriptions.

How to read this

If a resource sits in Pending with reason EngineNotAvailable, it is valid. It is waiting for its engine to be enabled for your project, and you do not need to change anything. Find out why something stays Pending covers the other reasons.

When something on this page changes, we date it in What's new.