Scalix Functions

Serverless with
MicroVM isolation.

Deploy serverless functions in hardware-isolated microVMs. Auto-scaling, per-request billing, scale-to-zero. Each invocation runs in its own isolated virtual machine.

Deploy a function Read the docs
scalix-functions — deploy
connected·eu-central
$0.18/1M invocations·one microVM per call·scale to zero·per-request billing
Hardware isolation

One request. One machine.

Most serverless platforms run your code in shared containers. Scalix Functions boots a fresh hardware-isolated microVM for every invocation — its own kernel, its own memory, destroyed the moment the response is sent. Try it: fire requests and watch the machines come and go.

active VMs: 0served: 0
$0
scaled to zero — nothing running, nothing billed
fire a request to boot a microVM
Simulation for illustration — boot times shown are representative. In production every invocation gets its own hardware-isolated microVM and is destroyed after the response.

Hardware-isolated microVMs

KVM-grade isolation per invocation — no shared runtime, no neighbors, no warm pool of other people’s code.

Auto-scaling

Concurrency scales with demand. A burst of traffic just means more microVMs, booted in parallel.

Scale to zero

No invocations, no machines, no charge. The meter only moves when your code runs.

Per-request billing

$0.18 per million invocations plus execution time, drawn from the same credit pool as every other service.

HTTP & event triggers

Invoke over HTTPS, from the event bus, or on a cron schedule.

Sized per function

Configure memory and CPU for each function independently. Health checks built in.