Skip to main content

Edge

Route/authoring/edge PreviewHosted planhosted

Edge — "Functions, versions, capability grants, egress allowances, personalization, simulation…" — records the edge runtime policy for the production lane. The page says no managed runtime tier is attached: "These functions are recorded policy: nothing is compiled, nothing is sandboxed and no code runs on any request…"; invocations carry no CPU, wall-clock or memory figures "because nothing ran"; and secrets are shown by name and alias only, never fetched.

TabWhat it does
FunctionsFunctions in precedence order, with "No version promoted…" and Shadowed: hints, and a staged rollout — Simulate at N% or Enforce on N% — behind an impact sheet
VersionsImmutable, content-addressed versions with a Live marker, and Revisions with Restore revision N
CapabilitiesRuntime capabilities (deny by default) with Revoke capability; Outbound destinations with Withdraw destination; Secret references. Revocation goes through a Revoke grant impact sheet; there is no grant control in the UI yet
PersonalizationEach variant with its audience rule, fallback, cache-key effect, analytics dimension, privacy classification and consent basis together; "No personalization variant is configured…"
SimulateA Method, Path, Country, Language, Cohort and Experiment: the function and variant chosen, capabilities denied, destinations refused, residency, ceilings, and the candidates considered
InvocationsFilter by dimension, with request evidence
AuditApprovals, the audit trail, CSV export

Functions, grants, egress allowances and secret references are reserved to the Platform operator role: "Residency and cache-key presets, simulation, the invocation explorer and the audit trail remain available."