/ on the same port as the API, 8780 by default. Release images of the server embed it. In local development, just dev runs it on localhost:5173 and proxies the API to the server.
The sidebar has four sections: Observability, Functions, Hosts and Invocations. / opens Observability. Every view keeps its state in the URL, so a link to a filtered list, a selected version or an open invocation reopens exactly that view.
Functions
Functions lists every function as a card with its current version, invocations in the last 24 hours, success rate, mean duration and its last ten statuses. The search box filters the list and is kept in?q=.
Create a function
New function opens a wizard with these steps:1
Choose source
Pick Code and a language to write the handler in the browser, or Image and an OCI image reference. Under the source, the Environment section holds Variables, which go to the version’s
spec.env, and Secrets, which are stored apart from the spec. Advanced holds the Command.2
Define contract
Write the input and output schemas, as JSON Schema or as Arrow fields. See Contracts.
3
Write code
Code only. One tab per file over a full height editor, seeded with a handler generated from the contract.
4
Set resources
vCPUs, memory, timeout, max concurrency and retries.
5
Name function
A name and an optional description.
Function detail
A function page has a heading with a version select, a banner while a version builds, and two actions. New version opens the same wizard without the name step. Invoke opens the workbench and is disabled until the function has a ready version.?version= selects the version the heading, workbench, contract and settings show.
Workbench
The file tree lists the version’s source files first, theninput.json, contract/input.json, contract/output.json and spec.json. Source files and input.json are editable, the rest are read-only. ?file= selects a file.
Run (or ⌘↵) invokes the ready version with input.json. The result shows the invocation id, which opens its drawer, the outcome, the output and a resizable logs strip. On a failure the outcome shows the reason and one line per contract violation, with its path and message.
Build ships edited source files as a new version. Builds run on a host, and the function page polls while a version is building.
Versions
Expand a row to see the image digest, contract, files with their runtime, command, timeout and root filesystem size. Each row’s menu has:- Open in workbench, for a ready version.
- View contract.
- Retry build, for a failed version.
Settings
Invocations
Invocations lists every invocation in the tenant, newest first. Filter by status and by timeframe (1 hour, 24 hours or 7 days). Both are kept in the URL. Click a row to open the invocation drawer, which?invocationId= keeps open across reloads. It shows:
- The outcome, with the failure reason and contract violations when there are any, and a phase bar of where the time went.
- Facts: function, version, call (sync or async), attempts, start kind, instance and creation time.
- The logs, as a resizable strip at the bottom. For an invocation that retried, an attempt select switches between each attempt’s log (
?invocationAttempt=).
Observability
Observability is the dashboard. From the top:- A KPI row: invocations running now, a count per final status, average duration, average acquire time and the share of warm starts.
- Invocations by status over the timeframe.
- Mean latency by start kind, cold boot or snapshot restore.
- A weekday by hour traffic heatmap, filled by volume or by cold boots.
- History, an infinite invocations table for the timeframe that takes over the scroll.
Hosts
Hosts shows one card per live host:- A slot map. A busy slot opens the invocation it runs.
- Capacity: instances, committed memory, cached images and root filesystem cache size.
- Runtime: uptime, Firecracker version and kernel.