/dev/kvm, so they run on bare-metal nodes or on VMs with nested virtualization. The server runs anywhere.
Components
The host image carries Firecracker, its jailer, a guest kernel and the in-VM supervisor, which the host copies into every function’s root filesystem as init. There is no container daemon. Hosts pull images straight from their registries. ECR, Artifact Registry and GCR authenticate with the cloud’s workload identity, and other registries use the Docker config or are pulled anonymously.
How a call moves
The server that accepts a call holds it in memory and waits for its result. Hosts publish each invocation’s record to a JetStream stream when it ends, and the servers write records to PostgreSQL in batches, so nothing is written to the database while an invocation runs. A call only reads its function and version. A busy fleet makes calls wait in the queue rather than fail. See Architecture.What scales how
A host holds nothing durable. Its data volume caches the kernel, built root filesystems and microVM jails, and losing it only means rebuilding on the next invocation.
One tenant per cluster
Run one deployment per tenant: its own servers, hosts, NATS and PostgreSQL. Nothing is shared between deployments, so a tenant’s queue, hosts and data are its own. Inside a deployment, the server still scopes functions, invocations and secrets to the caller’s tenant. With authentication off, every request runs in a built-in default tenant. With theproxy provider, AUTH_PROXY_TENANT pins the one tenant a deployment serves and refuses any other. See Authentication.
Next steps
Kubernetes
Install the Helm chart.
KVM nodes
Prepare the nodes hosts run on.
Storage
PostgreSQL, NATS and the buckets.
Configuration
Every environment variable.